Screening deployment OS for women's-health networks launching rapid HPV testing, routing results into same-visit referral and follow-up.

1. Bridge capital earmarked for IP, pilot manufacturing, and seed preparation suggests lab-free HPV testing is moving from science story to rollout reality, which is exactly when operators need deployment software.
2. A platform that works without centralized labs or external power shifts screening into distributed sites where legacy LIS and paper workflows break down.
3. PCR-quality molecular detection with a roughly 30-minute color-change result makes same-visit referral and counseling operationally possible for the first time in these environments.
4. If the same platform is meant for home, clinic, and resource-limited settings, operators will need one control layer that standardizes quality and follow-up across very different site types.

Catalyst. Intu's financing and reported pilot-manufacturing push make lab-free HPV testing feel operationally imminent, while the 30-minute anywhere-result format creates urgency to build the workflow layer that preserves that speed in real-world programs.

Rapid HPV Screening Ops gives every decentralized screening site a lightweight workflow app and a supervisor dashboard. Staff register each cartridge, record the result, and launch the next protocol step such as patient counseling, referral booking, or follow-up outreach from one flow instead of paper logs and callbacks. Program leaders see stock levels, invalid-test rates, completion by site, positive-result queues, and referral closure across the network. The first version is explicitly a deployment and follow-up operating system, not a diagnostic interpretation product, which keeps the wedge measurable and operational. Over time it becomes the system of record for decentralized molecular screening programs across many disease categories.

What's different. Most screening software is built either for centralized laboratories or for patient engagement after the fact. This product is designed for the messy middle: decentralized molecular testing that still needs chain-of-custody, protocol compliance, and referral completion across many low-infrastructure sites. The moat compounds through site-level performance benchmarks, workflow templates tuned to rapid diagnostics, and integrations that make the platform the operational system of record around each screening episode.

Jobs to be done

flowchart LR
  Buyer[Screening program ops lead] --> Pain[Decentralized HPV tests break result and follow-up workflows]
  Pain --> Product[Rapid HPV Screening Ops]
  Product --> Outcome[More completed referrals fewer lost positives and scalable screening rollout]

Executive takeaways

• The pain is real and immediate: once rapid HPV testing leaves the central lab, the operational choke point becomes result capture, referral closure, and quality control across dispersed sites.
• The market is not winner-take-all yet; buyers can patch together EHR, DHIS2, CommCare, or OEM tools, but none is purpose-built for decentralized HPV same-visit operations.
• The sharpest near-term wedge is not diagnostic interpretation but auditable workflow orchestration around same-day counseling, referral, and follow-up.
• The best early customers are organized screening operators already expanding self-collection or rapid-HPV pilots with donor, OEM, or public-health funding attached.

Market definition

A vertical operations layer for decentralized HPV screening programs: test registration, result capture, protocol enforcement, referral tracking, and program analytics across satellite, community, pharmacy, and mobile sites.

Customer and buyer

Primary economic buyer is the screening-program operations lead or medical-operations owner of rollout KPIs; daily users are site supervisors, nurses, and referral coordinators who need lightweight field workflows.

Buying triggers

• A funded push to reach the WHO coverage target or a national/provincial program redesign around HPV testing creates urgency to standardize workflows across sites. [1][4][5][14]
• A self-collection or rapid-HPV pilot that moves screening beyond the exam room exposes gaps in labeling, chain-of-custody, and referral follow-up. [9][10][11][37][38]
• Programs that already spend labor on recalls and navigation are primed to buy if software can improve closure rates or reduce repeat outreach. [6][7]

Willingness to pay

Buyers are likeliest to fund the product when it is attached to a concrete rollout or grant and when it can credibly reduce lost-to-follow-up, repeat outreach effort, or invalid/uncaptured episodes; a generic analytics-only pitch is unlikely to clear budget review. [6][7][12][13]

Category dynamics

Growth signal Policy-led expansion rather than a clean commercial CAGR; the implied screening volume must rise materially from today's low coverage toward the WHO 70% target.

Validation signals

