On my own

Maternal Revival

Launched · early daysmaternalrevival.com ↗

Problem: My wife runs a birth and postpartum practice in Kansas City. Her old site could show the work but couldn’t hold it. It had the warmth and the testimonials, but every real thing a client wanted to do, buy a course, book a session, or stay supported from pregnancy into postpartum, happened somewhere else. The job was to keep how the old site felt and give it the structure to carry a mother the whole way.
Constraints: I’m the only engineer. She’s the practitioner and the voice. That set the rule: rent the parts anyone can rent, payments, scheduling, the plumbing, and hand-build only the layer that has to feel like her.
Process: I started by untangling the offerings themselves. On the old site they were a flat list, but each one carried its own logistics: a course that runs online, an in-home follow-up a local mother can add, physical products that ship, some sessions virtual, some in person only. Understanding all of it well enough to re-architect it around where a mother actually is, instead of a menu of services, was the hardest part of the build. Then a small store, before the courses, to prove the payment path on something simple. Then bringing her courses and client relationships into one experience instead of tools that never felt connected. Booking came next, so a mother could choose a time and pay in one place. Last, the layer that adapts to where she is, prenatal or postpartum, and keeps supporting her between visits. Each piece only came after the one under it worked.
Outcome: What started as a brochure site is now one connected product, launched but early. A mother can discover the practice, understand what fits her stage, buy, book, learn, and stay supported without being handed off to a collection of unrelated tools. The infrastructure underneath is mostly rented. The experience on top is hers. It is live now.
Lessons: This one I built for the person I know best, which meant learning her whole practice before I could give it a shape. The lesson that stuck was where to spend the effort. Payments, scheduling, and infrastructure did not need to be unique. The experience did. Keeping the parts that carry trust and continuity custom, and letting everything else stay boring, left less software to own and a more coherent path for the mother using it.

← Back to Studio