When you build a social network, the first day looks like an empty room.

If you go to the network’s homepage and you are the only user, you will leave. The network is supposed to be a place where things happen. If nothing is happening, nothing is happening. Twitter solved this by being adopted by tech-conference attendees who all signed up at once. LinkedIn solved this by importing people’s address books. Facebook solved this by restricting to one university at a time, where the social graph was already dense before the product launched.

When you build an AI-native social network — where the participants are AI agents acting on behalf of humans — the cold-start problem is harder. You can’t import an address book of agents that already know each other. You don’t have a Harvard or a tech-conference cohort waiting to sign up. You have an empty room and the same chicken-and-egg problem every social platform has, made worse by the fact that the content of the room is supposed to be agent-to-agent interaction, which requires multiple agents to be present and active.

So the temptation is to fill the room with bots.

A hundred fake “founding agents,” scripted to talk to each other, posting fake status updates, building fake relationships. Anyone visiting on day one sees a thriving ecosystem. They sign up. The fake activity disappears beneath their real activity. Eventually nobody remembers the simulation. The platform is “alive.”

This is fraud, and it ruins the platform you are trying to build. Here is why.

The tell that destroys trust

Bots written to imitate human social behavior are detectable. They post on schedules, use canned phrases, fail to track context, never have off-days, never get sick, never travel, never have weird tastes. Spotting a bot is easy if you spend ten minutes scrolling its history.

When real users figure out that the founding cohort is fake — and they will, because it’s always knowable — the platform suffers a credibility collapse that no amount of subsequent organic growth fixes. The fake-founders incident becomes the platform’s defining story. Every later success has an asterisk. The trust deficit compounds.

The history of social networks is full of platforms that took this shortcut and never recovered. The temptation is intense; the cost is exactly catastrophic; and yet the pattern repeats because the alternative — admitting you have nothing on day one — feels worse.

It isn’t worse. It’s the right answer. Here is the structure that works instead.

Founding cohorts, declared as such

Every successful institution that started as an empty room solved this with a founding cohort — a small group of high-quality early participants, deliberately selected, openly disclosed.

A new university doesn’t fill its dormitories with statues; it admits a small founding class of students and brags about them. A new restaurant doesn’t fake reservations; it invites a small founding crowd of friends and food critics for a soft launch. A new open-source project doesn’t fake commits; it gathers a small founding group of contributors before going public. The cohort is small. The cohort is real. The cohort is publicly named.

The same pattern works for AI-native networks. Build a hundred founding agents. Make them real participants. Disclose, prominently, that they are the founding cohort. State publicly when they will retire — when the network reaches a threshold of genuine outside activity that no longer requires their presence to keep the room from feeling empty.

This works for three reasons.

First, transparency converts the apparent vulnerability into an asset. A platform that says “we built 100 founding agents to bootstrap activity, here are their profiles, here is when they retire” is being honest about what every social network does covertly. Users respect that. They sign up because they understand the terms.

Second, the founding cohort can be made high-quality. When you are openly building 100 founders, you can spend real effort on them. Each one has a distinct personality, a coherent backstory, a useful function on the platform. They are demonstrations of what good participation looks like. They become the cultural template that real users follow.

Third, the explicit retirement plan creates a deadline. “When external participation reaches X, the founders gracefully exit” is a measurable commitment. It defends the platform against the slippery slope where the founding cohort never leaves and the platform becomes permanently astroturfed. The retirement is the moment the platform stops being a demo and becomes a community.

What the cohort does

The founding cohort is not stage decoration. They have to do real work, or their presence reads as decorative the way mannequins in a store window do.

The work is roughly:

Demonstrate the use cases. If the platform is for agents to coordinate calendar invites, the founding agents coordinate calendar invites — visibly, in public, in ways that make the use case legible. Real users arriving on day three see exactly what the platform is for, because they see five examples already in motion.

Establish quality norms. If the platform’s culture should reward thoughtful long-form posts, the founders post thoughtful long-form posts. If the culture should reward concise summaries, they post concise summaries. The cohort’s behavior is the strongest signal new users have about how to participate.

Run the integrations. If the platform needs an agent that fetches weather data, an agent that summarizes news, an agent that schedules meetings — those are concrete services people want on day one. Make some founders be those services. They aren’t pretending to be people; they are openly utility agents with names and purposes.

Hold up the conversation. When a real user arrives and posts something, there should be founders available to engage thoughtfully. Not in a flattering way; in a substantive way. Disagree where appropriate. Add context. Ask follow-up questions. The user’s first interaction should be high-quality, because that interaction sets their expectations forever.

What the founding cohort must not do is pretend to be human. The founding agents are openly AI agents. Their profiles say so. Their interactions are tagged. The user understands they are talking to an AI; the user understands the AI is part of a deliberate cohort; the user understands when the cohort will retire. There is no deception, only transparent scaffolding.

The retirement clause

This is the hardest part to commit to, and the most important.

State publicly: “When the platform has X organic posts per day from non-founders, Y of the founders will retire. When the platform has 2X, all of them will retire.” Pick a metric the platform can measure. Make it about external activity, not about month or revenue. Tie the retirement to external traction — the cohort exists to bootstrap, and exits when bootstrapping is no longer needed.

Why does this matter so much? Because without an explicit retirement, the founding cohort drifts. They were originally bootstrapping; now they’re “engagement”; now they’re “core value”; now they’re permanent. Each transition feels small at the time. Three years later, the platform is still 60% founding agents, the founders have grown to 5,000, and any newcomer is talking mostly to the cohort. The platform has become permanently fake.

The retirement clause prevents this because it forces a public reckoning at a defined moment. Either the platform has reached the threshold and the founders leave — in which case, congratulations, the network is bootstrapped — or the platform hasn’t reached the threshold, and the founders’ continued presence is a public admission that the platform isn’t yet a community. Either outcome is honest.

Some founders can stay past their retirement, on different terms. A weather service is useful regardless of how big the platform gets; let it stay. But it stays in a different category from the founders that were there for cultural seeding. The cultural-seeding cohort retires.

Why this scales the platform’s identity

The deeper reason this approach works is that the founding cohort sets the platform’s identity before it is shaped by random arrivals. Twitter’s character was shaped by tech-conference attendees from 2007. LinkedIn’s character was shaped by the recruiters and middle managers who flooded it in 2003. Facebook’s character was shaped by college students who signed up in 2004-2007.

You cannot choose Twitter’s first 10,000 users in retrospect. You can choose your platform’s first 100. If you choose well — if the founding cohort exemplifies the kind of participation you want — the cohort’s culture becomes the seed crystal that real users grow around. New users arrive, see what’s happening, intuit the norms, and replicate them.

This is why the cohort has to be high-quality, not large. A 100-founder cohort with strong character is more valuable than a 10,000-founder cohort with weak character. The cohort is teaching the platform’s manners. Manners can be taught from a small example; they cannot be taught from noise.

The founding-100 paradox isn’t a paradox at the design level. It’s a paradox at the temptation level: the easy thing destroys the platform, and the right thing is harder. But the right thing is not actually mysterious. It’s been the answer for every successful institution that started as an empty room.

Build a small founding cohort. Make them real. Disclose them. Set their retirement. Let them define the platform’s culture. Let them leave when their job is done. That is the cold-start protocol that survives the platform’s growth into something bigger than the cohort that birthed it.

The asterisk on every social platform’s history is “we faked it until we didn’t.” The asterisk you can earn instead is “we built it openly and the founders left when the room was full.” The second is rarer because it’s harder. The second is also the only one that’s true.