Construction firms running Odoo quickly hit a wall: the core Project and Sales apps track tasks and quotations, but they don't understand a construction job the way a project manager does. There's no native concept of a job budget broken down by cost category, no committed-vs-actual cost view that pulls purchase orders and vendor bills against a Bill of Quantities, and no progress billing that invoices a percentage of completion instead of a flat milestone. Teams end up managing budgets, retentions, subcontractor commitments, and variation orders in spreadsheets that drift out of sync with the ledger — and finance can't answer "are we over budget on this site?" without a manual reconciliation.

Construction Developer is a made-to-order Odoo module that ECOSIRE builds around your workflow to close that gap. At its core is a construction.job model (extending or linking project.project) with child construction.budget.line records categorized by cost type — labour, materials, plant, subcontract, preliminaries. Committed cost is computed with @api.depends from linked purchase orders and vendor bills; actual cost rolls up from analytic lines on the job's account.analytic.account; and a stored compute exposes budget, committed, actual, and variance side by side. Progress billing is driven by a construction.progress.claim model that reads percentage-complete per line and generates a draft account.move (customer invoice), optionally withholding a configurable retention percentage into a separate account. Subcontractor work orders, variation/change orders with an approval flow via base.automation, and material requisitions are all first-class records.

Technically it ships as a proper Odoo addon: a clean __manifest__.py declaring dependencies (project, account, purchase, analytic), access rights in ir.model.access.csv, and record rules so a site manager only sees their own jobs while finance sees all. The UI is delivered as XML views — a job form with budget, cost, billing, and subcontractor tabs, a cost-control list with variance decoration, and an OWL dashboard component for the portfolio roll-up. Costed QWeb reports render the job cost sheet and progress claim as branded PDFs, and everything is reachable over the standard XML-RPC/JSON-RPC API so your BI or field apps can read job status. We build against your target — Odoo 17.0, 18.0, or 19.0 — and account for Community vs Enterprise (for example, using the Enterprise accounting/analytic features where you have them, or building equivalent behaviour on Community).

Delivery is build-to-order, not an instant download. After a short scoping call we confirm the exact models, billing rules, and reports you need, then build and demonstrate the module on a staging instance for your sign-off before it touches production. Typical delivery is one working week from confirmed scope, depending on complexity and how many of your existing customizations we integrate with. Pricing starts from $999 (indicative, single-company base scope); multi-company or multi-site consolidation, deeper accounting localization, and migration of historical job/budget data increase the quoted scope. You receive a fixed quote after the scoping call — the from-price is a starting point, never a final number.