LoginSchedule demoLoginSchedule demoCompany-wide is the right ambition. The programs that get there fastest all start the same way, and the ones that stall usually die in their own reporting.
Every enterprise advocacy program should end up company-wide. That is the whole point of buying one. Thousands of employees, every region, every function, a permanent distribution channel none of your competitors can purchase off a shelf.
The question was never whether to go big. It is what order you go big in.
Here is the order most programs try first. Buy the licenses. Build the content groups. Write the announcement. Send it to everyone on a Tuesday morning. Then watch.
What happens next is not a disaster. It is worse than a disaster, because a disaster gets attention. A few hundred people log in over two weeks. Fewer connect LinkedIn. Fewer still actually share anything. By week six the program owner is defending a percentage to a VP who was promised a movement, and the honest explanation, that this is roughly what a cold company-wide blast produces at scale, does not survive that meeting.
I run implementations for a living, so let me say the useful part plainly: the programs that reach the whole company fastest are the ones that spend their first thirty days on a hundred people. Scale is not the problem. Cold scale is. Sequence is what makes the big number stick.
Most people hear “pilot” and think risk mitigation. A cautious little test to make sure the software works before the real thing.
Stop using the word. The software works, you are not testing the software, and “pilot” is the word that gets a program funded at fifty seats and quietly reviewed a year later.
Call it wave one, because that is what it is, and because the name tells everyone in the room that wave two is already coming.
Wave one exists to manufacture proof. Its output is a set of true sentences you cannot say on day one and can say on day thirty. Two hundred of your colleagues shared something last month. Our CFO posted twice. Someone in field operations got a reply from a customer they had chased for a year. Here is what one post did for one person’s network, and that person sits two desks from you.
You cannot borrow those sentences from a vendor case study. They have to be yours, about your company, naming people your employees actually know.
So the shape of a fast enterprise launch is not one event. It is a first wave of 30 to 100 people, followed by a scale event that the first wave’s results trigger. Wave one is not the warm-up act. It is the accelerant, and company-wide is what it buys you.
One clarification before the examples, because it is the most common misreading of this argument. None of this is a case for buying fewer licenses. Size the agreement to the population you actually intend to reach, because that is what the program is for, and because the alternative is going back for budget in ninety days from a weaker position than you have today. Wave one is a rollout decision, not a procurement decision. You are choosing who gets the invitation first, not deciding how many people the program is eventually for.
Two examples, both anonymized, both from live program data. Watch where they end up, not where they start.
A global payments technology company opened with a leadership-first wave of roughly 100 users. That program now runs better than 95 percent activation, north of 490,000 monthly reach and 700-plus shares a month, and it is still widening.
A global medical device manufacturer started smaller. A 30-person first wave. Once that group had produced something to point at and leadership gave the green light, the program scaled sixteen times over in about a month, holding more than 80 percent activation, with 150 shares on day one of the wider launch.
Neither company could have posted those numbers off a day-one all-hands blast. The first wave is what made the expansion possible, and the expansion was always the point.
Everything above comes with a warning label, and it is the bigger of the two risks. A cold company-wide blast wastes a quarter. A program that opens narrow and stays narrow wastes a year.
Fifty seats in a 10,000-person company, parked with no scale plan, is not a strategy. It is a drop in the bucket with a subscription fee. Leadership never sees the needle move, because the needle is measured against the whole company and fifty people cannot move it. The program owner ends up defending a rounding error, and getting the real rollout funded from that position is harder than launching cold would have been.
The trap has a seductive version of the numbers. Ninety percent activation of fifty people is forty-five people. It feels like an A grade and it funds nothing, because the person who controls the budget is not grading the cohort. They are grading the company.
So wave one earns its existence only with three commitments, all made before it opens.
A clock. Thirty to sixty days. Wave one is a phase, not a program size, and everyone involved knows the date it stops being one.
A trigger agreed in advance. Write down what proof unlocks wave two while everyone is still calm. If the first wave produces the proof, scaling is not a new decision to relitigate. It already got made.
A target set against the whole employee base. Not 90 percent of almost no one. Wave one is the first step on a curve that ends at the whole company, and it should be presented that way from the first slide.
One more trap worth naming, because it stalls more expansions than any budget conversation: gating the rollout on a lagging indicator when a leading one is already sitting in front of you. Activation, sharing, and real engagement from real audiences are measurable in week one. Hires, sourced pipeline and influenced revenue compound as the footprint widens, which is exactly why they belong in the report rather than on the tollgate. Gate expansion on the proof you already have, and let the business outcomes grow with the program.
Every company already employs people who post on LinkedIn without being asked. They comment on industry news. They celebrate their team. They have opinions about their profession and they publish them. Nobody built them a program and they are doing it anyway.
You can find these people by looking. Someone in comms can assemble that list in an afternoon. At most large enterprises it runs to a few hundred names, and those names are the best available answer to who gets invited first.
A program’s hardest job is behavior change, and this group requires none. They already have the social muscle. They do not need a training arc to overcome the fear of posting, because they got over it years ago. Hand them a feed of approved content and they produce value in week one, which matters enormously when the proof you need has a thirty-day clock on it.
The second-order effect is the bigger one. These people are visible. When they share, their colleagues see it, and what those colleagues see is not a corporate announcement. It is a peer they respect, participating. You get the social proof engine for free by choosing the right people to invite first.
One related point that deserves its own article: your executive sponsor belongs in this first wave too, posting the day it opens, not three weeks later.
Every few implementations, a program owner reads the draft invitation and stops. “Are we really going to tell people we noticed what they post?”
Fair instinct. Here is how I think about it.
The invitation validates public behavior, it does not surface private behavior. These posts are on LinkedIn. They were written to be seen, by an audience the person chose, on a platform whose entire purpose is professional visibility. Noticing them is not surveillance. It is reading.
What makes the difference is what the invitation says, and the rule is simple: it never references monitoring, tracking, scoring, or any system. It references the person. You are already one of the strongest voices we have in this space, we are building something to make that easier, we would like you to help lead it. That is an acknowledgment of standing, not a report on activity.
And it is an invitation, not an assignment. Nobody is being told to post more. Nobody has a quota attached. The offer is that something they already do on their own gets easier, better supplied, and visible to their own leadership. That email consistently gets warmer replies than anything else in a launch, because professional recognition from your employer is rare enough that people notice when it arrives.
If it still feels off, that is usually a signal about tone rather than ethics. Rewrite it until it sounds like one person wrote it to another, because that is what it should be anyway.
The company-wide announcement is a broadcast. It is addressed to a population, it asks nothing specific of anyone, and it competes with every other all-employee email that week. Response rates are what you would expect.
A personal note from a named human, sent to one person, asking them specifically, does dramatically better. I do not have a clean industry number to hand you and I am not going to invent one, but it is the most consistent pattern we see across launches, and the gap is not small. Personalization is not the mechanism. Attribution is. Someone chose you and will notice whether you show up.
Which leads to the healthiest growth channel in advocacy, and the one most programs never deliberately turn on: employees inviting their own coworkers. In the payments program above, roughly three quarters of new members joined through a colleague’s invite rather than a central announcement. The program office did not recruit those people. The members did.
That channel is also the cheapest path to company-wide there is. It compounds in a way broadcasts never do, it self-selects for teams where the content is actually relevant, and it does not need a comms budget or another all-hands slot. Make peer invitations easy, make them visible, and then get out of the way.
This is where good programs get killed by their own reporting.
Activation is the number that matters, and the denominator is the population you invited, not the company directory. Those are two different measurements, and quietly swapping one for the other is how a healthy program gets described as a failure in a room full of people who would have called it a win an hour earlier. Both programs above cleared 80 percent of the people they opened to, one of them 95, and that is the bar worth writing down.
So write it down. Before launch, in writing, with your executive sponsor in the room. Set the twelve-month reach target the same way, against the whole employee base, because that is the number the program is ultimately for.
Programs rarely die because a result came in under a forecast. They die because someone was quietly holding a different number in their head, nobody surfaced it, and the gap got read as failure by the person who controls the budget.
First wave. Real proof. Then scale on the strength of the proof, and keep scaling in waves rather than one detonation.
The wave model has a second benefit nobody talks about: friction surfaces cheaply. Every launch has some. An invitation domain that was never allowlisted. A single sign-on flow that breaks for one region. A content group that is empty when people arrive. Discovering that with 40 people is a Tuesday. Discovering it with 20,000 is the story your program never lives down, because you get one first impression per employee and you just spent it.
So go big. Go in the order that makes big stick. Open with the people who were going to say yes anyway, give them thirty days and something to prove, then let what they proved do the recruiting, wave after wave, until the program is everywhere it should have been all along. And put a date on every wave, because the whole design only works if the next one is already scheduled.
Wave one is not the destination. It is the fastest road to the whole company.
Planning a company-wide launch? Our implementation team runs this sequence with every new program: the first wave, the clock, the trigger, and the benchmark you agree with your sponsor before anyone logs in. Book a demo and we will map yours.
See the platform that comms, marketing, and compliance teams use to run their advocacy program.
