ERPNext / Frappe
Best for
A custom ERP on an open-source base, with no per-seat lock-in
We deliver
Inventory, orders and finance modules, plus custom doctypes
Awards & Recognitions
ERP & CRM development
ERP and CRM built around how your business already runs
We implement ERPNext, Odoo and Microsoft Dynamics 365, build the modules they’re missing, move your data across and connect the systems around them. When none of them fits, we build one.
Northridge Supply Co.
Customer record · example
CRM
ERP
Mar 02
Website
Lead from web form
Assigned to Priya, sales
Mar 05
CRM
Quote Q-2291 sent
3 lines · price list B
Mar 09
ERP
Order SO-10482 created
From accepted quote, no re-keying
Mar 10
EDI
Stock reserved, PO raised
Supplier ACK matched by EDI
Mar 14
Accounting
Invoice posted
Commission calculated for Priya
Mar 21
CRM
Service ticket opened
Order history visible to support
Platforms
Which platform?
We usually can’t tell you until we’ve seen how your orders, stock and invoices move today. After that, the choice tends to be obvious.
Odoo
Best for
A modular ERP with strong e-commerce links
We deliver
Implementation and Shopify integration
Proof · Heads Up For Tails
Microsoft Dynamics 365
Best for
Organisations already standardised on Microsoft
We deliver
Implementation and customisation
Current work · Cook & Boardman Group
Custom-built
Best for
Workflows no off-the-shelf product can model
We deliver
.NET, Angular and React builds on Azure or AWS
Proof · DiSellCo, MCA, industry CRMs
Your process is close to standardYour process is unusual
The further right your process sits, the more a platform has to be bent to fit it, until a custom build is cheaper to own.
Services
What we do
Usually in this order. We start with the data because if it arrives messy, people go back to their spreadsheets within a month.
01
Migrate
Move data out of spreadsheets or a legacy system, cleaned and reconciled.
02
Implement
Configure the chosen platform to your mapped processes.
03
Customise
Build the modules and workflows the platform doesn’t cover.
04
Integrate
Connect e-commerce, payments, EDI and email.
05
Support
Upgrades, fixes and improvements after go-live.
How your data gets across
Old system stays live the whole way
01
Extract
Pull records from the old system
02
Profile
Find duplicates and gaps
03
Cleanse
Rules agreed with your team
04
Map
Old fields to new ones
05
Load
Trial loads first
06
Reconcile
Totals match both sides
Custom CRM
Custom CRMs we’ve built
Most of our CRM work is custom, for construction, healthcare and manufacturing companies whose sales process didn’t fit a standard pipeline.
The workflow the CRM runs
- Step 1Plans received
- Step 2Takeoff & estimate
- Step 3Quote issued
- Step 4Purchase order
- Step 5Supplier acknowledgement matched
Construction and distribution
Estimating, purchase orders and supplier acknowledgements in one system. This draws on Orion’s Takeoff and PO ACK work for large US door and hardware distributors.
The workflow the CRM runs
- Step 1Referral / intake
- Step 2Assessment
- Step 3Care schedule
- Step 4Visit notes
- Step 5Billing & audit
Healthcare and care providers
Client records, intake, scheduling, staff and compliance workflows, with role-based access and an audit trail on every change.
The workflow the CRM runs
- Step 1Enquiry
- Step 2Quote
- Step 3Order
- Step 4Fulfilment
- Step 5Invoice & commission
Manufacturing and multi-division
Dealer and division hierarchies, orders, commissions and ERP posting across 100+ divisions. Based on our AI Email Responder and PO ACK work.
Integrations
Integrations
If someone on your team copies orders from one screen into another, that’s the first thing we connect.
Sends data in
SHShopify / e-commerce
Order
PGPayment gateways
Settlement
EDIEDI
Supplier ACK
OCREmail + OCR
PO data
ERP · Sales order
SO-10482
Customer & itemsWeb order, 3 lines
Shopify
PaymentSettled
Gateway
Purchase orderRaised to supplier
Email + OCR
Supplier acknowledgementMatched
EDI
InvoicePosted
→ Accounting
Nobody typed any of this in.
Receives data out
Ledger
entry
GLAccounting
Sync
while migrating
DBLegacy databases
In production: PO ACK matches supplier acknowledgements to purchase orders across 100+ divisions.
Case studies
Recent work
Named references and architecture walkthroughs available under NDA.
Featured · DiSellCo
A desktop order and commission system, rebuilt for the cloud
DiSellCo ran orders, accounting and commissions on a legacy desktop product fed by nightly SQL jobs. We rewrote it as microservices on Azure Kubernetes and consolidated the databases behind it.
4
critical workflows integrated
0
scheduled SQL jobs remaining
US door & window manufacturer
PO ACK
Purchase-order acknowledgements automated across 100+ divisions, with a disposition recorded for every line.
Supplier emailOCRMatch to POERP
GPT-4o · OCR · EDI · ERP
Cook & Boardman Group
AI Email Responder
Reads inbound emails and attachments, pulls out the PO data and posts it to the ERP. Our Dynamics 365 work with them is ongoing.
InboxExtract POMatch divisionERP
GPT-4o · OCR · ERP
Pet e-commerce
Heads Up For Tails
Shopify storefront integrated with Odoo ERP.
Shopify orderOdooStock & invoice
Shopify · Odoo
Canadian merchandising company
MCA Operations Portal
One portal in place of disconnected systems: users, projects, payroll and invoicing.
UsersProjectsPayrollInvoices
.NET Core · Angular
How we deliver
How a project runs
You sign off each step before the next one starts. Your old system stays on until the numbers in both match.
01
Discover
Map current processes, systems and data.
Output · Process map
02
Design
Choose the platform and define scope.
Output · Solution design
03
Plan migration
Profile the source data and agree cleansing rules.
Output · Migration plan
04
Build
Configure and customise in sprints.
Output · Working releases
05
Test & parallel run
User testing on real data, with the old system still live.
Output · Reconciliation sign-off
06
Go live & support
Cutover, training and hypercare, then ongoing support.
Output · Support agreement
Indicative sequence
Relative, not to scale. Durations depend on scope.
Discover
Go live & hypercare
Old system live
Design
Plan migration
Build
Test & parallel run
Frequently asked
Questions before you commit to a new system
The questions we get asked most in the first call.
It depends how far your processes are from standard. We map them first, then pick the platform that needs the least customising. Sometimes that’s a custom build.
Yes. Source data is profiled and cleansed, the rules are agreed with you, and the old system runs in parallel until the reconciliation passes.
Yes. We’ve connected ERPs to Shopify, payment gateways, EDI feeds, email inboxes and accounting systems.
Yes. We build them on the platform’s own framework so you can still upgrade.
Yes, before and after go-live.
A hypercare period after cutover, then ongoing support for fixes, upgrades and improvements.
Start here
Start with a process review
Two hours with one of our ERP leads, walking through how work moves through your business today. You get a written recommendation afterwards, whether or not you hire us.
Your current process, mapped
Which platform we’d use, and why
What migration and integration would involve
Book a process review
An ERP and CRM lead will reply within one business day.
Confidential. NDA available on request.
