aakashprasad91

4 ms·

1.
InspectMind AI (YC W24) Is Hiring(ycombinator.com)
1 points by aakashprasad91 6mo ago
2.
by aakashprasad91 9mo ago
This is exactly the hard part symbols aren’t enough when each drafter overloads them, so we lean on the annotation + schedule context (fixture tags, notes like “DIM,” control zones, panel/ckt callouts, and control intents) to disambigu
3.
by aakashprasad91 9mo ago
Yep, exactly, when layer data survives the PDF export, it’s a huge help. We use it as a weak signal for clustering and object grouping, but never rely on it fully since it’s often inconsistent or stripped. When it’s there, accuracy and spee
4.
by aakashprasad91 9mo ago
Starting on their first project! Thank you!
5.
by aakashprasad91 9mo ago
Awesome — thank you! Easiest is email: aakash@inspectmind.ai or they can book a demo call on our website or upload plans directly on website. If they can share (1) a representative drawing/spec set (or a small sample) + (2) what trade&
6.
by aakashprasad91 9mo ago
We do best on CAD-originated PDFs where we can use the underlying vector data, but we can run on scanned/hand-drawn sets too. In that case we rely more on image-based detection + OCR (no clean vector layer), so accuracy depends on scan
7.
by aakashprasad91 9mo ago
Great question. By “vector geometry” we mean we’re using the underlying CAD-style vector data embedded in many PDFs (lines, arcs, polylines, hatches, etc.), not just raster images. We reconstruct objects and regions from that geometry, then
8.
by aakashprasad91 9mo ago
Great point! Owner’s reps and commissioning teams are becoming one of the fastest-growing user groups for us. At SD/DD we can surface coordination risks early, highlight spec–drawing mismatches, and give owners a clearer picture of des
9.
by aakashprasad91 9mo ago
Happy to swap notes. If you send a representative lighting plan set, we can run it and share how the detector clusters, resolves, and cross-references symbols across sheets. Always excited to compare approaches with teams solving adjacent p
10.
by aakashprasad91 9mo ago
Hallucinations still happen occasionally, but we bias heavily toward high-confidence findings so noise stays low. On typical projects we surface a few hundred coordination issues that are real, observable conflicts across sheets rather than
11.
by aakashprasad91 9mo ago
Yes today users simply gather the sheets for whatever phase they want reviewed (DD, 80% CDs, 100% CDs, etc.), ZIP them or upload PDFs directly, and the system handles the rest. It auto-detects disciplines, reconstructs callout graphs, and r
12.
by aakashprasad91 9mo ago
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.
13.
by aakashprasad91 9mo ago
Could you share a bit more about what didn’t work on your end?
14.
by aakashprasad91 9mo ago
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 th
15.
by aakashprasad91 9mo ago
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 d
16.
by aakashprasad91 9mo ago
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
17.
by aakashprasad91 9mo ago
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 allo
18.
by aakashprasad91 9mo ago
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,
19.
by aakashprasad91 9mo ago
We’d love that — perfect use case. Send a recent set and we’ll run a discounted comparison so you can see what we catch vs. what surfaced during construction. If helpful, we can hop on a quick call to walk through results and collect feedba
20.
by aakashprasad91 9mo ago
Most teams run us late DD through CD anywhere the set is stable enough that coordination issues matter. Subs especially like running it pre-bid at ~80–100% CDs so they don’t inherit coordination risk. Earlier checks also help designers tigh
21.
by aakashprasad91 9mo ago
We see that a lot — specs that are clearly boilerplate or outdated relative to the drawings. Our goal isn’t to force a change, but to surface where the specs and drawings diverge so the designer can quickly decide what’s intentional vs what
22.
by aakashprasad91 9mo ago
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 “safet
23.
by aakashprasad91 9mo ago
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 coordinatio
24.
by aakashprasad91 9mo ago
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 find
25.
by aakashprasad91 9mo ago
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 appli
26.
by aakashprasad91 9mo ago
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 f
27.
by aakashprasad91 9mo ago
BIM definitely helps, but most projects still rely heavily on 2D PDFs for coordination and permitting especially in the US. Even when BIM exists, drawings often lag behind the model and changes don’t stay perfectly synced. We see AI plan ch
28.
by aakashprasad91 9mo ago
Totally! Division 10 and specialty trades are often the first to see coordination issues show up in the field. We’re trying to bring that same early-warning benefit across the entire drawing set so errors never make it to construction. Woul
29.
by aakashprasad91 9mo ago
Great questions. We’re working on a more formal public benchmark and will share results as our dataset grows. Today, we typically catch coordination issues like conflicting dimensions, missing callouts, building code and clearance violation
30.
by aakashprasad91 9mo ago
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 i

More ›