Skip to content

The Built to Fit programme

From bought to bend
to built to fit.

The argument on our home page says the centre of gravity is moving from the suite to the operator. This is how an operator actually crosses: four three-month stages, each de-risked, each useful on its own, and each one earning the next. Nothing is ripped out on day one.

Start the conversation How it works

Four stages

Each one stands alone

12 months

End to end

Stop anywhere

Every stage pays for itself

The starting position

The suite was the right call. Then the business kept moving.

Nobody bought a suite foolishly. It was the conservative choice, and for a while it fit. The misfit arrives quietly, and it tends to look like this.

The shadow system

  • The real process lives in spreadsheets around the suite
  • Exports, re-keying, reconciliation every month end
  • The system of record stopped being the record

The bend

  • Workflows shaped around what the modules allow
  • The awkward steps are now "just how we do it"
  • New hires learn the workaround before the work

The queue

  • Every change is a ticket with a partner
  • Small requests priced like projects, delivered in months
  • The roadmap belongs to the vendor, not to you

The creep

  • Per-seat licences grow with headcount, not with value
  • Customisation debt makes every upgrade a small migration
  • The exit looks more expensive every year

None of this is an argument for a rewrite. Big-bang replacements fail for good reasons. The argument is for a crossing made in stages — small enough to be safe, real enough to compound.

The method

Buy where you're identical. Build where you're different.

The suite keeps the ground it is genuinely good at — the ledger, payroll, the standardised and the regulated. What moves is everything that makes you different from the next company: the workflows you compete with. We move those, one stage at a time, starting where the risk is lowest.

Every stage runs build → adopt → improve.

Month 1 — Build

Ship working software into the actual workflow. Not a pilot, not a deck.

Month 2 — Adopt

Training and habit formation, until the old way is the one that feels odd.

Month 3 — Improve

Refine against real use and lock the gains in before the next stage starts.

1

Edges

Build around the suite

 2

Layers

Your workflows, your software

 3

Core

The first module retires

 4

Fit

The business, encoded

The crossing

Four stages.

Stage 1 · 3 months

Edges — build where the suite never reached.

Start at the edges, where the suite was never fitted and the spreadsheets live: the quoting workflow that runs on exports, the reporting assembled by hand, the handovers between departments that happen over email. We build small, bespoke tools for those gaps — reading from the suite, never yet writing to it.

Nothing is replaced and nothing can break. By the end of the stage the team has working software shaped to how they actually operate, and a map of where the business bends around the suite — which is the blueprint for everything after.

What this earns: proof, on your own workflows, that built-to-fit is real — before anything of substance is at stake.

Typical outcomes

Month-end reporting

3 days of exports Live, assembled for you

The bend points

Folklore Mapped and priced

Zero replacement risk

Stage 2 · 3 months

Layers — your workflows move into your software.

The edge tools grow into layers: bespoke software that sits over the suite and becomes where the work actually happens. The suite is still the system of record underneath — ledger, stock, payroll — but the day-to-day workflows now run in software shaped to them, reading and writing through the suite's own interfaces.

This is the hybrid position from our segmentation map: ERP core, bespoke layers. The shadow spreadsheets go, because the thing they compensated for is gone. Change requests stop being tickets to a partner and become conversations with a build team.

What this earns: the operating layer is yours. The suite is demoted from the way you work to a database you keep — without a migration.

Typical outcomes

A workflow change

Partner ticket, months Shipped in days

The daily tools

The suite's screens Software shaped to the job

ERP core + bespoke layers

Stage 3 · 3 months

Core — the first module retires.

By now the layers carry the workflow and the suite's module underneath is doing little more than storing rows. So we pick one — the module where the misfit costs most — and move its data and its record-keeping into the system we have built. Not a migration project; a cutover of one bounded piece, rehearsed, reversible until the day it is not needed to be.

This is the stage the earlier ones were quietly preparing. The team already lives in the new software; the module's retirement is an event in the server room, not in anyone's working day.

What this earns: the proof that leaving is possible — module by module, on your schedule, with the licence bill shrinking as you go.

Typical outcomes

Module count

All of them One fewer, more to follow

The exit

Unthinkable A rehearsed procedure

Leverage over the vendor

Stage 4 · 3 months

Fit — the business, encoded in software.

The end state is not "no ERP". Where a module is genuinely commodity — the ledger, payroll, the regulated ground — keeping a standard product is the right answer, and we will say so. Everything else runs on systems shaped to how you operate, owned by you, integrated because they were born integrated.

What changes permanently is the posture. New requirements become conversations with your build team instead of items on a vendor's roadmap. Scope changes take days. The software follows the business, rather than the business following the software.

What this earns: built to fit, not bought to bend — as your operating reality rather than our slogan.

Typical outcomes

A new requirement

A vendor roadmap item A conversation, then a build

Licences & partner fees

Growing every year Commodity ground only

The operating layer is yours

What it takes

Time, not just money.

The scarce resource in a crossing like this is your team's attention, not the invoice. Here is the honest shape of the commitment for a company of around fifty people.

Stage Your team's time Timeline What it earns
Stage 1 — Edges 10–15 days (walkthroughs, access, adoption) 3 months Working proof, and the map of the bend
Stage 2 — Layers 20–25 days (workflow design, adoption) 3 months Day-to-day work runs in your software
Stage 3 — Core 25–30 days (data checks, rehearsal, cutover) 3 months First module retired, exit rehearsed
Stage 4 — Fit 20–30 days (consolidation, ownership handover) 3 months The business encoded, the posture changed
Total ~75–100 days 12 months A business that runs on software built to fit

Our fees are quoted per stage after the discovery call, once we know the scope. AI tooling and API subscriptions sit outside that and are usage-based — typically a few hundred to a few thousand per month depending on team size. Suite licences you retire along the way come off your side of the ledger, not ours.

How the risk is held down

  • The suite keeps running until each piece has a proven replacement
  • Every stage ships working software — nothing is theoretical
  • You can pause between stages to consolidate
  • Early stages fund later ones through time and licences recovered

The questions people ask

Can you stop after stage 2? Yes
ERP core plus bespoke layers is a durable position, not a halfway house.
Can you skip stages? No
Each one depends on ground the previous stage proved.
Do we have to leave the suite entirely? No
Commodity ground stays bought. We will tell you which ground that is.
We are greenfield — is this for us? Partly
You skip the crossing and start built to fit. Start with the field guide.

Not sure which side of the line you sit on? The field guide is the framework in five pages, and the home page is the full argument.

Next steps

Ready to start?

We begin with a conversation, not a proposal. If the suite genuinely fits your business, we will say so and save us both a year.

  1. 1 Discovery call Where does the business bend around the system? 30–45 minutes.
  2. 2 The map We put the bend points on paper — what they cost, and what order to take them in.
  3. 3 Stage 1 kickoff We start at the edges, where nothing can break.
  4. 4 The crossing We stay alongside through all four stages, hands on the keyboard.

Schedule a discovery call

No commitment. We will tell you if this is not right for you.