I didn't hire a doula. I married one.
DoulaFlow didn't come out of market research or a business plan or a gap I spotted in some industry report. It came out of my own kitchen, watching my wife, Megan, get ready to launch her doula practice, and realizing I could save her from a particular kind of headache before it ever found her.
So before Megan had taken on a single client, I built her a tool. This is the story of why.
Megan did everything right
When Megan decided to become a doula, she went about it the way she goes about everything: thoroughly. She read the books, built her website, sorted out her branding. She found a mentor and started showing up to the local meetups. And she thought hard about the kind of care she wanted to give families, and how she wanted her practice to feel.
Then she walked me through how she planned to actually run it day to day: the contracts, the birth plans, the resource packets, the intake forms, the stack of paperwork she'd print for every family. To hold it all together, she'd wired up a setup across Airtable, Google Drive, Google Calendar, Calendly, SignWell, Adobe, and a plain notepad.
You have to understand something about Megan: she is one of the most organized people I have ever met. This wasn't a mess. It was a genuinely clever system, stitched together with care. And it was holding together a practice that did not yet have a single client.
I build software for a living. Untangling complicated workflows is what I do all day. So while Megan showed me her setup, I was doing a quiet calculation in my head, and I could already see what this would look like at ten clients a year. Then fifteen. Then twenty. Seven different tools, each holding one piece of the puzzle, none of them talking to each other, every one of them depending on her to remember which corner each detail lived in.
Picture what a single client actually touched: the inquiry came through one tool, the consultation got booked in another, the contract was signed in a third, the birth plan and intake lived in a fourth, the dates went into a fifth, and the notes ended up wherever there was room. One client, half a dozen places. Now run eight of those at once, with due dates that drift and birth windows that overlap, and you start to see the shape of the problem. Not a hard problem, exactly. Just a relentless one, the kind that never fully lets you rest.
I could see the headaches coming
What worried me wasn't the work. Megan was made for the work. What worried me was everything piled up around it.
I've watched plenty of people fall in love with something, a craft or a calling or a small business, and then slowly come to resent it. Not because the thing itself stopped being meaningful, but because the administrative weight around it kept growing until it crowded out the part they loved. The contracts, the calendar conflicts, the "wait, did I send that?" at eleven at night, the mental tab always left open. I didn't want that for Megan. I didn't want her to discover this calling and then, two years in, feel buried by the logistics of it.
There's a quiet arrangement in our marriage that matters here. In our life together, anything that touches money or business is mine to carry: the taxes, the bills, the insurance, the contracts. That's my lane, on purpose, so Megan can pour herself into what she's actually here for. We're a family with three kids and more on the way, and Megan is the one who makes our house a home. Taking the administrative load off her plate isn't a favor I do. It's just how we divide the things that need doing.
So when she showed me that seven-tool setup, the answer felt obvious. I didn't want her practice to be the one part of her life where the paperwork landed back on her. I wanted her business to feel the way the rest of our shared responsibilities do: handled, so she doesn't have to think about the plumbing at all.
The rule: would it make Megan's work easier?
So I built it. Before her first client, on purpose, because the worst time to switch tools is after you've already got a tangle of spreadsheets and signed contracts to migrate. I wanted her to start clean, in one place, and never have to think about the system underneath again.
From the very first screen, the product had exactly one standard, and it still does today: would this make Megan's work easier? If the answer is yes, it ships. If the answer is no, it doesn't, no matter how clever or impressive or "industry-standard" it might be. There is no feature in DoulaFlow that exists because some competitor has it. Every single thing in there earned its place by making a real doula's real week a little lighter.
One detail I'm proud of, precisely because it's a thing we didn't automate: Megan loves her printed resource packets. The beautiful, personal, hand-assembled folders she gives each family. Early on, the instinct of a tools person is to digitize everything. But the printed packets were never the problem. The personal touch was never the problem. The problem was the seven disconnected tools behind the scenes. So the packets stayed exactly as they were, and we built the calm underneath them.
Automate the friction, protect the human part. That turned out to be the whole philosophy.
What we won't compromise on
As DoulaFlow grew from "a thing I made for my wife" into something other doulas could use, a few principles hardened into rules. These weren't marketing decisions. They came straight out of watching how Megan actually works.
Calm by design. Software should not add to your stress. A doula's days are already full of other people's biggest moments; the last thing she needs is a cluttered, anxious-feeling app demanding attention. Every screen in DoulaFlow is built to feel quiet and clear. If a screen ever feels busy, that's a bug to us.
Built with a doula, not for an imaginary one. Every form, every workflow, every default was tested against how a real working doula practices, starting with Megan. Not how a software company assumes a doula should work. There's a difference, and you feel it in a hundred small places. Megan has a standing habit of telling me what's driving her crazy, and as she once put it, the thing she'd flag at night would be fixed by morning. Her words: it feels like the tool is on her side. That's the bar.
Honest pricing. No long contracts. No surprise fees. No holding the basic things a practice obviously needs hostage behind some upgrade. I find that stuff distasteful in the software I use, so I wasn't about to do it to doulas.
Just enough. Everything your practice needs and nothing it doesn't. No forty-page onboarding, no certification required to find the button you're looking for. The goal was never to be the most powerful tool in the room. It was to be the one that disappears into the background so you can get on with the work.
From one doula to, we hope, a lot more
For a long time, DoulaFlow had exactly one user, and she happened to be the person I have dinner with every night. That was a strange and wonderful way to build software. The feedback loop was about twelve feet long, and the most important user in the world was also the one keeping me honest.
Now we want it shaped by more of you. We're a genuinely small operation, really just the two of us, building this out of Chattanooga, Tennessee. Megan is the doula it was built for and the co-founder who still vetoes anything that wouldn't make a practice easier. I handle the rest. We read every message that comes in, and the fastest way to change the product is still the same as it's always been: tell us what's slowing you down, and we'll go fix it.
That intimacy is a feature, not a phase we're trying to grow out of. The whole reason DoulaFlow feels the way it does is that it was made by people who care more about your Tuesday evening than about a roadmap slide.
What it's really for
If I had to put the whole thing in a sentence, it's this: doulas show up for women and families during one of the biggest moments of their lives, and DoulaFlow's only job is to handle everything around that moment so you can be fully present for it.
The births, the long prenatal conversations, the 3 a.m. text from a frightened first-time mom, the quiet postpartum visit where someone finally feels seen: that's the work. That's the part no software should ever touch. Everything else, the contracts and the calendars and the keeping-track, is just plumbing. And plumbing is my job, not yours.
But I'll be honest about the bigger hope underneath all of it. I'm not just trying to help doulas work. I'm trying to help them define a better way to do it. A way where the business side of a practice feels as calm and intentional as the care at the center of it. A way where growing doesn't have to mean drowning, and where the tools you rely on feel like they're on your side.
I built this for the doula I married. We'd be honored to build it for you, too. If you're curious what calm looks like, come take a look. No pressure, no contracts, just a conversation about whether it'd make your work easier.
Because in the end, that's still the only question that matters.
Erick, Founder, DoulaFlow