Investor overview — Estym8 portfolio

Product context: Estym8 is built from scratch as an AI-first construction preconstruction platform—not a legacy takeoff stack with AI bolted on. AI runs across the product: bid-package ingestion and classification, multi-model takeoff and vision, plan intelligence, cross-file synthesis, Estee, estimate-to-submittal draft review, and optimization recommendations. Canonical framing: AI-first positioning.

Purpose: One parent document for potential investors: what exists today (v1), where the product is going (v2), how we monetize Estym8, and how adjacent products (Bodi + plan-intelligence SKUs) fit in the same company. Estym8 is the primary GTM and revenue focus; Bodi and discovery SKUs are complementary upside under the same roof. All detailed docs are published at https://estym8.ai/docs/ (no login required).

Want the deal terms, use of funds, and financial projections first? Skip straight to the pitch deck → "Deal & financials at a glance" (the ask — ~$500K post-money SAFE, ~6–9 months runway to first paying seats — budget and milestones on the first screen). Full names, bios, and grant detail live only in the lean investor brief (NDA PDF). This overview leads with product/strategy; the deck leads with the deal.

New to construction estimating? Read Estym8 for new readers first (roles, bids, takeoffs, plan sets, opportunity—in plain English), then return here for business detail.

Last updated: July 2026 (ask aligned to lean investor brief: ~$500K post-money SAFE; path pipeline → UX → beta → Stripe post-beta; RSMeans API on backlog; ClearToPermit municipal contingent; Paul suite notes 2026-07-24; strategic-exit framing via valuation §6.5).

---

Disclaimers (read first)

• This page is informational for diligence conversations—not an offer to sell securities.
• Forward-looking statements (roadmap, v2, Bodi milestones) are plans, not guarantees. Priorities and timing change with customer feedback and capital.
• Valuation and revenue scenarios in the linked framework are illustrative and based on third-party sources; they are not investment advice. Engage legal and financial advisors for fundraising.
• Bodi is actively developed alongside Estym8; integration paths described in the Bodi doc are product strategy, not committed GA features until shipped.

Scope honesty (whole project vs deepest automation): Estym8 is aimed at whole drawing sets and bid-folder behavior on one project—multiple trades, spreadsheets, and supporting files—not only a single MEP PDF. Today, the richest automation and calibration are still MEP-forward; architectural, structural, civil, and GC-style scopes are on the same pipeline where drawings support them, with depth expanding on the public roadmap. We describe that mix plainly to investors.

Architecture (AI-first from scratch): Estym8 is a greenfield AI-native product—not a legacy takeoff stack with models bolted on. AI runs across ingestion, classification, multi-model takeoff and vision, plan intelligence, cross-file synthesis, Estee, and estimate-to-submittal draft review on one pipeline. That positioning is canonical in AI-first positioning (repo: docs/AI_FIRST_POSITIONING.md).

Model strategy: We orchestrate best-in-class third-party models today behind a model-agnostic pipeline (frontier capability, inference-only cost, no model-training spend). Our durable advantage is the proprietary ground-truth + calibration data that compounds with usage—which over time lets us bring domain-tuned proprietary models in-house for the narrow, repeatable tasks to lower cost and vendor dependence. This is a data-driven path, not a plan to build a foundation model from scratch.

---

Executive summary

Shared asset: one plan-reading spine (folder ingest, classify, sheet intel, organic legend/schedule/conflict reads, multi-model routing). Swap the job head per buyer — never sell city BOMs or invent compliance. Longer-term modules on the same spine: feasibility (parcel/zoning), revision intelligence / back-check, and — for ClearToPermit especially — native Revit / BIM import as a flagship differentiator vs PDF-only municipal AI. Detail: plan-intelligence SKUs · Paul suite notes · municipal · A/E design review.

