Investor overview — Estym8 and Bodi

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 Bodi fits as a secondary accompanying product held in the same company. Estym8 is the primary GTM and revenue focus; Bodi is 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 — a seed round (~$2–3M) to fund the team and scale — budget, and MRR projections are on the first screen). 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: May 2026 (refreshed for whole-project / multi-trade positioning, estimate-to-submittal shipped surface, and valuation-doc housekeeping).

---

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

Strategic value of two products: (1) Larger relevant footprint on the same pursuit (preconstruction + ICT), (2) differentiation vs single-purpose takeoff tools, (3) option value for partnerships or M&A (construction tech strategics often want bundled precon/ICT narrative), (4) shared AI and delivery muscle (stack patterns, prompting discipline) without merging the two domains into one bloated v1.

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); signed-in users open Settings → Billing for invoices. 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).
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.

Next: Deeper synthesis across documents (schedules vs plans, specs vs sheets), optional user-edited run plans, richer code/locale depth (AHJ-specific amendments applied to takeoff math), file-tied action lists, geometry tools so areas (SF) and lengths (LF) come from PDF measurement instead of AI inference, licensed catalog line-by-line unit pricing on quantities (deferred until cost-database licensing is procured), and vertical depth outside core MEP per the roadmap — not a single "v2 launch" date.

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.

---

Bodi — secondary accompanying product

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”), SaaS multiple context, illustrative company valuation tables, plan from pilots to optionality.

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.