OR turnover control plane that verifies terminal-clean steps and gets surgical rooms ready faster for multi-hospital systems.

1. Hospitals are now funding AI that acts inside physical rooms instead of only assisting with documentation.
2. Edge-native deployment reduces dependence on complex hospital IT integrations, which removes a major adoption blocker for physical-workflow software.
3. Infection control has a measurable outcome story now that the cited AI-plus-UV-C system reduced contamination by more than 93% in the referenced study.
4. OR turnover timing and staff movement are already named as core bottlenecks, giving the startup a narrow first workflow with immediate ROI.
5. Management’s stated expansion into cleanroom and pharmaceutical settings suggests the same control plane can grow beyond a single hospital workflow.

Catalyst. Shyld’s financing and cited 93% contamination reduction show hospitals are now funding room-native agents that can cut infection risk and unlock surgical capacity without a multi-year IT overhaul.

The product is a room-native operating layer for surgical turnover. It uses edge cameras and room sensors to detect case end, staff entry and exit, equipment removal, cleaning milestones, UV-C completion, and final readiness, then turns that activity into a live control plane for charge nurses and EVS leads. Each turnover gets an auditable sequence record, SLA clock, exception alerts for skipped steps, and a predicted ready time instead of a manual guess. Hospitals start with one site and a schedule feed rather than a heavy EMR integration, which shortens implementation and keeps the first ROI proof tied to turnover minutes, on-time starts, and infection-prevention compliance. Over time, the system builds a proprietary dataset on room patterns, staffing bottlenecks, and contamination-risk signatures that can power benchmarking and adjacent workflow automation.

What's different. Most healthcare AI vendors sell ambient note-taking, generic analytics, or horizontal computer vision that stops at observation. This company starts with a single high-stakes workflow where proving the exact order of physical steps matters, then turns those observations into operational decisions and audit evidence. The defensibility comes from room-level workflow data, service-line specific readiness rules, and integrations into perioperative operations rather than from a commodity model alone.

Jobs to be done

flowchart LR
  Buyer[VP Perioperative Services] --> Pain[Slow turnover and missed clean steps]
  Pain --> Product[Room-native turnover control plane]
  Product --> Outcome[More surgical capacity and lower infection risk]

Executive takeaways

• The wedge is the room-ready signal that schedule AI and UV-C hardware both leave incomplete.
• Hospitals will buy if the pitch ties directly to OR capacity recovery and infection-control evidence.
• The most defensible expansion path is multi-site benchmarking and workflow auditability, not generic computer vision.

Market definition

The relevant category is perioperative workflow software plus room sensing that can verify turnover completion, not the full OR-integration market or generic smart-hospital software.

Customer and buyer

Primary users are perioperative operations and infection-prevention teams; economic buyers are perioperative executives, nursing leaders, and COOs responsible for surgical throughput and quality exposure.

Buying triggers

• Throughput and margin programs make idle OR minutes and late starts newly visible to leadership. [16][15]
• HAI reviews or audit pressure make proof of cleaning sequence more valuable than manual logs. [2][3][10]
• Surgical-growth initiatives expose the gap between scheduled capacity and rooms that are actually ready on time. [19][4][5]

Willingness to pay

Hospitals already buy perioperative optimization when it shows volume, utilization, or cancellation impact. A room-native control plane is most fundable when sold as capacity recovery plus compliance evidence. [15][16][19]

Category dynamics

Growth signal 12.1% CAGR

Validation signals

• Hospitals already buy perioperative AI when it produces visible utilization or growth outcomes.
• Operational literature and AORN case work show that first-case starts and turnover discipline are persistent management problems with measurable upside.
• Shyld’s fundraise and product materials show room-native AI plus UV-C is moving from concept to budgeted deployment.
• Adjacent infection-control vendors continue to invest in OR-specific UV-C positioning, confirming buyer attention to room-readiness hygiene.

Regulatory & technical constraints

• Connected devices and room-sensing workflows must fit provider security-risk-analysis and ePHI protection practices.
• If the product markets direct clinical or disinfection-efficacy claims, evidence expectations move closer to adjacent device-cleared territory.
• Cleaning verification must map to accepted perioperative and environmental-cleaning practice or hospitals will treat alerts as advisory noise.

Incumbents cluster into schedule-layer AI, broad ambient-intelligence platforms, and disinfection hardware. None owns the room-state source of truth by default.

Why incumbents do not win by default

• Schedule optimization vendors. They optimize planned utilization but not verified in-room turnover completion.
• Smart hospital platforms. They have broad sensing breadth, but turnover-specific audit logic is not their default wedge.
• UV-C hardware vendors. They automate one cleaning step, not the full readiness sequence, alerts, and multi-site operating layer.
• Manual process improvement. Lean and accountability efforts improve starts, but they rely on recurring human enforcement instead of persistent room instrumentation.

