Swim Buddy Playbook
Thirty years of clinical practice, delivered one week at a time.
Dr. Bruce Rumsey spent three decades helping couples talk to each other. Swim Buddy Playbook turns that work into a weekly practice couples can actually keep.
Development 180 built the platform that delivers it.
Dr. Bruce RumseyFounderSwim Buddy Playbook
What they needed
The material already existed and it was good. The problem was delivery.
Couples don’t need another library to browse. They need something small to arrive at a moment they’ll act on, together, every week, without deciding to go and find it. That turns a content archive into a habit, and it’s a product problem rather than a content one.
So the brief was narrow: get one session in front of two people at the same time every week, in a form they can use in ten minutes, and make it feel like it came from Dr. Bruce rather than from a mailing list.
What we built
- A members-only platform.Subscribers pay, sign in, and get the library: each week’s session as video and as a printable guide, alongside everything released before it. The web app is the home of the content — the weekly message is the prompt, not the delivery mechanism.
- A weekly release, on a fixed rhythm.Every session goes out at 5pm on Wednesday. The fixed time is deliberate: a habit needs a slot, and couples plan around a time they can predict. Sixteen structured modules sit behind it, covering agreements, listening, talking, finances, intimacy, parenting, and the future.
- Two channels, one send.Each release goes out by email and by message. Email carries the designed session. The message is short and pulls them into the app.
- Messaging it didn’t have to build.Swim Buddy Playbook runs on delightful OS, where it exists as its own venture with its own iMessage line. It launched with real conversational messaging rather than a generic SMS blast, on day one, without paying to build that capability. Development 180 had already built the messaging infrastructure for other partners, so Swim Buddy inherited it. Each product in the portfolio makes the next one cheaper and faster to launch.
The part that’s harder than it looks
Delivering content on a schedule is easy. Delivering something two people will actually stop and do, together, at the same time, is not.
Most of the difficulty is in restraint. A weekly send that arrives too often becomes noise. A message that carries the whole session removes the reason to open the app. A library that shows everything at once turns a practice into a backlog, and a backlog is something you feel guilty about rather than something you do.
So the product releases one session at a time, on a fixed weekly rhythm, with the message doing nothing except getting two people to the same place. The constraint is the feature.
Where it is now
Launching shortly. Sixteen modules built, the platform live, and the weekly delivery running.
In their words
Thirty years of practice, in the hands of the couples who need it.