Construction: every job site's margin, in one question.
How a contractor went from 2 to 3 days of analysis to one question asked in French, starting from systems that didn't talk to each other.
Knowing whether a job site makes money, while there is still time to act.
The problem
The contractor could not analyze the profitability of its job sites while they were under way. Costs, hours and project documents were spread across several systems, and the ERP had no API.
To know whether a job site was making money, an analyst exported the data and reconciled it in Excel. Each answer took 2 to 3 days, often too late to correct course.
We connected its source systems, including the ERP with no API, and keep them in sync in one place. The team keeps its current tools.
- Autodesk (projects and documents)
- QuickBooks (accounting)
- Construction ERP (no API)
- Timesheets
The same job site had a different name in each system. We reconciled it, then wrote with the team what the terms that matter mean. Actual margin is now compared with planned margin, job site by job site.
- Job site
- Committed cost
- Labour
- Change order
- Planned margin
- Actual margin
On top of that context, we delivered the tools project managers use every day.
- Smart dashboards → Actual and planned margin, labour and change orders, by job site. Questions are asked in plain French.
- Access from AI tools → An MCP server that gives the team's AI assistant the same numbers and the same access rights.
- Alerts → A notice when labour exceeds a job site's budget or a signed change order is not yet invoiced.
Results
Project managers check the actual margin of their job sites without waiting for an export and a manual analysis.
- Before2 to 3 days of analysis to get a job site's margin
- Todayone question asked in French
- 21people checking these numbers
Tell us about your job sites.
Tell us which number you need on your job sites and which systems it lives in. We'll start with that one.