Estym8 DocsEstym8 Home

Suite expansion board — similar, supporting, ancillary

Product context: One company · one plan-reading spine · peer products. Canonical framing: AI-first positioning · suite map.
Purpose: Ranked board of what to add next so we offer more buyer value without cloning five engines or inventing a second suite. Monetization + marketing live here with the ranks.
Not a public rate card · not Now work · not five new apps this quarter.
Updated: 2026-09-01
Companions: Lines of revenue · Suite backlog · Suite value · Marketing · Paul notes

Public: /docs/suite-expansion


How to read this board

The five peer products already on the board are Estym8, ColdEyes, PlanM8, Bodi, and SiteM8. This file is everything adjacent that still uses the same folder-native, evidence-or-abstain engine.

ClassMeaningDefault packaging
SimilarNew job + buyer that could look like a peer workflow appBrand or a named mode on an existing product — brand only when GTM truly diverges
SupportingMakes a current product much more valuable inside the same jobMode, pack, export, or portal — not a sixth homepage
AncillaryMoney or access around the software (services, partners, channels, later regulated lanes)Services line, partner, or thin export until the core five have a working path

Rank score (1 = do next after the core five prove): spine fit × buyer value × time-to-cash × honesty (humans keep stamps / bid numbers) × GTM we already know how to run.

Gate before any new app: the parent product has an A0 golden path (suite autonomy). Do not start a diligence app, insurance app, or shop-drawing app to chase chrome.


1. Strategy in one page

PrincipleMeaning
Deepen before you multiply brandsEstym8 seats and ColdEyes city licenses fund the suite. Expansion attaches to those wedges.
Mode / pack / export before a new brandOwner diligence, addenda deltas, discipline packs, inspector exports — same spine, new output.
One company story, job-specific landingsDo not market twelve logos. Suite section + waitlist is enough until a product has A0.
Sell the work product, not “AI”Completeness memo, citation comment log, organic takeoff, BOD with sources.
Services close cities; software compoundsImplementation, training, and grant packaging are ancillary revenue that unlocks ACV — not a consulting firm identity.
NeverAuto-stamp, city BOM, chatbot-only product, full Estym8 clone per vertical, selling city package contents, success-fee on permit value as the primary meter.

Money order (unchanged): Estym8 seats → ColdEyes city license + implementation → PlanM8 firm seats → Bodi bundle → SiteM8 site credits → then this board, in the ranks below.


2. Similar products (ranked)

New jobs that look like the suite: distinct buyer, structured workflow, AI assist inside it.

RankIdeaBuyerJobPackageWhy this rank
S1Owner / CM bid-package diligenceOwners, CMs, developer’s repsCompleteness, conflicts, scope gaps before award — no BOMEstym8 Diligence mode first; brand only if owner GTM needs its own landingHighest unowned value next to takeoff; folder intelligence already points here
S2Applicant pre-checkGC / A/E / developers submitting“Will the city bounce this?” before submitInside ColdEyes (dual-sided) + PlanM8 city-style packs — not a third municipal brandSame rules as city review; attach revenue on both sides of one pursuit
S3Outsourced plan-check firm workspace3rd-party examiners serving many AHJsMulti-city queues, comment logs, back-checkColdEyes multi-tenant / membershipsFaster volume than town-by-town; needs memberships (PM8-28)
S4Campus / institutional AHJUniversities, hospital systems, federal campusesInternal “building department”ColdEyes shared-AHJ configSame product, different procurement; high ACV, slow cycle
S5Third-party peer reviewStructural / code peer reviewersComment log + back-check without being the AHJColdEyes tenant or PlanM8 hybridStrong if PlanM8 comment primitives exist; do not fork a “PeerM8”
S6Design-build bridging workspaceDesign-build GC + A/E on one pursuitShared folder, takeoff + pre-issue QA, one audit storyBundle Estym8 + PlanM8 (linked org) — not a new enginePackaging + auth (B2), not a sixth product

Do not rank as similar (wrong job): another estimating brand, municipal cost estimating, “Estym8 for plumbers” as a clone, chatbot plan-Q&A as the product.


