Key Features
Tech Stack
Isn't the target persona someone who'd be at best indifferent, and at worst distrustful, of a tech product that leads with how many people invested in it? Especially vs the explanation and actual testimonials you're pushing below the fold to show that?
Also, where would my firms documents end up (on whos servers) to do this checking? I dont know how any firm would just hand out their cd's just like that?
Or is being that lax normal these days?
how does this work behind the scenes?
Stupid question: Would BIM solve these issues? I know northern Europe are somewhat advanced in that direction. What kind of digitalization pace do you see in the US?
How do you get architect to agree with engineer with lighting designer with lighting contractor when they all have different non overlapping deadlines, work periods, knowledge and scope?
Even with a perfect BIM model, late changes and discipline silos mean drawings still diverge and coordination issues sneak through.
We’re trying to be the “safety net” that catches what falls through when teams are moving fast and not perfectly in sync.
The location + occupancy/use type tells us the governing code families (e.g., IBC/IRC, ADA, NFPA, local amendments), and then we parse the sheets for callouts, annotations, assemblies, and spec sections to map them to the relevant provisions.
So the system knows when to check (e.g., plumbing fixture clearances) because of the objects it detects in the drawings, and it knows what code to check based on jurisdiction + building type + what’s being shown in that detail.
The model still flags with human-review intent so designer judgment stays in the loop.
Also who is this targetted at? Subcontractors, GC, design?
I don't see how subs get much value unless they can use it on ~80% CD for bid phases
Do you check anything like cross discipline coordination (e.g. online searching specification data for parts on drawings like mechanical units and detecting mismatch with electrical spec), or it wholly within 1 trades code at a time?
One big issue Ive had is drafters use the same symbol for different things per person. One person's GFCi is another's switched receptacle. People use the specialty putlet symbol sometimes very precisely and others not. Often accompanied by an annotation (e.g. 6-15R).
Dimmers being ambiguous is huge; avoiding dimming type mismatches is basically 80% the lutron value add.
Compliance is a space we've branched into recently. Would be super interested in seeing how you guys are currently approaching symbol detection.
Our approach mixes OCR, vector geometry, and learned embeddings so the model can recognize a symbol plus its surrounding annotations (e.g., “6-15R,” “DIM,” “GFCI”).
When symbols differ by drafter, the system leans heavily on the textual/graph context so it still resolves meaning accurately. We’re actively expanding our electrical symbol library and would love sample sets from your workflow.
Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.