autotelic.build(720) 287-7958

Pricing the work

How construction estimating works — and how Autotelic prices a job

How contractors turn a scope into a price — assemblies, unit costs, labor, and code — and the live tools Autotelic runs to do it.

live

Back to the galaxy

Construction estimating turns a scope of work into a number. The reliable way to do it is with assemblies: a kitchen remodel, for example, isn't one line item, it's dozens — demo, framing changes, electrical circuits, plumbing rough-in, cabinetry, countertops, tile, paint — each with its own unit cost for materials and labor. Add them up against the actual quantities for a specific space, and the total reflects that project, not a rule-of-thumb square-footage guess.

Good estimates also carry code references where they matter — an electrical panel upgrade or an egress window isn't priced in a vacuum, it's priced against what the applicable code actually requires in that jurisdiction. And every honest estimate is a range, not a single number, because some quantities and some site conditions aren't fully known until later steps confirm them; a wide range usually means less is known yet, and a narrow one means more has been verified.

Autotelic's instant estimate wizard runs on that same logic instead of a lookup table: a trade router sends the project to the right catalog, a jurisdiction resolver checks which of several named local authorities applies (falling back honestly when it doesn't recognize one), catalog matching and a crew labor calculator price the actual scope, and code-compliance references get attached wherever the catalog has a verified one. A quantity validator checks the inputs before anything is priced, and how the resulting estimate is presented — grouped by section, with subtotals, notes, and optional lines — is a setting the team controls, not something baked into the wizard.

That live, catalog-grounded pricing runs today for a home remodel, an ADU, and a modular new build. A commercial tenant finish, A/V-heavy technology work, and venue projects are priced through a scoped consult while their estimate mode is still in build — the same honest distinction the feasibility study makes: real today, or a real path today, never a claim ahead of the code.

That is true whether the project is an ADU, a home remodel, a new build, a commercial tenant finish or a venue — every one of them gets priced against the same assemblies engine, whether the door into it today is the instant wizard or a scoped consult.

What it does

  • The instant estimate wizard runs a project through four steps and keeps the whole state serializable.
  • A trade router, jurisdiction resolver, catalog matcher, and crew labor calculator price the scope before a number is shown.
  • Code-compliance references attach to line items wherever the catalog has a human-verified citation.
  • A quantity validator checks inputs, and presentation settings — grouping, subtotals, notes, optional lines — are controlled by the team, not hard-coded.
  • Live, catalog-grounded pricing runs today for a home remodel, an ADU, and a modular new build.
  • A commercial tenant finish and technology-heavy projects still price through a scoped consult while that mode is in build.

What it sees

The example-lot estimate document (public, allowlisted) · live from GET /api/v1/estimate-documents/{token}; the website fetches it server-side with the example token and never renders the property field

What it replaced

Old phase: Procurement

Materials and trades locked before the schedule can slip.

Today sourcing runs on the same instant-estimate wizard: a trade router, a jurisdiction resolver, catalog matching, a labor calculator, and code-compliance references price the job before a lineup is locked.

This is where /process/procurement used to point.

Proof

  • 3,286 Catalog items costed
  • 3,290 Catalog items total
  • 275 Assembly components with a code reference
  • 11 Verified code citations

The example estimate document is not published yet.

The system layer

The system behind a price: the pipeline every scope runs through before a number is shown.

Topology

  • Trade router
  • Jurisdiction resolver
  • Catalog matching
  • Crew labor calculator
  • Code compliance references
  • Quantity validator
  • Partner price schedules
  • Presentation flags
  • Construction supplier scrapingdark
  1. Trade routerJurisdiction resolver
  2. Jurisdiction resolverCatalog matching
  3. Catalog matchingCrew labor calculator
  4. Crew labor calculatorCode compliance references
  5. Code compliance referencesQuantity validator
  6. Quantity validatorPartner price schedules
  7. Partner price schedulesPresentation flags
  8. Construction supplier scrapingCatalog matching (planned live pricing feed (not running))

The one-day clock

  1. 02:30Trade knowledge writes
  2. 03:00Citation checks
  3. every 2 hoursBuild-desk PR pulse

One replay

The example-lot estimate document (public, allowlisted) · live from GET /api/v1/estimate-documents/{token}; the website fetches it server-side with the example token and never renders the property field

Reveal the system layer

Questions

Why is my estimate a range instead of one number?

Because some quantities and site conditions aren't confirmed until later steps — a wider range means less is verified yet, a narrower one means more is.

Does the estimate include code requirements?

Where the catalog has a human-verified code citation for that line item, yes; the wizard doesn't invent a code reference it can't back up.

Can I get an instant estimate for a commercial buildout?

Not yet self-serve — commercial, along with A/V-heavy and edge-compute work, still prices through a scoped consult while that estimate mode is in build.

What is a jurisdiction resolver?

A step that checks which local building authority applies to the project, with an honest fallback when it doesn't recognize one, because code requirements vary by city.

Get an instant estimate

Next star: Design