Fresh from the lab.
— dispensed dailyRefillCalls
The pharmacy phone line, automated. Refills captured and queued around the clock while the humans stay with the humans.
Take a look → 02LIVEPharmacy Ops
Workflow tooling for the daily grind of an independent pharmacy — minus the paperwork nobody will miss.
Ask about it → 03ONGOINGClient Studios
Bespoke sites and native apps for practices and small businesses. Designed, built, hosted — end-to-end.
Start one →Like a prescription,
but for software.
— no prior auth required
Tell me where it hurts
A short call about the workflow that's broken — phones, refills, paperwork, or the vendor software everyone tolerates.
I mix the fix
Designed and built end-to-end by one person who understands both the clinic and the code. Native, HIPAA-first, no wrappers.
Shipped & maintained
Deployed, hosted, and looked after. Refills are automatic — updates included, no counseling required.
The origin story
Ten years at the counter taught me what to build.
Most health-tech is made by people who've never verified a script at 6 pm on a Friday. I have — thousands of times. Then I went home and built the software I wished existed.
Now pharmacies run on apps I designed, wrote, and deployed myself. Clinical judgment in, better healthcare out.
Common questions.
— ask your pharmacistWait — an actual, licensed pharmacist?
PharmD, licensed and still practicing. The kind that verifies prescriptions, gives immunizations, and then goes home and pushes to production.
What do you build with?
TypeScript and Python on the back, native SwiftUI on Apple platforms, Postgres underneath, self-hosted infrastructure around it. Web-view wrappers are contraindicated.
How do you handle patient data?
HIPAA-first, by default: self-hosted infrastructure, minimum necessary access, and patient data that stays where it belongs. It's the pharmacist part of the brain — it never switches off.
Do you take insurance?
No — but unlike your PBM, the estimate is free, the rejection rate is zero, and nobody asks you to try a cheaper developer first.