| Early stage | Enterprise | |
|---|---|---|
| Why anyone attends | They know the founder, or a guest they trust | The brand is credible on its own |
| Who invites | Founders and the first customers | A field marketing team, through reps |
| The scarce resource | Credibility | Coordination |
| Realistic scale | One city, a few rooms a year | Many cities, a calendar |
| Biggest risk | An empty-feeling room | Activity nobody can evaluate |
| Right measurement | Did these named accounts move | Programme-level pipeline contribution |
With no brand recognition, three sources of credibility are available, and they should be used in this order:
The failure mode at this stage is hosting a room that feels thin. Six well-chosen people is a good dinner; fourteen seats with eight filled is a bad one. Size the room to what you can genuinely fill.
A large company has brand credibility and has lost something harder to replace - knowledge of who knows whom. The relationships are there, distributed across hundreds of employees, and nobody can see them.
So the enterprise failure mode is not an empty room. It is a full room of the wrong people, invited by a marketing alias because identifying the colleague with the warmest tie to each guest is operationally impossible by hand.
That is the specific problem a relationship graph solves at scale: for forty invitations, it says which of two hundred colleagues should send each one.
Three things hold at any size:
Early-stage teams should not build a calendar, a sponsorship budget or an events function. Enterprise teams should not assume a founder can personally fill a room any more - at a certain size that network has been used, and the remaining relationships belong to people nobody has thought to ask.