Estym8 DocsEstym8 Home

Estym8 — prioritized backlog (partner view)

Audience: Paul, Jonas, Mike, and other design / GC / city partners.
Updated: 2026-07-24.
Share link: estym8.ai/docs/partner-backlog (after deploy).
Internal source of truth: UNIFIED_BACKLOG.md (engineering detail).

Product context: Estym8 is an AI-first construction preconstruction platform — folder-native plan reading, organic takeoffs, plan intelligence, and estimate documentation. Adjacent products (design QA, municipal review) share the same engine.


Path to testing (how we sequence)

1. Pipeline solid     → organic takeoff accuracy on real jobs (Jonas / GC)
2. Workflow / UI / UX → project → folder → review → export usable for testers
3. Closed beta        → expand testing (free / approved access)
4. Post-beta          → Stripe charging · RSMeans cost API (when procured)

We will not turn on paid Stripe Checkout as a near-term priority — billing waits until we are out of beta testing. RSMeans / licensed cost data is on the backlog (procurement-gated); it does not block takeoff accuracy or beta.

Municipal (ClearToPermit): May become an active priority if the Mike / Peoria conversation commits a city pilot — see Contingent below. Raise framing stays Estym8-anchored unless we explicitly re-plan.


How to read priorities

RankMeaning
P0Pipeline solid — takeoff accuracy
P1Workflow / UI / UX + security → ready for beta testers
P2Broader validation, corpus, ops polish
P3Suite discovery — ClearTo* (elevate if pilot)
P4Post-beta / later — Stripe, RSMeans API, optional depth

Where we stand (anchors)

ProjectStatusWhat it means for partners
7 Brew — LittletonDone / lockedSigned-off electrical takeoff baseline
Dogtopia — LongmontOpen — accuracyPackaging + power-plan counting restored; next prove closes duplex gap
7 Brew — Castle PinesOpen — accuracySpecialty devices after Dogtopia

Human BOMs / takeoffs are for validation only.


P0 — Pipeline solid (Estym8)

Primary focus for Jonas / GC calibration.

#ItemStatus
1Dogtopia — next proveReady after mechanism fix
2Dogtopia — stability ×3After #1 looks honest
3Castle Pines — accuracyAfter Dogtopia #1
4Model fitness checksOngoing

Partner ask (Jonas): Keep feeding human takeoff / BOM packages for compare-after-run.


P1 — Workflow / UI / UX → beta testing

#ItemWhy it matters
5Workflow / UI / UX for beta (folder → review → export)Testers can complete the job without founder babysitting
6Security auditSafe for wider design-partner access
7Onboarding / landing quality for testersTrust and first-run clarity
8Expand closed beta (Jonas + lined-up candidates)Free / approved access — not paid Checkout

P2 — Broader validation & polish

#ItemPartner angle
9Product walkthroughsSmoother demos
10Folder-pipeline corpusRegression across project types
11Soccer Stadium AC / surveillance over-countPaul feedback
12Estimate → submittal polish (optional)Cleaner GC-facing packages

P3 — Suite discovery (municipal may elevate)

Same plan-reading engine, different jobs. Not city cost estimating. Not auto-approving permits. Not replacing city reviewers — ClearToPermit makes staff more efficient and better at their jobs; humans keep the stamp.
UX: Cohesive workflow apps (queues, checklists, comment logs, back-check) with AI assist — not chatbot-first products.
Competition: Strong point tools in municipal / takeoff lanes — but no AI-first suite peer assembling takeoff + city review + design QA + ICT BOD on one engine.

Contingent — Mike / Peoria

If the city conversation commits a pilot, ClearToPermit MVP moves into the active queue (after or beside minimum pipeline trust — without thrashing takeoff proves).

#ModuleWorking nameBuyerNear-term slice
13Municipal permit review + back-checkClearToPermitCities / AHJsTitle-block & sheet index → comment log → audit → back-check
14Revit / BIM import (HUGE for cities)ClearToPermit (+ shared spine)Cities / AHJs (+ A/E later)Time-boxed APS/.rvt spike → model on same case as PDF → Revit↔PDF consistency
15A/E design QA + pre-submit checksClearToIssueDesign / engineering firmsFirm checklist + city-style pre-check
16Site feasibilityTBDArchitects / developersParcel / zoning → setbacks

Partner ask (Paul): ClearToIssue v1 checklist; brand vs Estym8 module; Revit priority confirmed.
Partner ask (Mike): Whether ClearToPermit is the next active pilot; what MVP slice; whether native Revit submittals are in scope for Peoria (flagship differentiator vs PDF-only AI peers).


P4 — Post-beta / later

#ItemNotes
17Stripe go-liveOnly after beta testing; billing code may already exist
18RSMeans / licensed cost APIOn backlog; integrate when procurement + API terms are done
19+Panel/load checks, geometry, e-sign, accounting exportScheduled when pulled into active queue

What already works

  • Full project folder ingest — classify every file, then takeoff with context
  • Electrical device takeoffs — accuracy improving on held-out jobs
  • Concerns / conflict flags with human-in-the-loop
  • Multi-model pipeline with fitness checks
  • Estimates, proposals, estimate-to-submittal packages
  • Written product briefs for municipal + A/E suite discovery
  • Stripe integration shipped in product code — charging deferred until post-beta

Working agreement

  1. Pipeline → UX → beta before paid monetization.
  2. Stripe is post-beta — do not prioritize Checkout go-live during closed testing.
  3. RSMeans is planned — procurement-gated; does not block organic takeoff.
  4. Municipal may jump the queue if Mike commits a pilot — otherwise stays discovery.
  5. Human takeoffs = validation only — never seed pipeline answers from the BOM.

Document history

DateNote
2026-07-24Initial partner backlog
2026-07-24Path to beta; Stripe post-beta; RSMeans named; municipal contingent (Mike)