Enterprise Solutions
We Replace the Systems Your Business Has Outgrown, a Piece at a Time.
Custom software for mid-size organisations: who can do what, who signs off, a record of every change, and links to the ERP and older systems you already run. Old systems get replaced in phases, so the business keeps running.
Available for new projects
Who This Is For
If one of these is you, keep reading.
Regulated Mid-Market Firms
Finance, health, or public sector, with an audit on the way and approvals still living in email.
Companies After an Acquisition
Two systems that don't fit together and a spreadsheet in the middle that has to become the one place everyone trusts.
Organisations Whose ERP Didn't Take
It's live. Departments still run their own manual workflows next to it.
Firms With a Decade-Old Core System
Kept going by one or two people, written down nowhere, and getting riskier every year.
Multi-Department Operations
Procurement, HR, and operations needing sign-offs by role and a view across teams.
Why Mid-Size Businesses Build Custom
One of these is usually the trigger.
Audit and Compliance
SOX, ISO 27001, SOC 2, and DORA all want proof that access was approved, reviewed, and taken away again. Approvals in email can't prove any of it.
An ERP That Doesn't Fit
The package can't do your process the way you run it, so teams run their own by hand next to it.
Merger and Acquisition
Two sets of systems, two ways of working, and a spreadsheet holding them together.
Legacy Cost
A big chunk of the IT budget goes on keeping old systems alive rather than building anything new.
Key-Person Risk
A core system that one or two people near retirement know how to keep running. When they go, so does the knowledge.
Executive Visibility
Approvals in email and chat are a second system nobody can see into. Leaders can't tell where work is stuck.
What Makes These Projects Hard
Size makes every normal software problem bigger.
Slow Decisions
On most big projects, getting sign-off and getting departments to agree takes longer than the technical work.
Change Management
Panorama's 2025 ERP report puts change management top of the list of reasons projects run late. The system works. People don't switch to it.
Data Migration
Old data is wrong, duplicated, and shaped for a system the business has outgrown. Move it as it is and you move the problems with it.
Living Alongside the ERP
The new system has to work with the finance package, the manufacturing system, and whatever the company you bought is running.
Security and Compliance
Tools nobody signed off on, and nobody keeping track of who has access to what, are behind a growing share of breaches.
Long Timelines
Big-bang ERP projects take most of a year, and every extra month makes the estimate less reliable. That's why we don't do them in one go.
Enterprise IT in Numbers
Why we work in small phases and build the controls in first.
45%
average budget overrun on large IT projects, which also deliver 56% less value than promised.
6%
of very large projects succeed, against 61% of small ones.
80%
of US federal IT spend goes on running and maintaining what's already there.
$4.44M
is what a data breach cost on average worldwide in 2025.
Sources: McKinsey & Oxford, Delivering Large-Scale IT Projects · Standish Group, CHAOS Report (2020) · US GAO, GAO-25-107795 (2025) · IBM, Cost of a Data Breach Report (2025)
Where Big Projects Go Wrong
None of this is a mystery. It's been studied, and we build to avoid all five.
Scope and Value Drift
McKinsey and Oxford looked at 5,400 large IT projects. On average they ran 45% over budget and delivered 56% less value than promised.
Big-Bang Size
Standish's numbers: huge projects succeed 6% of the time, small ones 61%. Size is the best predictor of failure there is.
Underestimated Staffing and Scope
Panorama puts most overruns down to staffing, scope growing, and surprises in the data. All three can be found up front if you look.
People Don't Switch
If nobody uses the new workflow, the email approvals come back and the new system is one more thing to keep in sync.
System Links Planned Too Late
Most system-to-system links fail at the planning stage, not the build. How the new system talks to the ERP and the old systems has to be worked out before anyone writes code.
How We Build It
Small phases, the old system kept running, and the controls built in from day one.
Assessment First
We map what depends on what, put a number on the technical debt, and score each system on what it's worth to the business. You know what you're taking on before you commit.
A Plan per System
Move it, re-platform it, tidy it up, rebuild it, retire it, or replace it. Most mid-size organisations need a mix.
Replace a Piece at a Time
New parts get built behind a routing layer while the old system keeps running. Nothing switches over in one go.
Controls in the Data Model
Who can do what, one person can't request and approve, multi-step sign-offs, and logs nobody can quietly edit. All there from the first release.
System Links Designed First
How the new system talks to the ERP, finance, and older systems is written down before the build starts.
Rollout Led by the Process Owners
Training and rollout come from the people who run the process day to day. We back them up and measure whether people switch.
What we build with
- Next.js
- TypeScript
- PostgreSQL
- .NET
- SQL Server
- Azure
- AWS
- SSO / SAML
- audit logging
- ERP integration
Built the same way: Receivables · Banyan · Egis · Lift
Why We Replace It in Waves
A two-year programme with one go-live is the 6% success rate in the numbers above. We ship a working workflow every two weeks, and the old system stays on until each piece is proven.
A Pilot in Use in Weeks
One contained workflow, moved off the old system and in daily use inside the first two months. The approach is proven on something real before the programme is committed.
Process Owners Steer the Roadmap
The people who run each process decide what moves next and lead its rollout. Adoption is measured. A workflow nobody switches to gets rethought before the next one starts.
Stop Between Any Two Steps
Every two weeks you see a live demo of what shipped and make a decision: keep going, change direction, or pause. You are billed per step, so if you pause, you pay for what shipped.
Change Priorities Cheaply
A change of priorities moves the next phase only. What is already live stays live. The things we fix early, because they are expensive to reverse, are the controls in the data model and the links to the ERP.
Riskiest System First
The ERP link, the dirtiest data, and the workflow with the most sign-offs get built and tested first. If the programme is going to hit a wall, you find out in the pilot.
No Big-Bang Cutover
New parts go live behind a routing layer while the old system keeps running. Every step can be undone. The old system is switched off last, when nothing depends on it.
How a Fixed-Price Wave Runs
In phases, measured, and each step can be undone. Working software from the pilot onward. You own the code throughout.
- First wave
- 12-20 weeks
- Pilot in use
- Week 6
- Live demo
- Every 2 weeks
- 01
Discovery and Assessment
Week 1-2A fixed-fee fortnight. We map the systems, what depends on what, the data, and the risks. Technical debt and business value get scored. You keep the assessment whether or not you go ahead.
- System map
- Debt and value scores
- Fixed price for the first wave
- 02
Strategy and Roadmap
Week 2-3A decision for each system, lined up in waves that stay clear of year-end and other busy periods.
- Per-system decision
- Wave plan
- 03
Pilot
Week 3-8One contained workflow gets moved first to prove the approach works, with the controls and the ERP link built in from the start.
- Pilot workflow live
- Controls in the data model
- Live demo every 2 weeks
- 04
Build in Stages
Week 6-16Features move from old to new behind a routing layer, one workflow every two weeks. The business keeps running the whole time.
- New workflow every 2 weeks
- 05
System Links and Migration
Week 8-18Data gets cleaned as it moves. Links to the ERP and older systems get built and tested.
- ERP links live
- Data cleaned as it moves
- 06
Rollout and Training
Week 14-20Led by the process owners, backed by us, judged on whether people use it.
- Owner-led rollout
- Adoption numbers
- 07
Switch-Off and Review
End of each wave, then ongoingThe old system goes off. We measure the results against the original business case, then plan the next wave, stay on a retainer, or hand over to your own team.
What It Costs
Fixed fee
Two weeks. Ends with a per-system plan and a fixed price for the first wave. Yours whether or not you go ahead.
- System map
- Per-system plan
- Fixed price for wave one
$80k - $400k+
The number moves with how many workflows there are, how many systems the new one has to talk to, and what state the old data is in.
- Billed
- Per 2-week step
- Pause
- Between any two steps
- First commitment
- A pilot
Build or Configure the ERP
Almost always both.
Configure the Package For
The standard stuff: general ledger, payroll, everyday purchasing. Nobody wins by building their own accounting system.
Build Custom For
The workflows that set you apart or keep you compliant, and that the package just can't do.
Get the Two Talking
The ERP stays the system of record for the money. The custom systems swap data with it, reliably.
What an Audit Trail Needs
Built in at the start.
Who, What, When, Where
Every change recorded with who did it, what they did, when, and in what context, in a form nobody can edit afterwards.
One Person Can't Do Both
Whoever asks for something can't be the one who approves it. The system stops it.
Keeping It and Finding It
SOX wants records kept for years. GDPR wants you able to pull up everything about one person. Both are decisions about how the data is stored, made at the start.
Common Questions
If yours isn’t here, book a call and ask.
Where Does the Process Live Today?
Tell us which approvals happen in email, which system nobody dares touch, and when the next audit is, on the call. If it's a fit, a two-week assessment follows, and at the end of it you know where to start, what the first wave covers, and its fixed price.