Services · most requested

Your ERP project stalled. That is more normal than anyone tells you.

Gartner expects more than 70% of recent ERP implementations to miss their original business case. We take over stalled, over-budget, and failed deployments — on whatever system you already bought — and get you to a clean close.

Book a free diagnostic

Two days on your configuration and your open issue list. The written assessment is yours whether or not you hire us.

1 / 3
NetSuite · Sage · Acumatica · Dynamics · Odoo · QuickBooksDiagnostic is free and writtenFixed scope after week 2

Warning signs

Six patterns, and they rarely arrive alone.

If three or more of these are true, the project will not recover on its current trajectory without an intervention.

The go-live date has moved twice

Slippage is rarely about engineering. It is usually unresolved decisions about the chart of accounts, entity structure, or who owns a process nobody wants to own.

You are past budget with no end date

Time-and-materials engagements with an open scope do not converge on their own. Somebody has to redraw the line.

Everyone is still in the old system

Parallel running past the planned window means the new system is not trusted. That is a data-integrity problem wearing a change-management costume.

The numbers do not tie

Balances that disagree with the legacy system, sub-ledgers that will not reconcile to control accounts, or a trial balance nobody can explain.

The partner has rotated staff twice

Institutional memory of your configuration decisions has left the building. Nobody remaining knows why anything was set up the way it was.

Customisation has become the plan

Every gap closed with a script. Each one is a future upgrade blocker and an undocumented dependency.

How we work

Diagnostic first. Always.

Week 0

Free diagnostic

Two days on your configuration, your data, and your open issue list. You get a written assessment whether or not you hire us — including if the assessment is that your current partner should finish the job.

Weeks 1–2

Stabilise

Stop the bleeding. Freeze scope, triage the issue list into blocking and deferrable, and get a reconciliation running so you can see whether the numbers are actually right.

Weeks 3–8

Close the gaps

Fixed scope, fixed price, weekly demo. We work the blocking list in the order that gets you to a clean close, not the order that maximises hours.

Week 9+

Prove and hand over

One clean month-end closed in the new system, documented configuration, trained staff. We would rather leave than become a dependency.

What it costs

The diagnostic is free and produces a written assessment you own outright. Rescue engagements run $15,000 to $40,000 depending on the state of the configuration and how much data needs remediation, quoted as a fixed scope after the diagnostic — never hourly.

We price it this way because hourly billing on a rescue recreates exactly the incentive that got you here. If the work takes longer than we estimated, that is our estimate to have got right.

When we tell you not to hire us

Roughly a fifth of diagnostics conclude that the existing partner should finish the job, that the project is closer to done than it feels, or that the right move is to stop and reconsider the system entirely. We put that in writing too. A rescue we talk you out of costs us a fee and earns a reference.

What we do not take on

We will not rescue a manufacturing or warehouse-management deployment. Those need deep vertical specialists and we would be the wrong people. We say so at the diagnostic rather than after the contract.

Questions

What people ask first.

Do we have to fire our current partner?
No, and often you should not. We frequently work alongside an incumbent partner, taking the workstream that has stalled while they continue the rest. Replacing a partner mid-project destroys context and usually adds months.
Which systems do you rescue?
NetSuite, Sage Intacct, Sage 100 and 300, Acumatica, Dynamics 365 Business Central, Odoo, SAP Business One, QuickBooks Enterprise, and Xero. We do not take manufacturing or WMS deployments.
Will you try to move us onto your platform?
Not during a rescue, and never as a condition of one. The engagement is to make the system you bought work. If a platform conversation makes sense later it is a separate decision, made from a position where your books are actually closing.
How fast can you start?
Diagnostics usually schedule within a week. Rescue engagements start within two to three weeks of a signed scope.
What if the numbers are already wrong?
That is the first thing we check and the first thing we fix. We stand up a reconciliation between the new system and your legacy records before touching anything else — there is no point completing a configuration on top of data that does not tie.

Get an honest read on where it stands.

Two days, a written assessment, no fee and no obligation — including the assessment that says you do not need us.