Book a call
Case study

Inside a six-figure community's churn problem

How the House's founder found the leaks, and built the system that catches members before they leave.

The situation

A paid community with hundreds of members and six figures a year in recurring revenue. Growing steadily on the front end through content and ads, but losing members every month out the back at the industry-typical rate of 6 to 9%. That's the part worth sitting with: this was a strong community. Great content, a founder members genuinely liked, healthy growth. And it still leaked, because almost every community does, at the same predictable moments. At 9%, a community replaces nearly half its member base every five months just to stand still.

The founder was excellent at getting people in. Nobody owned keeping them. That's not a failure. It's the industry default, and it's fixable.

The detective work

I went through the churned and cancelled member list one by one. Every exit got a personal DM asking one honest question: what made you decide not to continue? Then I mapped every answer and every exit against tenure.

The pattern was not random. Exits clustered into distinct lifecycle windows:

Underneath all of it: an onboarding survey of ~200 members showed 47% had never posted or spoken. Silent members do not complain before leaving. They just leave.

The system

Instead of reacting to cancellations, I built a retention operating system that covers every exit path.

Four messages, each firing at a specific moment:

Seven upstream goals so those messages fire less often: week-1 activation (target: 60% of new members posting by day 7), lurker-to-contributor engagement, monthly-to-annual ascension, member wins surfaced weekly, referral cultivation, feedback loops before cancellation, and a 90-day re-entry path.

The machine underneath: a churn watchlist and community health dashboard, AI-powered analysis that flagged at-risk members weekly, automated call-transcript mining for member pain points, and a weekly operating rhythm. The founder got a pattern report every week instead of anecdotes.

What happened

“What stood out most was her ability to move between the strategic and the operational without losing quality on either end. I'd recommend Aqeelah to anyone looking for someone who can build, think, and deliver.”

The community's founder
The point

Most community owners treat churn as a mystery or a mood. It is neither. It is a set of predictable leaks at predictable lifecycle moments, and each leak has a specific fix. I find the leaks in one week. Installing the fixes takes three or four.

Book a Call