Planning pipeline
Nine dependent stages ending in Ready to Build, with a lock and a baseline.
The product
Everything below runs on the same data. That is the whole design — there is no integration layer between estimating and the store, because there are not two systems to integrate.
The rest of the product is listed below. These five are where most of the day goes.
Twelve modules, one login, one set of numbers. Roles decide who sees which of them.
Nine dependent stages ending in Ready to Build, with a lock and a baseline.
Measurement rows with deductions; a typical floor measured once and multiplied.
Rates built from resources at effective-dated prices, never typed into a cell.
Magic-link bidding with a one-time code and a scope frozen at invite.
Work packages generated from the priced BOQ, nested to any depth.
Durations from quantity and output, dependencies with lag, calendars and baselines.
One RFQ, many vendors, one accepted quote, and an order generated from it.
Gate receipts, issues to an activity, reconciliation, and transfers between sites.
Revisions with review states and pin-point mark-ups on a specific version.
Daily progress, labour, plant, quality and safety, with geo-stamped photos.
Enquiry to booking, against unit inventory that cannot be sold twice.
Plotted layouts, plots and buyers for the land side of the business.
A working session with your BOQ, your programme and your vendors — not a slide deck.
Build smarter.Execute faster.Deliver better.