From the drawing to the takeoff to the estimate: an open vocabulary for the people who price the work, built sample by sample from real drawing sets on published classification standards, with its open questions in public view.
REAL SCREEN CAPTURE · THE REVIEW TOOL AT app.openbeam.ca, NOT A MOCKUP
The problem, then the fix
BEFORE
The same baseboard leaves the architect as a legend code, reaches the estimator as a guess, and reaches the trade as a phone call. Between each hop the data dies and gets re-typed.
WITH OPENBEAM
A component earns a name when a real document demands it. Over 200 named so far, most still drafts, each one traceable to the sample that produced it.
THE RESULT
Access is by invitation. A few minutes per item: do you recognise it, what do you call it, is the definition right, what is missing.
Proof
Not invented: OpenBEAM is built on published classification standards, not a taxonomy of its own. It is early, and its own front page says so; the studio says the same here. The estimating company of the studio, Cairo.so, is the first product built to speak it.
What one shared name does at each hand-off
A project-local legend code gets a name that means the same thing outside this drawing set.
No re-typing into a spreadsheet, no meaning reconstructed by hand.
Priced against a definition, not a memory and a call-back.
Drafts are marked as drafts. What is unresolved is visible.
Estimators answer a few questions per item, however they like.
Grows deterministically: a new name only when a real document demands it.