Release upgrades
Planned upgrades with impact analysis, regression testing and a cutover that fits inside a weekend.
Upgrade & Roll-Out
Extend what already works, without running a second programme.
A new plant, a new country, an acquired business, or a release you have put off twice. None of these should cost what the original implementation cost, and they only do when the template is treated as something to rebuild rather than something to extend.
Template first
We check the template is worth extending before extending it eight times.
Localisation handled
Statutory and tax requirements built in, not discovered at user acceptance testing.
Regression, every time
The existing entities keep working. That is the part nobody notices when it goes right.
The problem
Roll-outs go wrong in ways implementations do not.
The system already exists and already has users, so the risk shifts from building the wrong thing to breaking the thing that works.
The template drifted
After a few local changes, there is no template any more, just several systems that used to be one. Every roll-out then costs like a new build.
Local statutory rules arrive late
Tax, e-invoicing and reporting requirements differ by country and by state. Finding them during testing is the expensive way.
The upgrade backlog compounds
Skipped releases do not stay skipped. They accumulate into a single large upgrade that is harder to test and harder to justify.
Existing users pay for the new ones
Without regression testing, a roll-out to one entity quietly breaks a process in another, and the business finds it first.
A template you cannot roll out is not a template. It is just the first system you built.
How we assess every roll-out
What we do
Two related pieces of work.
Upgrades and roll-outs share the same discipline: change the system without disturbing the people already using it.
Template review
An honest read on whether the template is fit to extend, and what it would take to make it so.
Entity and country roll-out
New company codes, plants, entities and geographies onto the existing template.
Localisation
Statutory, tax and reporting requirements for each new geography, scoped before build rather than during test.
Post-merger onboarding
An acquired business brought onto your landscape, with the separation from its old systems handled cleanly.
Regression testing
Automated and manual coverage so the entities already live stay exactly as they were.
How it runs
Five stages, and the first one is a question.
Extending a template that is already wrong multiplies the problem. So the first stage is deciding whether to extend it at all.
- 1
Review
Assess the template, the drift between entities and what is genuinely reusable.
- 2
Localise
Country and entity requirements gathered and scoped, including statutory and reporting obligations.
- 3
Configure
Build against the template, with local variation kept to what regulation actually requires.
- 4
Test
Functional testing for the new entity and full regression for the ones already live.
- 5
Roll out
A planned cutover per entity, with training delivered locally and support through the first close.
Who this is for
This is the right page if any of these are true.
- You are opening a plant, entity or country on the existing landscape.
- You have acquired a business that needs onboarding onto your system.
- You have skipped two or more releases and the gap is now uncomfortable.
- Each roll-out costs more than the last, which usually means template drift.
- You need the existing entities untouched while the new one goes live.
What this does not do
A roll-out cannot repair a template that was wrong to begin with. If the review says the template needs work first, that is a separate piece of work and we will say so.
An upgrade also will not deliver new capability on its own. It gets you current and supported, which is necessary and rarely exciting.
Often bought with
These usually come up in the same conversation.
Find out if the template is ready.
A short template review tells you what a roll-out would actually cost and whether the drift between entities needs addressing first.