Employee advocacy

Twelve people posting the same words is not advocacy.

Every programme starts the same way: a Slack message with a link and a suggested caption. A few people paste it, the feed fills with identical sentences on the same morning, and the whole thing reads as coordinated because it is. The fix is not better captions. It is a different unit of work.

One idea, adapted per personApprovals before anything publishesNo employee passwords

Used by leaders from

★★★★★4.8/5on G2LinkedIn® Verified Partner
GoogleAppleMetaNVIDIACiscoSAPAccentureGoldman SachsAmerican ExpressHSBC
Why the Slack message fails

Three reasons nobody shares the post

None of them are that your colleagues do not care. They are all about what you are asking them to do.

It is not their words

Posting a paragraph you did not write, under your own name, to people who know how you talk, is genuinely uncomfortable. Most people quietly decline rather than say so.

It arrives at the wrong moment

The ask lands mid-morning with no context and competes with everything else in the channel. By the time anyone reads it, the window it was meant for has closed.

Nobody sees a result

The people who did post never hear what happened, so there is no reason to do it again. Advocacy dies of silence far more often than of refusal.

The change

One idea becomes twelve different posts

Not one post shared twelve times. Twelve posts that happen to be about the same thing, each in the voice of the person whose name is on it.

01

Comms writes the idea, not the post

The angle, the fact, the thing worth saying. One input, kept in one place, instead of a caption nobody wants to use.

02

It adapts to each voice

Every participating employee has their own voice profile, built from what they have already posted. The engineer’s version and the salesperson’s version are genuinely different posts.

03

They edit and approve their own

Nothing publishes under someone’s name until they have read it and said yes. That single step is the difference between a programme people tolerate and one they use.

04

Everyone sees their own numbers

Per person, not just programme totals. People keep posting when they can see that it did something for them, and not otherwise.

The part legal asks about

Nobody hands over a password

Employee advocacy tools have a habit of asking staff to install an extension or share credentials. That is where these programmes get blocked internally, and rightly.

What gets blocked

Extensions and shared logins

A browser extension acting on an employee’s session, or a shared account posting on their behalf. It puts personal accounts at risk, it is impossible to audit, and it usually breaches your own policy on credential sharing.

What we do

Each person authorises their own

Every employee connects their own account from LinkedIn and can disconnect it themselves the day they leave, without asking IT or comms. You keep an audit trail of who approved what. Nobody on your team ever sees a credential.

Being straight about scope: this is a publishing and voice tool, not a compliance product. It gives you an approval step and a record of who said yes, which is what most teams actually need. If you are in a regulated industry with formal archiving obligations, ask us before you buy rather than after.

What it costs at team size

Priced per employee account, published

The usual advocacy pricing is a per-seat licence and a call. Ours is on the page.

People posting
Plan
Per month
5A leadership team, or a first pilot group.
Studio
$59
10$59 for the first five, then $9 each.
Studio
$104
20Agency covers twenty and includes the API.
Agency
$149
50$149 for the first twenty, then $6 each. About $6.60 a person.
Agency
$329

Comms staff, editors and approvers are never charged for. You pay for the accounts that publish, so the people running the programme do not add to the bill.

Questions

What comms teams ask

Can we make employees post?+
No, and any tool that offers to is one you should not buy. Posting under someone’s own name without their explicit approval is a problem for them and for you. Every post here needs the account holder to say yes first, deliberately.
What happens when someone leaves?+
They disconnect their account, or you remove it from the workspace. Either way their posts stay on their profile, because it is their profile. Nothing of theirs was ever yours to take back, which is worth being clear about at the start of the programme rather than the end.
Will the posts still look coordinated?+
Less so, because they are different posts rather than the same words. It also helps to stagger them across a few days rather than publishing at nine on a Tuesday, and the calendar does that per account by default.
How do we report on it?+
Per person and across the programme: reach, engagement and how consistent each participant has been. The per-person view matters more than it sounds, because it is what keeps people going.
Do employees need training?+
Roughly ten minutes. They connect their account, read a draft, edit it and press publish. If a tool needs a training session, the programme will not survive its first busy month.

Start with five people, not the whole company

Fourteen days free, no card. Pilot it with a leadership team, see whether the posts actually sound like them, and add the rest only if it works.

Per employee account. Comms staff and approvers are free.