Cold eyes that never blink — you keep the stamp

Request accessProduct brief

Request access and we’ll confirm immediately. We review jurisdiction and firm requests with design partners, then send an invite when a batch opens — no charge while you’re evaluating.

Cold-eyes plan review for jurisdictions — cities, counties, and other AHJs — that refuse to drown in incomplete sets, and for the applicants who submit to them.

One upload. Applicant or staff. ColdEyes runs a tireless second look, drafts citation-backed findings, and wakes the right person. No re-import chore.

Staff approve, deny, return, or issue. Applicants resubmit when asked. We never act automatically — we make reviewers sharper and cut incomplete cycles so judgment time goes further.

Closed beta is open for jurisdiction and firm design partners. Request access — get in the next batch.

The loop

  1. 1

    Drop the set

    A signed-in applicant or staff member uploads a package — TI, grading / site, foundation, building, or the next phase on a large job. Status snaps to Submitted. Jurisdiction rules decide who may upload — owner, architect, firm, or GC.

  2. 2

    Cold-eyes draft + notify

    ColdEyes checks the package against that checklist, drafts citation-backed findings, and notifies the right staff member or applicant. No automatic approve, deny, return, or issue.

  3. 3

    Staff keep every decision

    Staff approve, deny, return incomplete (with reason), edit findings, send to review, or record permit issued — per package. On design-build jobs, that can mean issuing grading so site work can start while the building package is still in review. Applicants resubmit when asked. Only humans change the official outcome.

  4. 4

    Both sides stay sharp

    After staff act, the other side is notified (email + in-app). Sibling packages on the same project stay visible with their own status. The audit trail keeps system drafts separate from human decisions — clean and unmistakable.

What you unlock

  • Direct upload by applicant or staff — the set lands once, where the work happens
  • Cold-eyes draft review with citation-backed findings — then notify the person who can act
  • Staff review on the sheets — in-app plan PDF with finding overlays (Estym8-style verification path for issues and citations)
  • Jurisdiction comment library, typed findings, and parallel discipline queues — built for how plan check actually runs
  • Humans own every outcome: approve, deny, return incomplete, edit findings, issue
  • One consolidated deficiency package back to the applicant — plus resubmittal back-check with per-finding resolution
  • Phased and design-build ready — grading / site, foundation, shell, or building as separate packages under one project; issue early work when staff say so
  • Status you can trust — and an audit trail that keeps drafts away from human decisions
  • Alerts when drafts are ready and when a human moves the package
  • Pack improvements only when a jurisdiction admin promotes them — no silent learning into live rules

Hard lines

  • Never automatically approve, deny, return, or issue — we draft and notify; humans act
  • Not a replacement for the jurisdiction’s permit system of record — we accelerate the review layer
  • Not a workforce-reduction tool — we make reviewers more efficient and better at the job
  • Not a miracle “hours to approve” promise — we cut incomplete cycles and sharpen drafts so staff spend time on judgment
  • Not a zoning-code chatbot SKU — Clara assists; ColdEyes is the dual-sided review workflow

What happens next

  • Request access with your jurisdiction or firm email — confirmation lands instantly; invite when you’re approved.
  • Staff accounts stay invite-only. Applicant signup opens only when a jurisdiction says so.
  • Inside the product: upload → cold-eyes draft + notify → staff act → status updates. No automatic outcomes. Ever.
  • Ask Clara anytime — she searches and explains. Signed in, she digs into your packages and findings. She never takes the stamp. That power stays yours.

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.

  • Estym8Closed betaBrief

    GC / estimator takeoff and estimate from plan sets and bid folders — including ROM/WAG screening and full bid-grade depth on the same spine.

  • BodiDiscovery

    ICT / low-voltage project brain → Basis of Design — sources and claims for security, AV, cabling, and Wi‑Fi scopes.

  • ColdEyesClosed betaBrief

    Cold eyes that never blink for city / AHJ permit review — dual-sided upload, draft, notify; humans approve/deny/issue; you keep the stamp.

  • CheckSetDiscovery

    Design agency / A/E firm pre-issue QA — coordination flags, checklist completeness, city-style checks before seal or submit.

  • FeasibilityDiscovery

    Architect / 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 is cold-eyes permit package review for jurisdictions — cities, counties, and other AHJs. Signed-in applicants or staff upload a plan set; ColdEyes drafts citation-backed findings 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.
Does ColdEyes automatically approve or deny permits?
No. ColdEyes drafts findings 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 drafts — it does not replace examiners, and it does not stamp or issue permits on its own.
Can jurisdiction staff review the plans in ColdEyes?
Yes. Staff are notified when a cold-eyes draft is ready, open the package in an in-app PDF viewer with finding overlays on the sheets (pins / markup for draft and staff findings — the same idea as Estym8’s drawing verification overlays, showing issues and citations rather than device counts), work from discipline queues and the jurisdiction’s comment library, then take every official action (approve, deny, return, issue). Resubmittal back-check with per-finding resolution is part of the same initial deliverable. Humans still keep the stamp.
What does “cold eyes” mean?
A tireless second look with no prior context on the package — the same idea as a cold-eyes review in AEC practice. That independent second look is what ColdEyes is named for: 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 — for example a grading or site (“dirt”) package issued so earthwork can start while building plans are still in design or under review, or foundation-only then full building. Completeness, 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) Drop the set: A signed-in applicant or staff member uploads a package — TI, grading / site, foundation, building, or the next phase on a large job. Status snaps to Submitted. Jurisdiction rules decide who may upload — owner, architect, firm, or GC. 2) Cold-eyes draft + notify: ColdEyes checks the package against that checklist, drafts citation-backed findings, and notifies the right staff member or applicant. No automatic approve, deny, return, or issue. 3) Staff keep every decision: Staff approve, deny, return incomplete (with reason), edit findings, send to review, or record permit issued — per package. On design-build jobs, that can mean issuing grading so site work can start while the building package is still in review. Applicants resubmit when asked. Only humans change the official outcome. 4) Both sides stay sharp: After staff act, the other side is notified (email + in-app). Sibling packages on the same project stay visible with their own status. The audit trail keeps system drafts separate from human decisions — clean and unmistakable.
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 → cold-eyes draft + notify → humans act → status and audit trail. 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, clearer citation-backed drafts, and staff time spent on judgment — with humans still approving, denying, returning, or issuing.
Is ColdEyes the same as Estym8?
No. ColdEyes is municipal / AHJ cold-eyes permit 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’ll get an immediate confirmation. We review jurisdiction and firm requests with design partners and send an invite when a batch opens — no charge while you’re 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 — draft findings, notify, status, and audit. It is not a replacement for Accela, Tyler, or other systems of record, and it does not auto-write official outcomes into those systems.

Bring cold eyes to the queue

Closed beta for jurisdiction design partners and authorized applicants who want cold eyes on every set — and a queue that finally feels under control. Request access — confirmation first, invite when a batch opens.

Access is by approval — request access, then read the product brief anytime for the full workflow.

Request accessProduct brief