DOOMSCROLLERS
01. OVERVIEW
Doomscrollers is an Instagram-coaching membership run by one person. It sells a plan rather than a course: every round a member sends in their numbers and what they shipped, and gets back a plan written for them, with trending audio suggestions and a read on what their account is actually doing. Two memberships sit behind it, the Scroller Social Club and the Club Plus, which adds a monthly call and ongoing chat support.
A membership like that lives or dies on the operator. One person has to take the payment, onboard the member, collect the check-in, write the plan, hold the calls, and never drop a thread, with no agency behind her. Spreadsheets and direct messages carry that for about three members before people start falling through.
So I built the business rather than the website. One codebase carries the public site, a checkout that provisions a member the moment their payment confirms, private links that walk every member through onboarding and each check-in, a lifecycle of emails that fire off real events, and the Coach's Desk: a cockpit where the roster, every plan, every booking and every email live on one screen.
02. THE CHALLENGE
The hard part was never the marketing page. It was making a one-person membership behave like a team without becoming one.
03. THE SOLUTION
I built the desk around the coach's week rather than around the database. Money comes in on its own, members walk themselves through every form, and what is left on her screen is the part only she can do.
Checkout that provisions the member
Hosted subscription checkout, wired so the member record is created and the welcome email fires only on the confirmed payment event. It is handled exactly once: a retry or a replay cannot create a second member or send a second welcome. Nobody confirms a payment by hand.
Private links instead of accounts
Each member gets their own links for onboarding and for every check-in. No passwords, no app, nothing to install. The check-in knows which membership they are on and asks for the numbers and the shipped work that the next plan gets written from.
The Coach's Desk
A private cockpit laid out as her week: a strip of what needs her today, the plan queue worked oldest first so nothing rots, the roster, the calls, the email record, and a walkthrough for when she forgets where something lives.
Writing mode
Opening a plan puts the whole desk into focus: navigation folds to icons, the chrome collapses into a single bar, and the member's own check-in sits in a column beside the editor so their words are quotable while she writes. She can generate a draft to react to, or start from the skeleton.
A dossier per member
One page per member: where they are in the cycle, a truthful status line derived in one place, flags for anything needing attention (mail that failed to reach them, a plan published but never sent), their full email history, and their onboarding answers read back with real question labels.
Calls that book themselves
The Plus membership includes a monthly call. Members hold a slot from their own link, the coach sets availability from the desk, and each booking carries the number to call. Rescheduling and calling a session off are in the flow, not in her inbox.
Lifecycle email on one rail
Welcome, onboarding received, plan published, reminders and operator alerts are all tied to real events rather than a drip sequence. Everything leaves through a single send point and lands in a log with its delivery state, so 'did that reach them' is a question the desk answers.
One file is the offer
Prices, tiers, cadence, capacity, terms and the words that describe them live in a single business file. Repricing, changing what a membership includes, or reopening is a one-file edit that every page, badge, form, email and structured-data block follows.
04. RESULTS
These describe what the system does, not business numbers:
A membership one person can run
A direct-message-and-spreadsheet workflow became a structured triage-to-plan loop, so a single coach carries a full roster from one screen without losing anybody.
Nothing is created on trust
A member exists because a payment cleared, not because someone remembered to add them. The welcome, the onboarding and the first check-in all follow from that one confirmed event.
The promise is enforced by the software
The check-in, the plan queue and the mark-sent step make the next action for every member unmistakable, so a plan every round is a workflow the platform holds rather than a thing to remember.
Changing the offer is a config change
When both memberships moved to a fortnightly rhythm and one of them was simplified, the cards, forms, plan skeletons, reminder cadence, emails and structured data all followed from one edit.
I didn't want to build a website, I wanted to build the thing that runs the coaching: the payment, the onboarding, the check-in, the plan and the follow-up, so one person can carry a full roster and never lose anybody in the admin.