For academies, courses, memberships & communities

They bought. Then they went quiet.

Most students who never come back were lost in the first seven days — before they ever got a win. This sprint rebuilds that window, and calms the support chaos that comes with it.

Watch: why the first 7 days decide everything (3 min)

Mahmoud Assani — Founder, Assani Consulting
60 seconds · No obligation · Usually responds within 48 hours

For businesses with students already joining — this fixes what happens after they do.

Sound familiar?

The signs of a broken first week.

Tap what's true for your students
0 of 8 checked

Logins drop off sharply after the first few days.

Most students never finish the first module.

"Where do I start?" is your most common question.

Support answers the same five things over and over.

Refund requests arrive within the first two weeks.

You can't tell who's at risk until they've already gone.

The community is quiet — new members never post.

Nobody ever tells you why they stopped showing up.

Those all point to the same window.The first seven days after purchase — that's what this sprint rebuilds.

Before & after

What actually changes in the first week.

Same student, same product — a different seven days. The exact build is scoped to your business, so the right-hand column is filled in during the sprint.

 
How it runs now
After the sprint
Day 0
Receipt email, platform login, and a wall of modules.
A single clear first action — one thing to do, not forty.
Day 1
Nothing. They intended to start "this weekend."
Orientation that sets expectations and points at the first win.
Day 3
Silence. Nobody notices they haven't logged in.
Inactivity trigger fires — a nudge that references where they stopped.
Day 5
They email support with a basic question and wait two days.
The answer already exists in a macro; response is same-day and tagged.
Day 7
Still no progress. Quietly filed under "later."
First win reached and acknowledged — the habit has a foothold.
Day 14
Invisible. You'll find out when the payment fails.
At-risk flag raised early, while it's still recoverable.
Your version of this week is designed inside the sprint
What gets built

Six pieces. Always the same six.

This is a fixed, productised sprint — not a custom project. That's why it's fast and why the price doesn't move much.

First-win milestone

We define the single smallest meaningful win a student can reach, and design the path to it.

7-day onboarding sequence

Day 0, 1, 3, 5 and 7 messages built in your existing email or platform tools.

Inactivity triggers

Automated nudges when a student stalls — referencing exactly where they stopped.

Support macro library

Written answers to your most repeated questions, so replies are instant and consistent.

Risk tagging system

A tag taxonomy so support flags churn risk in real time instead of firefighting blind.

Cancellation capture

A short exit flow that finally tells you why people actually leave.

The process

Five to seven days, start to handover.

DAY 1

Access & walkthrough

I go through your purchase flow as a real student and read your last few weeks of support tickets.

DAY 2

First win defined

We agree what "activated" actually means in your business — the single milestone everything else points at.

DAY 3–5

Build

Sequence, triggers, macros, tags and exit flow built inside the tools you already use.

DAY 6

Test

Run through end to end as a test student before anything touches real customers.

DAY 7

Handover

Walkthrough recording, written docs, and a short session with whoever runs support.

The investment

Fixed scope. Fixed price. One week.

Activation & Support Sprint
$500 starting
5–7 days to handover 6 pieces built Fixed scope

Because the deliverables are the same every time, this is the most predictable offer I run. Price only moves with the size and complexity of your student base.

⏳ Limited sprints run at a time — each is a full week of build.
Honest qualification

This fixes one thing very well.

Right fit

  • Students are joining but going quiet in the first weeks
  • You have a course, membership, academy or community live
  • Support keeps answering the same early-stage questions
  • You want one thing fixed properly and fast

Not right yet

  • No students yet — there's no behaviour to fix
  • You're not sure the first week is the problem — start with an audit
  • You need several backend systems built — see the Fix Sprint
  • You want a guaranteed retention percentage
No pressure

What happens after you get in touch.

01

Three quick questions

Where students go quiet, how many join, what exists today.

02

Short call

We confirm the first week really is your gap — if it isn't, I'll point you elsewhere.

03

Scope confirmed

Fixed price and start date in writing. Nothing begins before you approve it.

04

Built in a week

Six pieces built, tested, documented and handed to your team.

Straight answers

Before you ask.

How is this different from the Backend Fix Sprint?+

Scope and flexibility. This sprint fixes one journey stage — purchase through first win — with the same six deliverables every time, in about a week. The Backend Fix Sprint is custom work across one to three systems anywhere in your backend, over 14–30 days. If your problem is specifically the first week, this is cheaper, faster and more focused. If several systems need building, that one fits better.

Will this actually reduce churn?+

I won't promise a number. What I'll say is that the first week is where the decision to disengage usually gets made, and most businesses have nothing structured there at all. Building it properly gives you a real chance of changing that outcome — but your product, market and follow-through decide the result, not me.

What if my product genuinely isn't good enough yet?+

Then onboarding won't save it, and I'll tell you that on the call rather than take your money. Activation systems help people reach the value that already exists — they can't manufacture value that isn't there.

Do you write the actual email copy?+

Yes. The sequence, nudges and support macros are written for you, in your tone, ready to use. You can edit anything — it's yours.

What tools do you need?+

Whatever you already use — Kajabi, Skool, Circle, Teachable, ConvertKit, ActiveCampaign, Intercom and similar are all fine. No migrations, no new software to buy.

Can I do this and a Fix Sprint later?+

Plenty do. This fixes the first week; a Fix Sprint handles deeper systems like payment recovery, dashboards or team SOPs afterwards. There's no obligation either way — you own everything built here.

How much of my time does it take?+

About two hours total — one call to define the first win, access setup, and a sign-off before anything goes live to students.