Every estimate checked before the client sees it.
Stuckan afternoon of copy-paste
Where it was stuck
Estimators read 30+ page PDF scopes line by line, built estimates against strict client margin rules and checked hundreds of rows by eye, then re-keyed everything into six locked client Excel formats. All inside a 5-day window from scope to quote. One missed line meant eating the cost on site.
What we built
We embedded with the team as a forward-deployed AI engineer and built a pre-estimate review agent. It catches zero-quantity lines, margin leakage and typo-class errors before anything reaches the client.
What changed
- Every estimate is checked before it reaches the client.
- The rules engine improves itself: every reviewer correction adds a new check.
- It runs on a client-owned, open-source stack on Australian infrastructure.
- 01
A scope becomes an estimate
Estimators build it from a 30+ page PDF scope, against the client’s margin rules.
- 02
The agent reviews it
It flags zero-quantity lines, margin leakage and typo-class errors before anything reaches the client.
- 03Person in the loop
An estimator decides
Nothing reaches the client unreviewed. Every correction becomes a new check the agent writes into its own rules.
- 04
One step to the client’s forms
The six locked client Excel bid forms are generated from the estimate, byte-perfect.