Employee Advocacy Share Tracker

The problem this kills

Employee advocacy almost always lives in a Slack message and a hope. A new blog post or product launch goes out, someone in marketing types "hey team, please share this!", drops a link, and that's the program. A few helpful people share it. Most don't. Nobody knows who did. There's no copy people can just grab, so the eager folks paste the same headline and the post looks like a bot wrote it. Two weeks later your boss asks "did the advocacy push work?" and you genuinely cannot answer, because there is no record of who shared what, where, or when.

Then the messy version: someone shares a post the legal team hadn't actually cleared. A link in one of the "ready" posts turns out to be broken, and now twelve employees have shared a 404. The same person reports the same share twice and the leaderboard is suddenly nonsense. And because it all lived in chat, the moment the thread scrolls away, the program has no memory at all.

This Implementation Plan replaces that whole mess with a small, private internal tool: a clean feed of approved posts employees can amplify, a simple way for them to self-report shares, an owner who confirms those shares before they count, a leaderboard that actually means something, and a permanent activity record you can export.

What you'll build

A login-protected web app for your marketing/comms team and your employee advocates that:

• Lets a marketing owner approve posts into a shareable feed - copy, asset or link, and which channels each post is meant for. Nothing reaches employees until the owner approves it.
• Gives each post suggested copy variants employees can personalize, so shares don't all look identical.
• Flags broken links in a post before it can be published, so nobody amplifies a dead URL.
• Shows employees a clean feed of ready-to-share posts - grab the copy, grab the asset, share.
• Lets employees self-report a share (which post, which channel, optional link to their post).
• Puts every self-reported share behind a confirmation step - the owner confirms it before it counts toward anything.
• Builds a participation leaderboard from confirmed shares.
• Exports a clean activity CSV so you can report on the program or feed it into whatever system you use.

It's built to fit your program, because the very first thing it does is interview you about how your team actually works.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code), and it builds the tool with you step by step. No prior coding needed.

• It starts by interviewing you about your business. Before writing a line of code, the plan has the agent ask about your current process, the channels your people share on, the exact shape of your posts and roster data, your typical and peak volumes, your approval and confirmation rules, and your real edge cases. Then it reads back a short tailored spec and waits for your thumbs-up. You get a tool shaped to your program - not a generic template.
• A clear definition of done so you know exactly what "finished" looks like.
• Every build step ends with a ready-to-copy prompt you paste into the agent.
• A "No API yet?" fallback so you can build the whole thing today using CSV/Google Sheet imports and a clean CSV export - no integration with a social platform or HRIS required.
• A verification checklist so you can prove it works before anyone relies on it.

The governance it includes (this is the point)

This isn't a toy. Every runbookify plan builds in the controls that make an internal tool safe to use:

• Login so only your team and your advocates can open it.
• Row-level security so each organization only ever sees its own posts, roster, and shares.
• A complete audit trail - who approved a post, who reported a share, who confirmed it, and when.
• A hard human-in-the-loop approval gate - the tool drafts and stages, but a post only reaches employees after the marketing owner approves it, and a self-reported share only counts after the owner confirms it. The AI drafts; a person commits.
• Duplicate guards keyed on employee + post, so the same share can never be double-counted on the leaderboard.

Who it's for

Marketing and comms ops people running employee advocacy without a paid platform - the folks who keep asking the team to "please share this" and wish they could prove it worked. If you can keep a clean spreadsheet, you can run this tool, and you'll finally have a measurable, auditable advocacy program instead of a chat thread.

You've got this - paste the first prompt and let the agent interview you.