Strategic value of the suite (Office metaphor): one processing engine + specialized workflow apps (intake, takeoff, design QA, permit review, back-check, feasibility, model audit) — AI assists inside those workflows; we do not ship chatbot SKUs. ClearToPermit makes city reviewers more efficient; humans keep the stamp. Sharing project data, audit trail, and rule packs without cloning Estym8 into four monoliths. (1) Larger footprint on the same pursuits, (2) differentiation vs single-purpose takeoff tools, (3) option value for partnerships or M&A, (4) shared AI muscle. Raise use of funds remains 100% Estym8-anchored; adjacent SKUs are discovery / optionality.

Suite competition: There is no AI-first competitor for this suite — peers compete as point tools (municipal AI, takeoff AI) or legacy platforms bolting AI on. Nobody else is assembling Estym8 + Bodi + ClearToPermit + ClearToIssue on one greenfield plan-reading spine. (detail)

Company strategy — testing, revenue, acquisition

How we frame the business for investors: Estym8 is building a credible, organic plan-intelligence product first. The near-term plan is disciplined validation and first paying seats. The intended exit is strategic acquisition by a construction-software leader—not a decades-long independent public-company path.

Why acquisition is the primary endgame: Public comps (Trimble ~$11–12B, Procore ~$8–9B) already pay for construction precon and are actively buying estimating and AI tuck-ins (see valuation §6.5 / §7.3). Estym8’s wedge—folder-native, AI-first, organically counted takeoffs—fills gaps incumbents have tried to close via M&A rather than rebuild. We are not optimizing the cap table for a hypothetical IPO; we are building proof that makes a strategic buyer the natural outcome once revenue and references exist.

What we are not claiming: No target acquirer, price, or timeline is committed here. Exit timing depends on traction, market conditions, and negotiation. Revenue matters because strategics pay for proof, not because we plan to operate indefinitely at scale alone.

Estimate-to-submittal (in product, GA-track): Reusable submittal catalog (manufacturer rows + uploaded PDFs on blob storage), submittal packages per estimate with optional links to BOM lines and workbook device-quantity rows, Markdown register + compliance matrix, merged PDF export, and draft spec AI cross-check that sends catalog PDFs attached to linked products (plus optional pasted spec text) to the model for internal review—not a compliance sign-off.

---

Version 1 (Estym8 — current product scope)

In one sentence: Upload plan PDF for the classic path (one drawing file → one takeoff run), or upload a bid-package folder on a project (drawings plus spreadsheets and supporting files) for classification, an AI project overview, and one or more takeoff runs from the generated plan—plus plan intelligence, a verbatim "As Printed on the Sheets" harvest, code-edition mismatch alerts, cross-file intelligence, a downloadable multi-discipline narrative report, estimate-to-submittal packages (catalog, register, compliance export, merged PDF, draft spec AI), and Estee (same Q&A and RAG as before; optional preview → confirm saves for supported estimate edits when chat is estimate-scoped).

Detail:

• Workflow: Create project → upload plan PDF and/or upload folder (plans & docs) → processing (typical 15–45 minutes per run depending on size and job count) → review estimates, folder run progress, AI project overview (when present), concerns, RFIs, recommendations, cross-file intelligence, As Printed on the Sheets harvest, and code-edition mismatch alerts on the project page → download the multi-discipline narrative report (Markdown / DOCX / PDF) and/or export individual estimates → chat with Estee.
• Disciplines on one pipeline: electrical, mechanical, plumbing, civil, architectural, structural — same classify → plan → execute loop, including multi-file discipline bundles. Coverage and depth vary by sheet quality and trade.
• Project-level intelligence: every project that has at least one harvested PDF gets the As Printed on the Sheets verbatim pass (title block, applicable code editions, exception clauses, printed allowances, calculation rules, cross-sheet references) and code-edition mismatch alerts when sheets disagree (e.g. NEC 2017 vs NEC 2020). Folder runs additionally generate a post-folder cross-file intelligence pass — consistency findings, coordination topics, RFI seeds — distinct from the per-folder AI project overview.
• Decision-ready report: the multi-discipline narrative report stitches the verbatim harvest, every completed takeoff, the conflict log, draft RFIs, and a bid-bucket reconciliation that compares AI counts against engineer-printed grand totals into a single Markdown / DOCX / PDF download.
• Monetization & billing: Stripe per-seat subscriptions (Solo / Studio / Firm) — integration shipped; charging deferred until after closed beta. Testers use approved / free access. See Pricing one-pager.
• Access: Takeoffs require an active plan or approved access (not a public no-signup funnel). See Upsell strategy for gating and conversion story.
• Lifecycle: See Estimate lifecycle for the path from takeoff to bid; submittal packages on an estimate carry the job from priced / counted lines toward GC-facing documentation (register, compliance matrix, merged PDFs) using the shared catalog.

