Estym8 DocsEstym8 Home

Suite — lines of revenue & ancillary products

Product context: One company · one plan-reading spine · peer products. Canonical framing: AI-first positioning · suite map.
Purpose: Internal + investor strategy SoT for how we make money and which adjacent products belong on the board — so wedges are not lost in chat.
Not a public rate card · not Stripe SKUs · illustrative until pilots lock meters.
Updated: 2026-09-01
Companions: ColdEyes competitive pricing (PM8-24) · Estym8 pricing strategy · Suite value & return · Suite backlog · Expansion board (ranked similar / supporting / ancillary + GTM)


1. Strategy in one page

PrincipleMeaning
Estym8 is the near-term cash wedgeSeat SaaS (Solo/Studio/Firm) funds proof and runway.
ColdEyes is the municipal ACV wedgeCity/AHJ annual license (population / volume / seats) — different ICP than Estym8.
One spine, many buyersSame plan-reading IP → GC, city, A/E, ICT, developer — do not clone five engines.
Services attach early for citiesConfig / checklist / training / grant packaging often close deals before pure SaaS alone.
Humans keep stampsNever sell auto-approve permits or city BOM estimating.
Defer exotic metersSuccess fees, selling municipal data, Estym8 seat checkout for cities — avoid as primary.

v1 priority order (money): Estym8 seats → ColdEyes city license (+ implementation) → PlanM8 firm seats → Bodi bundle → SiteM8 → later diligence / insurance / ops. Ranked expansion (modes, packs, services): SUITE_EXPANSION_BOARD.md.


2. Lines of revenue (by product)

2.1 Estym8 — GC / estimators

LineMeter (hypothesis)Notes
Core SaaSSeat / tier (Solo · Studio · Firm)Primary raise proof — see PRICING_STRATEGY.md
Usage / overageExtra projects or sheets beyond tierOptional hybrid later
ROM / WAG depthIncluded or higher-tierSame product, thinner depth — not a new brand
Estimate → submittalIncluded in Firm / add-onKeep inside Estym8
Trade depth packsVertical add-ons laterConcrete, openings, etc. — after MEP trust

2.2 ColdEyes — cities / AHJs

LineMeter (hypothesis)Notes
Annual city / AHJ licensePopulation band or package volume or staff seatsPick one primary meter for v1 (PM8-24)
Implementation / configOne-time or annual add-onChecklist, editions, comment library, training — often grant-funded
Package included + overageN packages/yr then $/pkgAlternative to pure seats once volume is known
Discipline / rule-pack add-onsPer pack / yearFire, accessibility, local amendments — after PM8-5c / PM8-8
Applicant pre-check feePer submit or credit packCity free / applicant pays — after PM8-22; not v1
Outsourced plan-check firmMulti-AHJ seats / packages3rd-party examiners serving many cities — high volume
County / COG / shared AHJRegional contractOne logo covering many small towns
Managed review (SaaS + services)Platform + contracted examinersHigh ACV, ops-heavy — optional
Coop / state catalogChannel (TXShare-class)Accelerates purchase; not a product SKU

Detail + competitor anchors: ops/coldeyes-pricing-competitive.md.

2.3 PlanM8 — A/E / design agencies

LineMeter (hypothesis)Notes
Firm seat SaaSSeats / officePre-issue QA workflow
City-style pre-submit runsPacks shared with ColdEyes AHJsUpsell when target city is on ColdEyes
Multi-office templatesEnterprise tierLater (CTI40)

2.4 Bodi — ICT / LV

LineMeter (hypothesis)Notes
Standalone seatsICT estimator / designerBOD from sources/claims
Bundle with Estym8Pursuit packageSame org, linked accounts (B2 / B5)

2.5 SiteM8 — architects / developers

LineMeter (hypothesis)Notes
Per site / portfolioSite credit or seatEarly go/no-go memo
Metro zoning packsGeography add-onAfter public-data path (F20)

2.6 Cross-suite attach (not separate brands)

LineHow it shows up
Estym8 → ColdEyes readinessFirm runs takeoff + completeness against target AHJ checklist before submit; city prefers cleaner packages
CheckSet → ColdEyes handoffPre-issue issues travel into applicant package (CTI23) — PlanM8 is the public brand
Feasibility → CheckSetEntitlement go → schematic QA (F21) — SiteM8 → PlanM8
Shared auth / orgOne company login story reduces churn across SKUs (B2, S*)

3. Suite products today vs gaps

3.1 Branded / on the board (do not re-invent)

ProductBuyerJob
Estym8GC / estimatorsTakeoff + estimate (+ ROM/WAG, submittal)
BodiICT / LVProject brain → BOD
ColdEyesCities / AHJs (+ submitters)Permit review; staff keep stamp
PlanM8A/E firmsPre-issue / city-style pre-submit QA
SiteM8Architects / developersParcel / zoning buildable envelope

