DoulaDay, the on call rota for people whose clients arrive at 3 a.m. · Updated September 8, 2026

What DoulaDay actually does

The product is organized around four steps, and they are refreshingly literal. You open a window rather than a date. You pair a named backup, and the window does not go live until that second doula accepts it in writing, at which point the backup receives the client brief and the birth preferences. You send the contract and the deposit request as a single link, so the client signs and pays in one sitting instead of two. Then you watch the season fill, with overlapping windows, outstanding balances and capacity limits on one dashboard.

The backup step is the one carrying the weight. Most doula cover arrangements live in a text thread and a mutual assumption, and DoulaDay's contribution is to turn "they said they would cover me" into a timestamped yes attached to a specific window. Everything else follows from that: a handover log for the birth timeline, deposit and balance tracking that flags a payment after 14 days, and a season capacity view designed to stop you accepting an inquiry you cannot physically staff.

Open a single window and the site says you should see six things: your own terms, timestamped, with the fee schedule the client actually agreed to; the retainer status and its clearance date; the written acceptance from the named backup; the client's birth preferences and support notes; the address, parking, access codes and household details, released only once the window goes live; and the contracted postpartum hours with their billing terms. Withholding the door code until the window is live is a small, sensible detail that suggests someone who has actually done this job was in the room.

It connects to Google Calendar and Apple Calendar, takes payments through Square and Stripe with funds landing in the doula's own account rather than DoulaDay's, and exports client records, contracts and history to CSV. That last one matters more than it sounds: a scheduling tool you cannot walk out of is a hostage situation.

What it costs, in plain dollars

Three plans, all billed monthly in US dollars. Solo Doula is $25 a month and covers one doula plus one backup seat. Doula Pair is $59 a month for two full accounts on a shared board. Collective is $119 a month for up to twelve doula accounts. Pricing is per plan, not per client and not per birth, which is the right shape for a job where one month brings five births and the next brings one.

Cancellation is unusually calm for software: the plan stops at the end of the month you already paid for, with no notice period and no cancellation fee. Clients sitting inside open windows are still your problem to move, and the site's own answer on migration is that most solo doulas finish in one evening while collectives tend to spread it over two sittings. Treat that as the optimistic version, as you would with any vendor estimate.

What is not on the page: a free trial, a money back guarantee, or a self serve signup. Every button is demo shaped (book a walkthrough, request a quote, send your practice details), so expect a conversation with a human before you get an account. If you want to poke at the product alone at midnight, this is not currently that kind of purchase.

Who it is for, and who it is not for

DoulaDay names three practice shapes it is built for: the solo doula at capacity, roughly four to six births a month with one regular backup; the reciprocal pair, two doulas who cover each other; and the metro collective, six to twelve doulas sharing inquiries and call. If you attend two births a season and your backup is your sister, a shared spreadsheet remains free and will not send you an invoice.

More usefully, the site draws its own line and tells hospital departments to go elsewhere: if you are rostering shifts inside a department, it says a shift scheduler will serve you better. A landing page that names a customer it does not want is rare enough to be worth crediting, and it is a decent signal that the product is built for windows and cover rather than generic staff rotas.

On informal arrangements, the answer is measured. It does not demand you tear up a handshake deal, it asks you to write down what you already agreed, and a colleague who does not use the platform can be recorded as an external backup with contact details. The window still wants a name on it before it goes live, which is the entire point.

Records, privacy and the line it does not cross

On access, the site is specific: client notes are visible to you, to the backup doula named on that particular window, and to the client. It states that nobody at DoulaDay reads client notes and that it does not sell, share or train anything on your records. On storage, it says application data sits with US based infrastructure providers, encrypted in transit with TLS and at rest with AES 256, that there are no advertising pixels or third party analytics cookies on the site, and that after you close an account everything is erased from live systems and backups within thirty days. Records stay exportable for as long as the account is open.

Now the important part. This is administrative software and nothing more. It schedules, pairs, reminds, logs a handover and chases a deposit. It does not chart, diagnose, advise or attend anything, and it makes no health claim of any kind: words like clinical, charting and diagnosis do not appear on the page. That restraint is the correct call, and it is worth repeating plainly here. Nothing in a rota tool is medical advice, the birth preference notes it stores are a briefing document for a colleague rather than a care plan, and no calendar has ever delivered a baby.

One block deserves a raised eyebrow. The site publishes practice outcome figures drawn from 312 US practices after a full season: 96 percent of windows opened with a confirmed backup, deposits collected 11 days sooner, 5.5 fewer admin hours a month, and $4,300 in added annual revenue per doula. Those are DoulaDay's own numbers about DoulaDay's own customers, printed without a visible methodology beside them. They are a claim, not evidence. Ask for the working during the walkthrough, and notice that the survivors of any product survey are, by definition, the people who stayed.