A real plan set, taken off inside the quoting engine — captures land on the canvas as editable counters.
Multi-unit and new-construction bids mean an afternoon working the set one counter at a time — a plan set the size of a door, nothing allowed to get missed. SlabOS reads the plan set up front — every vector, every ink line — so a counter goes from drawing to real geometry in one click. Every cabinet run, every room, every unit.
Beta We're building this in the open. It reads floor plans and elevations, detects counter areas and lands live geometry in the editor — and on production telemetry the first-shot clean rate has gone from 73% to 97%. The numbers, caveats included, are further down.
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.
Throw a rough box around a counter and the engine takes the largest complete shape inside it. Or just click inside an outline.
Click corner to corner and it snaps to the drawing's real lines. Enter to close. No sheet is un-takeoffable, however messy.
Place sinks and cooktops from your own catalogue, or punch the hole using the plan's own fixture linework.
Drag a vertex or re-trace a shape and the raw detection is stored against your corrected one, so it learns which ink was really the counter.
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 it, working through the set one counter at a time, page by page, 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.
One counter at a time, 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 takeoff reads the whole plan set before you touch it, so every counter on every sheet is one click away — kitchen, baths, laundry, bar. No working counter by counter. 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.
And when you commit, the marked-up plan is filed against the quote — every counter you captured, named, coloured by area and dimensioned, on the builder’s own drawing.
Every capture carries the area you assigned it to, in that area’s colour — kitchen, laundry, bar — so the plan reads at a glance.
Each counter is labelled with its own area, dimensioned edge by edge. Nothing to re-measure off the sheet later.
Kitchen sink, bar sink, bathroom sink — each one named where it sits, not listed in a schedule somewhere else.
The marked-up plan lands in the quote’s Files on commit and stays there. Six months on, you can show exactly what was taken off and from which sheet.
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.
What the elevation sheets carry — captured and attached to the right area.
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.
Most software in this trade tells you a feature works. Here are the actual numbers off our production telemetry, including the parts that aren’t finished yet.
Measured across 40 takeoff sessions, 364 sheets classified and 129 committed regions. Per document the clean rate ran from 100% and 96% on vector plan sets down to 33% on a scanned one.
The honest caveat. If somebody deletes a detected piece and traces it themselves, that leaves no correction behind to count — so the true “engine got it right” rate sits somewhere between 62% and 89%, not at 89% flat. We’d rather publish the range than the flattering end of it.
And what’s still manual. Shape detection is largely solved on vector plan sets. Edge typing is not — it’s the single biggest remaining click cost, and it’s what we’re working on next. Scanned sheets are the weak spot too, though they were only 3.4% of the thousand-page corpus we measured.
Every correction anyone makes is stored against the raw detection, so the engine learns the difference. That’s why the number moved from 73 to 97 — and why we want your plan sets. Book a demo and bring one, we’ll run it live and you can watch where it wins and where it doesn’t.
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 reads the whole set up front, so a counter goes to real geometry in one click; it attaches elevations to the areas they belong to, surfaces the comments written on them, and merges multiple views of the same room so open-concept spaces are not 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 one-at-a-time 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.