Map: product/plan-intelligence-skus.md · queues: SUITE_BACKLOG.md.

3.2 Already sketched as use cases (not full brands yet)

From the suite map — do not lose; brand later:

Use caseBuyerLikely packaging
Owner / CM bid-package diligenceOwners, CMs, developer’s repsEstym8 “Diligence” mode or thin ColdEyes-class memo product
Insurance / surety assistCarriers, brokersPartner / white-label after citation UX proven
Lender / special-inspector packLenders, SI agenciesExport mode on diligence or ColdEyes
Facility / as-built ops handoffOwners, facility managersLonger-term inventory from record drawings
Applicant pre-checkGCs / A/E / developersSurface on ColdEyes (dual-sided) + PlanM8 — not a third municipal brand
Model audit (Revit/BIM)All SKUsShared spine module (S8), flagship with ColdEyes

3.3 Ranked expansion (similar / supporting / ancillary)

Canonical ranks, meters, and GTM: SUITE_EXPANSION_BOARD.md (public: /docs/suite-expansion).

Prefer mode / pack / export before a new brand. Headline ranks:

ClassTop ranks
SimilarS1 owner/CM diligence · S2 applicant pre-check · S3 outsourced plan-check firms
SupportingP1 addenda/revision delta · P2 shop vs issued set · P3 sub bid-leveling · P4 discipline packs
AncillaryA1 implementation/training · A2 grant packaging · A3 code-edition packs · A4 insurance partner

The flat candidate list that used to live here is superseded by those ranks (shop drawings, ASI/delta, CA, prefab, energy/ADA/fire packs, SI workspace, peer review, HOA, campus AHJ, closeout, ITB/ROM, training, grants — all mapped). Do not maintain a second unordered table.

3.4 Explicit non-goals (do not add as products)

Anti-patternWhy
City cost estimating / municipal BOMConfuses Estym8 vs ColdEyes; wrong buyer job
Auto-approve / auto-deny permitsLiability; kills trust
Chatbot-only SKUWorkflow apps + AI assist is the suite rule
Full Estym8 clone per verticalShare libraries; don’t fork the app
Selling anonymized city package contentsProcurement / trust poison
Success-fee on permit value as primary meterHard for municipal procurement

4. What you might be “missing” for the suite (honest gaps)

GapWhy it mattersAction
Owner / CM diligence is sketched but unownedLarge buyer adjacent to Estym8 folder intelligence; no brand/pilot yetAssign after ColdEyes pilot: Estym8 mode vs thin SKU
Outsourced plan-check firms as ICPFaster multi-city volume than town-by-townGTM note under ColdEyes; needs PM8-28 memberships
Discipline packs as revenueCompleteness alone under-monetizes the compliance storyPrice packs when PM8-5c / PM8-8 land
Implementation services rate cardCities expect a SoW lineAdd with first paid ColdEyes logo
PlanM8 ↔ ColdEyes attachFirm pays + city pays on same pursuitCTI7 / CTI23 — keep funded
Shared citation / comment primitivesWithout S5, every SKU re-implements findingsSpine backlog S5–S7
Insurance / surety parkedReal money, regulated messagingPartner-first after citation UX
No “construction phase” productSuite is precon / permit / design-heavy todayShop drawing / CA / closeout only after core SKUs prove

You are not missing a second takeoff competitor product. The open holes are mostly downstream diligence, discipline packs, services, and multi-AHJ B2B — not another estimating brand.


5. Working decisions (keep open until pilots answer)

  • ColdEyes v1 primary meter: population vs packages vs seats (PM8-24)
  • Owner/CM diligence: Estym8 mode vs separate brand
  • PlanM8: separate brand vs Estym8 module (Paul / CTI1) — public brand is PlanM8
  • When to sell applicant pre-check fees vs city-only SaaS
  • Whether managed review (humans + ColdEyes) is ever in-house

Do not lose expansion ranks — canonical board: SUITE_EXPANSION_BOARD.md. Execution IDs: SUITE_BACKLOG.md §9 / COLDEYES_BACKLOG.md. This file stays the meter SoT for the five peers.


6. Doc map

DocRole
This fileSuite lines of revenue (meters) for the five peers
SUITE_EXPANSION_BOARD.mdRanked similar / supporting / ancillary + monetize + market
ops/coldeyes-pricing-competitive.mdColdEyes competitor signals + city bands
PRICING_STRATEGY.mdEstym8 seat / tier strategy
SUITE_VALUE_AND_RETURN.mdInvestor return optionality
product/plan-intelligence-skus.mdProduct / job map
SUITE_BACKLOG.mdExecution queues

Document history

DateNote
2026-08-11Initial SoT — ColdEyes revenue wedges + suite ancillary candidates
2026-09-01PlanM8 / SiteM8 brand names; ranked expansion moved to SUITE_EXPANSION_BOARD.md