Fusion

Escape SaaS

Escape Salesforce, ServiceNow & Dynamics. Own your data, your data model and your business logic.

We read your current system from the platform's own metadata, and we watch the people who use it. Then we rebuild the system on Fusion, on the hosting that you choose. In the same work, we fix the pain points, rewrite the documentation and the user guides, and close the compliance gaps.

Problem & Opportunity Statement session
1h
A Problem & Opportunity Statement session with your sponsor
Observation session
1–2h
For each observation session with the people who use the system
Seat licences on the new system
0
Seat licences for the people who use the new system
Tollgate fees on your own data
0
Tollgate fees when your LLMs read your own data

Four results

One piece of work. Four results.

The sessions and the metadata analysis feed four results at the same time. Each result comes from the same six steps, so no result needs a separate project.

01 · MIGRATION

The system, rebuilt on Fusion

We rebuild each part of the current system on Fusion: the data, the rules, the automation and the access.

Steps 03 · 04 · 06

02 · PAIN POINTS

The pain points, fixed in the rebuild

The observation sessions show the workarounds: the spreadsheets, the inboxes and the data that people type twice. The design removes each workaround, so the new system does not need it.

Steps 02 · 04

03 · DOCUMENTATION

Documentation and user guides that match the system

The metadata analysis documents the old system as it is configured today. Each new workflow has a spec, system tests, a user guide and a video, and Fusion keeps them current.

Steps 03 · 05

04 · COMPLIANCE

Controls with evidence

We turn each obligation into a control. We also turn each access rule from the old platform into a control. Fusion checks each control against the code.

Steps 01 · 04 · 05

Compliance and governance

Each control has its evidence from the first release.

Bring the obligations from any source. Fusion checks each control against the real code, and the audit trail is a by-product of the work.

01ObligationA contract, a regulator, a standard, your own policy, or an access rule in the old platform
02ControlEach obligation becomes a control
03EvidenceChecked against the file, the dependency and the version
04Met, or the fixIf the evidence does not show it, Fusion shows the gap and the fix next to it

What we read

The platform's own metadata describes the current system.

The metadata describes what your organisation built on the platform: the objects, the rules, the automation, the access and the screens. We read the metadata with the platform's own APIs. The analysis does not change your system.

Eight parts of each system

  1. 01Data model
  2. 02Business logic
  3. 03Automation
  4. 04Access
  5. 05Screens
  6. 06Reports
  7. 07Integrations
  8. 08Records

Each platform page uses the names that the vendor documents. The analysis can reach only the parts that your integration user can see. The standard behaviour of each platform is not in the metadata, so the observation sessions show us that behaviour.

The method

Hours of your people's time, not weeks of workshops.

Three of the six steps need people from the business. The other three steps run without them.

A ringed number shows a step that needs people from the business. There are three such steps.

  1. 01

    Problem & Opportunity Statement session

    1 hour Business time

    We meet the sponsor. We agree the problem to solve, the opportunity, the success measures and the platform system in scope.

    Session transcript Problem & Opportunity Statement
  2. 02

    Observation sessions

    1–2 hours each Business time

    The people who use the system today show us their work. We record the pain points, the workarounds and the work that happens outside the platform.

    Observation notes
  3. 03

    Metadata analysis

    We read the eight parts of the system from the platform's metadata. We compare them with the observation notes, to find the parts that people use and the parts that nobody uses.

    Current State System Architecture Current State Workflows
  4. 04

    Domain model and design

    We design the domain model and the workflows on Fusion. Each pain point has a fix, and each obligation has a control.

    Domain Model Workflows Value Stream
  5. 05

    Build, test and document

    Business time

    Fusion builds each workflow through the five lifecycle gates: spec, build, system testing, user guide and user testing. The people who use the workflow test it before it goes live.

    System tests User Guide User Guide Video
  6. 06

    Data migration and switch-over

    We move your records into your PostgreSQL database and deploy the new system to production. Then you can end your Salesforce, ServiceNow or Dynamics 365 subscription.

    Production deploy

System sovereignty

Your data, your data model and your business logic, on the hosting that you choose.

On Salesforce, ServiceNow or Dynamics 365, you rent the system that you designed. On Fusion, you own it.

You own

  • Your data and your data model

    A standard PostgreSQL database, with a standard schema that any engineer can read.

  • Your business logic

    Code in your own repository, built on proven open-source technology.

  • Your hosting

    Any hosting provider, or your own servers.

You no longer pay for

  • A licence for each user

    The people who use the new system need no seat licences, at any number of users.

  • A tollgate on your own data

    The LLMs that you already pay for can read your data and your business logic, with no fee each time.

What we believe

The big SaaS platforms are now legacy. Their vendors built them before AI, for “clicks, not code”. If you leave Fusion later, you keep your data, your data model and your business logic.

Bring the Salesforce, ServiceNow or Dynamics 365 system that you most want to leave.

One hour with your sponsor starts the work. Bring the problem that your current system does not solve today.

Salesforce, ServiceNow and Microsoft Dynamics 365 are trademarks of their owners. Fusion has no affiliation with them.