Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 59 posts

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#11

Post by aakashprasad91 »

testUser1228 wrote: post #10

The bathroom height example in your video is really interesting (checking the bathroom height above the toilet against building code), how does it know when to check drawings against code provisions and how does it know which code to look at?

We infer the applicable codes from the project metadata + the drawings themselves.

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.

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#12

Post by testUser1228 »

aakashprasad91 wrote: post #11
testUser1228 wrote: post #10

The bathroom height example in your video is really interesting (checking the bathroom height above the toilet against building code), how does it know when to check drawings against code provisions and how does it know which code to look at?

We infer the applicable codes from the project metadata + the drawings themselves. 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 i…

Gotcha, so the model is identifying elements on the sheets and determining when to run code checks? Is the model running thousands of code checks per drawing set? I would imagine there are lots of elements that could trigger that

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#14

Post by aakashprasad91 »

frogguy wrote: post #13

Are you doing code checks for structural issues? If so, how do you deal with licensing on common code orgs, such as ASCE?

Great question. We currently focus primarily on coordination, dimension conflicts, missing details, and clear code-triggered checks that don’t require sealed structural judgment. For structural code references (e.g., ASCE-7), we infer applicable sections and surface potential issues for a licensed engineer to review. We don’t replace engineering judgment or sealed design accountability.

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#15

Post by aakashprasad91 »

testUser1228 wrote: post #12
aakashprasad91 wrote: post #11

Earlier quoted context omitted.

We infer the applicable codes from the project metadata + the drawings themselves. 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 i…

Gotcha, so the model is identifying elements on the sheets and determining when to run code checks? Is the model running thousands of code checks per drawing set? I would imagine there are lots of elements that could trigger that

Yep, the model identifies objects/conditions on sheets (fixtures, stairs, rated walls, landings, etc.) and triggers the relevant checks automatically. It can run thousands of checks per project, but we only surface high-confidence findings where the combination of geometry + annotations + code context points to a real risk. Humans stay in the loop to confirm what matters.

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#16

Post by knollimar »

Doerge wrote: post #6

I love this! 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?

BIM just shuffles the problem around. There are firms that do "one source of truth" BIM models but the real issue is conflicts and workflow buy in.

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?

edit: if you don't work in the industry, BIM helps for "these two things are in the same spot", but not much for code unless it's about clearance or some spatial based calculation

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#18

Post by aakashprasad91 »

knollimar wrote: post #17

Is the pay as you go model % based or project sized? I've had issues with conflicts of interest of being lean vs not. It's hard to sell on % based revenue. Also who is this targetted at? Subcontractors, GC, design?

We price per-project based on size/complexity not % of construction cost, so there’s no conflict of interest around bigger budgets. Today our main users are architects/engineers and GC pre-con teams, but subs who catch coordination issues early also get a ton of value.

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#19

Post by aakashprasad91 »

knollimar wrote: post #16
Doerge wrote: post #6

I love this! 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?

BIM just shuffles the problem around. There are firms that do "one source of truth" BIM models but the real issue is conflicts and workflow buy in. 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? edit: if you don't work in the industry, BIM helps for "these two things are in the s…

100% agree the hardest problems are workflow and incentives, not file formats.

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.

Re: Launch HN: InspectMind (YC W24) – AI agent for reviewing construction drawings

#20

Post by knollimar »

aakashprasad91 wrote: post #18
knollimar wrote: post #17

Is the pay as you go model % based or project sized? I've had issues with conflicts of interest of being lean vs not. It's hard to sell on % based revenue. Also who is this targetted at? Subcontractors, GC, design?

We price per-project based on size/complexity not % of construction cost, so there’s no conflict of interest around bigger budgets. Today our main users are architects/engineers and GC pre-con teams, but subs who catch coordination issues early also get a ton of value.

At what stage do you run this on plans? like DD, some % CD? What's the intended target timeframe?

I don't see how subs get much value unless they can use it on ~80% CD for bid phases

Post reply on HN