Construction teams that run Odoo quickly hit the ceiling of the native Project and Sales apps. A project.project is a flat list of project.task records with no notion of a work breakdown structure, a bill of quantities, retention/retainage, or committed cost from purchase orders and subcontracts. Estimators build tenders in spreadsheets, foremen track progress on paper, and finance reconciles it all weeks later — so by the time you see a job is over budget, the concrete is already poured. Odoo core gives you timesheets and analytic accounting, but it does not give you the cost-code hierarchy, the budget-vs-committed-vs-actual view, or the progress-based invoicing that a builder actually manages by.

Construction Builder is a module ECOSIRE designs and writes for exactly that gap. We add a construction job layer on top of project.project — a hierarchical WBS/cost-code tree (models.Model with a parent_id self-relation and stored @api.depends compute fields that roll up budgeted, committed, and actual amounts), a bill-of-quantities model linked to your product catalog, and subcontract records that create and track purchase.order commitments against each cost code. Every labour timesheet, material PO, and subcontractor bill posts to the right analytic account and rolls up the tree, so the over/under-budget number is live, not a month-end surprise. Progress billing is driven by percent-complete or measured quantities and generates draft account.move customer invoices with retention withheld automatically, plus QWeb PDF reports for the payment application, cost-value reconciliation, and subcontract status.

Technically it is a clean, upgrade-safe addon: its own __manifest__.py declaring dependencies on project, account, and purchase; new models and inherited views (XML, with OWL components where an interactive planning board earns it); ir.model.access.csv plus record rules so a site foreman sees only their assigned jobs while a commercial manager sees the whole portfolio; and automated actions/scheduled crons for budget-breach alerts and retention-release reminders. Everything it exposes to project, purchase, and account is reachable over the standard XML-RPC/JSON-RPC API, so your BI tool or field app can read the same live cost picture. We build for your target — Odoo 17.0, 18.0, or 19.0 — and handle the Community vs. Enterprise differences (for example, wiring to Enterprise Accounting and Field Service where you have them, or providing Community-safe equivalents where you do not).

Because this is build-to-order, nothing ships until we agree scope. A short scoping call maps your cost-code structure, billing rules, and approval flows to concrete models and views; we then build on a staging instance, run UAT with your team against your real data, and cut over with a rollback plan. Typical delivery is one working week from confirmed scope, depending on complexity and integration count. Pricing starts from $999 (indicative, single-company base scope); multi-company consolidation, retention and tax localization depth, extra integrations (field apps, BI, payroll), and the volume of legacy job data to migrate increase the quoted scope. You get the full installable source, a git repo handover, and a support window after go-live.