The right membership size may be smaller than your audience

You open your membership doors to 200 people, then discover that every useful conversation now needs your attention. Questions arrive faster than you can answer them. New members cannot find the context they need. The people who joined for thoughtful discussion start scrolling past a room that feels more like a busy feed. The problem may not be demand. It may be that your membership is larger than the experience you promised.

A large audience tells you that people are willing to notice your work. It does not tell you how many will pay, how many will participate, or how many will need help after joining. Those are separate steps. A membership asks you to make a repeatable promise, then deliver it repeatedly. Capacity is the point at which you can still keep that promise without turning every week into unpaid operations.

Start with the experience, not the headcount

Write down what a member is actually buying. It might be a monthly workshop, a place to ask practical questions, feedback on work, a library of resources, or the feeling of being recognised by a small group. Each promise creates a different workload. A resource library can serve many people with little additional effort. Personal replies, live review and introductions become harder as membership grows.

Do the capacity arithmetic

1. 1List the recurring work for one member: onboarding, answering questions, reviewing submissions, hosting calls and handling access or billing problems.
2. 2Estimate the time required in a normal month. Use a range if the work varies. For example, if one member needs between 10 and 20 minutes of direct support, plan with the higher figure until you have real evidence.
3. 3Choose the hours you can protect each month. Do not count every hour that appears free; leave room for your main work, rest, illness and the unexpected.
4. 4Subtract fixed membership work such as preparing a call or updating the library.
5. 5Divide the remaining support time by the high estimate per member. That gives you a starting capacity, not a permanent target.

For example, suppose you can protect 12 hours a month for member support. A recurring workshop takes four hours to prepare, host and follow up. That leaves eight hours. If you promise up to 30 minutes of direct support per member each month, the arithmetic gives you 16 members. That number is not a prediction of demand. It is a check on whether the promise fits the time available.

Measure conversation quality

Conversation quality is not the same as message volume. A lively room can still be useful if members can find answers, respond to one another and return to an ongoing question. It becomes a capacity problem when good threads disappear before members can follow them, when the same question is answered repeatedly, or when you must intervene in every exchange to keep it useful.

Separate support from access

Many memberships become unsustainable because the creator treats every purchase as an open-ended request for personal help. You can make the boundary visible in the offer. Say how often you answer questions, whether replies are public or private, what kind of feedback is included, and what sits outside the membership. If members need individual diagnosis, a separate coaching call may be a better product than adding more promises to the community.

The same principle applies to your storefront. With store.fan memberships, you can make the paid offer the place where access and recurring value are clear, rather than relying on a large social audience to explain the difference. The free plan is link-in-bio only; paid plans start with a 14-day trial. Store.fan takes 0% of sales, while Stripe's own processing fee still applies and money goes straight to your Stripe account.

Choose a capacity model

There is no single correct way to limit a membership. Choose the model that matches the promise and the way you work.

• Fixed cohort: enrol a defined number of people, work with them for a set period, then decide whether to reopen.
• Rolling cap: keep enrolment open until you reach a number that your current support system can handle, then move new people to a waitlist.
• Tiered access: keep the core library open to more members, while limiting live calls, reviews or private feedback to a smaller tier.
• Seasonal intake: open at a few points in the year so onboarding and group activities happen together.
• No numerical cap: use this only when the main value is already-created material and your support boundary remains genuinely light.

A cap is not a scarcity trick. It is useful when an additional member changes the delivery of the product. If the cap is real, explain what happens when it is reached and when people can expect the next opening. If you are testing the idea, start with a founding group and promise access to the process rather than a perfectly finished system. You can read more about that distinction in the founding member offer.

Review your capacity using evidence from the work, not just your feelings about the room. Count the recurring support tasks, note where questions repeat, and look at whether members can use the product without your constant presence. Store.fan can support the operational side with creator-owned checkout and, on Pro, tools such as email marketing, discount codes, hosted course video and creator-run affiliate programmes. Those tools can reduce friction, but they do not remove the need to set a promise you can keep.