Every couple of weeks I get an email from someone, usually a friendly investor, asking some version of: "Why aren't you building your own lateral-flow test? The strip companies have terrible margins. You could replace them."
The answer is that the strip companies are doing exactly the work they should be doing, and we're doing exactly the work we should be doing. The regulatory posture isn't a side effect of being small. It's the product decision.
A lateral-flow strip is a diagnostic device. It runs immunoassay chemistry against a clinical sample and produces a signal whose accuracy is bounded by analytical sensitivity, specificity, and the regulatory clearance the strip manufacturer paid for. The strip manufacturer's PMA or 510(k) submission is the document that lets a clinician trust the result.
A reader, in the sense we mean it, is a piece of equipment that observes what the strip has already produced. It doesn't have an analytical sensitivity, and it isn't trying to. VynScan doesn't read the strip for you, and it doesn't decide what the lines mean. It captures a tamper-evident, timestamped photo of the strip and runs an anti-fraud pre-scan that flags an obviously used or substituted strip. The staff member still reads the result, the same way they do today. So the device can't be more accurate than the strip. It can only be more or less consistent at preserving an honest record of what the strip showed and who ran it.
The regulatory math
If we made our own strip, we would inherit the entire diagnostic regulatory burden: pre-clinical testing, clinical trials, 510(k) substantial-equivalence submissions for every analyte (COVID, flu, RSV, strep, ...), separate clearances for each combination of fluid type and analyte, and a perpetual obligation to surveil post-market performance. Even for a 510(k)-eligible analyte that's well understood, you're looking at 12 to 24 months and at least a million dollars per submission.
VynScan sits in a different bucket. We don't claim diagnostic performance, and to be clear, VynScan is not FDA-cleared and isn't sold as a diagnostic. What we claim is narrower: we capture and preserve a tamper-evident record of the test the facility already ran. The strip's clearance does the diagnostic-trust work. Staff do the reading. Our job is to do the capture-and-record work consistently enough that a surveyor can audit it without re-doing the test.
This is similar to the distinction between a CBC analyzer (regulated as a diagnostic device, makes its own measurement) and the lab information system that records the analyzer's output (regulated separately, mostly under software-as-medical-device rules where applicable, mostly not at all where it isn't). Different scopes, different burdens, different products.
The workflow math
Even if we wanted to spend three years inside the FDA on a competing strip, doing so wouldn't solve any problem the facility actually has. The facility doesn't have a strip-accuracy problem. The strips the manufacturers ship are good. The facility has a workflow problem: results sit on a clipboard for hours, transcription errors creep in, the surveyor can't find a coherent audit trail, and the nurse who ran the test has moved on to other tasks before the result is acted on.
None of those problems are solved by a better strip. They're solved by a device that captures the strip the moment it's developed, attaches that record to the right resident, timestamps it cryptographically, and surfaces it to a charge nurse's dashboard. The nurse still reads the line. What's fixed is the handling, the transcription, and the audit trail. That's a software-and-hardware problem, not a chemistry problem.
The engineering math
Lateral-flow strip manufacturing is a specialty manufacturing discipline that takes decades to learn well. Membrane chemistry, antibody conjugation, flow consistency, lot-to-lot reproducibility, shelf-life modeling. There are companies whose entire engineering org spends years on each of these. We'd be terrible at it, and we'd be terrible at it for years before we got mediocre at it.
What we are good at is computer vision applied to a constrained geometry, hardware that's reliable enough for a nursing-floor environment, and audit infrastructure that's compliant enough for HIPAA and CMS. Those are the disciplines that a reader requires. Pointing our team at the things we're good at is how a single-founder shop ships a real product in 18 months instead of "by 2030."
The customer-trust math
There's one more reason, and it's the one I usually lead with in customer conversations. A facility administrator who is buying a screening tool wants to know whose neck is on the line if a result is wrong. With VynScan, that answer is clear: the strip manufacturer's clearance is on the line for the analytical result; the clinician's judgment is on the line for the care decision; VynMed is on the line for the audit trail behind both. Three distinct accountabilities, none of them confused.
If we built our own strip, all three of those accountabilities would collapse onto us. That's a much harder sale to a SNF that's already nervous about a small vendor. The clean separation between "the strip is FDA-cleared, we're a reader" is the thing that lets a 120-bed SNF say yes to a pilot in 30 days instead of three years.
The takeaway
"We're a reader, not a diagnostic" sounds like a constraint. It's really the product. It's the regulatory posture that lets us ship. It's the workflow scope that lets us solve a problem facilities actually have. It's the engineering focus that lets us be good at the thing we ship. And it's the accountability story that lets a customer say yes.
The narrow definition is the moat.