3. Supporting products (ranked)

These make Estym8 / ColdEyes / PlanM8 / Bodi / SiteM8 obviously more valuable. Prefer shipping them into those apps.

RankIdeaParentJobPackageWhy this rank
P1Addenda / revision / bid-day deltaEstym8 (+ PlanM8)What changed between issues; what the takeoff / QA must reopenRevision memory + delta memoEstimators lose days on Friday addenda; spine already classifies folders
P2Shop drawing / submittal vs issued setEstym8 (CA / buyout)Drawn vs approved / shop-set gapsEstym8 CA depth — not ColdEyesNatural after estimate-to-submittal; GC money in buyout
P3Sub bid-leveling vs organic takeoffEstym8Compare sub quotes to drawn quantitiesLeveling grid on the estimateIncredible GC value; honesty = organic counts first, then bids
P4Discipline rule packs (fire, accessibility, energy / IECC)ColdEyes + PlanM8Edition-locked findings beyond completenessAnnual pack add-onCompleteness alone under-monetizes compliance; after citation UX (S5)
P5Spec vs drawing gap memoEstym8Productize folder cross-file intel into a named deliverableExport / “Diligence lite”Already partial; naming it sells it
P6Model audit (Revit / BIM)Shared spine; flagship ColdEyes + PlanM8PDF ↔ model consistency; measured vs required or not judgedModule S8 — not a chatbot HUDPartner signal is strong; spike before GA; do not block takeoff
P7ROM / ITB chase-vs-passEstym8Which of ~200 monthly invites deserve a full runAlready in product (runDepth) — finish promote + $ bandSupporting, not new; still the highest Estym8 attach
P8Inspector field packColdEyesDeficiency + evidence export for inspectionsThin export from comment logPaul module; cheap once comment log exists
P9Trade-partner portalEstym8Subs see only their scope / sheets / countsSeat add-on or guest linkRetention; don’t build until Firm orgs exist
P10Prefab / modular shop-set checkPlanM8 packFabrication set vs design intentNiche packHigh value, thin market; after PlanM8 A0
P11CA drawing conformancePlanM8 laterField RFI / sketch vs issued setLater phaseAfter pre-issue QA is trusted
P12Closeout / punch vs record setEstym8 → facility precursorRecord drawings vs punchExport modeBridge to ancillary ops; not a construction-PM product

4. Ancillary products (ranked)

Around the software: services, partners, channels, regulated-later lanes.

RankIdeaBuyerJobPackageWhy this rank
A1Implementation / config / trainingCities first; then firmsChecklist, editions, comment library, staff onboardingOne-time or annual servicesCloses ColdEyes deals; often grant-funded; do this as soon as a city pays
A2Grant-packaging assistCitiesCalAPP / DIGIT-class narrativesServices, not softwareSame motion as A1; unlocks license ACV
A3Jurisdiction / code-edition packsCities + A/EMaintained adopted-code + amendment packsAnnual subscriptionRecurring attach once S6 exists
A4Insurance / surety assistCarriers, brokersRisk flags with sheet evidence — not “approved for coverage”Partner / white-label after citation UXReal money, regulated messaging; partner-first
A5Lender / special-inspector packLenders, SI agenciesDrawn vs claimed; deficiency listsExport on diligence or ColdEyesThin; do not staff a lending product
A6Coop / state catalog channelPurchasing coopsFaster city procurementChannel, not a productTXShare-class; accelerates ColdEyes
A7Managed review (SaaS + examiners)Small AHJsPlatform + contracted reviewersHigh ACV, ops-heavyOptional; only if we want a services org
A8Facility / as-built ops inventoryOwners, facility managersDevice/system inventory from record drawingsLater product or Estym8 exportTakeoff-like counts, different buyer; after precon proof
A9Commissioning (Cx) drawing checklistCxA / ownersDrawing-derived Cx items with citationsPack on diligence / Estym8Valuable; after P5
A10Special inspection agency workspaceSI firmsDeficiency lists + evidenceThin ColdEyes cousin or A5 exportOverlaps A5; don’t double-brand
A11Estym8 trade depth packsGC / estimatorsConcrete, openings, etc. beyond MEP coreVertical add-onAfter MEP trust (E15)
A12HOA / private design-review boardPrivate DRBsLighter completeness + guidelinesColdEyes liteOnly if inbound demand; easy to distract
A13Lighting-vendor / manufacturer calibrationVendors + GCSymbol QA against human schedulesEstym8 ops / P9Supporting data, not a customer SKU