• WHO and national actors keep pushing toward high-performance HPV screening and coverage expansion.
• CHAI and Unitaid have already lowered key hardware costs and are funding real screen-and-treat deployments in multiple countries.
• Guidelines and approvals are opening self-collection and nontraditional care settings, increasing workflow complexity for operators.
• Recent Intu financing specifically signals that lab-free, low-infrastructure HPV testing is becoming operationally plausible rather than purely aspirational.

Regulatory & technical constraints

• Health-data handling in Europe is moving toward stricter interoperability, access control, and privacy obligations under the EHDS and adjacent rules.
• If the product crosses from workflow orchestration into diagnostic or management recommendation logic, MDR/IVDR software questions become materially more important.
• Offline-first capture is not optional in many target settings, but poor sync design can create duplicate episodes or orphaned referrals.
• Interoperability across clinician-collected, self-collected, near-point-of-care, and lab-based assays will be necessary if the product is to stay vendor-neutral.

Competition is fragmented. Organized-screening suites, generic field-workflow platforms, public-sector trackers, and EHR-integrated guideline tools all overlap with parts of the job, but no single category cleanly owns decentralized HPV result-to-referral operations.

Why incumbents do not win by default

• Diagnostic OEMs. They control assays, validation, and some program software, but they do not win by default because buyers often need a vendor-neutral workflow layer spanning multiple site types, referral pathways, and legacy systems.
• Generic workflow platforms. Platforms like CommCare can solve offline data capture and tasking, but most of the cervical-specific protocol logic, analytics, and integrations still become implementation work.
• Public-sector HMIS stacks. DHIS2-class systems are strong for reporting and supervision, but weaker at same-visit operational control and closed-loop referral execution at the edge.
• EHR/LIS and guideline tools. EHR-embedded tools can provide rules and record-keeping, yet they typically assume better infrastructure and do not naturally manage mobile, pharmacy, or outreach site operations.

Rapid HPV Screening Ops is a workflow platform for women's-health screening operators launching decentralized rapid HPV programs across 20 to 100 satellite, mobile, pharmacy, or community sites. The product's job is not diagnostic interpretation; it is to make every screening episode auditable from test registration through result capture, counseling, referral, and follow-up. The initial beachhead is donor-funded or private clinic networks rolling out rapid-HPV or self-collection pilots, because those programs have a visible launch event, measurable rollout KPIs, and enough site repetition to support a product instead of custom services. Go-to-market starts with high-touch deployments sold against referral-closure improvement, lost-to-follow-up reduction, and invalid-episode reduction, not a generic analytics pitch. Product sequencing stays vendor-neutral and operational so the first release can interoperate with multiple assay and reporting environments without taking on avoidable diagnostic-software regulatory burden. The main disconfirming risks are hardware adoption timing, slow public-health procurement, and whether OEMs expose enough event data to reduce manual entry. Research supports a roughly $120.0M serviceable market for organized multi-site programs and a modeled $3.0M year-three SOM, which justifies a disciplined pre-seed wedge but not a broad category land-grab yet. Missing facts that matter for underwriting are real reimbursement behavior, OEM data-sharing willingness, and whether buyers will fund this from operating, grant, or diagnostic rollout budgets.

Problem

• Rapid or lab-free HPV testing removes lab turnaround as the bottleneck, but decentralized programs still lose patients between result, counseling, referral, and follow-up.
• Current alternatives such as paper registers, spreadsheets, generic EHR notes, DHIS2 reporting, or configurable field tools do not natively control same-visit decentralized HPV workflows.
• Screening operators need one system that works across low-connectivity, mixed-infrastructure sites without turning each rollout into bespoke services work.
• If result capture, chain-of-custody, and referral closure fail, the economic and clinical value of same-visit screening collapses.

Solution

• Offline-capable field workflow app for test registration, result capture, protocol enforcement, and next-step tasking at each screening site.
• Supervisor dashboard for stock visibility, invalid-test monitoring, positive-result queues, referral status, and site-level completion metrics.
• Configurable protocol templates for decentralized HPV programs so new sites can launch on a repeatable operating model instead of custom spreadsheets and messaging threads.
• Vendor-neutral interoperability layer that can plug into assay vendors, DHIS2-class reporting systems, and local record systems while avoiding diagnostic decisioning in v1.

