Launch playbook

How to launch employee advocacy with 20, 50 or 100 employees.

The programme should get more structured as company size grows, but the principle stays the same: start with a focused advocate group, use real marketing content, remove friction, preserve employee choice and measure what happens after distribution.

Updated 6 Sep 2026Ripply Insights
20 employees

Keep it human and prove the habit.

Start with 5–10 advocates

Founder/leadership, Sales, Customer Success and one or two subject-matter experts are usually enough to test whether employee-powered distribution creates incremental reach and traffic.

  • One programme owner in Marketing.
  • 2–4 strong source assets per month.
  • Review-first posting.
  • Weekly check-in with advocates for the first month.
  • Track participation, clicks and examples of real conversation.
50 employees

Segment by relevance, not hierarchy.

Start with 15–25 advocates

Build groups around the content they can credibly speak about: leadership, Sales, CS, Product/technical experts, People and recruitment.

  • Route customer proof to Sales and CS.
  • Route technical insights to relevant experts.
  • Route employer-brand content to employees actually involved in the story.
  • Use saved voice preferences and scheduling to reduce admin.
  • Report by content type and advocate group.
100 employees

Add governance without turning it into bureaucracy.

Start with 25–40 advocates, then expand

At this size, the problem becomes consistency. You need clear permissions, content ownership, onboarding and reporting—but employees should still feel like participants, not distribution endpoints.

  • Nominate functional champions.
  • Define review-first vs auto-approved content types.
  • Create a simple social policy and escalation route.
  • Measure active advocates rather than licences issued.
  • Expand only after the first cohort has a repeatable rhythm.
30 / 60 / 90 days

A rollout rhythm that works at any size.

  1. Days 1–30: prove adoption.Can the right employees receive relevant content, review it quickly and actually publish?
  2. Days 31–60: prove distribution.Which content and advocate groups create incremental reach, clicks and engagement?
  3. Days 61–90: prove business value.Connect traffic to conversions, opportunities, hiring outcomes or other programme goals.
Read the full Ripply playbook →

Sources and methodology

Last reviewed 6 September 2026. Product capabilities change, so verify vendor details before making a purchase decision.

FAQ

Questions people ask

Should every employee be enrolled in employee advocacy?

No. Start with employees whose roles, networks and willingness make them credible advocates. Expand after the workflow is working.

How long should an employee advocacy pilot run?

Use 30 days to test adoption and at least 60–90 days to understand distribution patterns and downstream outcomes. Content and network effects need repeated activity.