Services

Most of our work runs on someone else's ERP

We implement, integrate, rescue, and extend the systems our clients already bought. Fixed scope, published prices, and a written assessment before anyone signs anything — including the assessment that says you should not hire us.

Get a free assessment

Three questions about your setup, then where to send it. You get a written read on what we would do first — and what it would cost.

1 / 3
Fixed scope, never hourlyTen systems supportedDiagnostic is free and written

What we do

Six engagements, one operating principle.

Every engagement leaves behind a working system and an integration layer you own. None of them require you to change platforms as a precondition.

ERP implementation

Standing up the system you bought, properly, on a fixed scope. Chart of accounts, entities, workflows, integrations, training, and a first clean close.

Learn more →

Implementation rescue

Taking over a stalled, over-budget, or failed deployment. Free two-day diagnostic first, fixed scope after.

Learn more →

Systems integration

Joining your accounting system, CRM, payroll, banking, and commerce stack into one business graph that everything else reads from.

Learn more →

Migration

Moving between systems with a reconciliation proof for every period. Nothing goes live until the trial balance ties.

Learn more →

Custom modules

The thing your ERP does not do, built on your data and hosted by us — not handed over as a codebase you then maintain.

Learn more →

Selection advisory

Independent help choosing a system, including when the answer is a competitor or staying where you are.

Learn more →

Systems

We work on all of these.

How we price

Fixed scope, because hourly rewards the wrong thing.

The chart below is the pattern we are hired to fix. It is not an argument about integrity — most consultancies are honest — it is about what an open scope does to a project over nine months.

0%25%50%75%100%m0m3m6m9time & materialsfixed scopethe gapcumulative cost against original estimate

Why the lines separate

Under time and materials, every discovered requirement is revenue. Nobody has to behave badly for this to end at 150% of the estimate — the incentive simply never points toward saying no, and across a nine-month engagement with a hundred small decisions, that is enough.

Under a fixed scope, a discovered requirement is a conversation about whether it is in or out. That conversation is uncomfortable and it is exactly the conversation that keeps a project finite. It also means the estimate is our risk, which is the correct place for it — we are the ones who have done this before.

What that means practically. Every engagement starts with a paid or free diagnostic, depending on the type. The scope and price come out of the diagnostic rather than out of a call. Change orders exist, they are written, and they are priced the same way. We do not bill for our own estimating errors.

What we will not do

  • Manufacturing and warehouse-management deployments. Those need deep vertical specialists and we would be the wrong people. We say so at the diagnostic, not after the contract.
  • Open-ended staff augmentation. Renting you developers by the month is a different business with different incentives, and it is the thing fixed scope exists to avoid.
  • Customisation as a first resort. Configuration before code, always. Every script written today is an upgrade blocker in two years, and most of them are solving a process problem rather than a software one.
The engagement always installs the platform

Every piece of work we do stands up the erp.io integration layer and starts a shadow ledger against your existing books. That is how a services engagement leaves you with something durable rather than an invoice, and it is why we can price the work the way we do.

How an engagement runs

A diagnostic, then a written scope with a fixed price, then weekly demos against that scope, then a handover that includes documentation and training rather than a call where we say goodbye. Most engagements run six to twelve weeks. The longest we will quote without breaking it into phases is sixteen.

You get a named lead for the duration. Not a pod, not a rotating bench — one person who knows your configuration and is still there at the end, which is the single most common complaint we hear about the partner our clients had before us.

Questions

What people ask first.

Do we have to buy your platform?
No. Most engagements run entirely on the system you already own. The integration layer goes in as part of the work, and whether you ever adopt our ledger is a separate decision you can defer indefinitely.
Are you a NetSuite or Sage partner?
We work on all ten systems listed above and we are not resellers for any of them, which means we have no licence commission steering our recommendation. When we tell you to stay on your current system, nobody at our end loses a referral fee.
What if the project turns out bigger than the diagnostic suggested?
That is our estimating risk under a fixed scope. Genuine scope additions — things that were not in the written scope — go through a written change order at the same published rate. Discovering that our own estimate was optimistic is not a change order.
Who actually does the work?
A named lead plus specialists as needed. For systems outside QuickBooks we bring in certified practitioners for that platform, and you are told who is on the engagement before it starts.
Can you work with our internal team?
Usually the best arrangement. We do the configuration and the data work; your team owns process decisions and adoption, because those cannot be outsourced and a partner who pretends otherwise is setting up a handover that fails.

Start with a free assessment.

Tell us what you run and what is broken. You get a written read on where things stand, whether or not you hire us.