Sign in to the construction operating system.
Plan Intake & Bid Intelligence Pipeline — MVP Prototype
Select a project to open its workspace, or onboard a new one.
Set up the contractor of record once. This identity carries onto every project, contract, bid package, and document the system produces.
Legal entity details of record.
Primary place of business and points of contact.
Illinois has no statewide GC license — municipal registration governs. Track jurisdiction registrations here.
Coverage must be bound before any construction activity. Track carriers, policy numbers, and expirations.
Key people and the domains they own. The BRAIN routes approvals to these roles.
Onboard a project before plans are analyzed. This record defines the owner, site, commercials, design team, and document set the pipeline depends on.
What has been received for this project. Missing items become clarifications in the pipeline.
Upload the construction plan set. The engine reads every sheet, extracts scope by CSI division, builds a quantity takeoff, and produces a clarification log — the specific questions that must be answered before the budget is trusted.
Extracted from the plan set, organized by CSI MasterFormat division.
Combines documents flagged in project onboarding (Document Intake) with conflicts and missing specs found in the plan read (Deep Analysis). Answer each before bidding — this is what keeps the budget and bids accurate.
Each scope item maps to a CSI cost code. Quantities × unit costs build the baseline budget — the schedule of values. Adjust any unit cost to see the budget recompute live.
Baseline budget by CSI division. Editable unit costs.
For each trade, the engine projects what a subcontractor should bid — a low / expected / high range based on the budget and that trade's typical volatility. This is your benchmark before any real bid arrives.
Expected = budgeted cost for the trade. Range widens for higher-volatility trades (steel, glazing, sitework).
As real vendor bids arrive, enter them here. The engine levels each against the simulated "should-cost" and flags variances: a bid above range signals a scope gap or padding; below range signals a possibly missed scope.
Enter actual bids as vendors respond. Flags and totals update live. (Sample actuals pre-filled to demonstrate the leveling logic.)