Docs (read in this order for “what exists”):

0. Estym8 for new readers — if you are not from construction: story, roles, takeoffs, opportunity (then continue below).
   0b. Pipeline proof tracker (repo: docs/ops/investor-pipeline-proof.md) — step audit A0→A8 + F4 on real bid folders.
1. Vision & value — pillars and outcomes.
2. Estimate lifecycle — v1 journey.
3. Pricing one-pager + Pricing strategy — tiers, ROI, competition.
4. Upsell strategy — access → paid motion.
5. Marketing & outreach — channels and ICP.

---

Version 2 (Estym8 — in motion)

Shipped (April–May 2026):

• Bid-package / folder workflow on every project — multi-type uploads (drawing PDFs + spreadsheets + text/images within supported extensions), per-file classification, persisted run plan, and AI project overview (game plan, estimate strategy, file roles), with execution including multi-file discipline bundles.
• 6+ disciplines on one folder pipeline — electrical, mechanical, plumbing, civil, architectural, structural and adjacent trades all run on the same classify → plan → execute loop.
• Verbatim plan harvest ("As Printed on the Sheets") — title block, applicable code editions, exception clauses, printed allowances, calculation rules, and cross-sheet references lifted from each PDF in a single focused pass per document.
• Code-edition mismatch alerts — flagged on the project page when sheets cite different code editions (NEC, NFPA, IBC, energy code, etc.).
• Cross-file intelligence — post-folder pass that surfaces consistency findings, coordination topics, and RFI seeds across the whole bundle, separate from (and in addition to) the per-folder AI project overview.
• In-drawing verification (where enabled) — reviewers can confirm legend-backed placements on the PDF before promoting counts on paths that expose overlay review.
• Multi-discipline narrative report — single downloadable Markdown / DOCX / PDF that stitches the harvest, every completed takeoff, conflict log, draft RFIs, and bid-bucket reconciliation against engineer-printed grand totals.
• Estimate-to-submittal (GA-track, evolving) — Prisma-backed packages / sections / items, submittal catalog (products + PDF uploads), Markdown register + compliance matrix, merged PDF export, draft spec AI cross-check using catalog PDFs on linked lines (optional pasted excerpt), BOM and workbook-quantity pickers on line items; deeper substitution workflow and richer spec ingestion remain next within §P10.

Execution priority (near term): (1) pipeline solid on real GC anchors, (2) workflow / UI / UX solid for testers, (3) expand closed beta, (4) Stripe go-live post-beta, (5) RSMeans / licensed cost API when procurement closes. Partner-facing backlog: partner-backlog.

Next (product depth): Deeper synthesis across documents (schedules vs plans, specs vs sheets), optional user-edited run plans, richer code/locale depth (AHJ-specific amendments), file-tied action lists, geometry tools (SF/LF from PDF measurement), licensed catalog / RSMeans API unit pricing once rights are procured, and vertical depth outside core MEP — not a single "v2 launch" date. ClearToPermit (municipal) may elevate into the active queue if a city pilot commits.

Docs:

• Project-level & bid-package workflow — current scope, data model, behavior.
• Product roadmap — deeper trade verticals, MEP extensions, and packaging on the shipped folder spine (not “folder v2” waitlist).

Single-PDF uploads remain the fastest path for specialist estimators; folder uploads widen the top of the funnel for whole-job packages.

---

Portfolio map (all apps & solutions)

Estym8 solution surface (modules, not separate brands)

Bid-folder / PDF takeoff · plan intelligence (conflicts, codes, RFIs) · Estee assistant · estimate-to-submittal packages · multi-discipline narrative report.

