Employee advocacy without an app: nothing for anyone to install

The advocacy platform is bought in March. By May, four of the fifteen invited people have logged in, two have posted through it, and the rest never opened the invitation. The tool works exactly as demonstrated. What failed is that fifteen busy people were asked to add something to their week.

This page shows how to run employee advocacy without an app: no installs, no logins, no queue anyone has to approve. What you give up, what you keep, and when a platform is genuinely the right call. For founders and marketing leads with a small team.

TL;DR

Why advocacy platforms stall

The cost is not the licence. It is the adoption tax paid by every participant, every week, forever. Each person has to remember a tool that is not part of their job, open it, find the queue, and choose something. That is three decisions before any content exists.

There is a second problem the demo never shows. A queue of pre written posts produces near identical updates from ten people on the same morning, which reads as coordinated to exactly the audience you were trying to reach. The employee gets the reach, and none of the credibility.

The distribution asset is the person's credibility. Anything that makes their feed look automated spends it.

The version with nothing to install

Strip the program back to what actually produces distribution: a person, a rhythm they agreed to, and something they wanted to say. The company's job becomes supply and measurement, not approval.

• Agree a cadence per person. One number, sized for their worst week. See posting cadence for teams.
• Supply raw material, not finished posts. Customer questions, product decisions, numbers they are allowed to share. The words stay theirs.
• Count from the public profile. Nobody reports anything, and the count cannot decay with enthusiasm.
• Make it visible. One board the group can see, ranked on cadence and never on reach. See content posting streak.

Total install count for the participants: zero. Total accounts connected: zero. The only thing anyone has to do is the thing you actually want them to do, which is publish.

What you give up, honestly

This approach is not free of trade offs, and the trade offs are worth naming before someone discovers them in month three.

The last row is the honest exception. If you are in a regulated sector where every public statement needs review before it is published, you need a workflow with an approval step, and a platform earns its cost.

The consent question nobody asks

Counting what an employee publishes publicly is not the same as monitoring them, but it deserves a conversation rather than a surprise. Tell people what is counted, which is posts on the handles they gave you, and what is not, which is anything private.

Two rules keep it clean. Only track handles a person hands over themselves, and stop when they ask. A program that has to be hidden from its participants is not a program, and it will end badly.

How to choose

• Under 15 people. No app. The adoption tax alone will beat any feature list.
• Regulated industry. A platform with an approval workflow, because the constraint is legal rather than motivational.
• Hundreds of employees. A platform, because supply and coordination genuinely become a logistics problem at that size.
• An agency running it for a client. No app, plus a client view of the numbers. See client reporting for personal branding.

How to supply raw material without writing the posts

The company's job in this model is supply, and supply is not a queue of finished posts. It is the raw material a person can turn into their own words in fifteen minutes.

• A weekly note with three things. A customer question, a decision made, a number you can share. Three lines each, in a channel.
• A shared list of what is not confidential. Most people post nothing because they are unsure what they are allowed to say.
• One prompt per person, occasionally. You saw this, you could tell that story. Personal, not broadcast.
• Nothing to approve. An approval step reintroduces the queue you removed, with a manager attached.

The test is simple. If the supply mechanism disappeared for a month, would people still post? If the answer is no, you built a queue with extra steps.

What to do when nobody posts

It happens in month two, and the reflex is to add pressure. That reliably converts a quiet program into a resented one. Do these three things first.

• Halve the cadence. The most common cause is a number agreed in an optimistic meeting.
• Check the material. If the weekly supply note stopped, the program stopped for a reason that is yours.
• Ask one person privately. The honest answer is usually about confidence or permission, and neither is fixed by a reminder.

The first thirty days, step by step

None of this needs a project plan. The whole setup is four conversations and a board, and it fits inside a week.

1. Start with the people who already want to. Five willing participants beat fifteen conscripted ones, every time.
2. Agree one number each, out loud. Ask what they could hold in a bad month, then write that down rather than the number they offered first.
3. Collect the public handles. One link each, sent from a phone. That is the entire technical setup.
4. Open the board on day one. People behave differently when the count is visible from the start, rather than introduced in month two as a correction.

Then leave it alone for four weeks. The first month exists to show whether the rhythm survives contact with a normal week, and adding pressure early removes the information you were trying to collect.

What to measure when there is no tool in the middle

Removing the platform removes its dashboard, and the reflex is to assume the program becomes unmeasurable. The opposite happens: the measurement stops depending on whether anyone used the tool.

• Posts published per person, against their own cadence. Counted from the public profile, so it is right even for the person who never opens anything.
• Periods held in a row. The streak is the program's health expressed as one number.
• Followers added per person. Public, and slow, so read it quarterly rather than weekly.
• Public reactions and comments per post. A weak signal about quality, and a decent one about which topics land.

What you never get is reach, because it does not exist outside the account owner's own analytics. That boundary is mapped in public social media metrics, and it applies to every product in this category, app or no app.

What the two versions actually cost

The licence is the number on the invoice and it is rarely the largest one. Put the full cost of both versions side by side before choosing.

The row that decides it is the third one, because it is paid by everyone, every week, forever. A platform has to buy back that weekly cost with something people actively want, and for a team of ten publishing under their own names, it almost never does.

The full practice, including what the reach arithmetic really returns once participation is discounted, is in employee advocacy.

How Groowth handles this

Groowth is the measurement half of the no app version. You paste the public handles people gave you, and it reads them once a day. Participants install nothing, connect nothing and log in to nothing, because there is nothing for them to use.

What the organiser gets is a board: one lane per person, the cadence each agreed, streaks, and one shared objective. What participants get is not being chased. Three accounts free, no card.

Frequently asked questions