Operating-room turnover is still coordinated through manual checklists, hallway handoffs, and partial system timestamps, even though each delayed clean pushes case starts back and each missed step raises infection-control exposure. The best first customer is a multi-hospital U.S. health system running 10-40 inpatient ORs per site with visible late-start or turnover-variance pressure, because the same buyer already owns both capacity and quality outcomes. The product wedge is an edge-deployed turnover control plane that verifies terminal-clean and UV-C completion, timestamps staff movement, and produces a trusted room-ready signal for charge nurses without requiring a heavy EHR replacement. Go-to-market should stay narrow: sell to perioperative leadership after a throughput initiative, HAI review, or surgical growth plan makes lost room minutes economically urgent, then start with a paid pilot on one campus before expanding across the system. Pricing should be tied to monitored rooms and implementation because buyers are purchasing recovered throughput and auditability, not generic AI automation. The strategic advantage is the room-level event dataset, service-line-specific readiness rules, and benchmark layer that schedule software, ambient platforms, and UV-C hardware do not own by default. The deliberate sequencing is to prove room-ready accuracy and pilot conversion in OR turnover before expanding into sterile processing, inpatient EVS, or regulated cleanrooms. The largest disconfirming risk is that hospitals treat the system as advisory only and do not operationally trust a single room-ready event enough to change staffing and scheduling behavior. Public evidence supports the pain and category momentum, but no public pricing or deployment counts are disclosed for the closest analog, so the first year must generate customer-owned proof on install friction, willingness-to-pay, and production conversion.

Problem

• Perioperative teams still lack a room-level source of truth for whether terminal-clean steps happened in sequence, so charge nurses rely on manual walk-throughs and fragmented logs to decide if the next case can start.
• Hospitals can already buy schedule optimization, RTLS, and disinfection hardware, but those tools do not verify actual room readiness, leaving throughput gains and infection-control accountability incomplete.

Solution

• Deploy a room-native control plane that uses edge cameras and sensors to detect case end, staff flow, equipment removal, cleaning milestones, UV-C completion, and final room-ready status in real time.
• Turn each turnover into an auditable sequence record with SLA clocks, exception alerts, and predicted ready times, starting from a schedule feed and local room instrumentation instead of a broad hospital IT overhaul.

Why we win

• The product sells one high-stakes operational decision, "is this OR actually ready now?", where proof quality matters more than breadth and where incumbent schedule tools or smart-hospital platforms do not currently own the workflow.
• Every deployment compounds a proprietary dataset of turnover events, exceptions, and benchmark patterns across campuses, which improves alert quality and creates expansion leverage into adjacent audited room workflows.

Milestones

flowchart LR
  Wedge[OR room-ready wedge] --> MVP[Room instrumentation and turnover control MVP]
  MVP --> Proof[Trusted ready signal plus audit proof]
  Proof --> Expansion[Multi-campus benchmark and adjacent workflow expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• Pilot campuses must show charge nurses acting on the room-ready signal in live operations within 90 days.
• The first 3 paid pilots must each reduce turnover variance or recover at least 5-10 median minutes per monitored room within one quarter.
• At least 50% of paid pilots must convert to annual production contracts within six months of pilot completion.
• Security, privacy, and facilities reviews must allow standard pilot deployment without custom governance work that turns every sale into a bespoke project.
• Gross margin must still trend above 70% after hardware support, implementation labor, and human exception review are included.

Open diligence questions

• How often do perioperative leaders currently quantify lost case capacity from turnover delays strongly enough to fund a new budget line?
• What false-positive or false-negative rate can charge nurses tolerate before they revert to manual room checks?
• Which stakeholder truly owns the budget: perioperative operations, infection prevention, EVS, or hospital operations leadership?
• How much installation and governance work is required before the first monitored room can go live?
• Do UV-C or perioperative AI partners accelerate sales, or do they complicate ownership of the room-ready signal?

Model sanity

• Revenue engine. The base case is driven by paid campuses growing from 3 at Y1 exit to 40 at Y3 exit while annual recurring revenue per campus ramps to the researched $270K steady state.
• Must go right. The company must prove a trusted room-ready signal and sub-eight-week deployment so first-campus pilots actually expand to second campuses inside the same health system.
• Model breaks if. If privacy reviews keep Y3 campus count in the low 30s or steady-state ARPU stalls near $240K, the cash cushion compresses sharply and the next round likely pulls forward.
• Next-round proof. The next financing is justified by reaching 8-10 production systems, showing second-campus expansion, and proving benchmark analytics can increase contract scope without a services-heavy reset.

Scenarios

Sensitivity

flowchart LR
  WorkflowAudits --> PaidCampuses
  PaidCampuses --> ActiveCampuses
  ActiveCampuses --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: Rule-of-40 looks unusually high because Y2 revenue is still small, so the metric overstates mature operating efficiency. · CAC and churn are modeled at the campus-equivalent level even though real procurement happens at health-system level, so cohort metrics are still heuristics until actual renewals exist. · Base-case margin improvement assumes implementation templates and exception handling reduce white-glove labor after the first few deployments. · The model excludes one-time deployment fees, which is conservative on revenue but means cash collection timing for services is not explicitly shown.

• Clinical trust failure. A missed or incorrect turnover verification could create infection risk and quickly kill credibility with perioperative leaders. Mitigation: Start with human-in-the-loop exception review, conservative alert thresholds, and audit trails tied to existing infection-control protocols.
• Room instrumentation friction. Cameras, sensors, and workflow monitoring can trigger privacy, facilities, and union concerns that slow deployment. Mitigation: Use edge processing with minimal retained footage, involve nursing and facilities leaders early, and begin in a limited pilot footprint with clear governance.
• Cross-functional budget ambiguity. Perioperative ops, infection prevention, EVS, and IT may all feel partial ownership, making procurement stall even when the pain is real. Mitigation: Sell against one quantified outcome such as turnover minutes recovered per OR, tie the champion to perioperative leadership, and package the first deployment as a capacity ROI pilot.