For memberships and communities
Paid communities, newsletters and membership sites get judged on audience size — a figure anyone can inflate and everyone discounts. The number that actually holds up is the one your members pay every month, and it can be read straight from your billing.
“Twelve thousand members” tells a reader almost nothing. It may count free signups from a launch three years ago, people who joined for one thread, and accounts that have not opened an email since. Nobody can tell which, so the sensible reader applies a large discount and moves on.
The same is true of every audience number in this category: list size, followers, Discord members, downloads. They are all trivially inflatable, all routinely inflated, and all therefore priced accordingly by the people you are trying to convince.
Recurring revenue cannot be padded with people who are not there. It counts only members who chose to pay and have not stopped, which is the exact population a sponsor, a partner or a prospective member wants to know about.
It is almost always a smaller, less flattering figure than your audience total. That is why it works. A number that is obviously not the most impressive one available reads as a number you did not choose.
A prospective member wants to know the place is alive and will still be running next year — the specific fear with paid communities, which have a reputation for emptying out quietly after launch.
A sponsor or advertiser has been shown inflated audience figures by everyone they have ever dealt with, and is budgeting for that. Paying members is the number that reprices you.
A partner or platform deciding whether to integrate, co-market or feature you is really asking whether the audience is real and durable.
All three are asking about durability, and all three currently get handed a total that cannot express it.
Most memberships charge through Stripe, whether directly or under a membership platform sitting on top of it, and a subscription is a subscription regardless of what it unlocks. The figures can be read the same way they are for any software company — read-only, from the account the money already runs through, under a published counting rule.
One check is worth doing first: confirm the subscriptions appear in your own processor account rather than the platform being merchant of record and paying you out. If charges show up in your dashboard, this works today. The eight processors that can be read.
Member identities are never stored or published. What goes on the page is totals, which for a private community is usually the only version anyone would accept.
A membership that has been paid for continuously for four years is a fundamentally different proposition from one with the same headcount and no history, and no audience metric distinguishes them. Duration is the thing that cannot be bought, borrowed or inflated, and it is the thing a paid community is most often doubted on.
Put the price changes, the relaunches and the format shifts on the dates they happened, and each one arrives with the measured figures from the months either side. That is a record of a community that has been run, not announced. Social proof before you have logos · self-reported versus verified
Connect your processor read-only and your history appears in about a minute. No member names, and nothing public until you say so.