About
We build the part of healthcare nobody wants to build
qPrescribe exists because the gap between a health idea and a legally prescribed medication is filled with work that is genuinely hard, genuinely boring, and genuinely does not get easier the second time.
Why we started
Three good products, none of them shipped
Between 2019 and 2021, our founders were close to three different health companies that never made it to market. None of them failed on demand. Each one stalled in the same place: forming the right clinical entity, finding providers licensed where their customers actually lived, and figuring out whether their model was legal in the eleven states that treat it differently.
That work took each team about a year, cost several hundred thousand dollars, and produced nothing a customer could see. Worse, all three teams did it independently and arrived at roughly the same answer.
That is the definition of infrastructure — a hard problem solved identically by everyone who encounters it. So we built it once, properly, and made it something you can integrate in a week.
How we work
Four positions we hold, including the inconvenient ones
Clinical judgment is not a checkout step
It is tempting to design prescribing as a conversion funnel with a doctor stapled to the end. We build the opposite: intake that screens honestly, providers with real discretion, and a denial rate we are not embarrassed by.
Compliance is engineering, not paperwork
A policy document does not stop a consult from routing to the wrong state. A routing constraint does. We encode regulatory requirements as controls in the system, where they cannot be quietly skipped under deadline pressure.
Our partners should own their patients
White-label means white-label. Your brand, your relationship, your data — exportable whenever you want it. Infrastructure that holds customers hostage is not infrastructure.
Say the constraint out loud
There are categories we will not support and states where a model does not work. Telling a partner that in week one is cheaper for everyone than discovering it in month nine.
Timeline
How we got here
- Phase 01
The problem, up close
Our founders watched health brands stall for a year each — not on product, but on entity structure and provider coverage.
- Phase 02
First partner live
A single-category brand went from signed agreement to its first prescribed patient.
- Phase 03
Nationwide coverage
Provider network extended to all 50 states and DC, with modality rules encoded into the routing engine.
- Phase 04
Oversight, formalised
Named medical directors per category, written protocols, and a documented chart review programme.
- Now
Building the network
Growing clinician capacity category by category, with the constraint stated out loud when a model does not work.
Team
Clinicians, regulators, and engineers in the same room
Every product decision gets reviewed by someone who has to defend it to a state board, and every clinical protocol gets reviewed by someone who has to implement it.
Dr. Naomi Alvarez, MD
Co-founder & Chief Medical Officer
Internal medicine physician who spent six years building clinical protocols for multi-state virtual care before starting qPrescribe.
Samir Haddad
Co-founder & CEO
Previously led product at a digital pharmacy platform, where the hardest problem was never the software.
Rachel Kim
Head of Regulatory Affairs
Healthcare regulatory attorney focused on telehealth practice standards, corporate practice of medicine, and pharmacy law.
Tobi Adeyemi
VP Engineering
Built payments and identity infrastructure before deciding that healthcare's plumbing needed the same attention.
Placeholder team profiles for this build — replace with real bios and photography before launch.
Work with us
If you are building in health, we should talk.
Whether you are three weeks from launch or still deciding whether the model works at all, the first conversation is usually worth having early.