Your Team Has More Reach Than Your Company Page. Here's How to Use It.

Do this before you read any further. Open your company page and write down the follower count. Then open the profiles of everyone who works with you — co-founder, the two people in marketing, the engineer who posts about their side project, the contractor who's been with you a year — and add those numbers up.

For most small companies the second number is bigger — often several times bigger — and it's an audience your company page will never reach.

That gap is the whole argument for employee advocacy. It's not a growth hack and it doesn't need a program, a platform, or a points system. It needs a few people willing to post about work occasionally, and a way of making that easy enough that they actually do.

Why a colleague's post travels further than your page's

Two reasons, and neither has anything to do with gaming an algorithm.

The first is that people follow people. A profile with a face and a job and opinions reads as a person talking; a company page reads as a company talking. Readers discount the second automatically, the same way you skim past an ad.

The second is reach overlap. Your company page's followers are mostly customers, competitors and people who clicked once. Your team's followers are former colleagues, people from their last job, their industry peers. When five people post about the same launch, it lands in five networks that barely overlap with each other — or with yours.

This is the same reason founder-led content outperforms the brand account. Employee advocacy is that idea extended past the founder.

Start with a smaller ask than "please share this"

The default move is to drop a link in the team chat with "would love a share 🙏". It mostly doesn't work, and when it does the result is the worst kind of post: a bare link with no comment, which signals obligation rather than interest.

Ask for something smaller and more specific instead. Not "share the launch post" but "if you want to post about the launch this week, here's the one thing worth saying about it." The difference is that you've done the thinking and they only have to decide whether they agree.

Make it opt-in and say so out loud. Someone who doesn't want their personal profile associated with work has a perfectly good reason you don't need to hear, and pressuring them produces a stilted post that helps nobody.

Send a starting point, not a script

The thing to hand your team is not finished copy. If five people post identical paragraphs on the same morning, everyone who follows two of them can see exactly what happened, and the credibility you were borrowing evaporates.

Send three things instead:

• The fact. What happened, in one line, with any number or detail they're allowed to repeat.
• The angle. Why it's interesting to their audience specifically — the engineer's followers care about the technical constraint; the designer's care about the problem it solved for users.
• A rough draft they're expected to rewrite. Say that explicitly. A draft labeled "change this to sound like you" gets rewritten; a polished one gets pasted.

This is where AI earns its place. Generating one caption and sending it to five people is the failure mode. Generating five genuinely different takes on the same fact — one technical, one customer-focused, one short and blunt — and letting each person pick the one closest to how they already write, takes about a minute and removes the blank-page problem without flattening everyone into the same voice. If your team already has a brand voice guide, note that personal posts should deliberately not match it. The brand voice is for the brand account.

The best things to post about aren't company news

Announcements are the weakest material. They're the thing you want shared and the thing people least want to post, because "my employer did a thing" is an ad and everyone knows it.

The posts that actually work are the ones that would be interesting even if the company name were removed:

• Work in progress. The problem someone is stuck on this week, or how they got unstuck.
• Something learned the hard way. A decision that turned out wrong and what replaced it.
• The customer problem. Not the product — the situation the product exists for, described by someone who talks to customers all day.
• An honest opinion about the industry. Disagreeing with something publicly is the single most reliable way to get a reply thread going.

Company news still gets posted. It just shouldn't be the only thing, or the thing you ask for most often.

Make it part of the calendar, not a side project

Advocacy dies when it lives in a separate channel that someone has to remember to check. The fix is to treat these posts as planned content like anything else — a lane on the same content calendar as the brand posts, with the fact and angle attached to the item, so the person who's going to post can see it a week out instead of being surprised on launch morning.

If your team already runs drafts through an approval workflow, keep personal posts out of it. Nobody should need sign-off to post on their own profile, and the moment they do, participation stops. The only review worth having is a confidentiality check on anything involving a customer name, a number, or an unannounced feature — and that's a question, not an approval gate.

A realistic cadence for a five-person company is one planned moment a month plus whatever people post spontaneously. Weekly is a job; monthly is a habit.

What not to do

• Don't mandate it, and don't track who posted. The moment it's measured per person it becomes compliance, and compliance posts read like compliance posts.
• Don't ask the team to pile into the comments on the brand account within the first hour. It's visible, it's obvious, and it teaches your team that social is theater.
• Don't push personal posting during a crisis. When something has gone wrong, the response belongs on the company account, where it can be corrected. Asking individuals to carry it exposes them to a pile-on you can't protect them from.
• Don't rewrite someone's post for them. Suggest a cut; never hand back an edited version.

Measuring it without fooling yourself

You will not get clean numbers, and chasing them is how good programs turn bureaucratic. You can't see the impressions on a colleague's personal post unless they tell you, and attributing a signup to one particular share is mostly guesswork.

What you can watch: whether traffic and inbound messages spike on the days team posts go out, whether new followers on the brand account arrive in clusters around those days, and — most usefully — what people say in replies. A good advocacy post generates conversations in someone's DMs that would never have reached your inbox. Ask the team what they heard. That's the real reporting line, and it's more useful than the follower chart anyway.

Start with two people

Don't launch this. Pick the two colleagues who already post occasionally, give them the fact-angle-draft treatment for one thing next month, and see what comes back. If it works, other people will ask to be included, which is the only recruitment method that produces posts worth reading.