Halozen runs the project.
Not just the bid.
Most teams meet Halozen at the bid. Then we don't leave. One fleet of specialized agents, one shared obligation register, one reasoning ledger. From first spec read to final retention check.
Specialized agents. One project brain.
Each agent does one job well. Every agent reads from the same obligation register. Every decision lands in the same reasoning ledger. No siloed tools, no copy-paste between products.
What your team actually opens.
A sample of what the Risk Register and Obligation Matrix look like for a real hospital expansion bid. Switch tabs to see the extraction layer (what the spec requires) vs. the assessment layer (what could hurt you). Click any row to drill into the source clause and reasoning trail.
- Builder's Risk all-risk policy w/ $50K deductibleFinancialCOVERED5/54/5R-01FinancialCOVERED$151KI·5L·4$151K
- Sub bond threshold dropped to $250K (Add. 03)FinancialSCOPE GAP4/54/5R-02FinancialSCOPE GAP+$140KI·4L·4+$140K
- LDs $7,500/day from substantial completionFinancialCOVERED5/53/5R-03FinancialCOVERED$7,500/dI·5L·3$7,500/d
- Imaging-suite vibration limits during demoRegulatorySCOPE GAP4/53/5R-04RegulatorySCOPE GAP+$92KI·4L·3+$92K
- Hospital ops shutdown coordination, 14-day noticeScheduleCOVERED3/52/5R-05ScheduleCOVERED$0–$35KI·3L·2$0–$35K
- Final retention release after as-built + O&MFinancialCOVERED2/52/5R-06FinancialCOVERED$18KI·2L·2$18K
From spec read to final retention check.
Every agent shares one source of truth.
A point tool reads the spec once. Halozen reads it once and keeps reading it for the life of the project. Every agent below pulls from the same three foundations.
Obligation Register
Every clause from every spec, addendum, and SC. Cited. Versioned. Read by every agent.
Reasoning Ledger
Every decision, exclusion, qualification, and risk acceptance. Deterministic citation. Survives change-orders.
Institutional Memory
Your firm's history. How you handled risk on past projects. Compounds with every bid.
┌─────────────────────────────────────────────────────────┐
│ 7 SPECIALIZED AGENTS (Bid Desk, Matrix, JHA, ...) │
└────────────────────────┬────────────────────────────────┘
│ read / write
┌────────────────────────▼────────────────────────────────┐
│ L-01 OBLIGATION REGISTER ── every spec clause │
│ L-02 REASONING LEDGER ── every decision │
│ L-03 INSTITUTIONAL MEMORY ── your firm's history │
└─────────────────────────────────────────────────────────┘No copy-paste between products. No data silo per agent. When the JHA Studio asks “is fire alarm tie-in covered?”, it reads the same answer Bid Desk wrote. When Bid Assist cites a decision, it cites the same Reasoning Ledger node Project Controls is auditing.
Halozen isn't fixed. It's a substrate.
Enterprise customers commission custom agents that share the same obligation register and reasoning ledger as the rest of the fleet. Insurance compliance, owner-specific reporting, BIM cross-checks, regional code variants. If it reads from the project, we'll build it.
Scoping call
What does the agent read? What does it produce? What workflow does it slot into?
Calibration
Train against your firm's institutional memory. Review against your obligation register.
Pilot
Run on one active project. Output reviewed against your existing process.
Production
Promotes to your fleet. Citation precision, version control, full audit trail.
Pick your way in.
Start at the bid
Bring a real spec from a bid you're chasing. We run it through Halozen and email back a Live Risk Register. Every clause cited. Every risk scored. 48 hours. No charge.
Deploy the fleet
For GCs evaluating a multi-project rollout. We deploy inside your VPN or Azure environment, scope custom agents, and run a structured pilot before any commitment.
Talk to DeploymentMost teams meet Halozen at the bid. Then they don't leave. Same register, same ledger, same memory through buyout, build, and closeout.