How a Multi-Division General Contractor Unified Construction, Restoration, and Service Operations on Odoo Enterprise

General Contract is a group of related contracting businesses spanning construction and renovation, restoration and repair, and ongoing service work. Like many contractors that grow through multiple business lines, the group had reached a point where spreadsheets, disconnected tools, and manual sign-offs were slowing down the business faster than the business itself was growing. Estimating lived in one place, purchasing in another, and nobody had a real-time view of what a project actually cost until weeks after the work was done.

Rather than bolt on point solutions, the group made a multi-year investment in Odoo Enterprise as a single operating system for every entity in the group — and treated the rollout as an operations redesign, not just a software install.

The starting problem: one group, several companies, no shared system

The group operates as several legally distinct companies under one ownership structure — roughly a construction arm, a restoration arm, and a services arm, each with its own bank accounts, vendors, and crews, but sharing back-office staff, management, and, in many cases, the same job sites. Before consolidation, each entity effectively ran its own version of "the process," which meant:

• Estimating and sales data that didn't talk to job costing or accounting.
• Purchase requests approved by email or verbally, with no audit trail.
• Inventory and material use tracked on paper or in disconnected spreadsheets per site.
• Field labour hours captured separately from the ERP, then re-keyed into payroll by hand.
• Management reporting that had to be manually stitched together across entities to see the whole group.

Building a true multi-company foundation

The core of the project was standing up Odoo as a genuine multi-company environment rather than running separate, disconnected instances. Each legal entity keeps its own books, its own chart of accounts, and its own approval chains, while shared elements — vendors, employees, product and material catalogs, and reporting — roll up cleanly at the group level.

• Shared master data, separate ledgers: vendors, employees, and materials are maintained once and used across companies, while financial transactions stay properly segregated by entity.
• Inter-company transactions: when one division's crew or equipment supports another division's project, the cost allocation and internal billing happen inside the system instead of through manual journal entries.
• Consolidated reporting: leadership gets a real-time, group-wide view of revenue, cost, and margin, while still being able to drill into any single company or division.

End-to-end workflow: from lead to final invoice

The bigger shift wasn't just technical, it was procedural. Every core business process was mapped and rebuilt inside Odoo so that information created once — a lead, an estimate, a purchase order — flows forward automatically instead of being re-entered at each stage.

1. CRM & estimating: opportunities and site assessments feed directly into structured estimates covering labour, materials, subcontractors, and equipment.
2. Sales & project setup: an accepted estimate converts into a project with budgets, cost codes, and schedules already attached — no re-keying.
3. Purchasing & procurement: material and subcontractor needs generate purchase requests that route through defined approval limits before a PO is issued.
4. Inventory & site logistics: stock movements, material requisitions, and deliveries to job sites are tracked so materials on hand match what a project actually needs.
5. Execution & field cost capture: labour hours, equipment use, and site expenses are captured against the project in real time (see timesheet integration below).
6. Vendor billing & invoice matching: vendor bills are matched against POs and received quantities before payment is released.
7. Project financial close: actual cost versus budget is visible throughout the job, not just at the end, and rolls into the group's consolidated financials.

Approval workflows built for governance, not bottlenecks

A recurring theme across the transformation was replacing informal, verbal approvals with structured, role-based workflows — without turning every request into a bureaucratic delay. Custom approval chains were built for the situations that actually needed control:

• Purchase and vendor bill approvals routed by dollar threshold and role, so a small material request and a large subcontractor commitment don't follow the same path.
• Quantity and pricing validations that flag a purchase or bill automatically if it falls outside expected ranges, catching errors before they become disputes.
• Expense approvals tied to project budgets, so spend against a job is visible to the project manager as it happens.
• Role-based security ensuring people only see and approve what's relevant to their entity, division, or project — important in a multi-company structure where several businesses share staff.

Behind the scenes, a large number of automated actions and standardized business rules — well into the hundreds — now handle work that used to require someone remembering to do it manually: routing a document, notifying an approver, flagging an exception, or updating a status.

The platform at work: transaction volume today

Beyond process design, the clearest sign of adoption is simply how much of the business now runs through the system every week. Pulling activity data straight from the live environment (figures below are rounded and randomized within about ±10% to protect exact business detail) shows a platform that has scaled from an initial pilot into the operational backbone of the group:

That last figure is worth pausing on. When the timesheet integration first went live, field hours trickled into the system in the low hundreds per month while crews and supervisors got comfortable with mobile clock-ins. Within about a year and a half, that volume grew roughly 20 to 30 times over, reflecting full adoption across the field workforce rather than a handful of pilot users. Purchase order volume tells a similar story — issued POs grew from well under 50 a month in the platform's early days to a steady several hundred a month as procurement moved fully into the system.

Connecting the field: third-party timesheet integration

Office systems are only half the picture for a contractor — the other half happens on job sites, with crews who aren't sitting at a desk. Rather than force field staff into the ERP directly, the group connected a dedicated field workforce management app (used for scheduling, mobile time clocks, and kiosk check-ins) to Odoo through an integration built on n8n, an automation platform used to synchronize data between systems.

• Employee sync: new hires and role/site assignments stay consistent between the field app and the ERP without duplicate data entry.
• Timesheets & scheduling: hours clocked from a phone or a site kiosk flow into Odoo and post directly against the correct project and cost code.
• Real project costing: because labour hours land in the system close to real time, project managers see actual labour cost building against budget during the job, not weeks later at invoicing.
• Payroll accuracy: eliminating manual re-entry of field hours cut down on the timesheet corrections and disputes that come with paper or spreadsheet-based tracking.

Platform stability through a two-version migration

Custom workflows and integrations only pay off if they keep working as the platform evolves. The group carried its customizations, automations, and security rules forward through an Odoo 17 to Odoo 19 Enterprise migration, reviewing every custom report, automated action, and access rule to make sure the system stayed reliable rather than accumulating technical debt.

Before Odoo vs. after Odoo, by the numbers

Before 2024, the group was already five separate companies with roughly 40 employees between them, but each one ran on its own spreadsheets and standalone tools rather than a shared system. No digital platform existed to measure that period precisely, so the "before" figures below are directional estimates built from the group's size and typical manual-process capacity at the time — not measured data. The "after" figures come from live platform activity, rounded and randomized within about ±10% to protect exact business detail.

The table above shows two endpoints. The chart below shows the path between them — a growth index by year (2023 = 100) for each metric, built from actual monthly platform activity for 2024–2026 and a directional estimate for the 2023 starting point.

Some of that growth is the business itself growing over the same period, not the platform alone — more employees naturally means more orders and more purchases. What the numbers do show clearly is that transaction volume scaled by roughly 6 to 12 times without a matching increase in administrative headcount, which only holds together because of the workflow and approval design covered above.

The result

Finance, project management, procurement, inventory, and field operations for the whole group now run on one connected platform instead of a patchwork of spreadsheets and side tools. Leadership gets a real-time, cross-company view of performance; project managers can see cost against budget while a job is still underway rather than after it closes; and approvals happen through a defined, auditable process instead of an email chain. The group also has a foundation — clean data, standardized processes, and integrated systems — that positions it for further automation and reporting as it continues to grow.