Company profile · 4 min read
AutoSitu: Cited project intelligence from feasibility to construction
AutoSitu connects site feasibility, jurisdiction research, plan review, code compliance, quantities and construction scope for built-world projects.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
AutoSitu is building an AI operating layer for the built world, from site feasibility and entitlement through design review, code compliance, quantities and construction scope. It fits developers, planning firms, cities and AEC teams that lose time rebuilding the same jurisdiction and project context across every review.
What it does
AutoSitu’s current site follows one project from parcel understanding to construction. It turns boundaries, zoning, setbacks, easements and utilities into structured constraints, then carries that context into feasibility, entitlement, design review, QA/QC, code checks, quantity takeoff and scope analysis. The planning-firm workflow adds precedent research, hearing records, zoning scenarios and cited site-plan findings.
The source trail is part of the product. AutoSitu says findings cite the page and sheet they came from and can draw a bounding box around the relevant part of a plan. That makes the system more useful to a professional who needs to review, correct and defend an answer than to a buyer who only wants an AI-generated summary.
The public homepage reports more than 25,000 developments analyzed, $18B in development value evaluated, 8.7M requirements checked and 420,000 design, coordination and compliance issues identified. The YC launch also reports 50–70% fewer city comments, resubmittals moving from 2–3 to 0–1 and approvals shortened by 3–6 months or more. These are company-reported operating and outcome claims, not independent measurements. The right pilot is one known project and one jurisdiction where the team can compare findings with human review.
Founder context and tradeoffs
The YC profile identifies Xuanshu (Asher) Lin as CEO, with urban-planning and architecture training and hands-on work across public and private projects, and George Zhai as CTO, with Georgia Tech and autonomous-robotics experience. That pairing is relevant to the gap between written code, actual jurisdiction practice and automation.
Pricing is not public; the current path is a private demo. A planning or development team should ask how jurisdiction knowledge is refreshed, which documents are authoritative, what happens when code and practice diverge and how professional sign-off is preserved. The platform can surface issues earlier, but it should not be treated as the architect, planner or building official.
Editorial take
I would shortlist AutoSitu for a firm or public agency reviewing many jurisdictions and repeatedly losing time to plan comments and precedent research. Its strongest advantage is context carrying forward with citations. Start with a familiar project and measure missed findings, review time and correction quality before broad deployment.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | Feasibility, entitlement, plan review, compliance, quantities and scope analysis |
| Buyers | Developers, planning firms, cities, architects and construction teams |
| Public metrics | Development, requirement and issue counts; company-reported |
| Public outcome claims | Resubmittal, review-time and comment reductions; company-reported |
| Pricing | Private demo; no numeric price observed |
Sources checked
| Source | Checked |
|---|---|
| YC profile | 2026-09-19 |
| AutoSitu homepage | 2026-09-19 |
| Planning-firm workflow | 2026-09-19 |
| AutoSitu launch | 2026-09-19 |
Cohort context
AutoSitu is listed in Winter 2026. In our 2026-09-18 directory snapshot, 126 of 199 listed companies in that cohort have YC’s primary industry label B2B (63.3%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:20:01.921Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Observed |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