Your ERP ends where the paper claims file begins, and in London that gap is the whole business
A custom ERP (Enterprise Resource Planning) for a London, Ontario insurer or manufacturer runs $90,000 to $220,000 over 5 to 9 months. The reason you outgrew NetSuite or SAP here is specific: your claims and patient-intake work still starts on paper or in a legacy AS/400 screen, and no off-the-shelf module bridges that to your general ledger without people retyping it. Custom is worth it when that transcription gap is the bottleneck.
You bought NetSuite or Microsoft Dynamics expecting one system of record. Instead your London operation runs three: the ERP for finance, a 1990s policy-admin or hospital system nobody will touch, and the real source of truth, a shared drive full of scanned PDFs that a clerk on Dundas Street retypes into both. SAP assumes clean structured input. Your input is a faxed claim form from a broker in Strathroy.
Odoo and Dynamics give you modules, not a migration path off the legacy core that Canada Life-era systems and London's mid-size insurers still depend on. The ERP demos beautifully on clean data and then meets a 40-year-old book of business and a PHIPA-regulated patient record that legally cannot be copy-pasted into a US-hosted cloud. That mismatch is why the rollout stalls at go-live.
What breaks first in London
- Claims and patient forms arrive on paper or fax, then get manually keyed into both the legacy system and the new ERP, doubling the work and the error rate
- Off-the-shelf ERP cloud hosting sits in the US, which collides with PHIPA and Ontario data-residency expectations for London Health Sciences Centre-adjacent vendors
- Legacy policy-admin and AS/400 cores cannot expose clean APIs, so every ERP integration becomes a nightly CSV export held together by one retiring employee
- Conservative London finance teams will not sign off on a system they cannot audit line by line, and SAP black-box logic fails that test
The fix: erp built for London, not rented
You build custom when the value is in the seams between your legacy core, your paper intake, and your ledger, which is exactly where packaged ERP refuses to live. A custom ERP for a London insurer or manufacturer wraps the legacy system instead of ripping it out, ingests scanned and faxed intake with OCR plus a human-review queue, and keeps regulated health and policy data on Canadian infrastructure you can point an auditor at. You stop paying for 200 modules to use 12.
What erp costs in London
| Project scope | Typical cost | Timeline |
|---|---|---|
| Legacy-wrapped ERP core with intake pipeline | $90k to $150k | 5 to 7 months |
| Full insurer or hospital ERP with claims, GL, and reconciliation | $150k to $220k | 7 to 9 months |
| ERP add-on layer over an existing system, no full replacement | $55k to $90k | 3 to 5 months |
The capability list that earns its budget
What we build under ERP in London
The engagements London teams bring us most often: SAP integration, Odoo development, Microsoft Dynamics 365, ERP migration, cloud ERP and manufacturing ERP.
Exactly what you get
You get an ERP that treats your legacy policy-admin or hospital system as a living source, not a thing to delete. It ingests the paper and faxed claims that London brokers and clinics still send, OCRs them, queues the uncertain ones for a person, and posts the rest to a Canadian-hosted ledger an auditor can trace. Finance, underwriting, and claims see the same reconciled numbers instead of three versions. Pair it with custom CRM (Customer Relationship Management) development for broker relationships and business intelligence dashboards for the board view.
How to choose a developer in London
Hire the team that asks to see your AS/400 screens and your scanned-claims folder in the first meeting, not the one that opens with a NetSuite logo. In a conservative, institution-anchored market like London you want a partner who can speak to PHIPA, Canadian hosting, and external audit, and who has wrapped a legacy core before rather than only deployed SaaS. Ask for a reference where they integrated with a system older than their newest developer.
- !They quote a fixed price before seeing your legacy core; ask instead how they will read and write to your existing policy-admin system
- !They assume US cloud hosting; ask where regulated Ontario health and insurance data will physically live
- !No plan for paper and fax intake; ask to see how scanned claims become structured ledger entries
- !They pitch a big-bang cutover; ask how the legacy system keeps running during a phased migration
- !No named data-migration owner; ask who maps 40 years of policy records and how they validate it
Teams investing in erp in London usually scope it next to internal tools, shopify, inventory management, since these systems share data and budgets.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Why not just configure NetSuite or SAP for our London insurance business?
You can, and if your processes are standard you should. The reason London insurers and hospitals end up custom is the paper-and-legacy gap: claims arrive on fax, the policy book lives in a 40-year-old system, and PHIPA limits where data sits. Packaged ERP assumes clean structured input and US cloud hosting, so it stalls exactly where your real work happens.
Does PHIPA really force custom development?
Not by itself. PHIPA forces you to control where patient and health-adjacent data lives and who touches it. Some packaged vendors offer Canadian hosting, but many bury the data model so you cannot prove the audit trail. Custom lets you keep regulated data on Canadian infrastructure with a trail you can hand to an auditor, which is why London health and insurance buyers lean that way.
How long before a custom ERP replaces our current system?
Plan on 5 to 9 months for a real London insurer or manufacturer, with a phased cutover rather than a single switch. The legacy core keeps running while the new ERP reads and writes to it, so you de-risk go-live. A lighter add-on layer over your existing system can ship in 3 to 5 months if you are not replacing finance outright.
What does it cost to maintain after launch?
Budget 15 to 20 percent of build cost per year for hosting, support, and the steady stream of changes a living business needs. That is the trade for owning the system: you carry the cost a SaaS vendor would otherwise bundle into a per-seat fee, but you also stop paying six figures for every SAP change request.
Can it work alongside our existing accounting and CRM tools?
Yes, and it usually should. A custom London ERP commonly integrates with accounting software for the books, custom CRM development for broker and patient relationships, and business intelligence dashboards for reporting. The point of building is the seams, so good ones connect cleanly to the systems you keep rather than forcing you to replace everything at once.