Feasibility — product brief (discovery)
Product context: Estym8 is built from scratch as an AI-first construction preconstruction platform. This brief is a separate job head on the shared plan-reading spine — for architects / developers considering a site, not GC estimating and not municipal permitting.
Status: Discovery (suite map 2026-07; public stub 2026-08).
Working brand: Feasibility (ClearTo* family or TBD — confirm before registrar buy).
UX: Structured site / parcel workflow with AI assist — not a chatbot.
Related (public): suite map · ClearToPermit · ClearToIssue · AI-first positioning.
One-liner
Ingest parcel / plat / zoning and early site documents → surface a buildable-envelope style read (coverage, parking, variance likelihood themes) so designers and developers can decide whether a pursuit is worth schematic effort — with citations, not invented entitlements.
Job (and what it is not)
| This product does | This product does not |
|---|---|
| Early site / zoning / parcel intelligence for designers & developers | Produce a GC BOM or bid price |
| Flag entitlement and envelope themes with evidence | Replace a land-use attorney or planner stamp |
| Feed the same plan-reading spine used by ClearTo* later | Auto-approve permits or variances |
Success metric = time-to-go/no-go + trust (evidence quality), not F4c takeoff exactness.
Who buys / who uses
| Role | Need |
|---|---|
| Architect / design principal | Early feasibility before heavy design hours |
| Developer / owner’s rep | Chase vs pass on sites |
| ClearToPermit / ClearToIssue path | Shared public-data and rule habits later |
Shared spine vs separate head
Same pattern as municipal and A/E: share ingest / classify / sheet intelligence; swap buyer, workflow, and success metric. Detail: plan-intelligence-skus.
Sequencing
Discovery after ClearToPermit / ClearToIssue pilots clarify public-data and rule-pack paths. Not in the Estym8 raise budget as a separate GTM line.