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

31–40 of 59 posts

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

#31

Post by aakashprasad91 »

an_aparallel wrote: post #29
aakashprasad91 wrote: post #4

Earlier quoted context omitted.

Totally fair callout and appreciate the feedback. We’re already testing alternative hero layouts focused purely on real customer results and example issues caught. Our goal is to win trust by demonstrating usefulness/results, not who invested in us.

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? Aside: this field is insanely frustrating, the chasm between clash detection and resolution is a right ball ache...between acc, revizto, and aconex clash detection (and the like)..the defacto standard is pretty much telling me x is…

We store files securely on AWS with strict access controls, encryption in transit and at rest, and zero sharing outside the file owner’s account. Only our engineers can access a project for debugging and only if the customer explicitly allows it. We can also offer an enterprise option with private cloud/VPC deployment for firms that require even tighter controls. Users can delete all files permanently at any time.

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

#32

Post by aakashprasad91 »

an_aparallel wrote: post #29
aakashprasad91 wrote: post #4

Earlier quoted context omitted.

Totally fair callout and appreciate the feedback. We’re already testing alternative hero layouts focused purely on real customer results and example issues caught. Our goal is to win trust by demonstrating usefulness/results, not who invested in us.

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? Aside: this field is insanely frustrating, the chasm between clash detection and resolution is a right ball ache...between acc, revizto, and aconex clash detection (and the like)..the defacto standard is pretty much telling me x is…

Yes one of the biggest values of our system is reducing “noise.” Instead of surfacing 2,000 micro-clashes, we cluster findings into higher-order issues (e.g., “all conflicts caused by this duct run” or “all lighting mismatches tied to this dimming spec”). We’re not a BIM viewer yet, but we do map issues back to sheet locations, callouts, and detail references so teams can navigate directly to the real source of the problem.

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

#33

Post by aakashprasad91 »

knollimar wrote: post #24

What kind of system to you have for parsing symbology? 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? edit: there's info that answers this on the website. It seems limited to the common ones (e.g. elec vs arch), which makes sense.

Symbol variation is a huge challenge across firms.

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.

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

#34

Post by an_aparallel »

aakashprasad91 wrote: post #32
an_aparallel wrote: post #29

Earlier quoted context omitted.

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? Aside: this field is insanely frustrating, the chasm between clash detection and resolution is a right ball ache...between acc, revizto, and aconex clash detection (and the like)..the defacto standard is pretty much telling me x is…

Yes one of the biggest values of our system is reducing “noise.” Instead of surfacing 2,000 micro-clashes, we cluster findings into higher-order issues (e.g., “all conflicts caused by this duct run” or “all lighting mismatches tied to this dimming spec”). We’re not a BIM viewer yet, but we do map issues back to sheet locations, callouts, and detail references so teams can navigate directly to the real source of the p…

Sounds good, what is the typical workflow aggregating sheet sets in question for a certain phase? I assume user collates and drops for analysis?

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

#36

Post by aakashprasad91 »

an_aparallel wrote: post #34
aakashprasad91 wrote: post #32

Earlier quoted context omitted.

Yes one of the biggest values of our system is reducing “noise.” Instead of surfacing 2,000 micro-clashes, we cluster findings into higher-order issues (e.g., “all conflicts caused by this duct run” or “all lighting mismatches tied to this dimming spec”). We’re not a BIM viewer yet, but we do map issues back to sheet locations, callouts, and detail references so teams can navigate directly to the real source of the p…

Sounds good, what is the typical workflow aggregating sheet sets in question for a certain phase? I assume user collates and drops for analysis?

Today the workflow is simple: users just drag-and-drop the full drawing/spec set (ZIP or PDFs) for whatever phase they want reviewed. The system automatically splits sheets by discipline, reconstructs callout relationships, and runs the checks. We’ll be adding integrations with ACC/Procore/Revit exports so this becomes even more automated.

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

#39

Post by aakashprasad91 »

breedmesmn wrote: post #38
aakashprasad91 wrote: post #37

Earlier quoted context omitted.

Could you share a bit more about what didn’t work on your end?

[flagged]

That comment comes across as racially loaded and isn’t helpful. If you ran into a real issue, I’m happy to take a look.

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

#40

Post by oscarmcdougall »

aakashprasad91 wrote: post #27
knollimar wrote: post #24

What kind of system to you have for parsing symbology? 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? edit: there's info that answers this on the website. It seems limited to the common ones (e.g. elec vs arch), which makes sense.

We parse symbols using a mix of vector geometry, OCR, and learned detection for common architectural/MEP symbols. Cross-discipline checks are a big focus as we already flag mismatches between architectural, structural, and MEP sheets, and we’re expanding into deeper electrical/mechanical spec alignment next. Would love to hear which symbols matter most in your workflow so we can improve coverage.

We're in a similar space doing machine assisted lighting take offs for contractors in AU/NZ, with bespoke models trained for identifying & measuring luminaires on construction plans.

Compliance is a space we've branched into recently. Would be super interested in seeing how you guys are currently approaching symbol detection.

Post reply on HN