Suite backlog — full product queues
Product context: One company · one plan-reading spine · peer products. Raise funds suite development (suite value & return). Estym8 remains the near-term revenue wedge.
Purpose: Execution backlog for every suite product — not discovery footnotes.
Public: /docs/suite-backlog
Internal SoT cross-link: UNIFIED_BACKLOG.md owns Estym8 Now takeoff thrash; this file owns per-product suite queues.
Partner view: PARTNER_BACKLOG.md
Vision map: product/plan-intelligence-skus.md · Paul notes
Last updated: August 2026.
Statuses: [ ] open · [/] doing · [x] done.
Portfolio at a glance
| Product | Buyer | Status | Deep brief |
|---|
| Estym8 | GC / estimators | Shipping — primary wedge | folder workflow |
| Bodi | ICT / LV | Companion — Pre-GA | bodi |
| ClearToPermit | Cities / AHJs | Discovery → elevate on pilot | municipal |
| ClearToIssue | Design agencies / A/E | Discovery — Paul | ae-design-review |
| Feasibility | Architects / developers | Discovery | feasibility |
1. Estym8 — takeoff + estimate (+ ROM/WAG)
Job: Organic multi-trade takeoffs from plan sets / bid folders; plan intelligence; estimate docs; ROM/WAG screening depth.
Raise role: Near-term revenue and case studies.
Now (execution lives in UNIFIED — mirrored here)
Full ordered queue: UNIFIED_BACKLOG.md Now (P0–P1).
| ID | Item | Notes |
|---|
| E0 | Pipeline solid (Dogtopia / Castle) | P0 — organic accuracy |
| E1 | Workflow / UI / UX for beta | P1 |
| E1b | ROM / WAG UX — chooser, badge, promote CTA, QA path | P1 #5b — do not skip |
| E2 | Closed beta expansion | After E0–E1 |
| E3 | Stripe charging go-live | Post-beta — UNIFIED Appendix A |
Next / Later (Estym8-specific)
| ID | Item | Status |
|---|
| E10 | Promote-to-full from completed ROM | [ ] UNIFIED #38 |
| E11 | ROM indicative $ band (rate book / defaults) | [ ] UNIFIED #39–40 |
| E12 | ROM eval (chase-vs-pass ranking, not F4c) | [ ] |
| E13 | RSMeans / licensed cost API | [ ] procurement-gated |
| E14 | Estimate-to-submittal depth (substitution, richer specs) | [ ] §P10 ongoing |
| E15 | Deeper trade verticals outside MEP core | [ ] roadmap / App B |
Done (selected)
| ID | Item |
|---|
| Ex1 | runDepth ROM | FULL + API + UI default FULL |
| Ex2 | ROM early-exit + labeled romJson |
| Ex3 | Folder classify → plan → execute spine |
2. Bodi — ICT / LV project brain → BOD
Job: Sources → claims → Basis of Design for security, AV, cabling, Wi‑Fi.
Raise role: Companion product; shared org/auth and Estym8→Bodi feeds funded as suite work.
Boundary: BODI_ESTYM8_WRITE_BOUNDARY.md · integration · vs Estym8.
Now / Next
| ID | Item | Status |
|---|
| B1 | Keep write-boundary enforced in any cross-product code | [x] docs; [ ] CI/review habit |
| B2 | Shared org / auth story (SSO or linked accounts) | [ ] |
| B3 | Estym8 → Bodi structured export (claims/sources feed) beyond Markdown | [ ] |
| B4 | Push / pull APIs (read Estym8 concerns/RFIs into Bodi sources) | [ ] |
| B5 | Bundle packaging narrative (sell Estym8 + Bodi on same pursuit) | [ ] GTM |
| B6 | Email / .msg ingestion path (Bodi-native; Estym8 stays supporting-only) | [ ] often separate repo |
| B7 | BOD draft UX polish for design-partner pilots | [ ] Bodi product |
| B8 | Claim lineage audit export for GC / owner review | [ ] |
Later
| ID | Item | Status |
|---|
| B20 | Expand “project brain” framing beyond ICT/LV only if product scope expands | [ ] |
| B21 | Two-way sync without overwriting Estym8 counts | [ ] after B3–B4 |
| B22 | Pricing / seating model for Bodi (standalone vs bundle) | [ ] |
Non-goals
- Bodi does not become the system of record for Estym8 device counts or
rawOutput.
- Do not silently merge Bodi into Estym8.
3. ClearToPermit — municipal plan check
Job: City / AHJ permit review workflow — completeness, comment log, back-check; staff keep the stamp.
Raise role: Funded discovery → active MVP when city pilot commits.
Brief: product/municipal-plan-check.md
Copy voice: MICROCOPY_GUIDELINES.md
Contingent elevate (Mike / Peoria)
If pilot commits: promote CTP Now items immediately after minimum Estym8 spine trust — do not thrash takeoff proves for municipal UI.
Now (when elevated) / Discovery prep (always funded)
| ID | Item | Status |
|---|
| CTP1 | Title-block / sheet-index completeness checklist | [ ] |
| CTP2 | Tabular comment log + citation fields | [ ] |
| CTP3 | AI pre-populate comments (human confirm) | [ ] |
| CTP4 | Audit trail (who/when/what on each comment) | [ ] |
| CTP5 | Examiner workspace UX (queue → review → package) — not chatbot-first | [ ] |
| CTP6 | Deficiency package export (PDF / Markdown) | [ ] |
| CTP7 | Resubmittal back-check triad (original + comments + revised) | [ ] |
| CTP8 | Locale / code pack scaffolding (jurisdiction config) | [ ] |
| CTP9 | Pilot onboarding kit (Peoria / Mike) — data, success metrics, training | [ ] |
| CTP10 | Marketing / UI copy audit vs “empower staff” bans | [ ] |
Next
| ID | Item | Status |
|---|
| CTP20 | Revit / BIM import spike (APS / .rvt) — flagship vs PDF-only peers | [ ] |
| CTP21 | Revit↔PDF consistency flags on same case | [ ] |
| CTP22 | Applicant-side pre-check (dual role on same rule packs) | [ ] |
| CTP23 | Changed-sheets-only / cost controls for resubmittals | [ ] |
| CTP24 | City pricing model (site license / seats) | [ ] |
Later
| ID | Item | Status |
|---|
| CTP40 | Multi-jurisdiction rule marketplace | [ ] |
| CTP41 | Inspector / field back-check mode | [ ] |
| CTP42 | Plumbing slope / civil geometry rule packs | [ ] |
Non-goals
- City BOM / cost estimating · auto-approve permits · replace examiners · “AI chatbot for cities” as the product.
4. ClearToIssue — design agency / A/E pre-issue QA
Job: Internal design QA before seal / issue; optional city-style pre-submit checks.
Raise role: Funded discovery with Paul → design-agency pilot.
Brief: product/ae-design-review.md
Now / Discovery
| ID | Item | Status |
|---|
| CTI1 | Confirm brand vs Estym8 module (one login vs separate surface) — Paul | [ ] |
| CTI2 | v1 firm QA checklist (title-block / index first?) — Paul | [ ] |
| CTI3 | Ingest design set / revision package on shared spine | [ ] |
| CTI4 | Coordination / completeness flag list with sheet citations | [ ] |
| CTI5 | Human confirm / dismiss workflow | [ ] |
| CTI6 | Redline / issue register export | [ ] |
| CTI7 | City-style pre-submit run (shared packs with ClearToPermit) | [ ] |
| CTI8 | Design-agency pilot plan (1–2 firms, success metrics) | [ ] |
| CTI9 | UX: checklist → flags → revision track (not chatbot-first) | [ ] |
Next
| ID | Item | Status |
|---|
| CTI20 | Design-phase memory (SD → IFC; flag regressions) | [ ] |
| CTI21 | Discipline-lead queues (E/M/P/S/A) | [ ] |
| CTI22 | Firm seat pricing | [ ] |
| CTI23 | Link issues forward into ClearToPermit applicant package | [ ] |
Later
| ID | Item | Status |
|---|
| CTI40 | Multi-office checklist templates | [ ] |
| CTI41 | PE/stamp responsibility reminders (never auto-seal) | [ ] |
Non-goals
- GC BOM · PE stamp replacement · municipal enforcement as the primary job.
5. Feasibility — parcel / zoning buildable envelope
Job: Early site go/no-go for architects / developers.
Raise role: Funded discovery after ClearTo* rule-pack habits; public-data path.
Brief: product/feasibility.md
Now / Discovery
| ID | Item | Status |
|---|
| F1 | Working brand / registrar decision (ClearTo* family vs standalone) | [ ] |
| F2 | Public parcel / plat / zoning data sources shortlist | [ ] |
| F3 | Ingest path for site docs + optional GIS/parcel IDs | [ ] |
| F4 | Buildable-envelope themes output (coverage, parking, setbacks, variance likelihood) with citations | [ ] |
| F5 | Go/no-go memo export | [ ] |
| F6 | Success metrics: time-to-decision + evidence quality | [ ] |
| F7 | Designer / developer pilot candidate list | [ ] |
Next
| ID | Item | Status |
|---|
| F20 | Jurisdiction zoning pack v0 (1–2 metros) | [ ] |
| F21 | Hand-off into ClearToIssue schematic checklist | [ ] |
| F22 | Pricing (per site vs seat) | [ ] |
Later
| ID | Item | Status |
|---|
| F40 | Variance likelihood model (explicitly non-legal advice) | [ ] |
| F41 | Portfolio site screening for developers | [ ] |
Non-goals
- Replace land-use counsel · auto-approve entitlements · GC estimating.
6. Shared spine (funded once — benefits all products)
| ID | Item | Status |
|---|
| S1 | Folder / multi-PDF ingest + classify | [x] Estym8 |
| S2 | Sheet / discipline intelligence | [x] ongoing depth |
| S3 | Organic legend / schedule / conflict patterns | [x] ongoing |
| S4 | Multi-model routing + capability preflight | [x] ongoing |
| S5 | Citation-backed concern / comment primitives reusable by ClearTo* | [ ] extract shared lib |
| S6 | Jurisdiction / checklist config schema (cities + firms) | [ ] |
| S7 | Audit log primitive (actor, timestamp, artifact) | [ ] shared |
| S8 | Revit/BIM extract module (owned with ClearToPermit flagship) | [ ] spike |
| S9 | Cost / cache controls for resubmittals and ROM promote | [ ] |
7. Cross-product GTM & docs (suite raise)
| ID | Item | Status |
|---|
| G1 | Public suite docs + landing peer section | [x] 2026-08 |
| G2 | Suite value & return doc for investors | [x] this pack |
| G3 | Per-product backlog (this file) kept current with UNIFIED | [ ] ongoing |
| G4 | Partner asks tracked (Paul CTI checklist; Mike CTP pilot) | [ ] |
| G5 | Pitch / one-pager: raise funds entire suite | [x] 2026-08 investor pack sync |
| G6 | Registrar buys for ClearToPermit / ClearToIssue when confirmed | [ ] |
8. How this relates to UNIFIED_BACKLOG
| Concern | Where to work |
|---|
| Dogtopia / Castle / takeoff F4c | UNIFIED Now P0 |
| ROM UX / beta UX | UNIFIED Now P1 |
| ClearTo* / Bodi / Feasibility execution lists | This file |
| Partner-facing summary | PARTNER_BACKLOG |
| Investor $ story | SUITE_VALUE_AND_RETURN + fundraise brief |
When a ClearToPermit pilot commits, copy CTP1–CTP7 into UNIFIED Now (contingent elevate) and keep detail here.