How to Get Employees to Post on LinkedIn Without Forcing Them

On this page

Start with five people, not the whole company
What advocacy actually costs, in hours and in money
The Supersonify First Five: how to choose who starts
The thirty minutes is the programme, and this is what happens inside it
Why advocacy programmes die in month three
What to ask for, and what never to ask for
How to report it so it keeps getting funded
When not to run an advocacy programme at all

The short answer

Pick five people, pay for the time, and cost it before you launch. A programme of twelve posters writing one post a fortnight at thirty minutes each costs about thirteen hours of paid time a month plus a coordinator. Asking everyone and paying nobody produces a spike in month one and silence by month three. The selection rule matters more than the enthusiasm.

Start with five people, not the whole company

Five is the right number to start with because the binding constraint is not employee willingness, it is coordinator attention. Every advocacy programme that collapses collapses at the same point: one person in marketing was quietly holding twenty relationships together in the gaps between their real job, and then they took two weeks off.

Assume the coordinator spends twenty minutes per post. That covers finding the idea, nudging the person, reading the draft, and logging that it happened. Twenty minutes is generous for a good week and light for a bad one, so treat it as an average and replace it with your own once you have three months of data.

That single assumption gives you a headcount ceiling. Coordinator hours available per month, multiplied by three, is the number of posts you can actually support. Divide by 2.2 and you have the number of advocates you can carry at one post a fortnight each.

Coordinator hours per month	Posts you can support	Advocates at one post a fortnight
2	6	3
4	12	5
8	24	11
16	48	22
32	96	44

Assumption: twenty minutes of coordinator time per published post, advocates posting once a fortnight. Replace both with your own figures once you have them.

Five advocates costs about four hours of coordinator time a month. That is the real reason to start at five, and it is the number to take to whoever owns that coordinator's calendar. Nobody argues about four hours. Everybody argues about a vague new initiative.

What advocacy actually costs, in hours and in money

A twelve person programme lands near 26 hours a month before you buy any software. That is the number missing from every page that tells you to lead by example and make it easy. Here is where it comes from, with every assumption labelled so you can argue with it.

Twelve advocates posting once a fortnight produce 26 posts a month, or 312 posts a year. Employee writing time at thirty minutes per post is 13 hours a month. Coordinator time at twenty minutes per post is 8.7 hours a month. One hour of training per advocate per quarter adds another 4 hours a month. The total is 25.7 hours a month and 308 hours a year.

Line	Assumption	Hours per month	Note
Employee writing time	30 minutes per post, 26 posts	13.0	The only line that actually produces a post
Coordinator time	20 minutes per post	8.7	Idea, nudge, read, log
Training and voice sessions	1 hour per advocate per quarter	4.0	Front loaded, drops after two quarters
Advocacy software	Optional	0.0	Under about thirty people a shared document beats a platform nobody opens
Total		25.7	308 hours a year

Illustrative cost model for twelve advocates posting once a fortnight. Every figure in the assumption column is a stated assumption, not a benchmark.

Now put a rate on it. Assume a blended fully loaded cost of 40 per hour in your own currency, which you should replace with your real one, and 308 hours becomes roughly 12,300 a year. That is the honest sticker price of a twelve person advocacy programme. It is not free, it was never free, and the pages calling it a free channel are counting nobody's time.

The 308 hours are borrowed, not new

This is not new headcount. It is time taken from people who already have full jobs. If you cannot name what those 308 hours stop being spent on, the programme is not funded, it is borrowed, and borrowed time gets repossessed in the first busy quarter.

Set that annual figure against what the same money buys in paid distribution before you commit. If your LinkedIn ads cost per lead sits at a level where 12,300 buys a meaningful number of qualified conversations, advocacy has to justify itself against that alternative rather than against zero. The comparison is covered properly in LinkedIn ads cost per lead.

The Supersonify First Five: how to choose who starts

