ORDANI, my company
ORDANI: HIPAA-compliant CRM for birth workers
A HIPAA-compliant CRM for birth workers, and a company I founded and built. Birth workers keep hundreds of dollars per client that a claims service would take. Active paying users in beta, none lost to a competitor, public release coming.
- My role
- Founder and sole engineer
- The work
- Practitioner interviews, a progressive intake flow, a HIPAA-compliant build shaped with birth workers and cyber security experts, and a closed beta
- Results
- Birth workers keep hundreds of dollars per client that a claims service would take. Active paying users in beta, none lost to a competitor.
Six apps and a Sunday night
Doulas, midwives and perinatal counselors ran their practices on half a dozen tools: a scheduler, an invoicing app, a form builder for intake, a notes app, a payments app, and a group chat holding it together.
Each one did its own job. None of them talked to the others, so the practitioner became the integration, copying the same client's details from one app into the next on a Sunday night. The monthly bill for six subscriptions added up to a system nobody had designed.
Nobody I spoke to was shopping for a platform. Nobody had ever offered them one built for their work, so they did not know to want it. And HIPAA is the law for all of it: every copy of a client's details in another app was one more place that data lived.
Why it matters
In the United States, non-Hispanic Black women die from maternal causes at 44.8 per 100,000 live births, 3.15 times the rate of non-Hispanic white women, per the CDC's 2024 release. Doulas and midwives, disproportionately Black women themselves, are one of the most evidence-supported interventions against that gap. The data they hold is sensitive and almost never properly protected. The market has not shipped for these workers because the market does not see them.
What I did
I talked to birth workers before writing a line of code. Four weeks of unpaid conversations: what they used, what they hated, what they would never give up, what they would pay for. Two patterns came back. Nobody asked for a platform, because nobody had been offered one that understood their work. And everybody wanted intake to stop eating their Sundays.
I put claims inside the calendar they already keep. Birth workers who take Medicaid or private insurance either pay a service like Loula a fee on every visit, or file the claims themselves, which costs no fee but takes time and knowledge. Ordani builds the claim from the visits already on the calendar and checks it before it goes out, so fewer come back rejected. Filing comes with the subscription.
I built it HIPAA-compliant, and not on my own judgment. An app holding this data has to be shaped by the people who understand both halves of it. That means the birth workers whose practice lives inside it, and people who work in healthcare and in cyber security. Ordani has a small team around it for that reason. How the protections work is not something a HIPAA product publishes, so this page does not.
I shipped to a closed beta first. Free for the first year in exchange for weekly feedback calls. By the end of it, practitioners were using it every week, referring peers, and none had left. That beta is where today's paying practitioners started.
What it became
Practitioners in the beta file real Medicaid and private-insurance claims from Ordani, with no separate claims charge. The practitioner opens a Tuesday-morning view of the week instead of a spreadsheet and a group chat. The screens hold real client data, so this page describes them rather than shows them.
Questions buyers ask
Can one person build a HIPAA product? One person can write the code. Nobody should decide alone what "compliant" means, which is why birth workers, healthcare people and security people shaped it.
If you have the idea and no team
You have the idea, the budget, and customers waiting. What you do not have is the team to build it. I build it: strategy, design, code, security and launch, with nothing handed to a second team.