Adjacent plan-intelligence SKUs (discovery)

Same plan-reading engine as Estym8; different buyer and success metric. Not in the raise budget as separate GTM lines — discovery / design-partner stage.

Why investors should care: expands the addressable surface of the same IP (gov permitting + design QA) without reinventing ingest/vision. Competition exists in municipal AI plan review (CodeComply, Blitz, Permittable); our wedge is messy multi-file organic reads already paid for by Estym8. A live city pilot (Peoria / Mike path) would accelerate ClearToPermit without changing Estym8-first use of funds unless we explicitly re-plan. Detail: municipal-plan-check.md · ae-design-review.md · plan-intelligence-skus.md · partner backlog.

Bodi — secondary accompanying product

What it is (plain English): Bodi is a "project brain" for the ICT / low-voltage trades — security systems, audio/visual, structured cabling, Wi‑Fi. Those contractors don't start from drawings; they start from scattered information: client emails, meeting notes, client standards, equipment schedules. Bodi ingests all of that, organizes it into traceable facts ("claims" — each linked back to its source), and assembles them into the contractor's key deliverable: the Basis of Design (BOD) — the formal document stating what will be built and why. In one line: Estym8 answers "what's in the drawings and what will it cost?" Bodi answers "what did everyone agree this system needs to be — and can you prove where each requirement came from?"

Positioning: Bodi is not a second takeoff product. It is a project-brain / BOD product for ICT, security, AV, low-voltage, ISP, Wi‑Fi scopes—adjacent buyer, complementary to Estym8 when the same whole-building pursuit needs multi-trade plan intelligence + quantities and ICT requirements traceability.

Why investors should care:

1. Same construction preconstruction budget — different line items (MEP estimator vs ICT lead), often same GC or CM.
2. Data synergy: Estym8 already produces structured concerns, RFIs, and recommendations; Bodi models sources → claims → BOD. One-way export/sync (Estym8 → Bodi) reduces duplicate manual rework (see integration doc).
3. Optional second revenue stream or bundle over time—pricing for Bodi can be developed independently; this overview does not commit to a single monetization model.
4. Risk balance: Estym8 can reach revenue without Bodi GA; Bodi is upside and strategic depth, not a blocker to Estym8’s core thesis.

Deep dive: Bodi + Estym8 integration — domains, API shapes, options (export file, push claims, shared project link).

---

Revenue, labor economics, and valuation context

Framework (external research + illustrative scenarios):
Valuation, labor economics, and revenue framework — BLS-backed estimator counts and wages, takeoff time bands, buyer ROI sketch, §5A (~$4–5B/yr labor pool at 20% of loaded SOC payroll—upper-hero case), §5B (hours × takeoff-share × automation capture—addresses “not every hour is takeoff”), §6.5 (public comps: Trimble ~$11–12B, Procore ~$8–9B, Autodesk-class platforms—how strategic buyers already value construction precon + AI), SaaS multiple context, illustrative company valuation tables (§7), §10.3 growth path from ~$5K MRR (month 6) through ~5,000 seats / ~$850K MRR scale scenario.

Strategic exit lens (one line): Category leaders are already public at $8–12B+ and buying estimating/AI tuck-ins. Our intended exit is strategic acquisition after testing sign-off and early revenue—not a standalone IPO story. Seed cap (§7.1) and ARR-multiple paths (§7.2) are near-term framing; §6.5 and §7.3 frame exit upside once proof exists.

Use that doc for slides and sensitivity analysis; supplement with your own pipeline ARR model and cohort assumptions. Pitch deck: https://estym8.ai/docs/pitch-deck.

---

Stakeholder pack (non-investor variant)

The original doc pack is optimized for design partners and early commercial conversations—it overlaps heavily with investor reading but leads with alignment narrative:

• Doc pack (overview + links)

Investors can use this page as the entry; operators can still start at the pack.

---

Optional deeper dives

Single link to share

Start here for investors:
https://estym8.ai/docs/investor

From that page, every other doc above is one click away—no GitHub or app login required.

---

For questions or a data room, contact the company directly.