Sales and pricing

Construction Estimating & Bid Intelligence

Quantity takeoff from drawing PDFs, coordination checks before bid, a win probability for each bid or no-bid decision, and schedule-delay risk from past schedules. Automatic Quoting sets the price.

The problem

Estimators spend most of their time measuring drawings rather than judging the job. Coordination errors found after award become costly changes, and the team bids on work it is unlikely to win while passing on work it could.

Who owns it

The head of estimating or preconstruction, with operations for schedule risk.

What it learns from

  • Drawing sets and specifications
  • Past takeoffs and estimates
  • Bid history, won and lost
  • Delivered cost and margin on past projects
  • Past project schedules

How it works

Predict, decide, act, measure

The same four steps in every solution, in this order, each one visible to the team that owns it.

  1. 01

    Takes off quantities, finds errors, and predicts the outcome

    Models read drawing PDFs to take off quantities and flag coordination conflicts between disciplines. Win probability is predicted for each opportunity, and schedule-delay risk is predicted from past schedules.

  2. 02

    Decides bid or no-bid through a policy

    Bid or no-bid follows win probability, capacity, and margin targets your team sets. Takeoffs below a confidence threshold go to an estimator to check, and the price is set by Automatic Quoting.

  3. 03

    Acts in the estimating workflow

    Quantities, flagged conflicts, and the bid recommendation land in the estimating tool your team already uses, with every quantity traced to its place on the drawing.

  4. 04

    Measures against the current process

    Hours per takeoff, bids per estimator, win rate, and margin on won work are compared with the current process, with a phased rollout by estimator or project type.

What it moves

The business levers

Estimator capacity

Fewer hours per takeoff and more bids per estimator.

Win rate

Effort on the bids most likely to be won.

Margin on won work

Errors caught before bid rather than after award.

Schedule risk

Delay risk visible before commitment.

Proof

How the return is proven

The return is the added estimating capacity, win rate, and margin on won work against the current process, stated against the return model agreed up front. Takeoff accuracy, checked against estimator review, is reported beside it.

What you see: the ROI readout

Every solution produces the same readout, assembled from the system's own records rather than built by hand.

Correctness

The checks the pipeline passed on your own data: leakage, point-in-time, and entity resolution.

Incrementality

The incremental effect against the holdout or equivalent design, with its confidence interval.

Return

The measured return against the investment, set beside the return model agreed before work started.

Guardrails

Complaints, cost, margin, fairness, and contact limits, each shown against its bounds.

Audit extract

Every score, action, and outcome, with the model and policy versions behind it.

Governance

What is governed

Access, approvals, and the audit trail are part of the solution, not a review step added at the end.

Identity-scoped access

Drawings, estimates, and bid history are visible by role through your single sign-on.

Approval gates

Every bid submitted and every no-bid decision is approved by an estimator or the estimating head.

Audit trail

Every quantity, flag, and recommendation is logged and traceable to its source drawing.

Explainable drivers

Win probability and delay risk carry the drivers behind them.

Why it holds up

Trained on your data, framed by the outcome

This solution trains models on your own data, checks every stage from data to decision, and is measured against the outcome it was built for. Because its predictive power is measured, it also shows the drivers behind the metric, so your team can fix causes as well as act on scores.

Why solutions hold up

Start with one decision

Bring the problem and the systems your team works in. We scope the first solution with you, agree how its return will be measured, and run it in production with your people.