Why deterministic
An estimate is a commitment. The numbers in it should come from the drawing's geometry, not a model's best guess.
The engine matches exact vector geometry — the shapes the CAD system drew — not a probabilistic guess over pixels. Re-run a sheet a hundred times and the totals never move. When a count is challenged at tender stage, you can click any number and see every location it came from.
Vision models do what they're good at — reading legend rows, pre-sorting the review queue — and nothing else. Every count comes from geometric matching, and every uncertain detection waits for a human decision. No hallucinated totals in your bid.
Distinctive symbols confirm automatically. Look-alikes, partial matches and drawing-edge cases land in a review queue you can clear with two keys — j to move, y to confirm. A sheet that took an afternoon of clicking becomes minutes of review.
Workflow
Drop the tender PDF. Sheets are triaged instantly — vector, scanned, or schedule pages — and grouped under the project.
Opening a sheet runs the engine: it reads the legend, matches every symbol's geometry across the drawing, and assigns each find to a class.
Confident matches confirm themselves. The rest queue up with thumbnails — confirm or reject from the keyboard, reclassify with one click.
Finalize the sheet and export XLSX or CSV. Every number stays traceable back to its locations on the drawing.
Features
The engine finds the legend or key on the sheet, extracts every row, and counts each symbol class across the drawing — one class per row, colors assigned, ready to review.
Legend drawn as a raster image, or on a cover sheet? Drag a box around it and a vision model reads the rows; the deterministic matchers still do all the counting.
Thumbnails of every flagged detection, j/k to move, y/n to decide, per-class bulk confirm. The queue is ordered so the same decision repeats — clear fifty items in a minute.
Place a few instances of a symbol the legend missed and the engine uses your placements as templates to recover the rest of the family across the sheet.
Tender packages stay grouped: one project per job, drawing sets inside it, per-sheet progress, and a drawer to flick between sheets while you work.
Finalized counts export to a clean spreadsheet — class, count, sheet — ready to price in your estimating workflow. CSV too, if that's your pipeline.
Built for your trade
Sockets, switches, luminaires, data outlets — including twin/single variants that fool pixel-based tools.
Detectors, sounders, call points, beam pairs — device schedules with the exact tags your drawings use.
Grilles, diffusers, valves, dampers — scheduled symbols across plant and distribution layouts.
Questions
The engine is precision-first: it only auto-confirms a count when the geometry matches distinctively, and everything uncertain goes to the review queue rather than into your totals. You always see — and can audit — exactly what was counted where.
PDF drawing sets — native CAD-exported vector sheets give the best results, and scanned/raster sheets are supported through AI-assisted legend reading with template matching. DWG support is on the roadmap.
Drawings are stored encrypted in the UK (London region), scoped to your organization, and never used to train models. Deleting a drawing set removes the file.
Free while in early access — upload a real tender package and see your counts in minutes.
Get started free