ColdEyes reviews permit packages.Staff keep the stamp.
Request access and you get a confirmation immediately.When a batch opens, you get an invite.After your jurisdiction is set up, the review loop runs without a vendor in the middle.No charge while you are evaluating.
ColdEyes is permit review for jurisdictions — cities, counties, and other AHJs.
Applicants and staff upload the same package.
ColdEyes drafts citation-backed findings, researches the adopted code behind each one, and notifies the person who can act.
Staff approve, deny, return, or issue.
We never take those actions automatically.
Request access once.Confirmation is immediate.An invite follows when a batch opens.
Why ColdEyes exists
Plan check is drowning in incomplete packages.
Examiners spend their best hours hunting missing sheets instead of exercising judgment.
Applicants wait without a status they can trust.
The usual answers are “replace the reviewer” or “chat with AI about the code.”
We refuse both.
The plan-reading work started as Estym8 for estimators.
Jurisdictions needed a different product that runs the review loop after setup, without a vendor in the middle.
We are building ColdEyes so every permit package gets a researched second look.
Humans take every official action.
Staff keep the stamp.
How ColdEyes works
Upload the package
A signed-in applicant or staff member uploads a package.Status becomes Submitted. Jurisdiction rules decide who may upload.Draft, research, and notify
ColdEyes checks the package against the jurisdiction checklist. It researches each draft finding against the adopted code edition.It notifies the right staff member or applicant.It never approves, denies, returns, or issues.Staff keep every decision
Staff approve, deny, return incomplete, edit findings, send to review, or record permit issued. Only humans change the official outcome.Applicants resubmit when asked.The loop keeps running
After staff act, the other side is notified. Once the jurisdiction is set up, that loop runs without a vendor in the middle.Sibling packages stay visible.The audit trail keeps drafts separate from human decisions.
Inside the workspace
Every package shows status, the next human action, and researched drafts. It is a queue, not a feed.
River Market TI — Suite 120
Riverbend · commercial TI · 2 researched drafts
Review draft findings on the sheets, then act — return, send to review, submit findings, deny, or record issued.
Egress path not dimensioned on A2.1
- Where
- Sheet A2.1 · Exit access travel path
- Measured
- Not shown
- Required
- IBC 2021 §1017.2
What ColdEyes does
Closed beta is for jurisdiction and firm design partners.This is the first-pilot loop.Upload, completeness, researched drafts, sheet overlays, staff actions, notify, and audit are already in the workspace.Comment library, parallel queues, deficiency export, and back-check land on that same first-pilot path.
- Applicants or staff upload once. The set lands where the work happens.
- Each draft finding is researched against the adopted code edition before anyone is notified.
- Staff review findings on the sheets in the in-app plan PDF.
- Status and the audit trail keep drafts separate from human decisions.
- After the jurisdiction is set up, that loop runs without a vendor in the middle.
- Pack improvements go live only when a jurisdiction admin promotes them.
- Humans own every outcome: approve, deny, return incomplete, edit findings, or issue.
What ColdEyes does not do
- ColdEyes never automatically approves, denies, returns, or issues.
- ColdEyes is not a replacement for the jurisdiction’s permit system of record.
- ColdEyes is not a workforce-reduction tool.
- ColdEyes does not promise miracle hour approvals.
- Clara assists. ColdEyes is the review workflow, not a zoning chatbot.
How to get access
Submit a request
Use your jurisdiction or firm email.
Get confirmation
It arrives as soon as you submit.
Wait for an invite
When a batch opens, we send a signup link.
Ask Clara to search and explain. She never takes the stamp.
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.
- BodiDiscoveryICT / 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.
- CheckSetDiscoveryDesign agency / A/E firm pre-issue QA — coordination flags, checklist completeness, city-style checks before seal or submit.
- FeasibilityDiscoveryArchitect / developer early site read — parcel, plat, and zoning toward a buildable envelope (working name).
Full portfolio map: suite docs.
Frequently asked questions
- What is ColdEyes?
- ColdEyes reviews permit packages for jurisdictions — cities, counties, and other AHJs.Signed-in applicants or staff upload a plan set.ColdEyes drafts citation-backed findings, researches the adopted code behind each one, and notifies the right people.It never auto-approves, auto-denies, auto-returns, or auto-issues a permit.Humans take every official action.Staff keep the stamp.
- Why are you building ColdEyes?
- Plan check is drowning in incomplete packages.Examiners spend their best hours hunting missing sheets instead of exercising judgment.Applicants wait without a status they can trust. We refuse the usual answers — replace the reviewer, or chat with AI about the code.ColdEyes exists so every package gets a researched second look.It drafts citation-backed findings and wakes the right person.Humans keep every official action.The plan-reading work started as Estym8 for estimators.Jurisdictions needed their own dual-sided, workflow-first product that runs after setup without a vendor in the middle.
- Does ColdEyes automatically approve or deny permits?
- No.ColdEyes drafts findings, researches each one, and notifies staff or applicants.Approve, deny, return incomplete, send to review, and record permit issued are always human actions.There is no automatic outcome path.
- Who keeps the stamp?
- Jurisdiction staff.ColdEyes helps reviewers catch incompletes sooner and work from clearer, researched drafts.It does not replace examiners.It does not stamp or issue permits on its own.
- Can jurisdiction staff review the plans in ColdEyes?
- Yes.Staff are notified when a researched draft is ready.They open the package in an in-app PDF viewer with finding overlays on the sheets.Overlays mark issues and citations, not device counts.Staff then take every official action: approve, deny, return, or issue.A jurisdiction comment library, parallel discipline queues, and resubmittal back-check are on the first-pilot path we are shipping with design partners.Humans still keep the stamp.
- What does “cold eyes” mean?
- A tireless second look with no prior context on the package.That is the same idea as a cold-eyes review in AEC practice.ColdEyes is named for that independent second look: draft findings without prior context.Staff still keep the stamp.
- Who can upload a permit package?
- Jurisdiction rules decide who may upload — owner, architect, design firm, GC, or staff.Both applicants and staff can be submitters when the jurisdiction opens that door.Accounts stay gated in closed beta.
- Does ColdEyes support phased or design-build permits (grading / dirt work first)?
- Yes.Large and design-build jobs often need more than one package on the same project.A grading or site (“dirt”) package can issue so earthwork can start while building plans are still in design or under review.Completeness, researched draft findings, status, and issuance are per package.ColdEyes does not invent a campus-wide “no work until every package is issued” rule unless the jurisdiction configures that.Staff still issue each package.ColdEyes never auto-issues.
- How does the ColdEyes review loop work?
- 1) Upload the package: A signed-in applicant or staff member uploads a package.Status becomes Submitted. Jurisdiction rules decide who may upload.2) Draft, research, and notify: ColdEyes checks the package against the jurisdiction checklist. It researches each draft finding against the adopted code edition.It notifies the right staff member or applicant.It never approves, denies, returns, or issues.3) Staff keep every decision: Staff approve, deny, return incomplete, edit findings, send to review, or record permit issued. Only humans change the official outcome.Applicants resubmit when asked. 4) The loop keeps running: After staff act, the other side is notified. Once the jurisdiction is set up, that loop runs without a vendor in the middle.Sibling packages stay visible.The audit trail keeps drafts separate from human decisions.
- What can Clara do?
- Clara is ColdEyes’s assistant.On the public site she explains the product, access, and workflow.Signed in, she can search and explain packages and findings.She never approves, denies, returns, or issues.That power stays with humans.
- Is ColdEyes just a chatbot for jurisdictions?
- No.ColdEyes is a review workflow: upload, researched draft, notify, humans act, status and audit trail.After setup, that loop runs without a vendor in the middle.Assistants help people find answers.They do not take official actions.Staff stay in charge of every outcome.Zoning or code Q&A tools are adjacent.They are not a substitute for package completeness and citation-backed plan review.
- Does ColdEyes learn from reviewers automatically?
- No silent learning.When staff catch something the draft missed, that can improve future drafts for that jurisdiction only after a jurisdiction admin (or ColdEyes with the AHJ’s approval) reviews and promotes the change.Live codes and checklists are never rewritten without humans.
- Will ColdEyes cut permit review to a couple of hours?
- We do not promise miracle hour SLAs.The honest win is fewer incomplete packages reaching examiners.Drafts are researched and citation-backed. Staff time is spent on judgment.Humans still approve, deny, return, or issue.
- Is ColdEyes the same as Estym8?
- No.ColdEyes is municipal / AHJ permit package review.Estym8 is a separate product — multi-trade takeoff and estimating for contractors and precon teams. Related technology.Different jobs and buyers.
- How do I get access to the closed beta?
- Request access at /coldeyes/request-access.You get an immediate confirmation.We review jurisdiction and firm requests with design partners and send an invite when a batch opens.There is no charge while you are evaluating.Staff accounts stay invite-only.
- Where can I read the product brief?
- The ColdEyes product brief is at /coldeyes/brief.For jurisdiction fit, notifications, or design-partner timing, use /coldeyes/contact.
- Does ColdEyes replace the jurisdiction’s permit system of record?
- No.ColdEyes accelerates the review layer — researched draft findings, notify, status, and audit.It is not a replacement for Accela, Tyler, or other systems of record.It does not auto-write official outcomes into those systems.
Request ColdEyes access
Request access if you want ColdEyes on every set.Confirmation comes first. An invite follows when a batch opens.
Access is by approval. Request access, then read the product brief anytime for the full workflow.