Pick on network relevance and writing stamina. Job title predicts nothing and kickoff enthusiasm predicts less than nothing, because the loudest person in a launch meeting is often the one with the least control over their own calendar.

The Supersonify First Five

Score every candidate out of ten across five tests, two points each. Take the five highest scorers rather than the five most willing. One of the five tests is a veto.

Buyer adjacency, 0 to 2Does their existing network already contain people who could buy or refer? A solutions engineer who has worked at three of your customers scores 2. A talented finance hire whose network is former classmates and former colleagues in an unrelated sector scores 0, through no fault of their own. LinkedIn's own targeting data says four out of five members drive business decisions, but that is a claim about the platform's total membership, not about the particular seven hundred people your advocate happens to know.

Stamina evidence, 0 to 2Have they written anything voluntarily in the last twelve months? An internal wiki page, a conference talk, a long explanation in a Slack thread that nobody asked for. Voluntary writing in the past is the only reliable predictor of voluntary writing in the future, and it beats every stated intention you will collect in an enrolment survey.

Opinion tolerance, 0 to 2Will they publish something a competitor would openly disagree with? An advocate who will only repeat approved messaging produces posts that nobody reads and nobody replies to, which is a worse outcome than no posts at all because it burns their credibility as well as the coordinator's hours.

Replacement depth, 0 to 2If this person resigns in six months, can somebody else speak on the same topic? Two means the topic survives them. Zero means you are building a programme that a single resignation ends. Score this at the start, when it is a selection question, rather than at the exit interview, when it is a problem.

Calendar reality, 0 to 2, and this one is a vetoDoes their working fortnight contain thirty uninterrupted minutes that their manager has explicitly agreed to give up? Not whether they could find it. Whether their manager has agreed to it, in writing, with a date. Anybody scoring zero here is out regardless of their total, and that veto kills more doomed programmes at week zero than every other rule on this page combined.

Candidate	Buyer adjacency	Stamina	Opinion	Depth	Calendar	Total	Decision
Solutions engineer, previously customer side	2	1	2	1	2	8	In
VP Sales, quarter end in three weeks	2	1	2	1	0	6	Out, no agreed time
Support lead who writes the help centre	1	2	1	2	2	8	In
Founder	2	2	2	0	1	7	In, with a depth warning
Product marketer	1	2	1	2	2	8	In
Account executive, three weeks into the job	1	0	1	2	2	6	Out for now, revisit at six months

Illustrative scoring. These are composite people assembled to show the rubric working, not real employees.

Notice what the rubric does to the VP of Sales. High on network, high on opinion, and out of the programme because nobody has actually protected thirty minutes of their fortnight. That is the correct answer. Enrolling them anyway is how you end up with a league table showing one senior person at zero posts, which is worse for the programme than their absence.

The thirty minutes is the programme, and this is what happens inside it

The thirty minutes of paid time is not administration. It is the step that turns a company sentence into a sentence the person would say out loud in a bar, and it is the only part of the process that cannot be delegated to marketing, to a tool, or to a model.

Most programmes skip it. They send a pre-written post and a share button, collect a burst of identical text across twenty accounts, and conclude that advocacy does not work. What did not work was the shortcut.

Minutes 0 to 5, read the source

One paragraph maximum, containing the claim and one piece of evidence. If the brief is longer than a paragraph, the coordinator has not finished their job yet and the advocate is about to spend their thirty minutes doing it.

Minutes 5 to 10, find the disagreement

Ask the advocate which part of the company line they would put differently. That answer is the post. If they agree with every word of it, there is no post this cycle, and telling them so is what keeps them in the programme next cycle.

Minutes 10 to 20, write it badly in their own words

A voice note into a transcription tool works better than a blank document for most people, because talking bypasses the internal editor that makes everybody write like a press release. Bad and theirs beats polished and yours.

Minutes 20 to 25, cut the marketing out

