Stress-test the project before the project becomes expensive.
ExpenseIntel tests a place and a plan together. It looks for utility uncertainty, fragile assumptions, approval bottlenecks, missing evidence, hard-to-reverse commitments and real-world failure patterns—then tells you exactly what to verify next.
Builder lens: sequence the work before the work sequences you.
The underlying model stays the same. The lens changes which decisions, evidence and actions are emphasized.
Describe the project like you would describe it to a person.
ExpenseIntel translates the narrative into editable project signals—use, area, timing, utility needs, risk triggers and planned interventions. Nothing detected from the narrative becomes a verified fact; you confirm the controls before the model runs.
Describe the place and the plan once.
Every system below uses the same fingerprint. Address data is verified where possible. Utility capacity is never assumed: if you do not provide known service data, ExpenseIntel leaves capacity unresolved instead of fabricating an answer.
Sequence approvals, utilities, scope and irreversible releases before construction hardens.
Switch Builder / Buyer above at any time. The core project scoring remains the same; actions and evidence priorities change.
Can the site support what the project wants?
ExpenseIntel separates modeled demand pressure from known capacity. A utility with no verified service rating stays unresolved. That distinction is the point.
How many things have to go right?
Fragility is a screening measure of dependency, uncertainty, schedule pressure and capital lock-in.
—
Where does friction concentrate?
Radar scores identify where verification effort should concentrate; they do not predict municipal approval time.
Which decisions destroy optionality?
The expensive mistake is not always spending too much. Sometimes it is committing to a change that is costly to reverse before the project has cleared its real constraints.
but flexible
capital
moves
choices
How much of this answer is actually proven?
A strong score with weak evidence is still a weak decision. Evidence Depth separates verified/project-specific proof from public signals, user-supplied facts and screening assumptions—and shows exactly what would strengthen the record.
The project is still assumption-heavy.
Mark an item only when you have a real document, written agency/utility response, inspection, plan review, quote or responsibility record behind it. The checklist is intentionally stricter than “someone told me.”
Which failure patterns does this project resemble?
Pattern matching remains a screen—not a probability. The new source layer begins connecting those patterns to public primary-source project records involving denial, expired entitlements, delayed construction and approval-path friction.
Real records behind the pattern library.
Loading official public records. The seed library is intentionally small and source-first; it can grow into a national corpus without pretending a handful of cases are statistics.
Do not end with “verify this.” Tell me exactly how.
Every major risk should terminate in an executable move: who owns the answer, what to ask, and what document or response actually closes the issue.
Does the exact same project survive better somewhere else?
Hold proposed use, area, timeline, contingency, triggers and interventions constant. Change the site and compare fragility, unresolved utility evidence, top bottleneck, reversibility and modeled operating cost—not price alone.
—
—
Turn the project from a one-time score into a living record.
Project Watch stores the project and scored snapshots in this browser. Re-run after adding evidence—or when returned public signals change—and save again to see what actually moved.
A project should get harder to misunderstand every time new evidence arrives.Describe → verify → stress → compare → act → save → re-score