5. How we monetize

Meters stay illustrative until pilots lock them. Prefer one primary meter per product. Detail for the five peers: SUITE_LINES_OF_REVENUE.md.

5.1 Default meters by class

ClassPrimary meterSecondaryAvoid as primary
Similar workflow appAnnual seats or org license (Firm / city band)Package or site creditsSuccess fee on permit or bid value
Supporting modeIncluded in parent tier or Firm add-onOverage on extra deltas / packsA second subscription for the same user
Discipline / code packAnnual pack per jurisdiction or code familyMulti-pack bundlePer-finding fees (feels like a tax)
Export pack (inspector, lender, Cx)Per-export credit or included in FirmPer-page (Jonas: pages are not equal)
ServicesFixed SoW (config + training)Annual “pack refresh”Hourly that never ends
Partner (insurance / surety)Seat license to the carrier or revenue share on underwriting assistsClaiming coverage decisions

5.2 Attach math (how expansion makes the core worth more)

MoveWho paysWhy it raises willingness-to-pay
Diligence mode on Estym8Owner/CM or GC precon selling a cleaner packageNew buyer on the same folder run
Applicant pre-checkSubmitter credits after city is liveCity stays “free enough”; applicants pay for speed
Discipline packsCity and PlanM8 firmSame pack sold twice (staff vs pre-submit) — honest dual GTM
Addenda deltaEstym8 Studio/FirmSaves the Friday panic; keep inside the seat
Bid-levelingEstym8 FirmTurns takeoff into buyout; enterprise conversation
ImplementationCityUnlocks the license; often a different budget line
Bundle Estym8 + Bodi / PlanM8Same orgOne pursuit, two jobs, one login (B2 / S*)

5.3 Packaging rule

  1. Ship the deliverable (memo, log, grid, export).
  2. Price it as a mode or pack on the parent.
  3. Brand it only when the buyer would not buy the parent (owner diligence vs estimator Estym8; carrier vs GC).
  4. Never five Stripe products that are the same PDF ingest with a different CSS theme.

5.4 What we will not sell

City cost estimating · auto-approve / auto-deny · chatbot-only · anonymized municipal package contents · success-fee on permit value as the headline meter · “approved for coverage” · PE stamp replacement.


6. How we market

6.1 Voice and surfaces

