Estym8 for new readers — bidding, estimating, and why this company exists

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.

Who this is for: Investors, advisors, partners, or teammates who do not work in construction estimating day to day. It explains the story (how commercial bids get built), the pain (time, risk, fragmentation), and the opportunity Estym8 is pursuing—in plain language. ~10 minute read.

Then read: Vision & value (product pillars) → Investor overview (business, Bodi, economics).

Last updated: May 2026.

---

1. The story in one minute

Someone wants to build or renovate a building. They hire a general contractor (GC) to run the job. The design team—architects and engineering firms—produces the construction documents (drawings, schedules, specs) everyone prices from.

On many jobs the GC solicits bids from specialty subcontractors (“subs”)—electrical, mechanical (HVAC), plumbing, concrete, steel, and many others. On others—or on the same job for different scopes—the GC’s own estimators work from those same plans to budget self-performed work, build a competitive bid to the owner, or validate sub numbers before award.

Each party—sub or GC—must answer: “What scope is on the drawings for my trade, what does it cost to install, and can I hit the deadline?” Getting to a defensible number means reading hundreds of pages of plans, schedules, and notes—counting outlets, feet of conduit, tons of duct, fixtures, gear, and checking that the documents do not contradict each other. That work is estimating (and related preconstruction). Estym8 helps teams do that faster and with fewer blind spots by treating whole plan sets and bid folders as first-class input, not a single PDF in isolation.

---

1b. How Estym8 is built (AI-first, from scratch)

Estym8 is not a decades-old takeoff product with an “AI features” checkbox. The team built it from scratch as an AI-first platform: models are wired into ingestion, classification, takeoff, plan intelligence, Estee, and estimate-to-submittal on one spine—not optional add-ons you turn on after manual counting.

In plain terms: you upload a PDF or folder, and AI reads, classifies, counts, flags problems, drafts RFIs, and answers questions about your run—grounded in what is printed on the sheets. That is the product architecture, not marketing copy. Detail: AI-first positioning.

---

2. Who is who (simple cast)

• Owner / developer — Pays for the project; cares about budget and schedule.
• General contractor (GC) — Runs the job; collects bids from subs and/or estimates in-house from design-team plans (self-perform, owner bids, buy-out).
• Subcontractor (sub) — Performs a trade (e.g. electrical). Employs estimators to prepare bids.
• Design team (architect / engineers) — Produces construction documents—the drawings and specs subs price from.
• Estimator / preconstruction — Reads those documents, quantifies scope, applies costs, and assembles the bid package the sub sends to the GC.

Estym8’s primary users today are estimators and preconstruction leads on sub and GC teams (often MEP-heavy: mechanical, electrical, plumbing), working on commercial-style jobs (offices, schools, hospitals, multifamily, etc.).

---

3. What is a “bid,” really?

A bid (or proposal) is the sub’s priced offer: “We will perform this scope for this amount by this date, subject to these clarifications.”

It rests on:

• Quantities — how much of each item (devices, pipe, duct, wire, concrete, etc.).
• Labor and equipment — how long crews need; what lifts or tools matter.
• Material and vendor pricing — often from internal price books or vendor quotes.
• Risk and clarifications — what happens if the drawings are ambiguous.

If quantities or scope are wrong, the sub either loses money (underbid) or loses the job (overbid). So accuracy and speed are both economic levers.

---

4. What is a “takeoff”?

In this industry, takeoff means deriving quantities from the construction documents—literally “taking off” counts and measures from drawings and schedules.

Examples: number of panels and receptacles from electrical floor plans; linear feet of conduit; duct CFM or linear feet by size; plumbing fixtures. It is detailed, repetitive, and easy to miss a sheet or misread a symbol legend.

Estym8 automates large parts of that reading-and-counting work for eligible drawing PDFs and bundles them with plan intelligence (conflicts, code-related notes, suggested questions for the design team—often called RFIs, Requests for Information).

---

5. What is a “plan set” or “bid package”?

A real pursuit rarely arrives as one neat PDF. Teams receive:

• Sheets — floor plans, reflected ceilings, enlarged plans, risers, details.
• Schedules — door, lighting, panel, equipment lists printed on drawings.
• Specs or spec excerpts — written requirements.
• Spreadsheets — BOQs (bills of quantity), pricing templates, alternates.
• Addenda — revisions before bid day.

Together, that is often called a plan set or bid package. Estym8 is built for that reality: you can upload a folder of mixed files; the product classifies them, builds a run plan, and runs takeoff jobs on the drawing PDFs that qualify—while still producing a useful project-level overview from the whole bundle.

---

6. Why is the old way slow and risky?

• Volume: Hundreds of sheets; many disciplines; cross-references (“see E-501”).
• Coordination: Schedules must match plans; details must match schedules; conflicts cost money if discovered after award.
• Time pressure: Bid dates are fixed; estimator time is expensive and finite.
• Documentation after the bid: Even after you win, you may owe submittals (cut sheets, product data, compliance matrices) to the GC—another manual assembly step from the same underlying quantities and products.

Estym8 attacks both the pre-bid takeoff/plan-QA problem and (with estimate-to-submittal features) part of the post-award documentation path—so the same pursuit does not get retyped in three different silos.

---

7. What Estym8 does (outcomes, not buzzwords)

Built from scratch, AI everywhere: Quantities and flags below come from an AI-native pipeline—models classify your folder, run takeoff (text and vision where needed), synthesize plan intelligence, and power Estee—not from a legacy counting tool with AI sprinkled on top.

If you only remember one column…

• Input — One plan PDF or a folder of drawings + supporting files.
• Core output — Bid-ready quantities and materials (especially strong today on MEP), plus flags where plans may conflict, codes may be unclear, or an RFI might be warranted—with draft text to speed communication.
• Trust layer — Verbatim extraction of what is printed on the sheets (title blocks, code references, notes) so claims are traceable; alerts when different sheets cite different code editions.
• Whole-job view — After folder runs, cross-file consistency and coordination hints across disciplines—not just page-by-page guesses.
• Downstream — Optional submittal packages linked to the estimate (registers, merged PDFs, draft spec review)—GC-facing documentation built closer to the source of truth.

Honesty that builds trust: The richest automation today is MEP-forward (electrical / mechanical / plumbing). Other trades (civil, architectural, structural) already run on the same technical pipeline where drawings support them; depth varies by trade and drawing quality. We say that plainly so reviewers are not surprised later.

---

8. The opportunity (why this can be a large company)

• Labor pool: Commercial construction preconstruction spends an enormous amount of highly paid specialist time on document reading, quantification, and rework. Even partial automation of the right slice of that time is a large efficiency story—see the illustrative labor and hours models in Valuation & revenue framework (not investment advice; not Estym8 revenue).
• Software wedge: Subs already pay for hosting, tools, and missed bid opportunities. A product that compresses calendar time and surfaces risk before bid day maps to subscription SaaS with clear ROI narratives—see Pricing one-pager.
• Expansion path: Deeper trade verticals, richer cross-document reasoning, and licensed cost data are sequenced on a public roadmap—the product is not “finished,” but the core bid-folder spine is already the container for that depth.

---

9. Suggested reading order

---

10. Glossary (quick)

---

This page is educational context for reviewers; it is not an offer to sell securities.