Complex hospital wall installations combine medical gas piping, water lines, electrical (primary and backup) outlets, and network ports in tight spaces. Off-script changes or misaligned piping cause installers major difficulties and costly errors. Existing tools provide limited multi-system overlay and conflict detection in construction environments.
“MepCheck is a mobile app that lets hospital construction field supervisors photograph existing pipe and conduit layouts and instantly flags NFPA 99, NEC, and fire suppression conflicts—no BIM model required. It targets the change-order and as-built verification workflow that Navisworks and Revit are architecturally incapable of serving.”
A software tool that allows engineers and installers to input or scan existing piping and conduit layouts and runs an AI-powered conflict detection algorithm to flag crossover, clearance violations, or incompatible connections. It supports visualization with layered views and recommends re-routing to minimize risk.
Advances in AI and 3D scanning technologies make real-time conflict detection in complex construction feasible and valuable.
Field supervisor or lead installer (journeyman or foreman level) at a mid-to-large MEP mechanical contractor running hospital renovation or new-build projects; non-BIM user, smartphone-native, accountable for RFIs and change-order documentation.
US hospital construction MEP spend ~$30B/yr (15% of $200B total); targeting field verification tooling at $500/user/yr across an estimated 80,000–100,000 field supervisors on hospital projects yields a serviceable market of $40–50M; realistic 3-year capture at 0.5% share = $200–250K ARR.
Build a Framer landing page describing the tool with a $49/mo pre-order Stripe link and a 'Book a 20-min demo' Calendly. DM field supervisors who commented on the r/Construction medical gas thread and post in r/hvac and r/construction with a Loom video showing a manual concierge version: supervisor sends you a photo, you return a conflict report within 2 hours using a spreadsheet rule checklist.
5 pre-orders at $49/mo OR 3 paid concierge sessions at $150 each within 2 weeks—either signals willingness-to-pay before writing a line of code.
None of the listed YC companies are direct competitors — Persana AI, co.dev, Vellum, and Multifactor operate in entirely different domains, while Merlin AI is the closest adjacency as a construction ERP but focuses on business operations rather than technical conflict detection. The actual competitive landscape includes established AEC (Architecture, Engineering, Construction) software players like Autodesk Navisworks and Bentley OpenPlant, which offer clash detection but are heavyweight, expensive, and not purpose-built for hospital MEP (mechanical, electrical, plumbing) installations. Smaller players like Procore integrate project management but lack real-time, on-site conflict detection for complex multi-system environments. The gap is a lightweight, field-deployable tool specifically tuned for healthcare facility construction with medical gas regulatory compliance built in.
Clash detection and coordination software for 3D model review in AEC projects, integrating multiple file formats for conflict identification.
Plant design software with clash detection for piping, instrumentation, and MEP systems in industrial and building projects.
Construction management platform with some RFI and submittal tools for field issues, but limited native clash detection.
Cloud collaboration platform with 3D model viewing and basic clash detection for construction teams.
Mobile-first field management app for task tracking, plans, and issues, with photo markup but no AI conflict detection.
Field collaboration tool for blueprints, tasks, and RFIs with mobile sheet viewing.
AI-powered construction progress tracking via photo analysis and issue detection.
AI 3D site capture from photos for progress tracking and quality control.
Existing tools like Navisworks require full BIM model imports and trained operators — a significant barrier for on-site installers and field engineers who need quick conflict resolution during active construction. A mobile-first, scan-and-detect tool designed for field use with healthcare-specific rule sets (NFPA 99 medical gas standards, NEC electrical clearances, infection control zones) would address a workflow that enterprise BIM tools explicitly ignore. Vertical specialization in hospital construction also creates a natural moat through compliance library depth and installer workflow integration.
The only conflict detection tool that works on a smartphone photo with zero BIM model—purpose-built for the change-order moment on legacy hospital floors where every other tool breaks down.
We are the field verification layer for hospital MEP installers who live on the job site, not in Revit.
Compliance library depth (NFPA 99 + NEC + local AHJ rules) becomes a defensible asset as edge cases are documented from real field reports; each project generates training data that improves photo parsing accuracy, creating a data flywheel competitors cannot replicate without field deployments.
Field supervisors on hospital renovation projects aren't asking for better BIM—they're asking for a tool that works when the drawings are wrong or missing, which is the default state on any floor built before 2010; every incumbent is architecturally blind to this because they were designed assuming a model exists.
Autodesk or Bentley could add healthcare-specific conflict detection modules to Navisworks or Revit, neutralizing the core differentiatorHospital construction projects are long-cycle and relationship-driven — sales cycles could stretch 12-24 months with heavy procurement bureaucracyRequires significant domain expertise in medical gas piping codes (NFPA 99), electrical (NEC), and fire suppression standards to build accurate rule enginesMarket is somewhat niche — healthcare construction is a subset of a subset, limiting total addressable market unless the tool generalizes to other complex facility types like data centers or labsLiability exposure is high — if conflict detection misses a critical clash resulting in a patient safety incident, the company could face serious legal risk
The construction field is heavily reliant on relationships and long-established workflows. Disruption is a tough sell in environments where contractors have invested in other tools and practices. Beyond competition from Autodesk, the risk of creating a reliance on mobile technology may panic traditional contractors who rely on paper-based methods, leading to high churn rates if the technology is not seamlessly integrated into their workflow. Moreover, unforeseen regulatory changes regarding safety standards could constantly require updates in the tool, posing operational challenges.
{"PlanGrid initially struggled to gain traction despite their promise of simplifying field communication due to the pushback on shifting established construction workflows toward a more digital experience.","Fieldwire, while acquired by Autodesk, faced challenges in evolving beyond a task management tool to effectively compete in the world of BIM and sophisticated conflict detection.","Budgets and project capacity within hospitals may constrict investment for non-essential tech, as noted when tools like CMiC, designed for construction management, failed to specifically address niche needs, leading to stagnant adoption rates."}
The startup claims to address a unique moment in the construction workflow that large players ignore, yet many big players have vast resources for R&D and could pivot quickly to penetrate this niche if they see it as lucrative. The 'why now' factor is also undercut by the fact that various issues in construction have been known for years, but the industry has been slow to change, indicating possible inertia that this app may not overcome. Furthermore, the promise of direct savings might not resonate enough with cost-conscious hospital administrations, leading to difficulty in selling the ROI justification.
Viable opportunity in underserved field-verification niche for hospital MEP, where incumbents like Navisworks/Procore dominate design/PM but fail real-time, mobile, non-BIM conflict detection. Landscape fragmented: heavy BIM tools entrenched but office-bound; field apps lack AI rules. Most dangerous are Autodesk ecosystem (Navisworks + Fieldwire/PlanGrid acquisitions). Best breakthrough via hospital reno supervisors, NFPA-tuned mobile scans exploiting rework pain points amid 17% contech growth.
Step 1: Reply to the r/Construction medical gas thread and DM the 5–8 users who commented with a link to a free concierge conflict check. Step 2: Email the program directors of 3 SMACNA regional chapters offering a free 'NFPA 99 field audit checklist' PDF in exchange for intro calls with member field supervisors. Step 3: Search LinkedIn for 'MEP field supervisor hospital' + 'Comfort Systems' or 'Tradewinds,' send 30 cold DMs offering a free conflict report on their current project photo.
$49/mo solo supervisor (1 user, 10 reports/mo); $129/mo team (up to 5 users, unlimited reports); 14-day free trial, no credit card required; annual plans at 2 months free.
A single avoided rework event on a hospital MEP project costs $2,000–$15,000 in labor and materials; $49/mo is noise relative to catching even one conflict per quarter. Fieldwire charges $54–89/user/mo for far less specialized functionality, anchoring market expectations above $49.
User photographs a pipe layout section and receives a flagged NFPA 99 clearance violation with a plain-language fix within 60 seconds of signup—before they've even talked to sales
If hospital-only TAM proves too small to reach $500K ARR, apply the same photo-scan + rule engine to data center power/cooling separation and lab gas/ventilation codes—same core tech, swap compliance library
If field supervisors won't pay but their ops managers or safety directors will, pivot to a project-level compliance dashboard sold to contractor HQ at $500–1,500/project instead of per-user monthly
If direct CAC exceeds $400 with no improvement, package the NFPA 99 rule engine as a Procore App Marketplace or Fieldwire integration—distribution through existing field tool user base
React Native (Expo) + Supabase + OpenAI Vision API for photo parsing + Stripe; rule engine as a JSON-configured compliance library
6–8 weeks solo dev; weeks 1–2 rule engine + input UI, weeks 3–4 photo parsing + conflict output, weeks 5–6 PDF report + Stripe billing
Strong problem specificity and a genuine gap in the competitive landscape earn high marks, but the niche TAM (hospital MEP field supervisors only), high liability exposure requiring legal infrastructure before revenue, and dependence on photo-parsing accuracy that isn't yet validated keep the score from reaching the 80s—this is a viable but execution-risk-heavy opportunity that lives or dies on fast manual validation and a very tight initial wedge.