wcisco17
Joined 4 years ago
Joined 4 years ago
The reality is people that work in construction (Excluding field work), refers to AI as a scam and compares it to the crypto hype back in 18 .. compares it to crypto in 2018 — all hype, no landing.. seriously they do not like it.
I built this selfishly. Eight months ago I wished I had a programmatic interface to interact with drawings. So I built one.
last point: our customers aren't just doing takeoffs and they aren't just subs or gc's either — they're building tools in the construction tech space and estimation is one use case. The broader opportunity is making all that structured data accessible.
great q!!
Also I didn't see Claude there "ai" tool (a bit weird they are letting the model providers own the entire interface) count any fixtures, and if it did it was probably pulling it from the markup's table which is enabled via their api, which you can technically just slap an llm on top of it. But hey kudos to them - this space is not easy. (https://developers.bluebeam.com/s/studio?language=en_US)
- Counting all the doors: https://www.getanchorgrid.com/developer/docs/endpoints/drawi... - Extracting schedules in architectural drawings: https://www.getanchorgrid.com/developer/docs/endpoints/drawi...
and use Claude or any other AI tool to wire up the UI
We're releasing toilets (division 10) later this week, then floors and pipes next.
we're thinking of adding a params for the ROC curve so that you can decide your own optimal thresholds depend on when false positive true positive rate is acceptable
so you would want these documents translated lets say to German, mandarin, ect?
The challenge we kept running into is that construction drawings in the wild aren’t always that clean. Unresolved xrefs, exploded dynamic blocks, version incompatibilities, SHX font substitutions — by the time a PDF hits a GC’s desk it’s often the only reliable artifact left. The CAD source may not even be available.
That’s why we see vision becomes the more pragmatic path — not because it’s more precise than structured CAD parsing, but because PDFs are the actual lingua franca of construction. Every firm, every trade, every discipline hands off PDFs. So we made a bet on meeting the document where it actually lives.
On consistency and reproducibility — that’s a real challenge with vision models. Our approach is to keep detection scope narrow and validate confidence scores on every output rather than trying to generalize broadly. Happy to go deeper on that if useful.
The generalization problem you're pointing at is real and it's the hardest part of this. Our approach is to keep the detection scope tight — rather than trying to generalize across every firm's conventions, we train on a small but high-quality set of fixtures and optimize for precision within that scope.
The result is high confidence outputs on the elements we support, rather than mediocre coverage across everything.
We're expanding the detection surface incrementally as we validate accuracy division by division!
Let me know if you find it useful or have any questions, happy to help.
https://cal.com/anchorgrid/anchorgrid-external-meeting?durat...