Advocacy Campaigns: One Brief, Every Leader

The problem we were solving

Campaign launches at most B2B companies produce one of two outcomes:

A wave of identical posts — everyone sharing the same caption from Slack.

Or comms teams ghostwriting individually for every leader, which doesn't scale past three or four people.

Neither is sustainable. And neither produces the kind of distinct, authentic-sounding content that performs on LinkedIn or X.

The right answer is: one campaign brief that generates original posts for every person in scope, each reflecting their voice and role.

That is what Advocacy Campaigns does.

How it works

The brief is the spec. Marketing fills in a structured campaign brief with these fields:

• Campaign name — internal label for the campaign
• Target audience — who each post is aimed at, specific enough to inform angle and vocabulary
• Key message — the one thing every post should communicate, regardless of who writes it
• Claims to include — approved supporting facts, features, or proof points
• Claims to exclude — language, topics, or claims employees should not make
• Tone direction — register for this campaign (not each employee's voice, which Bloomberry handles)
• Reference materials — product updates, press releases, one-pagers the AI draws from

The employees define the angle. Bloomberry maps each employee's voice profile and role context against the brief before generating. The CEO post opens at an executive framing level. The Head of Sales post anchors in customer perspective. The product manager post carries technical specificity. Same brief. Different angles.

LinkedIn and X in one run. For each employee in scope, Bloomberry generates a LinkedIn post and an X (Twitter) variant. LinkedIn posts are formatted for professional audiences. X variants are character-aware rewrites. Both generate from the same campaign — no duplicate writing.

Approval before anything publishes. All drafts enter a marketing review queue. Marketing edits inline if needed and approves. Employees see their final draft and provide a second approval. Nothing goes live without consent from both sides.

What this replaces

Before Advocacy Campaigns, teams running employee advocacy faced a manual distribution problem:

• Writing individual posts for every leader is too slow for regular campaign cadences
• Pushing a shared template produces copy-paste feeds that readers immediately recognize as amplification
• Asking employees to write their own versions produces variable quality and inconsistent messaging

Advocacy Campaigns removes the tradeoff. Every employee gets an original post. Every post goes through governance. The campaign runs on a brief, not on a ghostwriting team.

Use it with a structured brief

If you want a pre-built starting point, the employee advocacy brief template mirrors the exact fields inside Bloomberry's campaign brief intake. Fill it out before opening a new campaign.

What's coming next

• Signal-triggered campaign creation — start a campaign from a signal Bloomberry detected in the signal intelligence feed
• Saved brief templates — save a brief structure for recurring campaign types (quarterly product launches, weekly thought leadership series)
• Campaign performance analytics — reach, engagement, and participation data aggregated across all employees in a campaign run

---

For the full feature overview, see employee advocacy campaign software.

For the platform architecture behind it, see employee advocacy platform.