Remove every adjective that only a marketer would use. Remove the call to action. Keep the specific number, the specific customer situation, the specific thing that went wrong. Specificity is the only defence against sounding like the other nineteen accounts.

Minutes 25 to 30, they publish it themselves

Never schedule it centrally on their behalf. The replies arrive in their notifications, and the reply is where advocacy actually earns anything. A post published by a tool tends to be a post whose comments nobody answers.

The skip is a feature

Explicit permission to skip a cycle without explaining why is the single cheapest retention mechanism in an advocacy programme. It costs nothing and it removes the low grade dread that makes people stop opening your messages in month three.

If an executive wants marketing to draft for them properly, that is a different arrangement with different rules, and it needs a written position on disclosure. Set it out before the first draft, using an advocacy policy worth signing rather than a generic conduct document.

What to take away

Five posting employees is a programme, forty enrolled employees is a spreadsheet, and the difference becomes visible in month three.
Thirty minutes of paid time per post is the whole mechanism, because it is the step that converts a company message into a sentence the person would actually say out loud.
Pick advocates on network relevance and writing stamina, never on job title or on how loud they were in the kickoff meeting.
Budget the coordinator before you budget the software, because the coordinator is the part of the programme that fails first.
Report posts published and conversations started, never an internal participation rate, because participation rates make people feel policed and policed people write nothing worth reading.

Why advocacy programmes die in month three

Month three is when the novelty has gone and the calendar reasserts itself. Four failure modes account for almost all of it, and each one has a signal you can watch for in month one, before the programme is dead and the budget conversation has already happened.

Failure mode	How it looks in month three	Early signal	Fix
Unfunded time	Posts stop without anybody announcing it	Advocates whose managers never agreed the thirty minutes	Get the manager's written agreement before enrolment, not the employee's
Central drafting	Every post reads the same and only colleagues engage	Advocates changing fewer than half the words in the draft	Move drafting back inside the thirty minute session
Participation reporting	Advocates go quiet after the first internal league table	A per person participation percentage appearing in any deck	Report posts published and conversations started, never a compliance rate
One person carrying it	Output halves the week the top advocate is on leave	Top advocate producing more than 40% of posts, a house threshold rather than a published benchmark	Recruit for replacement depth, which is test four of the rubric above

The four common failure modes, the early signal for each, and the fix that is cheap in month one and expensive in month four.

of LinkedIn members post more than once a week. That is the base rate you are recruiting against, so a plan that assumes every enrolled employee becomes a weekly poster is a plan built on the exception rather than the rule.

Aggregate 2026 LinkedIn statistics reports

The participation reporting failure is the one that surprises people. A league table feels like gamification and reads like surveillance, particularly to anybody at the bottom of it who has a legitimate reason to be there. Once an advocate believes their posting rate is a performance metric, the posts they produce start optimising for the metric, and the metric is not the thing you wanted.

What to ask for, and what never to ask for

Ask for one post a fortnight in their own words on a topic they picked from a short list. Never ask for a verbatim reshare. The verbatim reshare is the most common ask on the internet and the least productive, because identical text arriving from twenty accounts reads as identical text and everybody scrolls past copy number three.

Ask for these

One post a fortnight, in their words, on a topic they chose from a list of three
Permission for the company page to reshare their post afterwards
A comment on the page post within a day, if they feel like it
Thirty minutes in the calendar, agreed by their manager, recurring

Never ask for these

Their login, under any circumstances, including a handover
A word for word reshare of a company post
A like target, a comment target or a share target
A post about a launch they had no part in and cannot answer questions about
Continued posting during leave, notice period or a personal crisis
A public explanation of why they chose not to post this cycle

The second list does more work than the first. Publish it in the enrolment email, above the obligations, and the enrolment rate goes up for a reason that has nothing to do with motivation techniques: people sign things faster when the limits are written down by the other side first.

How to report it so it keeps getting funded

