ERP · SAP
SAP for companies that have outgrown the easy answer
Business One and GROW with SAP, for scale-ups hitting the limits of a lighter ERP. The compliance depth, multi-entity consolidation and process rigour that investors and auditors start asking about after Series B.
Sound familiar?
You are consolidating across entities or currencies and your current system cannot do it without a spreadsheet at the end.
An audit, a regulator or an acquirer has asked for controls your ERP cannot evidence.
You are being pushed toward SAP by a customer or parent company and need someone who can scope it honestly.
What we do
Capabilities
- Product selection
- Business One, GROW with SAP or neither. These are genuinely different products with different costs and ceilings, and picking wrong is expensive to undo.
- Implementation
- Financials, controlling, procurement, sales and inventory configured to your process, using SAP's own activation methodology rather than a blank slate.
- Multi-entity and multi-currency
- Group structures, intercompany postings and consolidation set up so close is a process rather than a month of spreadsheet work.
- Migration from a lighter ERP
- Moving off Odoo, NetSuite or QuickBooks with the history, the open items and the audit trail intact.
- Integration and extension
- Extensions built on SAP BTP and clean-core principles, so your customisations do not block the next upgrade.
- Controls and audit readiness
- Segregation of duties, approval workflows and the documentation your auditor will ask for.
Outcomes
What changes
Before
Each entity closes on its own and consolidation is a spreadsheet exercise.
After
Entities close into one structure, so consolidation is a step rather than a project.
Before
Statutory and management reporting are reconciled by hand every cycle.
After
Both come from the same ledger, so reconciliation is an exception rather than a routine.
Before
Intercompany balances are agreed over email at quarter end.
After
They post against each other, and anything that does not match surfaces immediately.
How it works
The engagement
- 01
Fit assessment
2 weeks
Whether SAP is right for you at all, which product, and what it will cost across licence and implementation. Sometimes the answer is to stay where you are.
- 02
Explore and design
4–6 weeks
Fit-to-standard workshops against SAP best practice, with every gap logged and costed rather than absorbed quietly.
- 03
Realise
3–5 months
Configuration, extensions, integrations and iterative data migration, with your key users testing throughout.
- 04
Deploy and run
6–8 weeks
Cutover, parallel close, training and hypercare through the first full reporting cycle.
Go deeper
The playbooks set out how these processes run, step by step — what is standard, what gets configured, and what changes.
Stack
- SAP Business One
- GROW with SAP
- SAP S/4HANA Cloud Public Edition
- SAP BTP
- SAP Master Data Governance
- HANA
Questions
The things people actually ask
- Is SAP not overkill for a company our size?
- Often, yes — and we will say so. SAP earns its cost at the point where multi-entity consolidation, regulatory depth or industry-specific process becomes the constraint. Below that, Odoo does the same job for less. The fit assessment exists to answer this honestly before you commit.
- What is the difference between Business One and GROW with SAP?
- Business One is a self-contained product for smaller companies, typically deployed per entity. GROW with SAP is public-cloud S/4HANA on a fixed-scope, fast-start model, and is the better fit if you expect to grow into full S/4HANA process. They are not upgrade paths for one another, which is why the choice matters up front.
- How much does SAP cost?
- Licensing is negotiated with SAP and depends on user counts and modules, so we will not quote their number. Implementation we quote as a fixed price after the fit assessment. Budget for the two separately, and be sceptical of anyone who blends them into a single figure.
- Can we move from Odoo to SAP later?
- Yes, and it is a path we deliberately support. Starting on Odoo and graduating when the business demands it is cheaper than buying SAP three years early. Because we implement both, the migration is not a competitive handover.
- What does 'clean core' mean and why should we care?
- It means keeping customisations outside the standard SAP core, on BTP, instead of modifying it. It costs slightly more up front and saves you from being locked out of upgrades later. It is the single decision that most determines what your SAP system costs to own over five years.
- How long before we see value?
- First reporting cycle on the new system, so plan for one quarter after go-live. Anyone promising value during implementation is describing a demo, not your business.
Tell us what’s breaking.
Thirty minutes, no deck. We’ll tell you whether this is the right place to start.

