Replace legacy
Know the full scope of a legacy replacement before you commit to it.
Fusion starts with a discovery. The discovery is a free scoping session. The session finds exactly what your legacy system does, what it costs you to keep, and what a replacement needs. You leave with a written scope, a five-year cost baseline and a proposal priced from the savings. You do not leave with an estimate and an invoice.
Total cost of ownership
A legacy system costs more than its licence.
Add the full cost of the system over five years. Three cost lines are the largest. Fusion removes two of them and makes the third smaller.
Licences per user
Grows with headcount
Each person who logs in is a line on the renewal. When more of the business uses the system, the cost goes up. The cost makes it harder to give access to the people who need the system.
The implementation partner
Paid to configure, then paid to change
The partner who configured the product to fit your business is the partner you call for each change after that. Their day rate is part of the cost of the system, even if it is not on the same invoice.
The people who keep it running
Upgrades, workarounds, integrations
Your own people keep the system in operation long after it was the correct choice. They run the upgrade nobody wants, maintain the spreadsheet next to it, and repair the integration each time one end changes.
A Fusion replacement runs on machines and a subscription. The subscription scales with what you run, not with who logs in. There is no licence per user. There is no implementation partner between you and a change. The plumbing is a dependency that Fusion maintains. Two of the three cost lines are removed, and the third becomes the few people who build.
Up to 50% is the top of the range, not a promise. The discovery prices both sides over the same five years. The figure for your system is the figure your TCO baseline shows, and the proposal is built on that figure.
Discovery
A free scoping session with three outputs.
The discovery uses the same steps as each Fusion delivery. The discovery costs you nothing. The discovery ends with documents that you can use, even if you do not go ahead.
A ringed number shows a step that needs people from the business. There are two such steps.
-
01
Sponsor session
1 hour Business timeMeet the sponsor. Agree which system is in scope, what the system must continue to do on day one, and the result you want in the run costs.
Session transcript -
02
Observation sessions
1 hour each Business timeThe people who use the system today show us the work it carries. This work includes the parts that live in spreadsheets and inboxes around the system. The real scope is in those parts.
Observation notes -
03
Current state documented
We document the current workflows and the current system architecture. We also collect each cost line that touches the system: licences, partner days, hosting, and the people who keep it in operation.
Current State Workflows Current State System Architecture Cost inventory -
04
Domain model and value stream
We design the domain model that the replacement is built on, and the value stream that its workflows form. This step changes a wish list into a scope with limits.
Domain Model Workflows Value Stream -
05
Scope, baseline, proposal
We write the three outputs and give them to you. They are yours to keep. If you go ahead, the deal is measured against these documents.
Written scope TCO baseline Value-based proposal
Written scope
What the replacement includes, what it does not include, and what it must continue to do from the first day it is live.
TCO baseline
Five years of what you pay now, line by line, next to five years of the replacement. The same period and the same lines, so you can compare the two columns.
Value-based proposal
The share of the savings that Fusion is paid, when it becomes payable, and what occurs if the savings do not appear.
The discovery is not the Readiness Assessment. The Readiness Assessment maps where your delivery fragments. The discovery scopes the replacement of one system and prices it.
Value-based
Paid from the savings, after they arrive.
There is no build fee up front. Fusion is paid an agreed share of the TCO savings that the replacement realises. Fusion is paid only after those savings appear in your run costs, measured against the baseline from the discovery.
You pay
-
An agreed share of realised savings
The proposal sets the share. The share is measured against the baseline you approved at discovery. Fusion invoices the share after the saving appears in your run costs, not when the saving is forecast.
-
The Fusion subscription, at list price
The environments you run and the people who build, as shown on the pricing page. The value-based deal covers the replacement engagement. The deal does not change those lines.
You do not pay
-
A build fee up front
The discovery is free. Fusion does not invoice the build as a project. Fusion carries the delivery cost until the savings are real.
-
A licence per user on the new system
No user of the new system is a seat, at any number of users. More access does not change the price.
-
For savings that do not appear
The share applies to realised savings only. If a line in the baseline does not decrease, nothing is due on that line.
The proposal is a number you can check against your own run costs, every year, for the whole period.
How this sits with the pricing page
Delivery services are quoted for each engagement. This page is the quote for a legacy replacement. The subscription lines stay as listed. The share applies only to the engagement. The baseline that measures the share is the baseline you approved at discovery.
Bring the system you most want to replace.
One hour with your sponsor starts the discovery. You get the scope, the baseline and the proposal even if you do not go ahead. The discovery costs you nothing.