DoDon’t
One company, job-named landings (already: /, /coldeyes, /planm8, /bodi, /sitem8)Twelve brands in the hero
Completeness, organic counts, citation, human ownership“AI suite that does everything”
Waitlist + request access until A0 existsFake GA, live case counts, scarcity
Suite section on each landing (#suite-products)ColdEyes stamp language on Estym8, bid-day language on ColdEyes

Public copy rules: MICROCOPY_GUIDELINES.md. Psychology: UX_PSYCHOLOGY_GUIDELINES.md.

6.2 Channel by buyer (when that rank is in market)

BuyerProduct ranksWhere they listenOffer
GC / estimatorsEstym8, P1–P3, P7, P9r/estimators, LinkedIn precon, NECA / AGC, Advancing PreconstructionTime-to-number; addenda delta; ROM chase-vs-pass
City / AHJ staffColdEyes, S2–S4, A1–A3, A6ICC chapters, league of cities, plan-check associations, grantsIncomplete-package hours back; staff keep the stamp
Outsourced examinersS3Same as cities + consultant networksMulti-AHJ queue
A/E / design agenciesPlanM8, P4, P6, P10–P11, S6AIA, ACEC, Paul / design-partner pathIssues caught pre-issue; city-style pre-submit
ICT / LVBodiBICSI, security/AV integratorsBOD from sources, not re-keying
Architects / developersSiteM8, S1ULI, developer precon, AIA practiceGo/no-go with citations
Owners / CMsS1, P5, A8–A9CMAA, owner precon forumsDiligence memo before award
Carriers / brokersA4Wholesale brokers, surety associations — via partnerEvidence pack; underwriter stays in the loop

Estym8-only channel detail stays in MARKETING_AND_OUTREACH.md. ColdEyes city motion: ops/coldeyes-marketing-plan.md.

6.3 Content that actually sells expansion

Lead magnets should be the work product, not a newsletter:

RankAssetCTA
S1 / P5One-page “bid-package completeness” checklist (disciplines, index, addenda)Request Estym8 access — diligence is a mode later
S2“Will the city bounce this?” self-score (title block, index, code edition)ColdEyes / PlanM8 waitlist
P1“Friday addenda” one-pager (what to re-open on a takeoff)Estym8
P4Honest “what a fire/accessibility pack is not” (no auto-stamp)City / A/E waitlist
A1Grant-budget line samples (software + implementation)ColdEyes conversation

Do not invent city names, live case counts, or social proof. Do not pulse CTAs.

6.4 Sequencing GTM (do not market the whole board)

PhaseMarketSilence
NowEstym8 takeoff + ROM; ColdEyes waitlist as permit review (not estimating)Insurance, facility ops, HOA, managed review
City A0Implementation + grant packaging (A1–A2); applicant pre-check as a sentence, not a campaignMulti-brand ads
PlanM8 A0Pre-issue QA + city-style packs; design-build bundle with Estym8Prefab, CA, peer-review brands
After citation UXDiscipline packs, inspector export, owner diligence modeCarrier product until a partner is named
LaterFacility inventory, Cx, HOA liteAnything that needs a new engine

6.5 Bundle narrative (sales, not ads)

  • Same pursuit: Estym8 takeoff + PlanM8 pre-issue + ColdEyes city review — three jobs, one spine.
  • Same org: Estym8 + Bodi on an ICT-heavy bid.
  • Same site: SiteM8 go/no-go → PlanM8 schematic QA (F21).

Sell that in conversations and investor optionality. Do not put three full buttons in a hero.


7. Roadmap placement (when ranks become work)

Execution stays in SUITE_BACKLOG.md §9. This table is the promote rule, not a second Now queue.

WhenPromote
Estym8 organic trust + Firm orgsP1 addenda delta, P5 named gap memo, P7 ROM finish
ColdEyes comment log + notify loop (A0)S2 applicant sentence → credits later; P8 inspector export; A1 services rate card
PlanM8 A0 (checklist + findings)P4 first discipline pack; S6 bundle story
Shared citation primitives (S5) + jurisdiction schema (S6)P4 priced packs; A3 edition packs
Owner inbound or slow city GTMS1 Diligence mode (decide brand after 3 logos)
Memberships (PM8-28)S3 outsourced examiners
Revit spike bar met (S8)P6 GA decision
Citation UX trusted + counselA4 partner conversations only

Do not promote A7 managed review, A12 HOA, or a new brand until the parent A0 is boringly reliable.


8. Working decisions

  • S1: Estym8 Diligence mode vs separate landing/brand
  • S2: when (if ever) applicant credits vs city-only SaaS
  • P3 bid-leveling: Firm-only vs Studio
  • P4 first pack: fire vs accessibility vs energy
  • A4: named partner vs wait
  • A7: in-house examiners ever, or never

Keep this file and SUITE_LINES_OF_REVENUE.md §5 in sync.


9. Doc map

DocRole
This fileRanked similar / supporting / ancillary + monetize + market
SUITE_LINES_OF_REVENUE.mdMeters for the five peers + services
product/plan-intelligence-skus.mdJob map for branded products
SUITE_BACKLOG.mdExecution IDs (including §9 expansion)
MARKETING_AND_OUTREACH.mdEstym8 channels
ops/coldeyes-marketing-plan.mdColdEyes city GTM

Document history

DateNote
2026-09-01Ranked expansion board; monetization + marketing; roadmap promote rules