GRW-13 · SEC. 10 Marketing & Growth
Turn Organic Mentions Into a Repeatable Amplification Loop
A recurring weekly check that turns scattered organic mentions into a ranked, actionable queue.
- FORMAT
- loop
- DIFFICULTY
- advanced
- TIME
- 10 min
- TOOLS
- universal
- MODELS
- any
- COPIES
- 0 so far
When to use this
People are already posting organically about your product — tweets, reviews, community threads — but nothing systematic happens with it. Run this weekly with last week's queue as input; the good mentions stop getting lost after week one instead of amplification staying a one-off thing you remember to do sometimes.
The pattern
This is a recurring weekly loop. Last week's queue state and this week's new raw mentions are filled in below the line at the end of this block.
For each new mention:
1. Classify it: worth amplifying (specific praise, a real use case, a concrete before/after story) or noise (generic "nice tool," a complaint, spam). Drop the noise from the output entirely, don't list it.
2. For each mention worth amplifying, output: source and link, the person's name or handle if public, a one-line reason it's worth amplifying, and a suggested action — reply and reshare / ask permission to feature as a testimonial / invite to a case study call / repost with credit.
3. Rank the new mentions by amplification value: a specific, provable claim from an identifiable, credible source ranks above vague praise from an anonymous account.
4. Carry forward anything from last week's queue that's still unactioned, tagged "CARRIED OVER, N weeks". If something has been carried over 3+ weeks, flag it for a decision: act on it now or drop it.
5. End with an updated queue split into two sections: Done This Week (what got actioned) and Pending (everything still open, ranked), so next week's run only has to process what's new.
Last week's queue ("none, first run" if this is new):
New raw mentions this week (links with quotes, review excerpts, screenshots-as-text, any format):Real example output
Previous queue: None, first run. New mentions this week: 1. X post from @priya_builds (2,400 followers): "switched our whole team over to this from spreadsheets last month, saved probably 5 hours a week just on status updates" — worth amplifying. Specific claim, identifiable source, credible follower count. Action: reply publicly, then DM to ask permission to quote on the site. 2. G2 review, 5 stars, from "Verified User in Marketing": "great product, does what it says" — noise, dropped. No specific detail, no attribution. 3. Reddit comment in r/ProductManagement from u/throwaway_pm: "been using this for 3 months, the reporting feature alone is worth the price, went from a full day building the monthly deck to about 40 minutes" — worth amplifying. Specific before/after number, but anonymous account, so ranks below #1. Action: reply with a thank-you, ask if they'd do a short quote under any name they're comfortable with. Ranked queue: 1. @priya_builds — specific claim, public identity, high follower count 2. u/throwaway_pm — specific claim, anonymous account Updated queue: **Done this week:** none yet, both are new. **Pending:** #1 (new), #2 (new). Nothing carried over — first run.
Why it works
Splitting "finding mentions" (still manual, still your job) from "deciding what to do with them" (the actual bottleneck) means the loop only has to be smart about triage, not discovery. The carry-forward queue with an age tag is what stops a good mention from quietly dying in a bookmarks folder, which is the default failure mode of UGC amplification without a system.