You built the course. People bought it. Then somewhere past the first few lessons the logins thin out, the renewal notice arrives cold, and nothing on the site was built to catch any of that. We build the sales page and the member area as one thing, and we structure the curriculum so there is always something scheduled next.
One was designed. The other is whatever the platform shipped with, wearing your logo in the corner. The member paid, then walked through a door into a building that looks nothing like the one they bought.
There is a login screen and there is nothing else. A person who has never heard of you has nowhere to land, nothing to read, and no page a search engine can index.
Past the receipt the copy stops, the emails stop, and the calendar is empty. Nothing on the site was built to keep a member past the first month, because nothing on the site was built for after the sale.
Every module can carry one hook that gives a member a reason to come back. Where a module carries none, the calendar goes empty, and you can read off exactly which month that lands in. Below is an example curriculum, six modules released two a month, invented here so the shape is visible. Every month named below is counted off that cadence. Pick a module and read the hook attached to it.
One finished task before the member closes the tab. Something small they complete and can point at, in place of a tour of the portal.
Where the curriculum leaves a gapWith no first task, the only thing ever scheduled is the receipt. At two modules a month, module one opens month one and nothing in it asks for a second visit, so month one is where the account goes quiet.
What gets built for itA welcome sequence that fires off the purchase, and a first lesson written as a task with an end to it.
Saved progress, sitting on the dashboard the moment they log back in. The member never has to remember where they stopped.
Where the curriculum leaves a gapWithout saved progress the curriculum has no memory, so every return starts with a search. Module two closes out month one, so month one ends with a set of half watched lessons and no obvious next one.
What gets built for itA member dashboard that opens on the next lesson, with the finished ones marked, using whatever progress tracking your platform exposes.
The files live behind the login and get added to. The login keeps earning its place because the library keeps growing.
Where the curriculum leaves a gapIf the templates arrive as email attachments, the member already holds everything they came for. Module three opens month two and nothing is scheduled after it, so month two is where the account goes quiet.
What gets built for itA library page inside the member area, plus a short notice each time something is added to it.
A date the member has to show up for, announced before they need it and reminded twice.
Where the curriculum leaves a gapA curriculum with no dates in it competes with everything else in the week and never wins on urgency. Module four is the last one month two contains, so month two runs out with nothing on the calendar to argue for it.
What gets built for itA cohort or drip schedule, a booking page for the sessions, and the reminder sequence that carries people to them.
Somewhere to submit the work and have it looked at. The member is now owed a reply, which is a much stronger reason to return than a video is.
Where the curriculum leaves a gapOnce the lessons run out the curriculum stops asking for anything, and finishing and quitting look identical from the inside. Module five opens month three with nothing owed either way after it, so month three is where the account goes quiet.
What gets built for itA submission form wired into your CRM, a review queue you can work through, and a reply that lands back in the member area.
A next season named and dated before the current one ends, so renewing is a decision about something specific.
Where the curriculum leaves a gapModule six closes month three, so month four is the first month with nothing scheduled in it at all. The renewal notice arrives into that silence, as the first contact since the last lesson, asking for a decision nobody has been prepared for.
What gets built for itA season page on the public site, a renewal sequence that opens before the notice does, and a win back path for anyone who already stopped logging in.
Written for the cold reader, not for the person already on your list. It names who the course is for, what they walk out able to do, and what the first week looks like. It lives on your own domain, as a real page, so search can read it.
Same type, same colour, same voice, themed as far as your platform allows. We check the ceiling your platform gives us before we promise anything, then build to it.
Login details, the one task in module one, and a clear statement of what happens next and when. The gap between paying and starting is the easiest place in the whole thing to lose someone, so nothing is left to the member to figure out.
Dripped by date, dripped by progress, or run as a cohort with a start and an end. We map which modules carry a hook and which do not, then put the dates where the empty months are.
Triggered by inactivity, not by the calendar. It re-enters at the module they stopped on rather than at the beginning, because being sent back to the start is a reason to not come back at all.
Indexable pages on your site rather than files hidden behind an opt in. They give search something to rank and give a stranger something to read before they are asked for an email address.
Because a portal is built around the people who already paid. The fair version of this objection is narrower than it used to be, since most of the big platforms now ship a custom domain, marketing pages and SEO settings. What they ship is thin and templated, and the URLs are still the platform's. That is the part that bites later. Everything written inside is written for a member, so a stranger who lands on a login screen leaves, and on the day you move tools the pages that were doing the persuading, and whatever search history they had built up, stay behind. Keep the platform for the job it is good at, whether that is video, payments, the community, or all three. The site is the part that has to work on strangers and outlive whichever tool you are using this year.
Every module, the one hook attached to it, and the stretches where nothing is scheduled. That map is what the build is aimed at, and it is usually the first time the whole thing has been on one page.
The public pages get built on your domain. The member area gets themed to match as far as your platform allows. The reader should not be able to tell where one ends and the other starts.
Onboarding on the receipt, the drip or cohort dates, the live session reminders, the inactivity trigger, the renewal sequence. You do not touch any of it. We build it and walk you through it.
Your domain, your list, your pages. If you change course platforms later, the site does not move with it. The platform goes back to being what it should be, a tool you can replace.
Hosted course platforms, membership plugins, community tools: each one holds what sits behind the login, whether that is video, a forum, a feed, or all of it, and takes the payments for it. That job stays where it is. The public site sits in front of it on your own domain, and the member area gets themed to match. If you move platforms in two years, the site stays put.
Some platforms allow custom CSS, custom fonts and a domain of your own. Some allow a logo and one accent colour. We check yours first and tell you plainly which of the two you are on, then build to that ceiling. Where the ceiling is low, we put more of the experience on pages we control.
The sales page, the member area and the sequences are all built off the structure, not off the finished videos. If you know the modules and the order, we can build while you are still recording. If the outline keeps moving, we map it with you first, because everything else is aimed at that map.
An opt in hides the lesson from search as well as from the reader. We put the free lesson out in the open where it can be found and linked to, and put the email capture next to it rather than in front of it. The people who want the rest still tell you who they are.
We pull the list of accounts that have not logged in, then build a sequence that re-enters at their last module rather than at module one. It is a build, not a blast. Some of them come back and some do not, and the ones who do not are worth knowing about before the renewal date arrives.
The sales page gets a member in the door. The structure behind it decides whether they are still there in month three. Both get built here, as one thing.
Most projects start with a conversation.