Module 3: Employee Advocacy
This is the force multiplier. Your page posts reach a fraction of what personal posts do — but your employees' personal posts reach their full networks. The Advocacy Engine is the system that connects the two, and it's the highest-ROI tactic in this entire course.
The reach math that changes everything
Let's do the math. Your company page has 500 followers. A good page post reaches maybe 10–20% of them — call it 75 people. Now take one employee with 800 connections. Their personal post routinely reaches 30–50% of their network — call it 320 people. One employee's share reaches four times the page's entire post. Now multiply by your team.
This is the Advocacy Engine: your employees, sharing and engaging with company content from their personal profiles, acting as a coordinated distribution network. Ten employees sharing one page post doesn't add 10x reach — it compounds, because each share reaches a different network, triggers its own engagement, and signals to the feed that the content is worth showing. The page plants the flag; the people carry it into territory the page could never reach alone.
And there's a trust multiplier on top of the reach multiplier. People trust people more than logos — a post shared by "Priya, who actually works there" carries credibility that a logo post never will. Prospects see real humans standing behind the company, which feeds straight back into the Credibility Stack. Your team's networks are your most underused marketing channel. They already exist, they're free, and right now they're silent. This module turns them on.
The reach math
One employee beats the whole page
Build brief
Do the reach math for your business: how many people (employees, partners, contractors) could share page content, and roughly how many connections do they have combined? What's your potential reach vs your page's current reach?
Saved
Building the engine: notify, template, schedule
Advocacy fails when it's vague ("everyone please share our posts!") and works when it's a system. The system has three parts. Notify: every time the page posts, the team hears about it within the hour — a Slack channel, a team chat, a short email. Not a demand, a heads-up: "new page post is live, here's the link." People can't share what they don't know exists.
Template: give them words. Most employees don't share because they don't know what to say — staring at a blank comment box feels like homework. Provide two or three starter lines they can copy, tweak, or ignore: "Proud of what our team shipped here — the onboarding numbers surprised even us." "We've been working on this for months; here's what changed." The starters aren't scripts; they're on-ramps. Most people will personalize them, and that's better.
Schedule: make it a rhythm, not a campaign. The ask is two minutes, once or twice a week: when the page posts, share it with a line of your own. Put it in the team meeting agenda for the first month until it's habit. Recognize the people who do it — a shout-out in the team channel costs nothing and keeps the engine running. Make sharing the easiest thing on their to-do list. Friction kills advocacy; a link plus a starter line in the chat is zero friction.
The engine
Notify, template, schedule
The Advocacy Engine loop
Build brief
Design your notify system: which channel, who sends it, and what does the message say? Draft the actual notification message you'd send the team.
Saved
Reposts done right: thoughts beat bare shares
Here's a finding worth building around: a bare repost — clicking "repost" with no added words — gets a fraction of the reach of a repost with your own commentary. The research puts bare reposts roughly a third below reposts-with-thoughts. The feed treats a bare repost as low-effort duplication; it treats a repost with your own framing as new, original content worth showing. Same click, wildly different outcome.
So the engine's rule is simple: never bare-repost — always add thoughts. When the team shares a page post, each person adds one to three lines in their own voice: why it matters, what they saw behind the scenes, who should read it. "Sharing this" is a bare repost with extra steps. "I watched our team rebuild this onboarding flow three times — here's why version three finally worked" is a new post that happens to amplify the page.
The same principle applies to commenting, which is advocacy's quieter cousin. A thoughtful comment on the page's post from an employee does two jobs: it boosts the post's engagement signals (comments are heavier than likes), and it puts the employee's name and face in front of the post's audience. Teach the team the commenting basics: add to the conversation (never "great post!"), comment early (first-hour engagement shapes the post's trajectory), and reply when people respond to you. Thoughts are the currency. Bare shares are pocket change.
The finding
Thoughts beat bare shares
Build brief
Take your most recent page post (or a planned one). Write 3 different "repost with thoughts" starters — one for you, and two in voices that fit different team members.
Saved
Advocacy reach estimator
Play with the numbers — everything updates live.
Potential audience reached:0
vs. a page post reaching 15% of 500 followers:0 x the page's reach
A 20-person agency's page posts get ~150 impressions each. The founder asks the team to "please share our posts." Two people do, with bare reposts. Reach barely moves. What's the fix?
Your turn: Write your advocacy launch message to the team — the why (2 sentences), the ask (2 minutes, 1–2x/week), and what you'll provide (notification channel + starter lines). Keep it under 150 words.
Saved.
Your next 24 hours
Set up the notification channel (Slack, Teams, group chat) and send the first heads-up the next time the page posts — with two starter lines included. The engine starts with one message.
Steal this template
THE ADVOCACY LAUNCH MESSAGE
Team — our LinkedIn page is how buyers check we're real, but page posts barely reach anyone. Your shares change that: one share from you reaches more people than the page post itself.
The ask: 2 minutes, 1–2x a week. When the page posts, I'll drop the link + starter lines in [#channel]. Share it with a line of your own — never a bare repost, always your thoughts.
Totally optional, genuinely appreciated. First post goes live [day].
Module 3 cheat sheet
- One employee's share can out-reach the entire page post — the math compounds across the team.
- The Advocacy Engine: notify, template, schedule. A system, not a plea.
- Notify within the hour of every page post — people can't share what they don't see.
- Provide starter lines: the #1 reason people don't share is not knowing what to say.
- Repost with thoughts dramatically outperforms bare reposts — never share empty.
- Keep it voluntary, keep it 2 minutes, recognize the sharers, repeat weekly.