The four archetypes in a stadium crowd

Champion, Amplifier, Builder, Early Adopter were built and measured on Web3 community audiences. Here is what each one would look like in a stand of 40,000 - an illustration of the logic, not a sports result we have measured.

CommunityOS classifies real accounts into four archetypes - Champion, Amplifier, Builder, Early Adopter - based on scans of Web3 community audiences. Nobody has run this on a sports club's following yet. This post walks through what each archetype would look like in a stadium crowd, as an illustration of the logic, not a measured result.

Say "fan segmentation" to most people who work at a club and they picture ticket tiers, or a CRM field for "superfan" that someone set once and nobody has revisited. The four archetypes are a different kind of segmentation - not who spends the most, but who does what in the crowd. We built and scored the model on Web3 communities, where it has real numbers behind it. We have not run it on a sports following yet. What follows is a mapping exercise: taking a classification that works, and asking what it would mean for a stand of 40,000 people instead of a Discord server. Treat it as a way to think about a crowd, not as a report on one.

The four archetypes, briefly

The full reasoning behind the set - why four and not three or five - is in a separate post. In short, every real community member sorts into one of four classes along two axes: reach (can this account distribute a message further than the brand can alone?) and substance (does this account generate conviction, original content, or an early signal worth noticing?).

  • Champion - high substance, speaks with conviction people trust.
  • Amplifier - high reach, carries a message into rooms the brand can't enter.
  • Builder - high substance, produces original work rather than opinion.
  • Early Adopter - a timing signal, shows up before it's obvious and gives the first honest read.

CommunityOS scores accounts against this set using a deterministic 60/40 model - weighted toward what an account actually writes, with engagement metrics folding in at a smaller weight. That weighting matters here too: a sports account's archetype should come from what it says and does, not just how large it is.

What a Champion looks like in a stand of 40,000

In a Web3 community, a Champion is the account whose explainer thread on a protocol change gets screenshotted into three other Discord servers. The sports equivalent isn't hard to picture: the supporter whose 40-tweet breakdown of a tactical substitution gets quoted by the local beat writer, or the account a rival fanbase begrudgingly follows because the analysis is better than anything the club's own press office puts out. Champions are rare and high-value precisely because conviction is expensive to fake - the same reason the scoring model weights language this heavily in the first place.

What a club would actually do with a real Champion, once identified, is the same ask that works in Web3: give them something substantive early - a stat nobody else has, access before an announcement - rather than a generic "please post about our match" request that a Champion finds beneath them.

What an Amplifier looks like

Reach without a large account is the tell. An Amplifier in a Web3 community is often not the biggest account in the room - it's the one a message reliably travels through. In a stadium crowd, that's the fan account that doesn't write original analysis but whose repost of a highlight clip is what actually gets it in front of a rival fanbase, or the regional supporters'-group account that every match-day post passes through on its way to a diaspora audience the club's own channels never reach. The ask for an Amplifier is distribution logistics, not content: make sharing effortless at the moment it matters, which for a club is kickoff, a goal, or a transfer announcement, not a Tuesday press release.

What a Builder looks like

Builders ship artifacts, not opinions. In Web3 that's a dashboard, a tracker, a long-form explainer with original data in it. In a stadium crowd it's the fan who maintains the spreadsheet tracking every starting eleven this season, the account that clips and tags every set-piece routine, the supporter running a podcast that other fans treat as the record of the season. Builders are usually invisible to a club's social team because they rarely tag the official account - they're building for the community, not at the brand. The ask is access and materials: match footage, data, or simply being told their work was seen.

What an Early Adopter looks like

This is the archetype that rewards patience. In Web3, an Early Adopter is the account that showed up before a project was obviously worth showing up for and gave the first honest signal about it. In a club's following, that's harder to see in a single snapshot and easier to see over time: the account that was loud about a youth-team prospect two seasons before the senior squad call-up, or the supporter who started following a newly promoted club before the run of form that made it fashionable. Early Adopters are a predictive signal, not a present-tense one - the canonical path, as it is in Web3 communities, is Early Adopter into Builder or Champion as involvement deepens, which is a reason to track a following across scans rather than read it once.

What this mapping does not tell you

It does not tell you what share of a specific club's following falls into each archetype, because that number has never been measured for a sports audience. It does not tell you whether a stadium crowd produces more Amplifiers relative to Champions than a Web3 community does, or whether sports fandom's much longer time horizon changes how Early Adopters behave. Those are genuinely open questions, and the honest answer to all of them right now is: we don't know yet, and anyone claiming otherwise is guessing.

What we do know, from the one production scan CommunityOS has actually run, is what happens before any archetype gets assigned. On a Web3 project's X following, 78,181 accounts were scanned, 90.96 percent failed authenticity checks, and 5,806 real accounts remained to be scored and ranked. Crypto audiences are about as heavily farmed as anything on X, so that failure rate is a worst case, not a baseline to expect from a club's following - a sports audience is inflated too, just almost certainly at a different rate, and the only way to find out which rate is to run the scan.

Getting a real answer

The method doesn't change between verticals: pull the full following, filter it for authenticity first, and score only what survives. We've run that once, end to end, on a Web3 audience. The next step for sports is running it once on an actual club's following and publishing what comes out - not an illustration, a number. If you run a club, a league, or an athlete's account and want to be the first real data point instead of reading someone else's, that conversation starts at the waitlist. The full scoring method is on the methodology page.

Quick answers

Do the four archetypes already exist for sports audiences?

Not as a measured result, no. Champion, Amplifier, Builder and Early Adopter are CommunityOS's existing classification set, built and scored on Web3 community audiences. This post maps the same four categories onto a stadium crowd as an illustration of how the logic would apply to a club's following - it is not a sports scan, and no club's followers have been run through this yet.

What would a 'Champion' look like in a club's following?

The fan who writes the 40-tweet thread breaking down a tactical change, or the account whose match-day post gets quoted by the local paper. In the Web3 scoring model, a Champion is identified by depth and conviction in their own language, not by follower count - the same signal, applied to a stadium crowd, would be the supporters whose opinion other fans actually go looking for.

Isn't an 'Amplifier' just a fan with a lot of followers?

Reach is necessary but not sufficient - an Amplifier is an account that reliably moves a message further than the club's own channels can reach, which is a distribution pattern, not a vanity-metric threshold. A fan account with 200,000 followers that never reposts club news isn't acting as an Amplifier; a smaller account that a clip reliably travels through is.

Where do the real sports numbers for this come from?

They don't exist yet, and we say that plainly rather than imply otherwise. The only production numbers CommunityOS has are from one Web3 project's X following: 78,181 followers scanned, 90.96 percent failed authenticity checks, 5,806 real accounts remained. That is a crypto audience, which runs harder-farmed than almost any other category on X, so it is a worst case, not a sports baseline. A club's real split across these four archetypes has never been measured.

What would it take to get a club's actual breakdown?

The same method already run once: pull the full following rather than a sample, filter it for authenticity first, then score what survives across the four archetypes. CommunityOS is looking for one club willing to be the first sports scan - the method is ready, the number for any specific team just isn't yet. That conversation starts at the waitlist.

Next

See the numbers on your own audience.

CommunityOS scans your X followers, filters the bots, and ranks the people worth activating. Manual onboarding, real numbers.