Drawing register

Proof, framed by what it demonstrates

A club platform is multi-tenant SaaS engineering. A drawing set becoming a priced bill is document intelligence. Read these for the engineering underneath rather than the industry on top, because the industry on top is the part least likely to be yours.

Five pieces of work: two live, one in build, one a prototype and one a proof of concept. Nothing here is described as more finished than it is. What each word means.

Sheet: A-01
Title: Work
Issued for: Information
Drawn by: Snilld

W-02Estimating from drawing sets

Document and drawing intelligenceManufacturing and fit-outProof of concept

Sheet W-02 · Document and drawing intelligence · Manufacturing and fit-out

Proof of concept

A multi-sheet drawing set becomes a priced bill of quantities in the format the tender already asks for, with unreadable lines flagged rather than guessed.

Goes in: A multi-sheet drawing set, exactly as the client sent it
What we built: Layout-aware extraction for the structured sheets, vision for the drawn ones
Comes out: A hierarchical bill of quantities in the manufacturer’s own tender spreadsheet
The line it does not cross: A line it cannot read is marked and left blank, never guessed

Note 1 · The constraint

A commercial estimator at a luxury interior fit-out manufacturer spends days reading client drawings before pricing can begin. Rushed bids lose margin. Slow bids lose the job. The company cannot install new hardware in the factory and cannot expose its ERP, so anything we build has to work from the files themselves.

Note 2 · What transfers

Any business that quotes from documents it did not author has this problem — tenders, specifications, schedules of work, supplier price lists. The reading is the bottleneck, not the arithmetic.

Stage: Proof of concept, in progress
Client: Anonymised
Inputs: PDF, DWG, DXF, XLSX
Integration: File in, file out. No ERP coupling.

The full write-up →

Legend

How to read this register

Four status words and two rules. The words are load-bearing: each one is a claim about how finished something is, and we use them literally.

Live: Running in production and used by people who are not us. If it says live, you can look at it.
In build: Being built now, with a client, against a date. Some of what is described is working and some of it is not finished.
Prototype: Demonstrates a design rather than carrying real load. Where the stored state is simulated instead of a production database, the facts panel says so.
Proof of concept: Proves the hard part works on real inputs. It is not a product and it is not in production.
Clients: Anonymised. No client is named unless they have given written permission, so most entries describe the organisation rather than naming it. The constraint and the engineering are described exactly as they are.
Numbers: No accuracy or confidence figure appears anywhere on this page, because none has been measured under conditions we would be willing to publish.

W-02Estimating from drawing sets

Note 1 · The constraint

Note 2 · What transfers

How to read this register

Two of these are platforms we operate