Your advocacy program does not have a cadence. It has you.
Every post happens because you asked. You send the reminders, you supply the topics, you rebuild the same report from screenshots each month. The program works, and it only works while you push it.
€ 299/month flat · 5 seats included · Cancel anytime · 90-day ROI guarantee
Management Report Preview
June 2026
Network Growth: Last 6 Months
Do you need software to run an employee advocacy program?
Not always, and the threshold is specific enough to check. A program of three or four people runs fine on a spreadsheet and a group chat, and plenty do. Software starts paying for itself once three things are true at the same time:
- You are supplying topics to more people than you can hold in your head.
- You cannot tell who has gone quiet without checking profiles by hand.
- You are rebuilding the same report from screenshots every month.
Below that threshold a tool adds administration. Above it, the program depends on one person continuing to push, which is a fragile way to run anything. The decision that actually comes up at this point is rarely tool against no tool. It is tool against letting the program lapse, because the person carrying it ran out of room.
Disclosure before we go further: we build Authira, one of the tools in this category. The threshold above is the honest version, and it argues against buying anything for a good share of the people who read this page.
What employee advocacy program management actually consists of
Running a program without a tool is not one job, it is four, and they recur every single month. They are worth naming separately, because a tool only replaces some of them and you should know which.
Supplying topics
You answer "I don't know what to write about" for every participant, every month, and the ideas you hand over get posted almost verbatim.
Chasing and reminding
A monthly nudge, sometimes personalised, that you feel slightly bad about sending. Posting happens when you push and stops when you do not.
Noticing who went quiet
You find out six weeks late, by chance, when you happen to look at someone's profile. By then re-activating them is a conversation, not a nudge.
Building the report
Screenshots into a slide, impressions added up by hand, and a sentence about strong engagement that you know is thin.
Three of the four run continuously through the month. The fourth lands in one block at month end. That is why reporting is the line most people underestimate when they add up what the program costs them: it feels like a single task and rarely is.
A fifth job, deciding who joins and why the program exists, does not appear here on purpose. No tool replaces it and none should.
Price your own hours before you price the software
The objection that comes up first is that a spreadsheet is free. It is not, it is just unbilled. The comparison worth making is your own time against a licence fee, and it needs two numbers you already have.
First, your hours. Over the next month, count the time that goes into the four jobs above: topic supply, chasing, checking who has stopped, and reporting. Count it as it happens rather than from memory, and include the month-end block.
Second, what an internal hour costs. Use whatever figure your organisation actually plans with, fully loaded, not the gross salary divided by hours.
To make the shape visible, an illustration with placeholder numbers, not a benchmark, and not our data:
| Line | Illustration | Your figure |
|---|---|---|
| Hours per month on the four jobs | 10 h | ? |
| Fully loaded cost per hour | € 45 | ? |
| Monthly cost of doing it by hand | € 450 | ? |
| Authira licence, 5 seats | € 299 | ? |
The hours and the hourly rate are placeholders chosen to show the arithmetic. Substitute your own; the exercise is the point, not the result.
The licence line is not flat at every size. € 299 covers 5 seats, which is what the illustration above assumes, and every further seat is € 49 per month. A 10-person program is therefore € 544, not € 299. Everyone who drafts and uploads needs a seat, so put your real participant count in before you compare the columns.
Two honest caveats. The hours do not go to zero, they go down. Topic supply and reporting are largely removed, chasing is reduced rather than removed, and a new small task appears: each member uploading their own export. And this says nothing about whether the program is worth running at all, which is answered in euros of reach rather than in hours, in the guide to employee advocacy ROI. To compare the licence fee against other vendors instead, see the per-vendor cost breakdown.
What changes, job by job
Same four jobs, with the mechanism that takes each one over. Nothing here is a promise about participation, only a statement of what the software does.
| Job | What takes it over |
|---|---|
| Supplying topics | Each person generates three drafts from their own expertise profile, written in their own voice, with an idea generator when they are stuck. |
| Chasing and reminding | A shared monthly target and a team view everyone can see. The nudge is still yours, but it is informed and it is rarer. |
| Noticing who went quiet | A health check listing every member with their last data sync, posts in the past week, and consistency streak. |
| Building the report | Team impressions, posts published, share of members active, and earned media value in euros, exported as a PDF. |
The reporting line is the one most people buy for. Instead of a slide you rebuild each month, the reporting screen holds team impressions, posts published, the share of members who were active, and the reach valued in euros as earned media value. It covers any of the last twelve months and exports as a PDF. Which figures are worth putting in front of leadership, and which are noise, is covered in the guide to advocacy metrics and KPIs.
The topic supply line matters more than it looks. A topic you hand over tends to get posted close to verbatim, which makes it sound like you rather than like them, and that is the opposite of what the program is for. Why people freeze in the first place is covered in the piece on blank page anxiety.
Knowing who has gone quiet, before it needs a conversation
With two participants you hold all of this in your head. At five it gets harder. At ten the overview is gone, and someone drops from twice a month to once to not at all without anyone registering it. Re-activating that person six weeks later is a conversation. Catching it in week two is a message.
Team Health Check
Publishing activity in the last completed calendar week.
Healthy (Active)
7 Users
Pending Sync
2 Users
Inactive
1 Users
Creator Activity Matrix
The health check lists every member with posts in the last completed calendar week, their consistency streak, the date of their last data upload and a status. It sorts so that whoever needs attention sits at the top, which makes it a two-second read rather than a report.
One distinction on that screen is worth understanding before you rely on it. Someone whose upload is out of date shows as Pending Sync, not as inactive, because the product genuinely cannot tell the difference between a person who stopped posting and a person who stopped uploading. Only a member with a current upload and no posts is counted as inactive. That is the honest limit of an export-fed dashboard, and the screen is built to show it rather than hide it.
What the program asks of everyone else
Most of what is described above is your screen, not theirs. Members work in two places: the content assistant, where a draft is generated and edited, and the upload screen for their LinkedIn analytics export. Publishing does not change, because each person still copies the finished post into LinkedIn from their own account. Whether those drafts sound like the person or like a machine is answered in the FAQ below, with the mechanism rather than a promise.
The part that is easy to miss is what everyone can see. Participants each see the likes on their own post and nothing else, which is why a program that is working can still feel to its members like individual homework. The team view is visible to every member rather than to admins only: collective reach, the monthly target, streaks and a leaderboard with colleagues' names on it. For most teams that visibility is the point. For a few it is a conversation to have before the invitations go out.
If the program sits inside a larger organisation
Plenty of advocacy programs run inside companies of several hundred people, owned by one department rather than by the company. Authira works for that shape, and only for that shape: a pilot of roughly five to fifteen voluntary participants in one team, which sits well inside the 3 to 30 the product is built for. A company-wide rollout at several hundred seats is a different product, and an enterprise advocacy suite is the right buy for it.
Where the data sits. Each participant downloads their own LinkedIn analytics export and uploads it, so nothing reaches the dashboard that a member did not upload themselves. The data privacy page sets out processing and storage in full.
What it deliberately is not. Nothing in the product feeds a performance review. There are no individual targets and no manager-facing scoring, and the one shared goal is a monthly team target rather than a quota per person.
Codetermination. In Germany a works council conversation usually belongs before a pilot rather than after it, because a system able to record activity per person can fall under codetermination. The FAQ below sets out what that hinges on. It is orientation rather than legal advice.
Getting it signed off. Billing is a monthly Stripe subscription and every invoice downloads as a PDF from the billing screen, which usually covers a departmental expense line. If procurement, a data processing agreement or a works council has to be walked through it first, the demo is faster than signing up.
What Authira does not do
Worth knowing before you evaluate rather than after. These are design decisions, not gaps waiting to be filled, and any one of them is a good reason to buy something else.
- No approval workflow. No review queue and no admin view of drafts. Guardrails flag your blacklisted terms while someone writes and once more before they mark a post ready, and the author decides.
- No scheduling and no auto-posting. Finished drafts are copied into LinkedIn by the person who wrote them.
- No LinkedIn API connection. Analytics come from each member uploading their own export and refreshing it. Nobody uploads, nobody appears in the reporting.
- No reminder emails. The product shows you who has gone quiet. It will not message them for you.
- No click tracking or pipeline attribution. Reach and earned media value, never revenue.
- No company content library to reshare. Drafts start from the individual. That is a deliberate rejection of the megaphone model, and the wrong answer if a curated library is what you came for.
- The team view is visible to everyone. Reach, streaks and a leaderboard with colleagues' names go to every member, not only to admins.
- Built for roughly 3 to 30 participants, self-managed. It is also not an agency: nobody at Authira runs the program for you.
€ 299/month flat · 5 seats included
5 seats included · Cancel anytime · 90-day ROI guarantee
See full pricingRunning an advocacy program: FAQ
We already run a program without software. What would a tool actually change?
Four recurring jobs change hands, and one new job appears. Topic supply moves to each member drafting from their own expertise profile. Reporting moves from screenshots in a slide to a dashboard you export as a PDF. Noticing who has stopped moves from checking profiles by hand to a weekly status list. Chasing gets smaller but stays with you, because there are no reminder emails. What no tool replaces is the relationship work, who joins, and what the program is for. The new job: every member uploads their own LinkedIn analytics export and keeps it current, or the reporting stays empty.
How much time does running an employee advocacy program take?
That depends on the number of participants and on how much of the writing you absorb yourself, and any average quoted for it is guesswork unless it comes from your own calendar. The shape is more useful than a figure. It is four recurring jobs: supplying topics, chasing participants, noticing who has stopped, and building the report. Three run continuously and one lands in a block at month end, which is the line most people underestimate. Authira publishes no hours benchmark, because there is no customer dataset behind one.
Can I approve posts before my team publishes them?
Not in Authira. There is no approval queue and no admin view of drafts. Brand guardrails work preventively instead: your blacklisted terms are flagged while someone writes and again before they mark a post ready, and the author decides. If sign-off before publication is mandatory in your organisation, Authira is the wrong tool and an enterprise suite with a review workflow is the right one.
Will the posts sound like they were written by AI?
Every draft the assistant generates goes through a second pass before anyone sees it. A deterministic check reads each paragraph for eight patterns that give machine-written text away. Among them: the dash used as an aside, the three-part list as a rhetorical figure, and the rhetorical question answered in two words. Anything flagged goes to an editing pass that may rephrase but may not invent facts, numbers or names. Underneath sits a profile per person holding tonality, expertise topics, red lines and their own anecdotes. It is a mechanism, not a guarantee, and drafts stay editable.
Does my team have to learn a new tool?
They work in two screens: the one where a draft is generated and edited, and the one where they upload their LinkedIn analytics export. The heavier screens, brand rules and the team health check and the reporting, belong to you as the admin. Members also see the team view: collective reach, the monthly target and a leaderboard carrying colleagues' names. Publishing does not change, because each person copies the finished post into LinkedIn from their own account.
We have a works council. Can we still run an advocacy program?
Often yes, as a voluntary pilot, and that conversation belongs before the rollout. In Germany a system capable of monitoring employee performance or behaviour is generally subject to codetermination under section 87 (1) no. 6 of the Works Constitution Act. Authira does record posting activity per person, consistency streaks and a named leaderboard. What tends to make a pilot workable: participation is voluntary, the data comes from an export each person uploads themselves, and nothing feeds a review or an individual target. None of that clears a mandatory rollout. This is orientation written with German law in mind, not legal advice, and the question belongs with your works council and qualified counsel.
How large can a program get before this stops working?
Authira is built for roughly 3 to 30 participants who run the program themselves. Past about 30, a dedicated program manager, formal approval workflows and enterprise administration start to matter, and an enterprise advocacy suite is the better fit. We compare that market openly rather than pretending the ceiling is not there.
Where does the reporting data come from?
From each member's own LinkedIn analytics export, which that person downloads from LinkedIn and uploads to Authira. There is no API connection, no account linking and no background collection, so the dashboard only shows what people have uploaded. A team that drafts in Authira but never uploads will see empty reporting.
Is this the same as a corporate influencer program?
In practice yes. Corporate influencer is the term that established itself in German-speaking markets, employee advocacy is the term used in English-language material, and both describe employees publishing under their own name about their work. Some practitioners reserve corporate influencer for a small group of deliberately developed voices, but the operational problems are identical.
Keep reading
- Why employee advocacy programs fail: the four failure modes, and why collapse is a design problem rather than a people problem.
- The employee advocacy software market, compared: nine tools by category, pricing model and team-size floor.
- What employee advocacy software costs: verified per-vendor pricing, and the per-seat against flat-rate maths.
- The LinkedIn EMV calculator: put a euro figure on the reach your team already produces.
- Launching a program from scratch: the four internal conversations and the pilot shape, if you are setting one up rather than already running it.
Let the program stand up without you
Topic supply and reporting stop being your job. You keep the parts that actually need you. Flat € 299 per month, 5 seats included, cancel any time.
5 seats included · Cancel anytime · 90-day ROI guarantee
Last updated