Sources become the BOD.You still decide.
Request access and you get a confirmation immediately.When a pilot batch opens, you get an invite.No payment until you choose a plan.
ICT and LV jobs still leave the firm with emails, meeting notes, and unmarked drawings no one can defend.
The usual answers are another spreadsheet or “chat with AI about the scope.”
We refuse both.
Bodi walks sources like a project brain: intake, claims, evidence, then you confirm the BOD.
Request access once.Confirmation is immediate.An invite follows when a batch opens.
Why Bodi exists
ICT and LV jobs still drown in emails, meeting notes, and unmarked drawings.
Reviewers spend their best hours hunting sources instead of judging the design.
The usual answers are “another spreadsheet” or “chat with AI about the scope.”
We refuse both.
Bodi turns sources into claims, then a Basis of Design you can defend.
You still decide.
How Bodi works
Drop the sources
Upload emails, transcripts, client standards, schedules, and PDFs.Bodi classifies each file as a source.Extract claims
Requirements, constraints, assumptions, and decisions land in a claim log with lineage back to the source.You still decide
Confirm, dismiss, or add claims. Draft the Basis of Design.You still own what leaves the firm.The loop keeps running
Later sources update the claim graph.No restart from a blank spreadsheet.
Inside the workspace
Every project shows status and the next human action. It is a queue, not a feed. Sample only — not a live case.
Campus LV — BOD draft
Security · AV · cabling
Open the claim log and confirm sources before the BOD leaves. You still own the claim.
What Bodi does
Closed pilot is for ICT / low-voltage teams. Deeper email-native ingest stays on the horizon — not in this list.
- Drop emails, transcripts, standards, schedules, and PDFs as sources once. Bodi classifies each file.
- Extract claims with lineage back to the source — requirement, constraint, assumption, decision.
- Cover security, AV, cabling, and Wi-Fi scopes in one claim graph.
- Draft a Basis of Design from confirmed claims, not from a chat transcript.
- Accept an Estym8 plan-intelligence export as a source. Bodi never overwrites Estym8 counts.
- Export the BOD for owner or GC review with the claim trail attached.
- You still review, confirm, and issue the BOD. The claim stays human.
What Bodi does not do
- Bodi is not a replacement for the ICT designer of record.
- Bodi does not auto-issue a Basis of Design.
- Bodi is not a takeoff or bid-estimate product — that is Estym8.
- Bodi is not municipal plan check — that is ColdEyes.
- Bodi is not A/E pre-issue QA — that is PlanM8.
- Bodi is the sources-to-BOD workflow, not a chatbot SKU.
How to get access
Submit a request
Use your work email.Get confirmation
It arrives as soon as you submit.Wait for an invite
When a batch opens, we send a signup link.
Bodi is the sources-to-BOD workflow. It is not a chatbot and it does not own the claim.
One spine.Multiple products.
The same AI-first plan-reading engine powers distinct products for different buyers — takeoff, municipal review, design QA, ICT/BOD, and feasibility.Each is its own product with AI assist inside the workflow.
- GC / estimator takeoff and estimate from plan sets and bid folders — including ROM/WAG screening and full bid-grade depth on the same spine.
- ICT / low-voltage project brain → Basis of Design — sources and claims for security, AV, cabling, and Wi‑Fi scopes.
- Permit package review for jurisdictions.ColdEyes researches each draft finding and notifies staff or applicants.Humans approve, deny, or issue.Staff keep the stamp.
- Design agency / A/E firm pre-issue QA — coordination flags, checklist completeness, city-style checks before seal or submit.
- Architect / developer early site read — parcel, plat, and zoning toward a buildable envelope.
Full portfolio map: suite docs.
Issue a defendable BOD
Closed pilot for ICT and LV teams who refuse another all-nighter on the claim trail.Request access — confirmation first, invite when a batch opens.