Why we win

• The wedge is narrow and urgent: result-to-referral orchestration for decentralized HPV programs, not a broad EHR, LIS, or consumer testing platform.
• Vendor-neutral and offline-first design fits mixed site types better than OEM-specific software or clinic-bound guideline tools.
• Every deployment can improve reusable protocol templates and benchmark data on invalid rates, counseling latency, referral lag, and closure.
• By staying on the operational side of the workflow first, the company can move faster than teams that start with diagnostic or triage automation.

Milestones

flowchart LR
  Wedge[Decentralized HPV workflow wedge] --> MVP[Offline MVP for registration result capture and referral queues]
  MVP --> Proof[Paid pilots prove closure improvement and repeatable onboarding]
  Proof --> Expansion[OEM channels multi-site expansion and adjacent screening workflows]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least one buyer segment can fund the product from rollout, grant, or operating budgets without waiting for a national platform decision.
• The first pilots can improve referral closure enough that program leaders treat the software as mission-critical, not optional reporting.
• A repeatable deployment can go live across 20+ sites in under 60 days with limited custom work.
• Generic alternatives such as CommCare, DHIS2, or EHR workflows are materially worse on same-visit decentralized HPV operations.
• At least one OEM, distributor, or implementer partner will co-sell or share integration access within the first 12 months.

Open diligence questions

• Which budget line actually pays for workflow software in the first three target programs?
• What measurable lift in referral closure or nurse time savings is required for a paid conversion?
• How much of the MVP can be automated without vendor event and serial-number feeds?
• Which geographies combine decentralized screening pain with tractable privacy and interoperability requirements?
• How often do buyers choose DHIS2 or CommCare plus local integrators instead of a vertical product?

Model sanity

• Revenue engine. Base-case revenue is driven by converting two Y1 pilots into 10 paid programs by Q4Y2 and 20 by Q4Y3 at roughly $147K annual ARPU.
• Must go right. Pilot proof must convert inside 6-9 months so OEM and implementer channels reduce CAC instead of adding another slow procurement layer.
• Model breaks if. If buyers default to DHIS2 or CommCare plus local integrators and sales cycles slip two quarters, the downside case nearly consumes the cash buffer.
• Next-round proof. The seed story is strongest once Q4Y2 shows 10 paying programs, two production conversions, one working channel, and a path to positive Q4Y3 EBITDA.

Scenarios

Sensitivity

flowchart LR
  Programs[Paid programs] --> Sites[Active screening sites]
  Sites --> Episodes[Completed screening episodes]
  Episodes --> Revenue[Site + episode revenue]
  Revenue --> GrossProfit[Gross profit after implementation and support]
  GrossProfit --> Cash[Operating cash runway]
  Programs --> Renewals[Pilot to production conversion]
  Renewals --> Revenue

Flags: The base case assumes grant- or rollout-backed budgets release on time; there is no self-serve demand engine if public-health procurement stalls. · Gross margin only reaches target if onboarding and protocol configuration become templated rather than custom services work. · Y3 revenue lands close to the researched $3.0M SOM, so post-seed upside depends on adjacent screening workflows or faster site expansion within each program.

• Hardware adoption dependency. If lab-free HPV platforms take longer to gain regulatory or commercial traction, the software wedge may arrive before enough customers are ready. Mitigation: Start with pilots and workflow tooling that can support any rapid HPV rollout, then expand alongside whichever diagnostics platforms actually deploy first.
• Procurement drag. Screening programs, NGOs, and clinic networks can have slow budget cycles and fragmented decision-making across medical, operations, and funder stakeholders. Mitigation: Sell into concrete rollout events with site-level ROI metrics such as referral completion and invalid-test reduction, and package deployment support with the software.
• Workflow fragmentation. Referral pathways vary widely by site and geography, so a rigid product could become expensive services work instead of repeatable software. Mitigation: Design the first product around configurable protocol templates and narrow the initial ICP to multi-site programs with repeatable workflows rather than bespoke one-off pilots.