Report three lines and put everything else in an appendix: posts published, conversations started, and cost per conversation. Impressions get the programme cut in the first budget review that goes badly, because impressions are the number an unconvinced finance director already suspects you of hiding behind.

Reporting line	How you get it	Why it survives
Posts published	Count them, by hand if necessary	It is an output, not a claim, and nobody can dispute a count
Conversations started	Advocates log inbound messages and calls that referenced a post	It is the only advocacy number a salesperson also recognises
Cost per conversation	Programme hours times your blended hourly cost, divided by conversations	It sits directly beside your cost per lead on paid without needing translation
Impressions and engagement rate	Available from the platform in two clicks	It does not survive. Keep it in the appendix where it can do no harm

The three reporting lines that survive a budget review, and the one that does not.

Cost per conversation is the line that gets the second year funded. Using the model above, 308 hours at an assumed 40 per hour is 12,300 a year. Thirty conversations makes that 410 per conversation. Ten conversations makes it 1,230. Both numbers are defensible sentences in a board meeting. Neither of them requires you to explain what an impression is worth.

Before you promise a reach figure to anybody, run the arithmetic yourself rather than borrowing a vendor multiplier. The method is set out in the advocacy reach arithmetic, including the overlap correction that most calculators quietly drop.

When not to run an advocacy programme at all

Do not run one if you cannot fund the time, if fewer than three people have buyer adjacent networks, or if the last internal initiative was announced with enthusiasm and then abandoned without comment. The third disqualifier is the one people ignore and it is the most reliable predictor of the outcome.

No funded time. If no manager will protect thirty minutes a fortnight, the programme is a request for unpaid overtime with a dashboard attached, and people recognise that faster than you think.
Fewer than three buyer adjacent networks. Network relevance beats headcount every time, and a six person consultancy where four people know the buyers has a better programme than a two hundred person company where only sales is visible to the market.
Credibility debt from the last initiative. Every abandoned programme raises the cost of the next one, because the rational response to the fourth launch email in two years is to wait it out.

One person properly beats twenty badly

If the honest answer is that nobody will be given time, run one person properly instead. One founder posting fortnightly with real attention gives the market something specific to react to. Twenty accounts resharing the same graphic gives the market twenty copies of one thing, and copy number two adds nothing that copy number one did not already say.

That is not a consolation prize. One well chosen advocate at 26 posts a year costs 13 hours of their writing time and about 9 hours of coordination. It fits inside a marketing manager's month without a budget line, and it tells you whether the mechanism works in your market before you ask twelve people to commit to anything.

Questions people ask next

Should I pay employees extra to post on LinkedIn?

Pay for the time rather than for the post. Thirty minutes inside the working day, agreed with their line manager, is the payment. A per post bonus turns advocacy into piecework, which produces volume without judgement, and it also creates a material connection that your disclosure policy then has to handle explicitly.

What do I do if an employee refuses to post?

Nothing. A refusal is information about fit, not about loyalty, and a programme that penalises refusal produces compliant posts that read as compliant to every reader. Take them off the advocate list, keep them on the internal distribution list, and spend the coordinator hours you just recovered on somebody who volunteered.

How many employees do you need before advocacy is worth running?

Three people with buyer adjacent networks is the practical floor, and it is not a headcount threshold. Company size matters far less than network relevance. A six person consultancy where four people personally know the buyers has a stronger programme than a two hundred person company where only the sales team is visible.

Can marketing write the posts and have employees publish them?

It works for executives inside an agreed voice process and it fails for everybody else. Centrally drafted posts written for somebody who did not choose the topic read as centrally drafted, and the advocate cannot answer the comments because the opinion was never theirs. Either way, write your disclosure position down first.

How long before an employee advocacy programme shows up in pipeline?

Expect conversations well before pipeline, and anybody quoting you a fixed timeline is guessing. What you can control is the input, which is posts published per month, and you can measure that from week one. If the input stalls in month two, nothing downstream will arrive in month six.

Sources