IT, for reproductive & abortion care
We build the IT this work actually needs.
Custom integrations, patient-facing tooling, and quietly reliable infrastructure for reproductive health and abortion care providers. Our medical director is a practicing nurse midwife who spent a decade in software before going into medicine — not a generalist vendor that happens to take your call.
What we offer
Three things, done carefully.
Custom integrations
Your EHR, scheduling, payments, and telehealth tooling don't talk to each other — or they talk in ways that require staff to copy data by hand. We connect them, properly.
Privacy & security
Patient privacy isn't a checkbox on a vendor questionnaire. We design how data is stored, transmitted, logged, and backed up so that the careful answer to a privacy question is the boring one.
Tools for staff & patients
Most clinic software was clearly never used in a clinic. We build interfaces with the people who'll click them every day, then prune the parts they don't need.
How we work
Specialty IT means specialty habits.
We learn your workflow before we touch a keyboard.
Most clinic software fails because it was built from a vendor's mental model of how a clinic should work, not how yours actually does. We start by watching.
We ship in increments, not big-bang launches.
Small, demonstrable wins first. Nine-month implementations are where projects go to die — and where staff lose patience. We trade scope for cadence on purpose.
We test what fails quietly.
Backups that have never been restored from, audit logs nobody reviews, migration scripts nobody rehearsed. The boring patterns are where most failures hide. So we rehearse.
We track state-by-state law as part of the work.
What's lawful, who can prescribe, what data crosses state lines — this varies in ways that matter to your operations. It's part of the job, not an upcharge.
We keep working after launch.
Software ships and then keeps running. We treat ongoing reliability as part of the contract — the point isn't a successful go-live, it's a year from now when nobody's had to think about the system in months.
Selected work
What this looks like in practice.
Client names aren't on this site.
Two national telehealth abortion providers
Replaced a Zapier/Keragon intake stack with a custom AWS pipeline — roughly twice as fast, fewer ineligible patients in the clinician queue, and one system instead of four.
A primary care + abortion practice
Built a dedicated public site that separates their abortion-care work from primary care, plus an intake-to-payment integration using the browser session ID — eliminating the emailed-link drop-off between steps.
Two national telehealth abortion providers
Migrated off cloud tools whose subpoena exposure was wrong for the legal environment of this work, onto infrastructure they control directly — with audit trails they can actually point at.
A multi-state abortion provider organization
Stood up self-hosted infrastructure — VPN gateway, application servers, shared cloud drive — in a data center in a state with the strongest available shield laws. The infrastructure is unremarkable; where it lives is the work.
A reproductive health organization with multiple providers and a robust admin team
Built a custom web interface to replace Excel/Sheets for a multi-provider mail-order practice — batch shipping operations and tracking ingested back into the EMR.
About
A specialty shop, on purpose.
Most healthcare IT vendors take any client. We don't. Our medical director is a practicing nurse midwife who spent ten years in software before going into medicine — so we don't have to translate between the people who understand the technology and the people who understand the work.
More about usGet in touch
Tell us what you're trying to do.
Five sentences is enough. Specifics over polish. We read every message and reply within a business day.