Multi-unit and new-construction bids mean an afternoon with a scale ruler, a highlighter, and a plan set the size of a door. SlabOS reads the plans and draws the counters — every cabinet run, every room, in one sweep.
Beta We're building this in the open. It already reads floor plans and elevations, detects counter areas, and lands live geometry in the editor — and it's getting better every week.
The plan set — floor plans and elevations, the same PDFs the builder sent you.
The countertops as live SlabOS geometry — detected, dimensioned, sitting in the drawing editor ready to price, nest, and render. Not a PDF markup.
Blueprint takeoff, the short version — plans in, live counters out.
You know the drill. A builder sends a plan set — forty units, twelve floor plans, a stack of elevations — and wants a countertop number. So someone in your office loses the afternoon to a scale ruler, tracing cabinet runs page by page and hoping nothing got missed.
Miss a splash. Misread a scale. Skip a bathroom on sheet A-402. The number's wrong before you ever send it.
Scale ruler on paper, room by room, sheet by sheet.
Splash heights and face details live on a different sheet than the layout.
The takeoff lives on paper. The quote lives somewhere else. You bridge them by typing.
On multi-unit work, a small miss multiplies across every unit.
The takeoff finds the cabinet runs on the floor plan and reads the countertop areas that sit on them.
Kitchen, baths, laundry, bar — every counter surface in the plan set, not just the page you're staring at.
Multiple views of the same room get merged into one picture — and open-concept spaces that show up on more than one drawing get deduped, so nothing counts twice.
Upload the plan set — floor plans and elevations together. The automated takeoff detects cabinet runs and countertop areas across the whole home in one pass. No tracing. No sheet-by-sheet slog.
And where the plans repeat a room from a different angle, SlabOS knows it's the same room — it merges the views instead of double-counting the stone.
A floor plan tells you where the counters are. The elevations tell you what they look like — and that's where bids quietly go wrong. SlabOS reads the elevation sheets and attaches them to the detected areas, so the vertical details ride along with the layout.
That elevation intelligence drives details like miter face heights — the kind of thing a plan-view takeoff never sees, and a fabricator always pays for.
The details that live on the elevation sheets — captured, attached, priced.
The software measures spans straight off the drawings and scales itself against the black lines — so the counters come in at drawing dimensions, whatever scale the architect printed at.
No "set the scale first" step — it reads the drawing and works it out.
A takeoff is only as good as its scale. SlabOS doesn't ask you to calibrate anything — it measures spans from the drawings themselves and scales the whole takeoff to match.
Then you shape the result. Spec-driven materials pull what the plans call for, and drag-and-drop refinement lets you correct, merge, or adjust anything the detection got close-but-not-quite on. It's a first draft you finish — not a black box you argue with.
Most takeoff tools hand you a marked-up PDF and a spreadsheet. SlabOS hands you the actual counters, drawn in the actual editor. Detected counters land as live SlabOS geometry — the same counters you'd have drawn by hand, minus the drawing.
The detected counters flow straight into the quote. Your price list, your edges, your splash — the bid builds from the same geometry the takeoff produced.
Because the counters are real geometry, they nest onto slabs like any SlabOS job — so your builder bid is grounded in actual material yield, not a square-footage guess.
The same counters render in 3D. Walk the builder through their own plans as finished countertops instead of a highlighted PDF.
Anything the beta gets close-but-not-perfect, you fix with the full drawing editor — the takeoff is a head start on the drawing, never a lock-in.
Takeoff, drawing, quoting, nesting, 3D, scheduling, inventory, the crew app — 150+ capabilities behind one login, one bill. Blueprint takeoff is one more door into the same platform: this one opens with a plan set.
Blueprint takeoff is in beta, and we're building it in the open. Here's what that means: it already handles whole-home detection from floor plans and elevations, self-calibrating dimensions, splash and fireplace geometry, multi-view room reconstruction, spec-driven materials, and live-geometry output into the editor. And because it's a beta, you review the result — drag-and-drop refinement is part of the workflow, not an apology. Every plan set that goes through it makes the detection better.
If you bid builder or commercial work from plan sets, we want your plan sets. Book a demo and bring one — we'll run it live.
Book a demo and bring a real builder plan set — we'll run the takeoff live, walk the detected counters in the editor, and price the bid in front of you.
Blueprint takeoff is in beta · one login, one bill · see pricing
The plan set — floor plans and elevations. The takeoff detects cabinet runs and countertop areas across the whole home, attaches elevations to the areas they belong to, and merges multiple views of the same room so open-concept spaces don't get counted twice.
No. The dimensions are self-calibrating — the software measures spans from the drawings and scales itself against the black lines of the plan.
No. Blueprint takeoff is for bidding from plans — builder and commercial work where you need a number before anything exists to measure. You'll still field-measure and template before you cut. What it replaces is the scale-ruler afternoon on the front end of the bid.
It means we're building it in the open. The core flow works — plans in, detected counters out as live geometry — and drag-and-drop refinement is part of the workflow so you can correct anything the detection gets close-but-not-quite on. It's improving continuously, and real plan sets are what improve it.
Live SlabOS geometry — not a PDF markup. The detected counters land in the drawing editor, where you can price them against your price list, nest them onto slabs, and render them in 3D like any other SlabOS job.
