From Construction Brief to Priced Budget with an AI Agent

A construction estimate usually begins with an incomplete description: "reform a 15 m² kitchen," "replace the flooring in a flat," or "price a façade repair." The hard part is not writing the first line item. The hard part is turning that brief into a budget structure that can be checked, updated, and defended.

How does an AI agent turn a brief into a budget tree?

Omnicost approaches this as an agentic budget system. The agent reads the brief, creates chapters and subchapters, proposes measurable line items, assigns units, estimates quantities, and links each item to catalog data when a market match is available.

The output is a budget tree, not a chat transcript. A kitchen reform might break into demolition, masonry, plumbing, electrical, finishes, cabinetry, appliances, labour, overhead, and contingency. Each leaf row carries a unit, a quantity, a unit price, and a total — so the estimate can move into execution instead of staying as paragraphs of text.

That structure matters because it mirrors how professionals already work: in the BC3/FIEBDC-3 world, a budget is a tree of chapters → items → resources. Producing that shape directly means the result drops into the rest of the workflow — exports, comparisons, revisions — instead of needing to be retyped.

Why is auditability the whole point?

The key design choice is that a generated estimate must show its sources. For each row it should be clear what the agent created, what was priced from catalog evidence, and what is still a placeholder. If the catalog doesn't have enough data for a line, the system marks the gap rather than pretending the number came from the market.

This is what lets contractors and architects use AI without surrendering control. A confident-but-wrong number is worse than a labelled assumption, because someone has to stand behind the total when the client pushes back.

How do you keep the human in control?

A draft is a starting point, not a verdict. From the first pass, a user can:

• ask the agent to fill missing prices from the catalog,
• add a themed section ("add waterproofing for the wet areas"),
• scale the total toward a target budget,
• or clean up empty wrappers and merge duplicate rows.

The budget stays editable at every step, and every change is visible — so the estimate remains the team's, not the model's.

Who does it help?

For small teams, this removes the blank-page cost of estimating — the slow, error-prone first draft that eats an afternoon. For larger teams, it creates a consistent first pass that can be reviewed, benchmarked against live prices, and improved as catalog coverage grows. In both cases the goal is the same: get from a vague brief to a defendable number faster, without trading away the ability to explain it.