Community ops

Two years running the operations of a paid community, 200 members to 900

Stephen G. Pope, AI Architects Skool

Client
AI Architects Skool (Skool)
Ran
About 2 years, daily
Result
200 to 900 members, churn 24% to 9%
TWO YEARS, ABOUT AN HOUR A DAY, SEVEN DAYS A WEEK Members 200 → 900 Churn 24% → 9% Support, onboarding, tutorials, classroom upkeep, and the free to paid conversation kept deliberately manual.
The only two outcome numbers from this engagement that are cleared for use.

Who

Stephen G. Pope runs AI Architects Skool, a paid Skool community for people building AI automation systems.

Before

A paid community is not a course. Members show up every day with questions, and every one that goes unanswered is a renewal that quietly doesn't happen. The community needed to run well without consuming the person whose name is on it.

What the work actually was

One package, run daily for about two years:

What changed

Over that period the community grew from around 200 members to around 900, and churn came down from 24% to 9%.

Why it matters

Most people who can run community support can't build the automations that fix what they're triaging. Most people who build automations don't do hands-on support. This was both jobs, every day, for two years, which is where the habit of turning a repeated support ticket into a system came from.

Want to remove founder dependency from fulfillment? Start with a fulfillment diagnostic. I will show you where delivery waits on you, and if nothing is broken I will say so.

Book a fulfillment diagnostic

← All projects