ERP · Odoo
Odoo, implemented properly
The natural ERP for companies from seed to Series B. Broad enough to replace most of your spreadsheet stack, cheap enough to change when you learn something, and quick enough to be live this quarter.
Sound familiar?
You have outgrown spreadsheets and QuickBooks but a full enterprise ERP would cost more than the problem.
You tried Odoo already and it stalled, because it was configured by someone who had never run a finance process.
Different teams have each bought their own tool, and none of them agree on what a customer is.
What we do
Capabilities
- Module scoping
- Odoo has dozens of apps and turning them all on is the most common way an implementation fails. We start with the three or four that pay for the project.
- Finance and accounting
- Chart of accounts, tax configuration, multi-currency, bank feeds and a close process your accountant signs off on.
- Inventory and manufacturing
- Stock, warehouses, bills of materials and work orders modelled against how your operation actually moves goods.
- Custom modules
- Odoo covers 80% of most businesses. We build the remaining 20% as proper modules that survive version upgrades, not as patches.
- Integrations
- Shopify, Stripe, shipping carriers, payroll and your warehouse. Built on Odoo's API rather than bolted on with scheduled exports.
- Version upgrades
- Odoo ships a major version annually. We keep customisations upgrade-safe so you are not stranded three versions behind.
Outcomes
What changes
Before
The business runs on spreadsheets that one person fully understands.
After
It runs on a system, and the knowledge sits in configuration rather than in somebody's head.
Before
Every new process means another spreadsheet and another hand-off.
After
It means a configured flow, with the hand-off recorded and visible to both sides.
Before
An ERP project is an eighteen-month commitment nobody wants to start.
After
The first go-live is measured in weeks, and scope grows from something already running.
How it works
The engagement
- 01
Discovery
1–2 weeks
Process mapping, module shortlist, fixed-price scope for the build.
- 02
Configure
4–8 weeks
Core modules configured and demoed fortnightly, with your team in the system from week three rather than at the end.
- 03
Migrate and test
2–3 weeks
Data migration, parallel running and user acceptance testing against real transactions.
- 04
Go-live and hypercare
4 weeks
Cutover, training, and support through your first close on the new system.
Go deeper
The playbooks set out how these processes run, step by step — what is standard, what gets configured, and what changes.
Stack
- Odoo 18
- Odoo.sh / self-hosted
- Python
- PostgreSQL
- XML-RPC / JSON-RPC API
Questions
The things people actually ask
- Odoo Community or Enterprise?
- Enterprise for most companies: you get the accounting engine, studio, and official support, and the per-user cost is usually lower than the engineering time Community would need. Community makes sense if you have strong in-house Python capability and a narrow use case.
- Odoo.sh, Odoo Online or self-hosted?
- Odoo.sh for most teams, because it gives you staging environments and git-based deployment without running infrastructure. Odoo Online is simpler but blocks custom code. Self-host only when a data residency or compliance requirement genuinely demands it.
- Will customisations break when Odoo upgrades?
- Badly written ones will. We build customisations as separate modules against documented APIs rather than modifying core, which is what makes annual upgrades routine instead of a project.
- Can Odoo handle manufacturing?
- Yes — bills of materials, work orders, routings and quality checks are all native. It fits discrete manufacturing well. Process manufacturing with complex batch genealogy is where you should pressure-test it carefully during discovery.
- We started an Odoo project that stalled. Can you pick it up?
- Usually. We start with an audit of what has been configured and what has been customised, then tell you honestly whether it is cheaper to continue or to restart. We have no incentive to recommend a rebuild you do not need.
- How many users do we need to license?
- Only people who log in. Customers using a portal and staff who only receive reports do not need paid seats, which is a common way teams overpay.
Tell us what’s breaking.
Thirty minutes, no deck. We’ll tell you whether this is the right place to start.

