ERP
The backbone that scales with you
One system your finance and operations teams actually run on, implemented in weeks rather than quarters. Start on Odoo, graduate to SAP when you outgrow it, and keep the same partner through both.
Sound familiar?
Your month-end close takes three weeks and the numbers still get argued about.
Inventory, orders and invoices live in four spreadsheets, and reconciling them is somebody's full-time job.
Every new hire in ops adds headcount instead of capacity, because nothing is automated end to end.
What we do
Capabilities
- ERP selection
- A structured comparison against your actual processes, not a vendor matrix. Sometimes the answer is that you are not ready for an ERP yet, and we will tell you that.
- Implementation
- Finance, inventory, procurement, CRM and manufacturing configured against how your business really runs, delivered in two-week increments you can see.
- Data migration
- Moving history out of spreadsheets and legacy systems without importing a decade of bad data along with it.
- Master data governance
- One trusted record of customers, vendors, products and materials, with the rules and ownership that keep it clean after go-live.
- Integration
- Your ERP talking to the rest of the stack — payments, logistics, e-commerce, payroll, data warehouse — without nightly CSV exports.
- Hypercare and handover
- Training, documentation and admin access from day one, so your team can run the system without us.
Outcomes
What changes
Before
Finance closes from spreadsheets, and the numbers are argued over before they are published.
After
The close runs from one set of books, so the argument is about the business rather than the data.
Before
The same transaction is re-keyed into two or three systems.
After
It is entered once and flows, because the systems share a record rather than a copy of one.
Before
Nobody can say what stock or cash looks like without someone preparing a report.
After
The position is in the system and current; the report is a view of it rather than a rebuild.
How it works
The engagement
- 01
Discovery
1–2 weeks
We map your current process, agree the target, and produce a scope and a fixed number. Paid, and useful even if you stop there.
- 02
Design
2–3 weeks
Chart of accounts, process flows, roles and the data model. We settle how the business should run before configuring anything.
- 03
Build and migrate
6–12 weeks
Configuration, integrations and data migration in two-week increments, each one demoed to the people who will use it.
- 04
Go-live and hypercare
4 weeks
Cutover, training and intensive support through the first close. Then we hand over the keys.
Go deeper
The playbooks set out how these processes run, step by step — what is standard, what gets configured, and what changes.
Stack
- Odoo
- SAP Business One
- GROW with SAP
- SAP Master Data Governance
- PostgreSQL
- REST / webhooks
Questions
The things people actually ask
- How long does an ERP implementation actually take?
- For a company of 20–300 people on Odoo, typically 10–16 weeks from kickoff to go-live, depending on how many modules you turn on and how clean your existing data is. SAP midmarket implementations run longer. Anyone quoting you a fixed timeline before seeing your processes is guessing.
- Should we pick Odoo or SAP?
- Odoo suits most companies from seed to Series B: fast to stand up, cheap to change, and broad enough to cover finance, inventory, CRM and manufacturing in one place. SAP earns its cost when you need deeper compliance, multi-entity consolidation or industry-specific process rigour. We cover how to choose on the Odoo and SAP pages, and the decision is part of discovery.
- What does it cost?
- Two separate costs: licensing, which you pay the vendor per user per month, and implementation, which you pay us once. We quote implementation as a fixed price after discovery, because quoting before we have seen your processes would be a number we would have to revise.
- Can you migrate us off our current system?
- Yes, and that is usually the hard part. The risk is not moving the data, it is deciding what not to move. We treat migration as a cleanup exercise rather than a copy.
- What happens after go-live?
- Four weeks of hypercare covering your first month-end close, then an optional support retainer. Your team gets admin access and documentation from day one — you should be able to stop working with us and keep running.
- Do we need AI on top of this?
- Not on day one. Get the system of record right first; an agent reading from a messy ERP produces confident nonsense. Once the data is trustworthy, the agent layer is where the compounding returns are.
Tell us what’s breaking.
Thirty minutes, no deck. We’ll tell you whether this is the right place to start.

