Similar language.
Different obligations.
“Startup balancing” does not establish independent certified TAB coverage. A matching phrase is not enough.
PRECONSTRUCTION SCOPE INTELLIGENCE
Know what
your bid carries.
Messy subcontractor proposals. Source-linked scope intelligence. Your existing bid tab.
We’re building a review layer for commercial general contractors: reconcile MEP scope, expose unresolved obligations, and keep the evidence behind every comparison.
Walk through a bid packageEarly-stage concept · Synthetic demonstration · No live AI processing
M23 / HVACReview required
Lowest submitted price$475,000Contractor C · revised proposal
01
Controls added. BMS still excluded.
The revised price changes one obligation.
The earlier qualifications still apply.
“BMS gateway and tie-in to the existing system remain by others.”C-02 · C2-1 · Current revision
Unresolved ≠ $0Estimator decision pending
THE PROBLEM
A clean spreadsheet can hide
an incomplete scope.
Similar language.
A new price does not
erase an old exclusion.
Revisions and clarification emails can change just part of a proposal. Review must preserve what still applies.
The cheapest number
may be incomplete.
Priced adjustments belong in the comparison. Unpriced scope belongs in a visible decision queue.
THE PROPOSED WORKFLOW
From proposal to a reviewable decision.
Establish the baseline
Bring proposals, addenda and an estimator-approved scope checklist.
Reconcile the scope
Interpret exclusions, allowances and conflicting revisions against that baseline.
Resolve exceptions
Inspect the source. Own the adjustment. Request the missing clarification.
Keep your bid tab
Return reviewed values and open issues to mapped Excel cells.
PRODUCT CONCEPT / FIVE VIEWS
One package. Every decision in context.
Explore a hand-authored expected result for a fictional office renovation. This interface demonstrates the intended workflow; it does not call Claude or accept real project files.
Harbor Point / M23 / Review workspaceConcept
WHY CLAUDE
Reason across the documents.
Keep arithmetic in code.
Claude is the planned reasoning layer, not a chat box attached to a spreadsheet. It will connect differently worded scope statements, interpret qualifications, flag ambiguity and draft focused clarification questions.
Application code validates references and calculates adjustments. Estimators approve material decisions. Model quality will be measured on held-out bid packages before production use.
CLAUDE / PLANNED
Document reasoning · scope normalization
Qualification interpretation · clarification drafts
DETERMINISTIC CODE
Currency and arithmetic · schema validation
Source lookup · controlled Excel mapping
ESTIMATOR
Baseline approval · adjustment acceptance
Risk ownership · award decision
WHO WE ARE BUILDING FOR
Commercial GC preconstruction teams
that still make decisions in Excel.
Our initial focus is U.S. mid-market general contractors reviewing mechanical packages for occupied office renovations. The proposed entry point is unresolved scope and revision conflicts before bid submission—not a replacement procurement network.
TRUST BY DESIGN / PLANNED CONTROLS
Show the basis. Preserve the unknowns.
Evidence beside the claim
Document version, page or cell, exact supporting text and the applicable baseline requirement. Source presence is not proof that the interpretation is correct.
Human-owned decisions
No silent scope plugs. Proposed adjustments, remaining uncertainty and estimator changes stay separate. No autonomous awards or supplier messages.
Controlled customer data
Production requirements include tenant isolation, access controls, retention settings and auditable changes. These are design requirements, not implemented certifications.
PRODUCT VISION
A connected record of
what was promised.
Start with bid review. Expand toward a traceable chain from requirement to proposal, clarification, award scope and later change. Build useful institutional memory around reviewed obligations—not another disconnected cost database.
Download the concept brief