
Complex work. Clear evidence.
Complex operations. Concrete work.
Explore how we handled legacy migration, company boundaries, job costing, workforce policies and stock accounting. Each study explains what was built and where it stands.
Prepared from implementation records, module source and system configuration reviewed on 12 October 2026. Business names are withheld. Figures describe delivery scope or dated verification, rather than estimated savings.
Live implementations & phased rollouts
Delivered systems and production changes, with the scope of each rollout stated.
From Oracle history to a controlled Odoo rollout
A multi-company engineering group needed a new operational ERP without losing access to its Oracle history. We separated the historical archive from new business transactions, rebuilt the group structure and brought HR live as the first department.
2.8M · legacy rows preserved in the reference archive
Read moreConnecting vehicle jobs, sales and finance
An automotive group needed more than a vehicle list and invoices. Its Odoo implementation connects workshop job cards, job quotations, vehicle identifiers, customer sale agreements and group finance, with a separate engine for prepaid expense schedules.
VIN · vehicle reference on sales and invoice lines
Read moreCentral purchasing without losing company boundaries
A group combining retail, hospitality and specialist orders needed central purchasing with an auditable route into its subsidiaries. We added a holding-company pilot, branch-aware intercompany controls and a florist order workflow connected to POS.
7 · companies configured in the database
Read moreMaking workforce rules behave correctly in healthcare
A healthcare employer’s Odoo 15 system brings employee service history, contracts, attendance, payroll and leave together. A bespoke accrual extension solves a subtle policy problem: capping unused leave without permanently stopping future entitlement.
Balance · cap across leave allocations
Read moreReconciling restaurant stock with the books
A restaurant’s Odoo 15 implementation needed a controlled move to periodic inventory accounting while keeping purchasing, stock and POS operational. We rehearsed the cutover, reconciled valuation with the ledger and verified the future stock-movement behaviour.
15 · categories aligned at cutover
Read moreA clean clinic go-live across bookings, tills and stock
A clinic with two reception tills needed to move from a working reference system into a clean production ERP. We preserved master data and future bookings, loaded counted opening stock and connected each till to its own stock location and the client’s chart of accounts.
2 · tills with separate reception stock
Read moreReference builds & working proofs of concept
Working software built for real requirements. These studies describe the delivered engineering and demonstration scope.
Engineering a maintenance system around the plant
For an industrial manufacturer, we built an Odoo 17 maintenance and procurement suite covering equipment hierarchies, preventive scheduling, work-order execution, costing and purchasing controls. The implemented reference environment keeps the delivery demonstrable without presenting it as a live plant rollout.
8 · custom modules installed in the reference
Read moreFrom a kitchen quotation to installed, costed work
A working proof of concept for a joinery group connects sales, Finance, site measurement, material approvals, CNC, a separate coating company, delivery, installation and after-sales repairs. We built it from the client’s workflow documents and existing-system menu evidence.
3 + 2 · legal companies and sales branches
Read moreWebsite portfolio
See what we have designed and built
Explore real website screens, the journeys they support and the scope we delivered.
Explore the website portfolioTell us what's slowing your business down
Get a free 30-minute consultation — we'll map your workflow and show you exactly what to automate first.