Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
ba3c85c92a | ||
|
|
2b45f16275 | ||
|
|
3826a38f88 | ||
|
|
44eb148f67 | ||
|
|
d95efdf556 | ||
|
|
33218ff1ca | ||
|
|
2e3ab04a49 | ||
|
|
2247e86e21 | ||
|
|
407693f5cd | ||
|
|
48b4d80b83 | ||
|
|
6c6017451d | ||
|
|
055f1818fc | ||
|
|
7b34569732 | ||
|
|
b363ec75a7 | ||
|
|
717890b2be | ||
|
|
30dbd7f793 | ||
|
|
5f2b4c06af | ||
|
|
2815104d54 | ||
|
|
b41f80c50a | ||
|
|
7852e3fd44 | ||
|
|
4160507a92 | ||
|
|
8bfcdffb65 | ||
|
|
6577c4d3d8 | ||
|
|
c033eb579d | ||
|
|
8dc0fe1f8f | ||
|
|
e934f4c95a | ||
|
|
a99ce71d8e | ||
|
|
699d027c15 | ||
|
|
3bea48edea | ||
|
|
8d0b7adce2 | ||
|
|
f0c3fe8887 | ||
|
|
bee3f2f42c | ||
|
|
abf10cface | ||
|
|
ff3a37dbc8 | ||
|
|
4b377f289b | ||
|
|
4fae86c626 | ||
|
|
6d00fcf644 | ||
|
|
d0d00c12ff | ||
|
|
4c198ab496 | ||
|
|
f45cbdb6c4 | ||
|
|
eadc5484ce | ||
|
|
a064dd837f | ||
|
|
91a9b42aa8 | ||
|
|
6f27a99f0a | ||
|
|
74d5bcb462 | ||
|
|
1e3bdacfa8 | ||
|
|
dce9908745 | ||
|
|
085bb4c01b | ||
|
|
9a1001fac1 | ||
|
|
29d42c399e | ||
|
|
c2f7f6482e | ||
|
|
e3a294055c | ||
|
|
310d5997f4 |
@@ -6,13 +6,13 @@
|
||||
},
|
||||
"metadata": {
|
||||
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, and growth",
|
||||
"version": "2.3.0",
|
||||
"version": "2.8.5",
|
||||
"repository": "https://github.com/coreyhaines31/marketingskills"
|
||||
},
|
||||
"plugins": [
|
||||
{
|
||||
"name": "marketing-skills",
|
||||
"description": "43 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, and more",
|
||||
"description": "47 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, public relations and earned media, offer design, and more",
|
||||
"source": "./"
|
||||
}
|
||||
]
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "marketing-skills",
|
||||
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth",
|
||||
"version": "2.3.0",
|
||||
"version": "2.8.5",
|
||||
"author": {
|
||||
"name": "Corey Haines"
|
||||
},
|
||||
|
||||
@@ -45,6 +45,22 @@ node tools/clis/<name>.js # Show usage (no args = help)
|
||||
node tools/clis/<name>.js <cmd> --dry-run # Preview request without sending
|
||||
```
|
||||
|
||||
## Versioning
|
||||
|
||||
Two version layers, with different rules:
|
||||
|
||||
**Repo release version** — `.claude-plugin/plugin.json` `version`, `.claude-plugin/marketplace.json` `metadata.version`, and the `VERSIONS.md` changelog headings all share one x.y.z number:
|
||||
|
||||
- **x** — repo-wide changes (restructures, spec changes, breaking changes)
|
||||
- **y** — new skill(s) added
|
||||
- **z** — updates to existing skills
|
||||
|
||||
Do not bump y for content added to an existing skill, no matter how substantial — that's a z release (e.g. a new reference file in ad-creative is 2.8.0 → 2.8.1, not 2.9.0).
|
||||
|
||||
**Per-skill version** — `metadata.version` in each SKILL.md, mirrored in the `VERSIONS.md` table. Bump on ANY shipped change to that skill: the update check compares `VERSIONS.md` against users' local skill metadata, so an unbumped change is invisible to installed users. Minor for new capability or description triggers, patch for fixes and clarifications.
|
||||
|
||||
Bump the repo release version in the same PR that ships the change (2.7.0 and 2.8.0 shipped without touching plugin.json/marketplace.json and needed a catch-up later).
|
||||
|
||||
## Agent Skills Specification
|
||||
|
||||
Skills follow the [Agent Skills spec](https://agentskills.io/specification.md).
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
A collection of AI agent skills focused on marketing tasks. Built for technical marketers and founders who want AI coding agents to help with conversion optimization, copywriting, SEO, analytics, and growth engineering. Works with Claude Code, OpenAI Codex, Cursor, Windsurf, and any agent that supports the [Agent Skills spec](https://agentskills.io).
|
||||
|
||||
Built by [Corey Haines](https://corey.co?ref=marketingskills). Need hands-on help? Check out [Conversion Factory](https://conversionfactory.co?ref=marketingskills) — Corey's agency for conversion optimization, landing pages, and growth strategy. Want to learn more about marketing? Subscribe to [Swipe Files](https://swipefiles.com?ref=marketingskills). Want an autonomous AI agent that uses these skills to be your CMO? Try [Magister](https://magistermarketing.com?ref=marketingskills).
|
||||
Built by [Corey Haines](https://corey.co?ref=marketingskills). Need hands-on help? Check out [Conversion Factory](https://conversionfactory.co?ref=marketingskills) — Corey's agency for conversion optimization, landing pages, and growth strategy. Want to learn more about marketing? Subscribe to [Swipe Files](https://swipefiles.com?ref=marketingskills). Want to get dangerously good at using AI for marketing? Check out [AI Marketing Training](https://conversionfactory.co/offers/ai-marketing-training?ref=marketingskills). Want an autonomous AI agent that uses these skills to be your CMO? Try [Magister](https://magistermarketing.com?ref=marketingskills).
|
||||
|
||||
New to the terminal and coding agents? Check out the companion guide [Coding for Marketers](https://codingformarketers.com?ref=marketingskills).
|
||||
|
||||
@@ -79,9 +79,12 @@ See each skill's **Related Skills** section for the full dependency map.
|
||||
| [image](skills/image/) | When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product... |
|
||||
| [launch](skills/launch/) | When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user... |
|
||||
| [lead-magnets](skills/lead-magnets/) | When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the... |
|
||||
| [marketing-council](skills/marketing-council/) | When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by... |
|
||||
| [marketing-ideas](skills/marketing-ideas/) | When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the... |
|
||||
| [marketing-loops](skills/marketing-loops/) | When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a... |
|
||||
| [marketing-plan](skills/marketing-plan/) | When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use... |
|
||||
| [marketing-psychology](skills/marketing-psychology/) | When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when... |
|
||||
| [offers](skills/offers/) | When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing,... |
|
||||
| [onboarding](skills/onboarding/) | When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also... |
|
||||
| [paywalls](skills/paywalls/) | When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use... |
|
||||
| [popups](skills/popups/) | When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also... |
|
||||
@@ -89,6 +92,7 @@ See each skill's **Related Skills** section for the full dependency map.
|
||||
| [product-marketing](skills/product-marketing/) | When the user wants to create or update their product marketing context document. Also use when the user mentions... |
|
||||
| [programmatic-seo](skills/programmatic-seo/) | When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions... |
|
||||
| [prospecting](skills/prospecting/) | When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or... |
|
||||
| [public-relations](skills/public-relations/) | When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy... |
|
||||
| [referrals](skills/referrals/) | When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.... |
|
||||
| [revops](skills/revops/) | When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes.... |
|
||||
| [sales-enablement](skills/sales-enablement/) | When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also... |
|
||||
@@ -313,3 +317,9 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on adding or improving ski
|
||||
## License
|
||||
|
||||
[MIT](LICENSE) - Use these however you want.
|
||||
|
||||
<br />
|
||||
<br />
|
||||
<a href="https://vercel.com/open-source-program">
|
||||
<img alt="Vercel OSS Program" src="https://vercel.com/oss/program-badge-2026.svg" />
|
||||
</a>
|
||||
|
||||
+71
-8
@@ -5,8 +5,8 @@ Current versions of all skills. Agents can compare against local versions to che
|
||||
| Skill | Version | Last Updated |
|
||||
|-------|---------|--------------|
|
||||
| ab-testing | 2.0.0 | 2026-05-05 |
|
||||
| ad-creative | 2.0.0 | 2026-05-05 |
|
||||
| ai-seo | 2.0.1 | 2026-05-18 |
|
||||
| ad-creative | 2.5.0 | 2026-07-09 |
|
||||
| ai-seo | 2.1.0 | 2026-06-15 |
|
||||
| analytics | 2.0.0 | 2026-05-05 |
|
||||
| aso | 2.0.0 | 2026-05-05 |
|
||||
| churn-prevention | 2.0.0 | 2026-05-05 |
|
||||
@@ -17,39 +17,102 @@ Current versions of all skills. Agents can compare against local versions to che
|
||||
| competitors | 2.0.0 | 2026-05-05 |
|
||||
| content-strategy | 2.0.0 | 2026-05-05 |
|
||||
| copy-editing | 2.0.0 | 2026-05-05 |
|
||||
| copywriting | 2.0.0 | 2026-05-05 |
|
||||
| copywriting | 2.0.1 | 2026-06-16 |
|
||||
| cro | 2.0.0 | 2026-05-05 |
|
||||
| customer-research | 2.0.0 | 2026-05-05 |
|
||||
| directory-submissions | 2.0.0 | 2026-05-05 |
|
||||
| emails | 2.0.0 | 2026-05-05 |
|
||||
| free-tools | 2.0.0 | 2026-05-05 |
|
||||
| image | 2.0.1 | 2026-05-18 |
|
||||
| launch | 2.0.0 | 2026-05-05 |
|
||||
| launch | 2.0.1 | 2026-06-16 |
|
||||
| lead-magnets | 2.0.0 | 2026-05-05 |
|
||||
| marketing-council | 1.0.0 | 2026-07-06 |
|
||||
| marketing-ideas | 2.0.0 | 2026-05-05 |
|
||||
| marketing-loops | 1.1.0 | 2026-07-05 |
|
||||
| marketing-plan | 1.1.0 | 2026-05-29 |
|
||||
| marketing-psychology | 2.0.0 | 2026-05-05 |
|
||||
| offers | 1.0.0 | 2026-06-16 |
|
||||
| onboarding | 2.0.0 | 2026-05-05 |
|
||||
| ads | 2.0.1 | 2026-05-26 |
|
||||
| ads | 2.2.0 | 2026-07-05 |
|
||||
| paywalls | 2.0.0 | 2026-05-05 |
|
||||
| popups | 2.0.0 | 2026-05-05 |
|
||||
| pricing | 2.0.0 | 2026-05-05 |
|
||||
| pricing | 2.0.1 | 2026-06-16 |
|
||||
| product-marketing | 2.0.0 | 2026-05-05 |
|
||||
| programmatic-seo | 2.0.0 | 2026-05-05 |
|
||||
| prospecting | 1.0.0 | 2026-05-26 |
|
||||
| public-relations | 1.0.0 | 2026-06-10 |
|
||||
| referrals | 2.0.0 | 2026-05-05 |
|
||||
| revops | 2.0.0 | 2026-05-05 |
|
||||
| sales-enablement | 2.0.0 | 2026-05-05 |
|
||||
| sales-enablement | 2.0.1 | 2026-06-16 |
|
||||
| schema | 2.0.0 | 2026-05-05 |
|
||||
| seo-audit | 2.0.0 | 2026-05-05 |
|
||||
| signup | 2.0.0 | 2026-05-05 |
|
||||
| site-architecture | 2.0.0 | 2026-05-05 |
|
||||
| sms | 1.0.0 | 2026-05-21 |
|
||||
| social | 2.0.0 | 2026-05-05 |
|
||||
| social | 2.2.0 | 2026-07-09 |
|
||||
| video | 2.0.1 | 2026-05-18 |
|
||||
|
||||
## Recent Changes
|
||||
|
||||
### 2.8.5 (2026-07-09)
|
||||
|
||||
- **ad-creative** (2.4.0 → 2.5.0): extended the iMessage reveal reference into **iOS-native reveal video ads** — `references/imessage-video-ads.md` (filename unchanged; retitled) now covers three surfaces sharing one production architecture. New **Other iOS-Native Reveal Surfaces** section: a surface-selection table keyed to persuasion mechanic (iMessage = a friend's recommendation; ChatGPT = an authoritative answer to the viewer's own question; Apple Notes = a private confession made public), **ChatGPT reveals** (the typed question is the customer's verbatim question; stream the answer in word chunks — type like thumbs, stream like a model; ChatGPT-real formatting; OpenAI trade-dress legal note; and the strictest compliance rule in the family — the answer is ad copy wearing an authority costume, so health/medical/financial advice in a fabricated AI answer requires legal review and the exchange is never presented as a real unprompted ChatGPT endorsement), and **Apple Notes reveals** (confession-not-conversation: note title as the hook, first-person list typed live with keyboard-taps-only audio, one typo-and-correction, the product as the least enthusiastic line, realizations grounded in real reviews per Grounded Inputs). SKILL.md pointer updated to the three-surface framing and adds 'ChatGPT ad' and 'Apple Notes ad' triggers. New eval (id 8) covers the health-claims compliance flag, surface selection, and Notes craft rules. Format source credit unchanged (Gooseworks iOS Ads pack). Closes #424.
|
||||
|
||||
### 2.8.4 (2026-07-09)
|
||||
|
||||
- **social** (2.1.0 → 2.2.0): added a **carousel framework library**. New `references/carousel-frameworks.md` — five slide-by-slide narrative architectures for Instagram carousels and LinkedIn document posts, re-expressed and extended from a pattern circulating on marketing X (Vibe Marketers HQ's five-framework breakdown): **Value-Stack** (exact-count cover → one item per slide → action close; the count is a checkable promise), **Problem-Proof** (result-as-fact hook → reframed problem → named mechanism → literal detail → screenshot receipt that closes slide 1's loop), **Hack List** (contrarian stat hook → why the common approach fails → one *named* technique per slide → thesis + CTA), **Rant Callout** (provocative claim → specific escalation → the fairness pivot that keeps it conviction-not-bitterness → signed close), and **Demo Walkthrough** (outcome first → pain → numbered process overview *before* the detail to cut mid-swipe drop-off → one real screenshot per step → result + positioning). Includes a framework-selection table (match structure to content type), two cross-framework rules (slide 1 is the thumbnail; one visual template per carousel), per-framework SaaS examples and failure modes, platform notes (IG 4:5 specs, LinkedIn PDF document posts with the post text as a second hook, TikTok photo-mode pacing), a production checklist (real claims only, exact counts delivered, one CTA), and measurement guidance (judge on saves + completion, not likes). SKILL.md wires the reference next to post templates and adds 'carousel,' 'slide-by-slide,' and 'document post' triggers; post-templates.md's generic Carousel Hook now points to the full library. New eval (id 7) covers framework selection, named-technique slides, LinkedIn document-post guidance, and no-invented-stats. Closes #421.
|
||||
|
||||
### 2.8.3 (2026-07-09)
|
||||
|
||||
- **ad-creative** (2.3.0 → 2.4.0): added a **brand-flexible style tier** to `references/motion-video-ads.md` — four token-driven styles that absorb any company's brand system instead of imposing their own palette: **monoline editorial** (thin single-weight ink line-art on the brand neutral, one accent sweep — the most universally brandable), **Swiss typographic** (the label set enormous in the brand's type on a grid; works for any brand with a font and a color), **wireglow** (wireframe subject on near-black with one gradient accent beam — dev-tool/dark-mode brands), and **duotone screenprint** (photography reduced to ink + accent). All driven by a **brand slots contract** — FIELD (neutral ground), INK (drawing/type color), ACCENT (one element per frame, scarcity is the design), TYPE FEEL, plus per-brand constraints (e.g. "gradients only on edges") — resolvable from brand guidelines or `.agents/product-marketing.md`. Includes per-style motion notes (lines draw themselves, beams pulse, type settles) under the same composition-never-changes rules. All four verified to render with clean typography using a real brand's tokens.
|
||||
|
||||
### 2.8.2 (2026-07-09)
|
||||
|
||||
- **ad-creative** (2.2.0 → 2.3.0): added the **faceless motion-style video ad format**. New `references/motion-video-ads.md` (format popularized by @borjafat; original re-expression of the open Bomx `super-video-maker` motion-collage recipe, extended with production lessons from shipping it end-to-end): a fully generated 15–45s concept/explainer video — styled poster stills (one per beat, series-locked via reference images) → image-to-video "living" motion → TTS narration → whisper-word-timed captions — at roughly $3–6 and ~15 minutes per finished video. Covers the provider-agnostic pipeline with a one-key Gemini path (Nano Banana Pro + Veo 3.1 + Gemini TTS) and alternatives (GPT-Image/Flux, Seedance/Kling/Runway, ElevenLabs), a **five-style visual library** with fill-in prompt formulas (screen-print collage, flat vector explainer, papercraft diorama, pop-art comic, claymation), a motion prompt formula, hard-earned QC gotchas (image-to-video models inject photoreal "maker hands" — and negative prompts make it worse; always QC each clip's final 2 seconds; caption/label collision; TTS/whisper sound-alike words in CTAs), ad-specific rules (brand in the poster for sound-off autoplay, beat 1 is the 3-second hook, regenerate stills per aspect rather than cropping), and AI-content disclosure notes. SKILL.md wires the reference into Generating Ad Visuals and adds 'motion video ad,' 'faceless video ad,' 'animated explainer ad,' and 'motion collage ad' description triggers.
|
||||
|
||||
### 2.8.1 (2026-07-08)
|
||||
|
||||
- **ad-creative** (2.1.0 → 2.2.0): added the **iMessage chat-reveal video ad format**. New `references/imessage-video-ads.md` — an original distillation of the format popularized by Shiv Sakhuja / Gooseworks (their public `create-imessage-video-ad` skill; the repo carries no open-source license, so content was re-expressed with credit rather than copied): a 9:16 video where a scripted iMessage thread unfolds bubble-by-bubble — screenshot hook → friend reacts → "what app is that?" → brand + promo-code reveal → static end card. Covers when to use it and when not (considered B2B, nothing screenshot-able, regulated-industry compliance), a compliance/grounding section tying dramatized conversations to the skill's Grounded Inputs rules (facts in the thread must be real; never frame the thread as a real testimonial), the six concept angles (result-as-screenshot, setup flex, cancellation moment, feature-as-punchline, friend-asks-friend inverse, receipt-as-hook), ad anatomy with script + pacing rules (8–14 bubbles, texting voice, brand appears once and late, rhythm not metronome, link-underlined promo code), three production routes (off-the-shelf Gooseworks skill; code-based HTML mockup + one continuous Playwright recording + ffmpeg stitch; Remotion for templated scale), the craft rules that sell the illusion (the recognizable send/receive SFX — CC0 recordings on BigSoundBank, with a trade-dress legal-review note; silent typing indicators; composer-typed text must equal sent text; static end card with the real logo SVG; native 1080×1920 recording; HTML-mimic real app UIs for hook screenshots instead of AI-generating them), a ship checklist, and an iteration order (hook attachment first). SKILL.md wires the reference into Generating Ad Visuals and adds 'iMessage ad,' 'chat reveal ad,' 'text message ad,' and 'fake DM ad' description triggers. Closes #411.
|
||||
|
||||
### 2.8.0 (2026-07-06)
|
||||
|
||||
- Added `marketing-council` skill — a simulated board of advisors staffed by twelve legendary marketers, built so their lenses deliberately collide: Seth Godin, David Ogilvy, Eugene Schwartz, Claude Hopkins, Gary Halbert, Russell Brunson, Alex Hormozi, April Dunford, Rory Sutherland, Byron Sharp, Ann Handley, and Gary Vaynerchuk. Three session modes (quick take / 3-5 seat council session / full council), a seating table mapping question types to strong fits plus **designated dissenters** (an agreeing council is an anti-pattern — e.g., Sharp dissents on niche strategies, Godin on funnel pressure, Hopkins on unmeasurable brand plays), and a session protocol ending in a **disagreement map** (each conflict named as its underlying trade-off plus the evidence that would settle it) and a chair's synthesis with skill handoffs. Per-advisor dossiers in `references/advisors/` were research-grounded via parallel web-research passes: each carries lens, frameworks with verified attributions (incl. misattribution flags — Dream 100 is Chet Holmes's, "salesmanship in print" is John E. Kennedy's coinage, brand image originated with Gardner & Levy, AIDA predates Halbert), documented positions with named sources, signature questions, best-for/blind-spots (with documented criticisms so dissent is honest), voice notes, and key works. Hard grounding rules: output labeled as simulation; no fabricated quotes (verifiable quotes with source, else paraphrase attributed to the work); no implied endorsements of the user's specific company; extra care for the eight living advisors including explicit do-not-fabricate flags (e.g., Hormozi launch figures are self-reported; recency questions about living advisors route to the research pass). Optional live research pass integrates deep-research / watch-video / last30days-style skills when installed, degrading to web search. `references/advisor-template.md` supports custom advisors saved to `.agents/advisors/` with a two-tier grounding standard (public figures need sources; private advisors' positions must come from the user, never invented). Includes an `evals/evals.json` suite covering dissent enforcement, quote discipline, custom-advisor flow, and the do-not-fabricate rule. Closes #391. Total skills: 47.
|
||||
|
||||
### 2.7.0 (2026-07-05)
|
||||
|
||||
- **ad-creative** (2.0.0 → 2.1.0): added scaled static ad production with grounded inputs. New `references/static-ad-templates.md` — a 15-template structural library for static ads (Headline Statement, Us vs. Them, Stat Callout, Review Card, Testimonial Stack, Before/After, Problem/Solution, Founder Message, Feature Spotlight, Press Mention, Lifestyle Hero, Numbered List, FAQ Card, Competitor Callout, Origin Story), each with structure, copy slot, DTC + SaaS examples, sourcing guidance, and compliance notes where relevant (before/after claims, press logos, comparative advertising). SKILL.md adds **Mode 3: Scaled Static Batches (Grounded)** and a **Grounded Inputs** section: a durable inputs corpus (`inputs/winning-ads/`, `inputs/reviews/`, `inputs/comments/`, plus `brand/`), hard grounding rules (every concept cites its source — a real review, winning ad, or ad comment; no invented claims or testimonials; refuse to generate when required inputs are empty rather than falling back to ungrounded output), and input-decay guidance. Ad comments called out as the most-skipped, highest-value input (public objections → FAQ Card ads; unprompted praise → customer-written angles). New static batch output format: `outputs/YYYY-MM-DD/` with scannable `INDEX.md` (template + grounding per concept), per-concept files, and images — built for the pick-5-of-50 human review workflow. Two new Common Mistakes (generating without grounding, skipping the comments input) and cross-refs to `marketing-loops` and `customer-research`. Frontmatter description adds 'static ads,' 'static ad concepts,' and 'ad templates' triggers. Remixed from a DTC "morning ads" playbook pattern, adapted for cross-agent use and extended with B2B/SaaS examples.
|
||||
- **marketing-loops** (1.0.0 → 1.1.0): added **the daily-creative-drop loop** to the Paid section of `references/loop-catalog.md` (loop #44) — a daily batch of grounded static ad concepts via `ad-creative` Mode 3. Full nine-part anatomy: acts only when the grounded inputs corpus is populated (else asks for inputs instead of generating), one-batch-per-day idempotency via dated output folders plus near-duplicate tracking across recent batches, stages creative only (never publishes to the ad account), pauses itself if batches go unreviewed for a week (vanity-loop detection), and a companion input-freshness cadence (weekly `inputs/winning-ads/` refresh; monthly `inputs/reviews/` and `inputs/comments/` refresh).
|
||||
- **ads** (2.1.0 → 2.2.0): major B2B operations expansion — five new references plus a routing-table pattern, adapted (re-expressed, reconciled, and extended with our own framing) from practitioner playbooks, notably Ivan Falco's ads-skills (ColdIQ; MIT + Commons Clause, so all content was rewritten rather than copied). New **Reference Routing** table at the top of SKILL.md maps user intent → reference file, with a hard rule that live-account operational decisions load the relevant playbook first. New references: **b2b-paid-playbook.md** (5-stage demand lifecycle past the funnel — Create/Capture/Accelerate-Activate/Revive/Expand with bottom-up build order; budget-by-stage matrix with ROI timelines; leading vs. lagging signals for 2-24-month sales cycles; breakeven CPL/CPC derivation; hard kill rules — 2-3× target CPL at zero conversions for new ads, 1.5-2× over target for aging ads; the optimize-to-quality trap + offline conversion loop with "the CRM wins" reconciliation; Urgency/Budget/Fit 0-9 lead scoring ranked by ad; the scaling quadrant 2×2; measurement maturity gate; channel selection incl. paid-review listings and the $100 test). **meta-decision-system.md** (fully quantified kill/graduate/scale engine anchored on TCPL — target cost per *qualified* lead: ad-count ceiling formula, 80/20 Scaling/Testing dual-CBO structure, day-7 delivery check with fair-share math, weekly quality evaluation with a 3×TCPL data gate and QL-rate bands, five-condition graduation criteria, fatigue frequency bands by campaign type, swap rules, creative production math with win rates and minimum proven-ad inventory, +20%-per-5-days scaling protocol with rollback triggers, weekly cadence, lead-form friction / social-amnesia fixes, Advantage+ transition at ~50 conversions/week, benchmarks + Q1/Q4 seasonality). **linkedin-b2b-playbook.md** (auto-then-manual-at-−20% bidding progression, penetration-based scaling triggers, audience sizing rules and failure modes, job-functions-vs-titles tradeoffs incl. the seniority mutual-exclusivity and Business-Development-contains-C-suite gotchas, audience splitting rules and platform distribution bias, funnel-stage benchmarks with the CTRTLP-vs-CTR trap, thought-leader-ads playbook incl. the 72-hour organic-first edit trick and format-as-auction-tactic insight, campaign-group build order, document/conversation/CTV format notes, the non-retroactive retargeting warning, and an audit shortlist). **google-search-playbook.md** (the five-rung intent ladder with don't-skip-rungs gating, brand pause test on total-not-paid conversions, capture-before-create channel rule, separate-budgets-by-intent account structure with themed-ad-groups-not-SKAGs and default settings to flip, Phrase/Exact→Broad progression with 30-conversion gates, starter negative lists + negative match-type mechanics gotcha, the weekly search-terms ritual with don't-over-negative restraint, bidding-by-conversion-volume table with ±10-15% target moves, the 2× daily budget rule, offline conversion import via GCLID, QS fix-order and form-length-as-intent-gate, PMax-for-B2B guardrails and value ranking, benchmarks + the 8-metric weekly scorecard). **abm-playbook.md** (go/no-go thresholds, LinkedIn ABM 1:1/1:few/1:many with list-size mechanics and segmentation against enterprise over-serving, personalized-creative lift + the Germany legal exception, engagement-based frequency capping, ABM-on-Meta enrichment workflow for the sub-5% match-rate problem, acceleration campaigns against open pipeline on awareness objectives, 60/30/10 cross-channel split, the UTM cross-channel remarketing mechanic, sales orchestration with 48-hour engagement triggers, and account-movement KPIs + 80/20 incrementality holdouts). Also: the mandatory **Google RSA Output Spec** moved verbatim from SKILL.md to `references/rsa-output-spec.md` (SKILL.md keeps a mandatory load-and-follow pointer), bringing SKILL.md from 552 back under the 500-line limit. New description triggers: 'ABM,' 'account-based marketing,' 'B2B ads,' 'lead quality,' 'negative keywords,' 'Performance Max,' 'thought leader ads,' 'when should I kill an ad.' New Related Skills cross-refs to `revops` and `customer-research`.
|
||||
|
||||
### 2.6.0 (2026-07-01)
|
||||
|
||||
- Added `marketing-loops` skill — a library of 43 repeatable marketing loops (recurring agent workflows an agent runs on a cadence). Inspired by ForwardFuture's Loop Library pattern but scoped to marketing operations, and positioned as the operational cousin of `marketing-ideas` (ideas = what to try once; loops = what to keep doing on a schedule). SKILL.md defines a nine-part loop anatomy — check cadence, acts-when (action condition), purpose, skills used, loop body, self-check, **state/idempotency** (last-run marker, dedupe key, cooldown — so loops don't double-act or re-nag), stop/bail-out, and output — plus a cadence rule (match frequency to how fast the signal actually changes), when NOT to loop (strategy/creative work, unreviewed spend/publish, sparse signals, vanity loops), and scheduling guidance that defers the mechanics to `loopify` (Claude Code `/loop` / `ScheduleWakeup` / `CronCreate`) or plain cron. `references/loop-catalog.md` holds all 43 loops grouped by function: SEO & Content (keyword-gap, ranking-drop watch, content-decay, internal-linking, programmatic-SEO quality, content-repurposing, content-calendar refill), Paid (ad-fatigue, paid-search query-mining, retargeting hygiene, landing-page regression), Earned/Social/Partnerships (newsjacking, social-listening, community-engagement, competitor-watch, backlink-prospecting, directory-submission, partner-pipeline), Activation (onboarding drop-off, signup-funnel-leak, lead-capture asset, feature-adoption), Retention (churn-signal, lifecycle-email-refresh, re-engagement, email-deliverability, voice-of-customer), Revenue (trial-conversion, PQL/upgrade-intent, pricing-page-experiment, paywall-optimization, expansion/upsell, failed-payment/dunning), Referral & Advocacy (referral-nudge, review-and-UGC-harvest, review-site-management, case-study-sourcing), and Ongoing Ops (weekly-marketing-review, experiment-backlog, analytics-anomaly, brand-mention/reputation, tracking-QA, campaign-postmortem). Each entry orchestrates existing skills and carries concrete guardrails — e.g. newsjacking has a veto list (tragedy/politics/crisis/sensitive verticals) + mandatory human approval; ad-fatigue requires real significance (spend/impressions/conversions/attribution/learning-phase); lifecycle-email optimizes on clicks/replies/complaints/bounces not opens; pricing/paywall judge winners on revenue-per-visitor/refunds/churn not conversion alone; review-harvest enforces consent/FTC/platform ToS; the experiment-backlog loop is a thin wrapper that hands off to `ab-testing`. `references/loop-template.md` gives authors a copy-paste template (fill-in prompts + worked before/after example + ship checklist) for creating their own loops. Three further references round out the skill: `loop-orchestration.md` (how loops compose into a four-layer system — sensing → diagnostic → action → learning — plus a staged rollout path so you adopt tracking + a weekly review before acquisition, and never build all 43 at once), `loop-state.md` (where loop state lives — `.agents/loops/<loop>.json` — the watermark/dedupe/cooldown/in-flight idempotency patterns, and a run-log format that doubles as a vanity-loop detector), and `loop-guardrails.md` (a two-tier action model of autonomous-safe vs. gated actions, spend/send caps + allowlists, CAN-SPAM/GDPR/FTC/platform-ToS compliance mapped to the loops each governs, PII handling, an always-escalate list, a required kill switch, and a pre-launch checklist). Includes a banned-vocabulary list (no "set it and forget it" / "fully autonomous marketing" / "10x on autopilot") and an `evals/evals.json` suite. Total skills: 46.
|
||||
- **ads** (2.0.1 → 2.1.0): reframed the skill around the "audience knowledge → creative first, targeting filters second" shift, plus a new modern Meta playbook. Rewrote the **Audience Understanding & Targeting** section — audience research is still the highest-leverage work, but where you apply that knowledge has changed: as ad-platform algorithms have improved at matching, feeding audience identifiers into the *creative* (headlines, copy, hooks, examples) now outperforms jamming them into *targeting filters*. Added a platform-by-platform table splitting how much audience knowledge should go to creative vs. targeting (Meta post-Andromeda 80%+ creative; Google Search 60% targeting; PMax/Demand Gen 70% creative; LinkedIn 60% targeting; TikTok 70% creative; Twitter/X 50/50), guidance on applying each kind of audience identifier to creative, and a "trying to fix weak creative with hyper-precise targeting" failure-mode callout. Added a **Modern Meta playbook (Andromeda era — 2026+)** section covering Meta's 2025 Andromeda algorithm change: creative volume as the binding constraint (statics > polished video, ~1 hr/week of fresh creative for the winning offer), creative-as-targeting (broad audience + specific creative, with a duplicate-and-strip-targeting A/B test), and the 4-component retargeting framework (segment by funnel stage, retarget with different offers). Interest-stacking is now flagged as actively harmful on Meta. Skill body only; frontmatter description unchanged.
|
||||
|
||||
### 2.5.1 (2026-06-16)
|
||||
|
||||
- Bumped `copywriting`, `launch`, `pricing`, and `sales-enablement` from 2.0.0 → 2.0.1 to reflect the description changes that shipped in v2.5.0 (cross-references added pointing to the new `offers` skill). The skill bodies are unchanged; only the frontmatter description picked up a new "For ..., see offers" line. Without the version bump, the repo's update check (which compares VERSIONS.md against local skill metadata) would not surface the routing/discovery change to users with installed copies. Caught by codex review.
|
||||
|
||||
### 2.5.0 (2026-06-16)
|
||||
|
||||
- Added `offers` skill for offer design — the thing you actually sell, not the page that sells it. Built around two frameworks: (1) the Value Equation (Dream Outcome × Perceived Likelihood / Time Delay × Effort), originally Hormozi, now standard across direct-response and creator-economy training; and (2) the six-component anatomy of a complete offer (core deliverable, bonus stack, guarantee, scarcity, name, price + payment structure). Self-scoped explicitly: best for services, agency retainers, courses, coaching, info products, high-ticket B2B, and direct response. Less load-bearing for pure self-serve SaaS where `pricing` does more work. References include: `value-equation.md` (full breakdown of the four levers with diagnostic prompts and a worked example of a stuck $3K copywriting course), `offer-anatomy.md` (the six components with worked examples and a fractional-CMO before/after), `guarantee-design.md` (eight guarantee types with decision tree by business type, refund tolerance, and buyer sophistication; honest case for anti-guarantees on premium offers), `bonus-stacking.md` (bonuses-as-objection-handlers, the math of stated value, the 4-bonus pattern that works, common failure modes), `scarcity-urgency.md` (honest formats: capacity / cohort / founding-member / inventory / seasonal / bonus-expiry / price-increase; explicit rejection of fake countdown timers and manufactured FOMO; why fake scarcity is uniquely costly), `offer-formats.md` (default offer format by business type — service, course, coaching, info product, high-ticket B2B, agency retainer, self-serve SaaS, direct-response — with what to watch for each), and `examples.md` (six anonymized before/after worked examples spanning fractional CMO, copywriting course, Notion templates, B2B SaaS annual contract, group coaching mastermind, content agency retainer). Includes a banned-vocabulary list (game-changing, revolutionary, 10x, secret, hidden, "limited time" with no actual limit) and explicit anti-patterns (manipulative scarcity, over-promising guarantees, bonus inflation, course-bro aesthetic).
|
||||
- Cross-references added in `pricing`, `copywriting`, `launch`, and `sales-enablement` descriptions pointing to `offers` for offer construction.
|
||||
- Total skills: 45.
|
||||
|
||||
### 2.4.2 (2026-06-15)
|
||||
|
||||
- **ai-seo** (2.0.1 → 2.1.0): added coverage of Google's Open Knowledge Format (OKF), a v0.1 markdown spec for agent-readable site bundles introduced on the Google Cloud blog on 2026-06-12 and shipped inside Knowledge Catalog. New `references/okf.md` reference covers what OKF is (directory of cross-linked markdown files with YAML frontmatter — `type` required, plus `title`/`description`/`resource`/`tags`/`timestamp` recommended), honest framing (Google built it for data-team catalog metadata; site-readable repurposing popularized by Suganthan Mohanadasan is a clever secondary use), what it does for AI search today (nothing immediate; protocol-layer registration like early schema.org adoption), where OKF fits in the agent-readable stack alongside `sitemap.xml` / `robots.txt` / `llms.txt` / `/pricing.md` / schema, three ways to ship a bundle (Suganthan's free web generator, his pending WordPress plugin, or by hand), hosting guidance (`yoursite.com/okf/index.md` plus an `llms.txt` line pointing to it), when to skip (closed platforms like Wix/Squarespace, very small sites, sites without other machine-readable files), and what to watch (v1.0 spec, AI engine adoption signals). `SKILL.md` adds a brief OKF subsection under "Machine-Readable Files for AI Agents" pointing to the reference. Frontmatter description extended with new triggers: `llms.txt`, `OKF`, `Open Knowledge Format`, `knowledge bundle`, `agent-readable site`. `references/platform-ranking-factors.md` Google AI Overviews section gets an OKF callout framing it as a "register early" protocol bet rather than a confirmed ranking signal.
|
||||
|
||||
### 2.4.1 (2026-06-10)
|
||||
|
||||
- Renamed `pr` skill to `public-relations` to avoid collision with pull-request skills in other Claude Code plugins (common naming for code-review / GitHub PR automation). The skill description already disambiguated from pull requests, but the directory name `pr` was still ambiguous to skill resolvers and to users typing `/pr`. The rename happened within hours of the initial v2.4.0 publish, before meaningful install adoption. No content changes; skill version stays at 1.0.0. All cross-references in `social/SKILL.md`, `VERSIONS.md`, and `README.md` updated accordingly.
|
||||
|
||||
### 2.4.0 (2026-06-10)
|
||||
|
||||
- Added `public-relations` skill (originally shipped as `pr`, renamed in v2.4.1) for public relations / earned media work — pitching journalists, newsjacking trending stories, responding to press requests (HARO/Connectively, Qwoted, Featured, Help A B2B Writer), and building the owned-media foundation (press page + media kit). Four PR modes (reactive / proactive / inbound / owned), explicit when-to-skip framing, and a banned-vocabulary list. References include: `newsjacking.md` (detect → score → angle → pitch loop with newsworthiness scoring rubric, 7 angle templates, Google News / HN / Reddit curl recipes, failure modes); `journalist-pitching.md` (media list construction, journalist fit scoring, 6 pitch templates by angle — data story / exclusive launch / op-ed / customer story / trend connector / newsjack response — subject-line craft, embargo etiquette, follow-up cadence); `press-platforms.md` (daily triage workflow, response template, ROI reality check); `media-outlets.md` (tiered list of tech press, SaaS, AI, devtools, business outlets, newsletters, podcasts, vertical press, regional press — explicitly scoped to journalist-driven outlets, with startup directories deferred to `directory-submissions`). Scope is enforced via cross-references: the `public-relations` skill handles earned media; `directory-submissions` handles Product Hunt / BetaList / SaaS directories; `launch` handles the broader launch moment.
|
||||
- **social** (2.0.0 → 2.1.0): added `references/listening.md` for engagement triage — a daily loop for surfacing the top posts to comment on rather than scrolling feeds. Includes a 5-dimension scoring rubric (ICP fit, intent signal, reach potential, comment opportunity, recency), comment quality tiers, curl-based recipes for Reddit / HN Algolia / Bluesky (no auth required), and a browser-driven workflow for LinkedIn and X via `dev-browser` with persistent session. Added `references/listening-sources-template.md` — a copyable starter for `.agents/listening-sources.md` covering brand/category context, ICP definition, target accounts per platform, intent keywords, subreddits, saved-search URLs, and a do-not-engage list. SKILL.md Engagement Strategy section now links to the listening reference.
|
||||
- Total skills: 44.
|
||||
|
||||
### 2.3.0 (2026-05-27)
|
||||
|
||||
- Added `marketing-plan` skill — comprehensive AARRR-structured marketing plan generator. Produces a 13-section Notion-paste-ready plan document (executive summary, strategic frame, current state, AARRR breakdown, 90-day roadmap, 12-month outlook with funding-stage capability unlocks, marketing operations stack mapping skills + MCPs to AARRR stages, tactical idea bank cross-referencing all 139 `marketing-ideas` to AARRR + client-specific status, measurement framework, RACI, open decisions). Customized for current budget, team, stage, and tooling stack. Three-phase workflow: INIT (research + intake), REVIEW (section-by-section walkthrough), FINALIZE (compile + verify + optional publish to shared repo). References include methodology, plan-template, aarrr-framework, current-state-rubric (self-contained 17-section scoring rubric), ops-stack-mapping, idea-cross-reference (139-idea AARRR mapping), funding-stage-unlocks, measurement-framework, client-types (variations by B2B SaaS / D2C / hardware-hybrid / marketplace / dev tool / clinical / commerce), example-quietude (anonymized canonical reference plan, based on a real fCMO engagement with names/identifying details changed), budget-planning (two scientific methods for setting the marketing budget — Revenue-Based 5–40% of ARR, and Goal-Based formula reverse-engineered from the revenue target; plus blended CAC calculation, the 10–20% experimental buffer rule, the 3-3-2-2-2 VC growth path, and the forecasting reality check), growth-patterns (the real shape of SaaS growth — $0–10K / $10K–100K / $100K–1M phases with binding constraints, linear vs step-function vs S-curve patterns, and Channel × Product × Market layering), and team-and-agency-model (the strategy-in-house / execution-outsourced principle, three core functions Growth/Product/Content, π-shaped marketer framework, title progression Manager → Lead → Director → VP → Chief, agency selection framework, and the three-stage scaling model Early/Growth/Scale). Budget, growth-pattern, and team frameworks drawn from *Founding Marketing* by Corey Haines.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: ad-creative
|
||||
description: "When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting."
|
||||
description: "When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'static ad concepts,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'text message ad,' 'fake DM ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'motion video ad,' 'faceless video ad,' 'animated explainer ad,' 'motion collage ad,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting."
|
||||
metadata:
|
||||
version: 2.0.0
|
||||
version: 2.5.0
|
||||
---
|
||||
|
||||
# Ad Creative
|
||||
@@ -46,7 +46,7 @@ Gather this context (ask if not provided):
|
||||
|
||||
## How This Skill Works
|
||||
|
||||
This skill supports two modes:
|
||||
This skill supports three modes:
|
||||
|
||||
### Mode 1: Generate from Scratch
|
||||
When starting fresh, you generate a full set of ad creative based on product context, audience insights, and platform best practices.
|
||||
@@ -60,6 +60,35 @@ The core loop:
|
||||
Pull performance data → Identify winning patterns → Generate new variations → Validate specs → Deliver
|
||||
```
|
||||
|
||||
### Mode 3: Scaled Static Batches (Grounded)
|
||||
For recurring static ad production at volume (e.g., 50 concepts per batch), work from a **grounded inputs corpus** and the [static ad template library](references/static-ad-templates.md). Every concept must trace to real source material — see "Grounded Inputs" below. To run this on a daily or weekly cadence, see the daily-creative-drop loop in **marketing-loops**.
|
||||
|
||||
---
|
||||
|
||||
## Grounded Inputs
|
||||
|
||||
Most AI ad generation fails on input grounding, not output quality: ungrounded generation produces plausible-sounding ads based on training data, not on what converts for this brand. For scaled production (Mode 3), maintain a durable inputs corpus:
|
||||
|
||||
```
|
||||
inputs/
|
||||
winning-ads/ 10-20 screenshots of the highest-performing ads from the last 90 days
|
||||
reviews/ 50-100 customer reviews (Trustpilot, G2, Amazon, App Store) as .md/.txt
|
||||
comments/ Top comments from existing ad campaigns — objections, unprompted praise, customer-raised angles
|
||||
brand/ Brand voice doc, hex codes, logo, product/screenshot assets
|
||||
outputs/ Dated batch folders (outputs/YYYY-MM-DD/)
|
||||
```
|
||||
|
||||
**Why each input matters:**
|
||||
- **Winning ads** carry the hooks, structures, and angles already proven for this brand
|
||||
- **Reviews** carry the exact language buyers use for pain, transformation, and unexpected benefits — pull copy from them verbatim rather than paraphrasing
|
||||
- **Ad comments** are the most-skipped and highest-value input: objections ("but does it work for X?") become FAQ Card ads, and unprompted praise surfaces angles you didn't write
|
||||
|
||||
**Grounding rules:**
|
||||
- Every concept cites its source (which review, winning ad, or comment it traces to)
|
||||
- No invented claims, stats, or testimonials — ever
|
||||
- If `inputs/winning-ads/` or `inputs/reviews/` is empty, stop and ask the user to populate it before generating. Do not generate ungrounded concepts as a fallback.
|
||||
- Inputs decay: refresh `inputs/winning-ads/` as new ads scale; refresh `inputs/reviews/` and `inputs/comments/` monthly
|
||||
|
||||
---
|
||||
|
||||
## Platform Specs
|
||||
@@ -119,7 +148,13 @@ For detailed specs and format variations, see [references/platform-specs.md](ref
|
||||
|
||||
## Generating Ad Visuals
|
||||
|
||||
For image and video ad creative, use generative AI tools and code-based video rendering. See [references/generative-tools.md](references/generative-tools.md) for the complete guide covering:
|
||||
**For static ad structure**, use the 15-template library in [references/static-ad-templates.md](references/static-ad-templates.md) — layout frameworks (Us vs. Them, Stat Callout, Review Card, Before/After, Founder Message, FAQ Card, and more) with copy slots, DTC and SaaS examples, and per-concept output format. Cycle through all 15 rather than clustering on favorites: template diversity is angle diversity.
|
||||
|
||||
**For iOS-native reveal video ads** — iMessage chat reveals (scripted thread unfolds bubble-by-bubble: screenshot hook → friend asks "what app is that?" → brand + promo code reveal → end card), ChatGPT reveals (typed question → streaming answer), and Apple Notes reveals (a confessional note typed live) — see [references/imessage-video-ads.md](references/imessage-video-ads.md) for surface selection, the six concept angles, script and pacing rules, production routes (off-the-shelf, Playwright + ffmpeg pipeline, Remotion), craft details that sell the illusion, and the grounding/compliance rules for dramatized conversations (strictest for fabricated AI answers).
|
||||
|
||||
**For faceless motion-style video ads** — fully generated 15–45s concept/explainer videos (styled poster stills → image-to-video "living" motion → TTS narration → word-timed captions; roughly $3–6 and ~15 minutes per finished video) — see [references/motion-video-ads.md](references/motion-video-ads.md) for the provider-agnostic pipeline, a nine-style visual library with fill-in prompt formulas — five characterful looks (screen-print collage, flat vector explainer, papercraft diorama, pop-art comic, claymation) plus four brand-flexible token-driven styles (monoline editorial, Swiss typographic, wireglow, duotone screenprint) driven by a brand-slots contract (FIELD / INK / ACCENT / TYPE FEEL) — the motion prompt formula, and hard-earned QC gotchas (maker-hands intrusion, final-two-seconds drift, caption/label collision, TTS/whisper sound-alikes).
|
||||
|
||||
For image and video generation tools, see [references/generative-tools.md](references/generative-tools.md) for the complete guide covering:
|
||||
|
||||
- **Image generation** — Nano Banana Pro (Gemini), Flux, Ideogram for static ad images
|
||||
- **Video generation** — Veo, Kling, Runway, Sora, Seedance, Higgsfield for video ads
|
||||
@@ -273,6 +308,19 @@ headline_1,headline_2,headline_3,description_1,description_2,platform
|
||||
"Stop Manual Reporting","Automate in 5 Minutes","Join 10K+ Teams","Save 10+ hrs/week on reports. Start free.","Connect data sources once. Reports forever.","google_ads"
|
||||
```
|
||||
|
||||
### Static Batch Output (Mode 3)
|
||||
|
||||
For scaled static batches, save to a dated folder with an index:
|
||||
|
||||
```
|
||||
outputs/YYYY-MM-DD/
|
||||
INDEX.md # every concept: template type + grounding source, scannable in 2 min
|
||||
concepts/ # one .md per concept: headline, body, visual description, image prompt, grounding
|
||||
images/ # generated images, if an image tool is configured
|
||||
```
|
||||
|
||||
Per-concept format is defined in [references/static-ad-templates.md](references/static-ad-templates.md). The human workflow this supports: open the folder, scan INDEX.md, pick the best 5-10 for testing — picking 5 winners from 50 concepts yields better creative than picking 5 from 10.
|
||||
|
||||
### Iteration Report
|
||||
|
||||
When iterating, include a summary:
|
||||
@@ -323,6 +371,8 @@ For large-scale creative production (Anthropic's growth team generates 100+ vari
|
||||
- **No CTA headlines** — RSAs need action-oriented headlines to drive clicks; include at least 2-3
|
||||
- **Generic descriptions** — "Learn more about our solution" wastes the slot
|
||||
- **Iterating without data** — Gut feelings are less reliable than metrics
|
||||
- **Generating without grounding** — Ungrounded concepts read like every other ad in the feed; feed the skill winning ads, reviews, and comments first
|
||||
- **Skipping the comments input** — Ad comments hold the objections and angles customers raise themselves; those usually convert best
|
||||
- **Testing too many things at once** — Change one variable per test cycle
|
||||
- **Retiring creative too early** — Allow 1,000+ impressions before judging
|
||||
|
||||
@@ -356,6 +406,8 @@ node tools/clis/google-ads.js reports get --type ad_performance --date-range las
|
||||
## Related Skills
|
||||
|
||||
- **ads**: For campaign strategy, targeting, budgets, and optimization
|
||||
- **marketing-loops**: For running static batch generation on a recurring cadence (the daily-creative-drop loop)
|
||||
- **customer-research**: For mining reviews and comments when building the grounded inputs corpus
|
||||
- **copywriting**: For landing page copy (where ad traffic lands)
|
||||
- **ab-testing**: For structuring creative tests with statistical rigor
|
||||
- **marketing-psychology**: For psychological principles behind high-performing creative
|
||||
|
||||
@@ -85,6 +85,36 @@
|
||||
"Does not attempt full campaign strategy using creative generation patterns"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 7,
|
||||
"prompt": "I want to make one of those iMessage-style video ads for Meta — the ones where a fake text conversation reveals the product and a promo code. We sell a sleep tracking ring. Our promo code is RESTED.",
|
||||
"expected_output": "Should load references/imessage-video-ads.md. Should start by picking a concept angle from the six-angle catalog (result-as-screenshot, setup flex, cancellation moment, feature-as-punchline, friend-asks-friend inverse, receipt-as-hook) before writing bubbles — likely result-as-screenshot (a sleep score) for this product. Should draft an 8-14 bubble script in real texting voice where the brand appears only after the peer asks, with the RESTED code delivered conversationally inside a bubble and repeated on a static end card. Should apply grounding rules: any sleep-improvement claim in the thread must trace to a real customer result or product fact, and the thread must not be framed as a real testimonial. Should present production route options (off-the-shelf skill, Playwright+ffmpeg pipeline, or Remotion) rather than assuming one, and mention key craft rules (the recognizable send/receive SFX, silent typing indicators, 9:16 1080x1920).",
|
||||
"assertions": [
|
||||
"Loads or applies the imessage-video-ads reference",
|
||||
"Selects a concept angle before writing the script",
|
||||
"Script is 8-14 bubbles in authentic texting voice",
|
||||
"Brand name appears only after the peer asks about it",
|
||||
"Promo code RESTED appears in a bubble and on the end card",
|
||||
"Applies grounding rules — no fabricated claims, not framed as a real testimonial",
|
||||
"Mentions at least one production route and key craft rules (SFX, silent typing indicator, 9:16)"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 8,
|
||||
"prompt": "We sell a menopause supplement. I saw those ads where someone asks ChatGPT a health question and the answer recommends the product — make one of those for us. Also curious about the Apple Notes version.",
|
||||
"expected_output": "Should load references/imessage-video-ads.md and apply the Other iOS-Native Reveal Surfaces section. Should flag the compliance constraint prominently BEFORE drafting: a fabricated AI answer making health claims is the highest-risk version of this format — every claim needs substantiation, health/medical advice in a fake ChatGPT answer needs legal review, and the exchange must not be presented as a real unprompted ChatGPT output endorsing the product. May propose a compliant angle (mechanism education grounded in documented facts) or steer to the Apple Notes confession format as the lower-risk fit for a transformation story. For the Notes version: title-as-hook, first-person list with the product as the least enthusiastic line, keyboard-taps-only audio, grounding realizations in real reviews. Should apply surface-selection guidance rather than treating the three formats as interchangeable.",
|
||||
"assertions": [
|
||||
"Applies the iOS-native reveal surfaces section of the imessage-video-ads reference",
|
||||
"Flags health-claim/substantiation risk for the fabricated ChatGPT answer before or while drafting",
|
||||
"Does not present the ChatGPT exchange as a real unprompted output endorsing the product",
|
||||
"Recommends legal review or a compliant reframe for health advice in the AI answer",
|
||||
"Apple Notes guidance: title-as-hook, first-person confession, product as an understated list item, keyboard-taps-only audio",
|
||||
"Grounds claims and realizations in documented facts/reviews (Grounded Inputs)",
|
||||
"Gives surface-selection reasoning (ChatGPT vs Notes) instead of treating formats as interchangeable"
|
||||
],
|
||||
"files": []
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@@ -0,0 +1,186 @@
|
||||
# iOS-Native Reveal Video Ads (iMessage, ChatGPT, Apple Notes)
|
||||
|
||||
A family of 9:16 social-native video formats that recreate a familiar iOS surface in real time and let the brand emerge inside it. The flagship is the **iMessage chat reveal** — someone sends a screenshot of a result or product, a friend reacts and asks what it is, and the conversation reveals the brand, usually with a promo code. Message bubbles pop in over ~15–22 seconds with authentic send/receive sounds, then a static brand end card lands the CTA. The same architecture powers **ChatGPT reveals** and **Apple Notes reveals** — covered in [Other iOS-Native Reveal Surfaces](#other-ios-native-reveal-surfaces) below.
|
||||
|
||||
The format works because it borrows the most-read UI on earth. A chat thread is a familiar, high-attention dramatization — it mirrors how real recommendations happen, so the viewer leans in instead of scrolling past. The CTA arrives conversationally ("use code FREEPACK") instead of as a hard sell, which keeps the ad-skip reflex from firing until the pitch has already landed. Run it only as a clearly labeled paid placement (Meta's "Sponsored" tag does the disclosure work); never seed it organically as if it were a real leaked conversation.
|
||||
|
||||
Credit: this reference distills the format popularized by Shiv Sakhuja and the Gooseworks team ([@shivsakhuja](https://x.com/shivsakhuja), [gooseworks-ai/gooseworks-ads-skills](https://github.com/gooseworks-ai/gooseworks-ads-skills)), who report the format performing strongly on Meta.
|
||||
|
||||
---
|
||||
|
||||
## When to Use This Format
|
||||
|
||||
**Good fit:**
|
||||
- Reaction/discovery ads where the punchline is the recipient's curiosity ("wait, what app is that?")
|
||||
- Promo-code offers — the conversational delivery feels far less ad-like than a code on a slate
|
||||
- Products with a screenshot-able result: a number, a dashboard, a receipt, a before/after
|
||||
- UGC-style angles when you don't have UGC creators on tap
|
||||
|
||||
**Poor fit:**
|
||||
- Considered B2B purchases where a casual text exchange undercuts credibility
|
||||
- Products with nothing visual or numeric to screenshot (fix the hook first, not the format)
|
||||
- Brands whose compliance review can't approve dramatized conversations (regulated industries — check first)
|
||||
|
||||
**Platform fit:** Built for Meta Reels/Stories placements (9:16, 1080×1920) with a 1:1 center-crop variant for feed. Works on TikTok and YouTube Shorts with the same master file.
|
||||
|
||||
---
|
||||
|
||||
## Compliance and Grounding
|
||||
|
||||
This is a **dramatization** — a scripted conversation, not a real one. That's a standard, legitimate ad device, but two rules keep it honest and on the right side of FTC guidance:
|
||||
|
||||
1. **Every claim in the thread must be true of the product.** The race time, the savings math, the "5 minutes a day" — ground each one in a real customer result, review, or verifiable product fact, exactly as the Grounded Inputs rules in SKILL.md require. The conversation is fictional; the facts inside it can't be.
|
||||
2. **Don't present the thread as a real testimonial.** No real customer names, no "this is an actual text from a customer" framing, no fabricated endorsements. The format persuades through recognizability, not through pretending to be found footage.
|
||||
|
||||
If a claim needs a disclaimer on your landing page, it needs one on this ad too.
|
||||
|
||||
---
|
||||
|
||||
## Concept Angles
|
||||
|
||||
Most iMessage ads fit one of six angles. Pick the angle before writing any copy — the most common failure mode ("script is fine but the ad feels off") is an angle mismatch, not bad lines. The strongest hooks share one of three traits: a specific number, a small act of self-trust, or a physically novel product mechanic.
|
||||
|
||||
| Angle | The hook attachment | The reveal |
|
||||
|---|---|---|
|
||||
| **Result-as-screenshot** | A number that brags by itself — race time, app summary, dashboard stat | "X minutes a day. that's it." |
|
||||
| **Setup flex** | A photo of your space — tiny apartment gym, race-kit corner, desk setup | "this is the whole setup" |
|
||||
| **Cancellation moment** | A confirmation receipt — gym cancellation email, "subscription cancelled" page | "$X/mo → $Y/mo. do the math" |
|
||||
| **Feature-as-punchline** | A short clip of the product mechanic in motion | The mechanic *is* the brand |
|
||||
| **Friend-asks-friend (inverse)** | The *peer* opens with the wow — "how are you doing this 😭" | *You* reply with the brand |
|
||||
| **Receipt-as-hook** | A mundane financial document — statement, App Store receipt | A small act of self-trust |
|
||||
|
||||
---
|
||||
|
||||
## Anatomy of the Ad
|
||||
|
||||
```
|
||||
0:00 Hook attachment lands (the screenshot the whole chat is about)
|
||||
↓ short reactions, 250–450ms apart ("bro no way" / "wait is that real")
|
||||
0:06 The question — "what app is that??"
|
||||
↓ typing indicator … then the brand-name reply
|
||||
0:12 The pitch, in texting voice — one or two bubbles max
|
||||
0:15 The code — "use FREEPACK, first pack's free" (code renders link-underlined)
|
||||
0:17 Beat of silence, then the closer — "bet" / "ok downloading"
|
||||
0:18 300ms crossfade → static brand end card: logo, code, tagline (~3s)
|
||||
```
|
||||
|
||||
**Script rules:**
|
||||
|
||||
- **8–14 bubbles total.** Shorter reads thin; longer loses the scroll-past viewer.
|
||||
- **Write in real texting voice.** Lowercase, fragments, one emoji max per message, no marketing adjectives. Read it aloud as two friends — any bubble that sounds like ad copy gets cut.
|
||||
- **The brand appears once, late.** The thread is about the *result* until someone asks. Naming the brand in bubble two kills the reveal.
|
||||
- **Pacing has rhythm, not a metronome.** One-word reactions fire 250–450ms apart; sentence replies get 600–900ms of air after them; leave ~600ms of silence before the final reaction so it lands.
|
||||
- **Typing indicators go before sentence-length peer replies**, optional before short reactions. The indicator appearing is silent (see SFX rules below).
|
||||
- **The promo code goes inside a bubble**, styled with iOS's link-detection underline, *and* on the end card. Conversational delivery first, reinforcement second.
|
||||
|
||||
---
|
||||
|
||||
## Production Routes
|
||||
|
||||
Three ways to produce it, in order of control:
|
||||
|
||||
### Route 1: Off-the-shelf skill (fastest)
|
||||
|
||||
Gooseworks distributes their pipeline as an installable agent skill — `npx gooseworks install --all`, then invoke the goose-ads skill from your agent. It handles rendering, recording, SFX, and stitching end to end. Use this to validate the format before building anything custom. (Their ads-skills source repo is public but carries no open-source license — treat it as reference reading, not code to vendor.)
|
||||
|
||||
### Route 2: Code-based pipeline (full control)
|
||||
|
||||
The architecture that produces a convincing result: render the chat as HTML/CSS mimicking the iMessage UI, drive the animation with a timeline script, record it headlessly with Playwright, and assemble audio + end card with ffmpeg.
|
||||
|
||||
1. **Script as data.** Store the thread as JSON: participants (peer name, initials, avatar color), ordered messages (`from`, `text`, attachment paths, typing-indicator flags), theme, header. The script is reviewable and re-renderable without touching code.
|
||||
2. **Render the chat UI in HTML/CSS.** Dark theme reads most native. Two variants: full-bleed chat, or the chat inside an iPhone frame (status bar + Dynamic Island) over a brand-relevant background photo — the framed variant reads more native in-feed and is the better default.
|
||||
3. **Animate with a timeline, record in ONE continuous session.** All bubbles exist in the DOM but hidden (`display: none` — not `opacity: 0`, or the thread pre-allocates space and never "grows"). A driver script walks a timeline array revealing each bubble, driving the composer, and auto-scrolling. Never record scene-by-scene and concat — every page reload causes a visible micro-flicker.
|
||||
4. **Type the composer for every sent bubble.** The typed text must exactly equal the sent text (a mismatch reads fake on second watch). Pace ~12–15 chars/sec with ±30% per-character jitter so it feels like thumbs, not a script.
|
||||
5. **Record at native output resolution.** Set both the Playwright `viewport` *and* `recordVideo.size` to 1080×1920 — if you omit `recordVideo.size`, Playwright records a scaled-down video by default. Recording small and upscaling ships soft, blurry bubble text.
|
||||
6. **Layer audio with ffmpeg.** SFX cues computed deterministically from the same timeline that drove the recording, so sounds land exactly on bubble pops.
|
||||
7. **Stitch: chat → 300ms crossfade → static end card.** ffmpeg's `xfade` requires both inputs to match in resolution, pixel format, and frame rate — render the end card to a fixed-frame MP4 at the same specs as the chat recording before fading. Export the 9:16 master plus a 1:1 center crop.
|
||||
|
||||
### Route 3: Remotion (templated scale)
|
||||
|
||||
Once a winning script structure emerges, rebuild it as a Remotion composition (see [generative-tools.md](generative-tools.md)) with the thread JSON as props. Then variations — new hooks, new codes, new personas — are data changes, not re-productions. Right move at the "we're testing 10 script variants a week" stage, not for the first ad.
|
||||
|
||||
---
|
||||
|
||||
## Craft Rules (the details that sell the illusion)
|
||||
|
||||
These are the difference between "feels like a real chat" and "feels like a mockup":
|
||||
|
||||
- **The real send/receive sounds, never generic notification sounds.** The iMessage feel is mostly the audio. BigSoundBank hosts recordings of Apple's message sounds under CC0: send whoosh (`bigsoundbank.com/UPLOAD/mp3/1313.mp3`, ~0.5s) and receive tritone (`bigsoundbank.com/UPLOAD/mp3/1111.mp3` — trim to ~1.4s with a 400ms fade). Normalize loud (≈ -9 LUFS) so they cut through the music. Note the recordings being CC0 doesn't mean Apple has licensed its sound marks or UI trade dress — this is standard practice in the format, but regulated brands and risk-averse legal teams should review the iMessage mimicry as a whole; a generic chat-app skin (neutral bubbles, non-Apple sounds) is the fallback that keeps the mechanic.
|
||||
- **No sound on the typing indicator.** iOS is silent when someone starts typing. Play the receive sound only when the actual bubble replaces the dots. This is the single most common tell.
|
||||
- **Music bed: quiet lofi/hip-hop instrumental.** ~30% volume, highpass around 60Hz to clear room for the SFX, fade out ~1.5s before the code reveal so the CTA lands in relative silence.
|
||||
- **Static end card — no zoom, no Ken Burns drift.** The brand slate must land hard; a drifting end card reads as filler.
|
||||
- **Real brand logo SVG on the end card, never CSS-styled text.** Font-approximated wordmarks look amateur even when close. Pull the official SVG from the brand's press kit, Wikimedia, or brandfetch.com.
|
||||
- **Hook screenshots: mimic the real app's UI, don't AI-generate it.** AI-generated app UIs ship garbled chrome that reads as slop. Build a small HTML page copying the actual app's brand colors, typography, and layout conventions (the Strava-orange strip, the "Public · 2h ago" timestamp) and screenshot it. Reserve AI image generation for *photographic* hooks — a beach photo, a lifestyle shot, the framed variant's background.
|
||||
- **Audio mixing gotcha:** ffmpeg's `amix` divides volume by input count by default — pass `normalize=0` or the whole mix comes out mysteriously quiet. Then run the mix through a limiter with the ceiling just under full scale (e.g. `alimiter=limit=0.95`, ≈ -0.4 dB) so it's loud without clipping.
|
||||
|
||||
---
|
||||
|
||||
## Quality Checklist
|
||||
|
||||
Before shipping:
|
||||
|
||||
- [ ] Every factual claim in the thread traces to a real review, result, or product fact (Grounded Inputs)
|
||||
- [ ] Script reads as real texting voice when read aloud — no marketing adjectives in bubbles
|
||||
- [ ] Brand name appears only after the peer asks
|
||||
- [ ] No sound on any typing indicator; receive SFX fires when the text bubble lands
|
||||
- [ ] SFX land exactly on bubble pops (spot-check first and last)
|
||||
- [ ] Every sent bubble had a full composer drive; typed text equals sent text
|
||||
- [ ] No micro-flicker anywhere in the chat — the only cut is chat → end card (300ms crossfade)
|
||||
- [ ] Promo code is link-underlined in its bubble and repeated on the end card
|
||||
- [ ] End card is static with the real logo SVG
|
||||
- [ ] Master is native 1080×1920; 1:1 variant is a crop, not a squeeze
|
||||
- [ ] Final bubble gets ~600–800ms of air before the crossfade
|
||||
- [ ] Audio is limited just under full scale (no clipping); music never fights the SFX
|
||||
|
||||
---
|
||||
|
||||
## Iterating the Format
|
||||
|
||||
Treat the thread as the variable and the pipeline as fixed. Test in this order — hook first, everything else after:
|
||||
|
||||
1. **Hook attachment** — the screenshot is the thumbnail and the first 2 seconds; it decides the scroll-stop
|
||||
2. **Angle** — result-flex vs. cancellation vs. inverse changes who the viewer identifies with
|
||||
3. **Code reveal phrasing** — "first pack's free with FREEPACK" vs. "FREEPACK gets you one free"
|
||||
4. **Peer persona** — name, avatar, and texting style shift the perceived audience
|
||||
5. **Length** — try a 12-bubble and an 8-bubble cut of the same script
|
||||
|
||||
The same architecture extends to further surfaces too — WhatsApp, Slack, a search box — same timeline-driven recording, different UI shell.
|
||||
|
||||
---
|
||||
|
||||
## Other iOS-Native Reveal Surfaces
|
||||
|
||||
Everything above about production (UI mockup → timeline-driven continuous recording → deterministic SFX cues → static end card), grounding, and disclosure carries over unchanged. What changes per surface is the *persuasion mechanic* and a handful of craft details.
|
||||
|
||||
| Surface | Persuasion mechanic | Reach for it when |
|
||||
|---|---|---|
|
||||
| **iMessage** | A friend's recommendation — social proof through dialogue | The product is discovered through results people share ("what app is that?") |
|
||||
| **ChatGPT** | An authoritative answer to the viewer's own question | The problem is question-shaped — something people would literally type into ChatGPT |
|
||||
| **Apple Notes** | A private confession made public — first-person, no dialogue | The angle is transformation or realization ("things nobody told me about 45") |
|
||||
|
||||
The strongest signal for choosing: which of these three surfaces already fills your audience's day. Recommendation products want iMessage; advice-seeking problems want ChatGPT; identity/transformation stories want Notes.
|
||||
|
||||
### ChatGPT Reveal
|
||||
|
||||
The viewer identifies with the *asker*. The typed question is the hook and must be the target customer's verbatim question — awkward phrasing and all ("why is my stomach so bloated all of a sudden at 47?"). The streaming answer names the problem's real mechanism, then the solution category; the brand lands in the answer's recommendation or in a typed follow-up ("what's the best one?").
|
||||
|
||||
**Craft details:**
|
||||
- **Stream the answer in word chunks**, not character-by-character (that's typing, not generation) and not whole paragraphs at once. A subtle tick underneath the stream and a clean stop when the response completes; no iMessage tritones anywhere.
|
||||
- **Type the question like thumbs, stream the answer like a model.** Two distinct rhythms — the contrast is what reads as "real ChatGPT."
|
||||
- **Keep the answer scannable:** short paragraphs, a bolded phrase or a short list, exactly the way ChatGPT actually formats. A wall of text breaks the illusion and loses the viewer.
|
||||
- OpenAI's interface is their trade dress — same legal-review posture as the Apple UI mimicry note above, with a generic "AI assistant" skin as the fallback.
|
||||
|
||||
**Compliance — stricter here than anywhere else in this family.** The "answer" is your ad copy wearing a lab coat: an authority costume. Every claim in it needs the same substantiation as a claim in your own voice, and the format's borrowed authority raises the bar, not lowers it. Do not put health, medical, or financial advice in a fabricated AI answer without legal review — that's the highest-risk version of this format. And never present the exchange as a real, unprompted ChatGPT output endorsing your product; it's a dramatization, same as the iMessage thread.
|
||||
|
||||
### Apple Notes Reveal
|
||||
|
||||
A different genre from the chat formats: **confession, not conversation.** The viewer watches someone type a private note — a list of realizations, a "things I wish I knew" entry — with the keyboard visible. The note's title is the hook and does the job slide 1 does in a carousel ("Things nobody told me about 45."). The product appears as one item in the list, named the way a person would actually write it to themselves — not the way a brand would.
|
||||
|
||||
**Craft details:**
|
||||
- **Audio is keyboard taps only.** No chat SFX, no receive tones — a note has no other party. A quiet music bed still works underneath.
|
||||
- **Type at real thumb pace with jitter**, same as the iMessage composer rule. One typo-and-correction reads as human; several read as staged.
|
||||
- **Get the Notes chrome right:** title styled larger than body, the formatting bar above the keyboard, iOS-yellow accents. Same HTML-mimicry approach — and the same Apple trade-dress review note and generic-notes-app fallback — as everything else here.
|
||||
- **Fit the note to the frame.** Write short enough that the whole note fits without scrolling, or scroll once, deliberately, late.
|
||||
- **First person or it doesn't work.** The moment the note reads like ad copy ("[Brand] changed everything!"), the intimacy that makes the format convert is gone. The product mention should be the *least* enthusiastic line in the note.
|
||||
|
||||
The grounding rule hits differently here: the confession is a dramatization of a *composite, true* customer story — pull the realizations from real reviews and interviews (the Grounded Inputs corpus), and keep any numbers or outcomes to documented ones.
|
||||
@@ -0,0 +1,126 @@
|
||||
# Motion-Style Video Ads (Faceless, Fully Generated)
|
||||
|
||||
> Format popularized by Borja ([@borjafat](https://x.com/borjafat)) and the open `super-video-maker` motion-collage recipe by [Bomx](https://github.com/Bomx/super-video-maker-skill); this guide is an original re-expression of the method, extended with a multi-style library and production lessons from building and shipping it end-to-end.
|
||||
|
||||
Produce a 15–45s faceless video ad or explainer from nothing but a concept: a styled
|
||||
poster still (image model) → brought to life with subtle motion (image-to-video model)
|
||||
→ narrated (TTS) → word-timed captions. No footage, no presenter, no editor. Cost per
|
||||
finished video is roughly $3–6 in API calls; wall-clock ~15 minutes.
|
||||
|
||||
The format works because the *still* carries the idea (one literal, slightly surreal
|
||||
visual per beat) and the *motion* only makes it breathe. Resist the urge to make the
|
||||
video do the storytelling — this is animated poster design, not filmmaking.
|
||||
|
||||
## When to use
|
||||
|
||||
- Concept/explainer ads: one idea made concrete ("your CRM is a junk drawer")
|
||||
- Top-of-funnel social video (9:16 Reels/Shorts/TikTok, 4:5 and 1:1 feed)
|
||||
- Brand-response hybrids where a distinctive owned style beats stock UGC
|
||||
- NOT for: demo/proof ads (screen recordings win), testimonial/UGC formats,
|
||||
anything requiring a real product shot as evidence
|
||||
|
||||
## Pipeline (provider-agnostic)
|
||||
|
||||
1. **Script** 3–6 beats, 20–45s of VO. One idea per beat. Calm and specific beats
|
||||
hype. End on a single CTA line.
|
||||
2. **Poster stills** — one per beat, using a *style formula* (below). Generate beat 1,
|
||||
approve it, then pass it as a reference image for every later beat so the set reads
|
||||
as one series. Fix garbled label text by regenerating with a shorter phrase.
|
||||
3. **Animate** each approved still with an image-to-video model (5–8s per beat).
|
||||
Motion belongs to the objects in the frame; the composition must not change.
|
||||
4. **VO + captions**: one continuous TTS take, transcribe with word timestamps
|
||||
(whisper), cut beats at sentence boundaries, burn 2–3-word caption groups.
|
||||
5. **Assemble**: concat beats trimmed to their VO spans (hold the last frame to pad),
|
||||
loudness-normalize to `I=-16:TP=-1.5:LRA=11`, export per-placement aspect.
|
||||
|
||||
**Provider options** (any combination works; the recipe is model-agnostic):
|
||||
|
||||
| Stage | One-key Gemini path | Alternatives |
|
||||
|---|---|---|
|
||||
| Stills | Nano Banana Pro (`gemini-3-pro-image-preview`) — excellent label typography | GPT-Image, Flux, Ideogram |
|
||||
| Motion | Veo 3.1 fast image-to-video (note: 1080p requires 8s clips) | Seedance 2.0 via fal.ai, Kling, Runway |
|
||||
| VO | Gemini TTS (calm voices: Charon/Kore) | ElevenLabs, OpenAI TTS |
|
||||
| Captions | whisper word timings + PIL/ASS burn-in | CapCut, platform auto-captions |
|
||||
|
||||
## The style library
|
||||
|
||||
Five proven looks. Each is a fill-in-the-slots prompt formula; keep ONE style per
|
||||
campaign so the account builds a recognizable visual identity. All five animate well.
|
||||
|
||||
### A. Screen-print collage (editorial, "In a Nutshell" docu energy)
|
||||
> Flat screen-print collage poster, single saturated `<COLOR>` background, subtle newsprint grain. Centerpiece: a black-and-white halftone cutout of `<SUBJECT DOING THE LITERAL CONCEPT>`, treated as a paper sticker with a thin white die-cut outline, slightly torn edges, and a soft drop shadow. Visible halftone dot texture, vintage editorial photo feel, grayscale subject. Accent cutouts: 2–4 flat shapes (cream circle sun, black zigzag, scattered dots). A torn-paper label near the bottom with the words "`<LABEL>`" in bold condensed uppercase newspaper type. Matte printed risograph aesthetic, limited palette. No gradients, no glow, no 3D, no photorealism, no extra text.
|
||||
|
||||
### B. Flat vector explainer (clean, techy, infinitely brandable)
|
||||
> Flat vector explainer illustration in the style of a premium animated science channel: a friendly simplified `<SUBJECT>`, bold flat shapes with clean rounded edges, solid `<BRAND COLOR>` background, limited palette of `<2-3 ACCENTS>`, flat geometric accents, soft long shadows, completely flat 2D design. A clean rectangular banner near the bottom reads "`<LABEL>`" in bold geometric sans-serif uppercase. No outlines, no 3D, no photorealism, no texture, no extra text.
|
||||
|
||||
### C. Papercraft diorama (warm, tactile, premium-crafty)
|
||||
> Layered papercraft diorama: `<SUBJECT>`, every element hand-cut from colored construction paper with visible paper thickness and real drop shadows between layers, `<COLOR>` paper background with cut-paper accents, tactile handmade craft feel with slightly imperfect scissor cuts. A cut-paper banner near the bottom reads "`<LABEL>`" in chunky cut-out paper letters. Soft studio lighting on the paper layers. No digital gradients, no photorealistic humans, no extra text.
|
||||
|
||||
### D. Pop-art comic (loud, scroll-stopping, promo-friendly)
|
||||
> Vintage pop-art comic panel: `<SUBJECT>`, bold black ink outlines, Ben-Day halftone dots shading, flat process colors (`<PALETTE>`), comic starburst accents, thick panel border, aged newsprint paper texture. A comic caption box near the bottom reads "`<LABEL>`" in bold comic lettering. 1960s printed comic aesthetic, slight ink misregistration. No 3D, no photorealism, no gradients, no extra text.
|
||||
|
||||
### E. Claymation (charming, high pattern-interrupt)
|
||||
> Stop-motion claymation scene: a charming handmade plasticine `<SUBJECT>`, visible fingerprints and clay texture, `<COLOR>` clay backdrop and floor, chunky clay props, warm soft studio lighting like a stop-motion film set, shallow depth of field. A small clay sign near the bottom reads "`<LABEL>`" in hand-molded clay letters. Handcrafted miniature feel. No 2D illustration, no photorealistic humans, no extra text.
|
||||
|
||||
## Brand-flexible styles (token-driven)
|
||||
|
||||
The five looks above are *characterful* — they impose their own palette. This second
|
||||
tier is *brand-first*: each style is defined by *slots*, so any company's tokens drop
|
||||
in and the output reads as that brand's own design system.
|
||||
|
||||
**The brand slots contract.** Before generating, resolve these from the brand's
|
||||
guidelines (or `.agents/product-marketing.md`):
|
||||
|
||||
- `FIELD` — the neutral ground (brand white/off-white, or brand dark)
|
||||
- `INK` — the drawing/type color (brand gray/charcoal, near-black)
|
||||
- `ACCENT` — ONE brand color or gradient, used sparingly (a rule, a beam, a square)
|
||||
- `TYPE FEEL` — the brand's typographic voice ("clean modern grotesque sans", "geometric sans", "mono captions")
|
||||
- Any per-brand constraints (e.g. "gradients only on borders/edges, never fills")
|
||||
|
||||
Keep the accent genuinely scarce — one element per frame. Scarcity is what makes
|
||||
these read as designed rather than generated.
|
||||
|
||||
### F. Monoline editorial (the most universally brandable)
|
||||
> Minimal editorial monoline illustration poster: `<SUBJECT>`, drawn entirely in elegant thin single-weight `<INK>` lines on a clean `<FIELD>` background, the style of a premium tech company blog illustration. Sparse composition with generous whitespace, a few small monoline accent details, and ONE restrained `<ACCENT>` element: `<a thin accent underline sweep / a small accent arc>`. A small caption near the bottom reads "`<LABEL>`" in `<TYPE FEEL>`, `<INK>`, letterspaced uppercase, with a thin `<ACCENT>` underline. Precise, technical, refined. No fills except the single accent, no gradients, no 3D, no photorealism, no texture, no extra text.
|
||||
|
||||
### G. Swiss typographic (type IS the visual — any brand with a font and a color)
|
||||
> Swiss International Typographic Style poster: the words "`<LABEL>`" set enormous in a bold `<TYPE FEEL>`, `<INK>` on a `<FIELD>` background, filling the upper two thirds with tight leading and cropped edges. A small black-and-white photographic cutout of `<SUBJECT>` sits on a thin baseline grid in the lower third, aligned to an asymmetric grid with one thin `<ACCENT>` rule line and a small `<ACCENT>` square as the only color. Visible faint grid lines, precise margins, mathematical composition. Flat, printed, matte. No gradients, no 3D, no decoration, no extra text beyond the label and one small letterspaced caption line.
|
||||
|
||||
### H. Wireglow (dark keynote — dev-tool / dark-mode brands)
|
||||
> Dark minimal tech-keynote poster: `<SUBJECT>` rendered as an elegant thin light-gray wireframe line drawing on a near-black `<FIELD>` background with subtle film grain. From `<the focal object>` emanates a soft narrow beam of glowing `<ACCENT>` gradient light, the only color, feathered and atmospheric. Faint thin concentric geometric guide circles. A caption near the bottom reads "`<LABEL>`" in `<TYPE FEEL>`, light gray, letterspaced uppercase, with a hairline gradient rule beneath it. Restrained, premium, technical. No photorealism, no 3D render look, no busy elements, no extra text.
|
||||
|
||||
### I. Duotone screenprint (photo brands — editorial punch from two tokens)
|
||||
> Bold duotone screenprint photo poster: a dramatic photograph of `<SUBJECT>`, reproduced as a two-color screenprint — `<INK>` for the shadows and `<ACCENT>` for the highlights — on an off-white `<FIELD>` paper background with visible coarse halftone grain and slight ink misregistration. Strong diagonal composition, the figure large and cropped. A wide solid `<INK>` bar near the bottom carries the words "`<LABEL>`" reversed out in bold condensed `<TYPE FEEL>` uppercase, with a small `<ACCENT>` square bullet. Editorial poster energy, matte printed feel. No gradients beyond the duotone, no 3D, no extra text.
|
||||
|
||||
**Motion notes for this tier**: F/G animate as drawing motions (lines extend, the accent
|
||||
sweep draws itself, type settles by a few pixels); H animates as beam pulse + slow
|
||||
wireframe rotation feel; I as grain shimmer + slow push. Same hard rules apply — motion
|
||||
belongs to existing elements, composition never changes.
|
||||
|
||||
## Motion prompt formula
|
||||
|
||||
> Subtle living-`<style>` motion of the existing elements only. `<ONE literal motion tied to the concept: the pile inflates / the arrow creeps higher / the megaphone trembles with each shout>`. `<Secondary ambient motion: accents drift, gentle push-in>`. Every element that is visible now is the only thing that ever appears; the composition stays exactly as it is. Everything stays `<style descriptor: a flat printed collage / flat 2D vector / cut paper / printed comic / handmade clay>`. No camera whip, no scene change, no morphing, no added text.
|
||||
|
||||
## Hard-earned gotchas
|
||||
|
||||
- **Video models love adding photoreal "maker hands"** reaching into frame, especially
|
||||
on pressing/handling motions — and *negative prompts make it worse* ("no hands" is an
|
||||
attention trap). Never mention hands; describe motion as belonging to the objects,
|
||||
and include "the composition stays exactly as it is."
|
||||
- **Always QC each clip's final 2 seconds** — that's where intruding objects and style
|
||||
drift appear. Trim before them or regenerate; never ship a "realified" frame.
|
||||
- **One dominant motion per beat.** Two motions read as chaos at feed speed.
|
||||
- **TTS + whisper disagree on sound-alikes** ("laws" → "loss"). Read the transcript
|
||||
against the script before burning captions; prefer phoneme-unambiguous CTA wording.
|
||||
- **Keep captions clear of the label band** (captions ~60% height, label ~80%).
|
||||
Clamp caption groups so two never overlap; shrink-to-fit long groups.
|
||||
- **Ad-specific**: put the brand/label in the poster itself (it survives sound-off
|
||||
autoplay), front-load the concept in beat 1 (the 3-second hook is the poster), and
|
||||
export 9:16 + 4:5 + 1:1 from the same beats by regenerating stills per aspect
|
||||
rather than cropping.
|
||||
|
||||
## Compliance
|
||||
|
||||
Fully synthetic characters — no likeness/UGC disclosure issues, but check platform
|
||||
AI-content disclosure requirements (Meta and TikTok label AI-generated media).
|
||||
Don't fabricate statistics or testimonials in the VO; ground every claim.
|
||||
@@ -0,0 +1,200 @@
|
||||
# Static Ad Template Library
|
||||
|
||||
Fifteen structural templates for static (image) ad creative. Each is a layout framework with slots for brand-specific copy — the structure is proven; the inputs make it yours.
|
||||
|
||||
Use these when generating static ad concepts at volume (Meta, Instagram, LinkedIn, display). Cycle through **all** templates rather than clustering on 2-3 favorites: template diversity is angle diversity, and the winner is usually not the one you'd have picked by hand.
|
||||
|
||||
## How to Use This Library
|
||||
|
||||
1. **Ground first.** Read the inputs corpus (winning ads, reviews, ad comments, brand voice) before generating anything. See "Grounded Inputs" in SKILL.md.
|
||||
2. **Cycle templates.** For a batch of N concepts, spread across all 15 templates (3-4 variations each for a 50-concept batch).
|
||||
3. **Fill slots from source material.** Every variation pulls its copy from a real review, a winning ad pattern, or an ad comment — and cites which one.
|
||||
4. **Write the visual description.** Each concept includes enough visual direction that a designer or image-generation tool can produce it without guessing.
|
||||
|
||||
## Generation Rules
|
||||
|
||||
- Every variation must include: **template name, headline copy, body copy, visual description, source grounding**
|
||||
- Source grounding = which review, winning ad, or comment this concept is based on
|
||||
- Never produce a variation without source grounding — no invented claims, stats, or testimonials
|
||||
- Pull copy directly from customer language whenever possible; don't paraphrase reviews into marketing-speak
|
||||
- Match the brand voice doc on tone, not generic direct-response voice
|
||||
- Real names, real stats, real quotes only — fabricated social proof is a compliance and trust violation
|
||||
|
||||
---
|
||||
|
||||
## The 15 Templates
|
||||
|
||||
### 1. Headline Statement
|
||||
|
||||
Bold one-line claim. Single product hero shot. Minimal background. The headline does all the work.
|
||||
|
||||
- **Structure**: One dominant text line (60%+ of visual weight), product image, logo small
|
||||
- **Copy slot**: One claim specific enough to stop the scroll
|
||||
- **DTC example**: "The last greens powder you'll ever buy."
|
||||
- **SaaS example**: "Close your books in 3 days, not 3 weeks."
|
||||
- **Source it from**: Your strongest winning-ad hook or the most repeated benefit in reviews
|
||||
|
||||
### 2. Us vs. Them
|
||||
|
||||
Side-by-side comparison. Competitor or "old way" on the left (grayed out), your product on the right (full color). 4-6 comparison rows.
|
||||
|
||||
- **Structure**: Two columns, check/cross marks per row, your side visually alive
|
||||
- **Copy slot**: Comparison rows — each row a real differentiator, not filler
|
||||
- **DTC example**: "Their multivitamin: 13 ingredients. Ours: 60."
|
||||
- **SaaS example**: "Spreadsheets: 6 hours a week. Us: 6 minutes."
|
||||
- **Source it from**: Reviews that mention switching, or comments comparing you to a competitor
|
||||
|
||||
### 3. Stat Callout
|
||||
|
||||
One dominant number takes up 60% of the visual. Supporting context below.
|
||||
|
||||
- **Structure**: Giant stat, one line of context, product or logo anchor
|
||||
- **Copy slot**: A real, defensible number — measurement beats superlative
|
||||
- **DTC example**: "97% of users feel a difference in 14 days."
|
||||
- **SaaS example**: "11 hours saved per rep, per week."
|
||||
- **Source it from**: Case studies, product analytics, or survey data — never invent the number
|
||||
|
||||
### 4. Review Card
|
||||
|
||||
A five-star testimonial styled as a screenshotted product review. Reviewer name, star rating, date.
|
||||
|
||||
- **Structure**: Looks like a native review UI (G2, Trustpilot, Amazon, App Store — match where your buyers read reviews)
|
||||
- **Copy slot**: A real review, verbatim — the artifact's credibility is its realism
|
||||
- **DTC example**: A Trustpilot card: "I've tried 6 of these. This is the only one I reordered."
|
||||
- **SaaS example**: A G2-styled card: "Killed 4 tools and replaced them with this."
|
||||
- **Source it from**: `inputs/reviews/` verbatim — with permission where the platform requires it
|
||||
|
||||
### 5. Testimonial Stack
|
||||
|
||||
Three customer quotes arranged vertically, photo + name + one-line quote each.
|
||||
|
||||
- **Structure**: Three short rows; quotes must be scannable in 2 seconds each
|
||||
- **Copy slot**: Three quotes covering *different* objections or benefits — not the same praise three times
|
||||
- **DTC example**: Three customers on results, taste, and convenience
|
||||
- **SaaS example**: Three roles (IC, manager, exec) each praising their own outcome
|
||||
- **Source it from**: Reviews — pick for coverage, not just enthusiasm
|
||||
|
||||
### 6. Before / After
|
||||
|
||||
Split image with arrow between. Transformation framing — product results, workflow, or visual proof.
|
||||
|
||||
- **Structure**: Two panels, arrow or divider, minimal copy labeling each state
|
||||
- **Copy slot**: Label the states in the customer's words ("Sunday-night spreadsheet dread" → "Reports send themselves")
|
||||
- **DTC example**: Skin, energy, space — the classic visual transformation
|
||||
- **SaaS example**: Cluttered 6-tab workflow → one clean dashboard
|
||||
- **Compliance note**: Before/after claims are regulated in health, finance, and beauty — verify platform policy before using
|
||||
- **Source it from**: Transformation language in reviews ("I used to X, now I Y")
|
||||
|
||||
### 7. Problem / Solution
|
||||
|
||||
Pain point on top (text or image), product as the answer below.
|
||||
|
||||
- **Structure**: Two zones — tension above, relief below
|
||||
- **Copy slot**: The pain in the customer's exact words, then the product's one-line answer
|
||||
- **DTC example**: "Tired of 6 supplements every morning?" → one scoop visual
|
||||
- **SaaS example**: "Your CRM knows nothing about product usage." → integration screenshot
|
||||
- **Source it from**: The most common pain phrasing in `inputs/reviews/` — verbatim beats paraphrase
|
||||
|
||||
### 8. Founder Message
|
||||
|
||||
Handwritten-style or plain-text note from the founder. Conversational, personal tone.
|
||||
|
||||
- **Structure**: Note-style layout, founder name/photo, no product glamour shot
|
||||
- **Copy slot**: "I built this because..." — one honest paragraph, no marketing polish
|
||||
- **DTC example**: "Hey — I made this because every 'healthy' snack was secretly candy."
|
||||
- **SaaS example**: "I ran RevOps for 6 years. This is the tool I kept wishing existed."
|
||||
- **Source it from**: The actual founding story — this template collapses if fabricated
|
||||
|
||||
### 9. Feature Spotlight (Ingredient Spotlight)
|
||||
|
||||
Product hero in the center, 4-6 callout boxes around the edges highlighting key components.
|
||||
|
||||
- **Structure**: Center image, radiating callouts, each callout 3-6 words
|
||||
- **Copy slot**: The components buyers actually ask about — not your full feature list
|
||||
- **DTC example**: Product bottle with callouts per key ingredient and what it does
|
||||
- **SaaS example**: Dashboard screenshot with callouts on the 4 features reviews mention most
|
||||
- **Source it from**: Which features/ingredients appear most in reviews and comments
|
||||
|
||||
### 10. Press Mention
|
||||
|
||||
"As seen in" with publication logos and a pull quote.
|
||||
|
||||
- **Structure**: Logo row + one strong quote + product anchor
|
||||
- **Copy slot**: A real quote from real coverage
|
||||
- **DTC example**: "The category's first genuinely new idea in years." — [publication]
|
||||
- **SaaS example**: Analyst or industry-newsletter quote with the outlet's logo
|
||||
- **Compliance note**: Only use logos of outlets that actually covered you; check their logo-usage terms
|
||||
- **Source it from**: Actual press, podcasts, newsletters, or analyst mentions
|
||||
|
||||
### 11. Lifestyle Hero
|
||||
|
||||
Product in use in a real environment. Minimal copy. Aspirational, not salesy.
|
||||
|
||||
- **Structure**: One photograph does the work; a short line and logo at most
|
||||
- **Copy slot**: 5-8 words, identity-flavored ("Mornings, handled.")
|
||||
- **DTC example**: Product on a kitchen counter mid-routine
|
||||
- **SaaS example**: The tool on-screen in a real work moment (standup, close call, ship day)
|
||||
- **Source it from**: Winning ads' visual patterns; identity language in reviews
|
||||
|
||||
### 12. Numbered List
|
||||
|
||||
"5 reasons [audience] are switching to [brand]." Icons next to each point.
|
||||
|
||||
- **Structure**: Numbered rows, icon + short line each, product anchor at bottom
|
||||
- **Copy slot**: Each reason a distinct angle — pain, outcome, proof, differentiator, price
|
||||
- **DTC example**: "5 reasons runners switched to [brand] this year"
|
||||
- **SaaS example**: "4 reasons finance teams are leaving [legacy tool]"
|
||||
- **Source it from**: Aggregate the most common switching reasons across reviews
|
||||
|
||||
### 13. FAQ Card
|
||||
|
||||
A common objection as the question, answered directly.
|
||||
|
||||
- **Structure**: Question prominent, answer concise, product anchor
|
||||
- **Copy slot**: The objection *as customers phrase it* — the recognition is the hook
|
||||
- **DTC example**: "But does it work for sensitive skin? Yes — and here's why."
|
||||
- **SaaS example**: "Will this survive our security review? SOC 2 Type II, SSO, EU hosting."
|
||||
- **Source it from**: `inputs/comments/` — the objections people post publicly under your ads
|
||||
|
||||
### 14. Competitor Callout
|
||||
|
||||
Name a specific competitor (or the category default) and explain the difference. Bold but factual.
|
||||
|
||||
- **Structure**: Their name vs. yours, one clear axis of difference
|
||||
- **Copy slot**: A difference you can defend with facts — comparative claims invite scrutiny
|
||||
- **DTC example**: "Like [competitor], minus the 14g of sugar."
|
||||
- **SaaS example**: "[Competitor] charges per seat. We don't."
|
||||
- **Compliance note**: Comparative advertising must be truthful and substantiatable; some platforms restrict naming competitors
|
||||
- **Source it from**: Competitor mentions in reviews and comments — customers name the alternative for you
|
||||
|
||||
### 15. Origin Story
|
||||
|
||||
Founder photo with the why-we-built-this narrative. Longer copy than other formats.
|
||||
|
||||
- **Structure**: Portrait or team photo, 2-3 short paragraphs, product secondary
|
||||
- **Copy slot**: The specific moment or frustration that started it — specificity is the credibility
|
||||
- **DTC example**: "We spent 2 years and 47 batches getting this right. Here's why."
|
||||
- **SaaS example**: "We were the customer. The tool we needed didn't exist, so we built it."
|
||||
- **Source it from**: The real story — pairs with warm/retargeting audiences better than cold
|
||||
|
||||
---
|
||||
|
||||
## Per-Concept Output Format
|
||||
|
||||
Each generated concept follows this structure:
|
||||
|
||||
```markdown
|
||||
## Concept [N]: [Template Name]
|
||||
|
||||
**Headline**: [the headline copy]
|
||||
**Body**: [supporting copy, if the template uses it]
|
||||
**Visual**: [layout description specific enough to design or generate from]
|
||||
**Image prompt**: [prompt for the image tool, if generating — see generative-tools.md]
|
||||
**Grounded in**: [which review / winning ad / comment this traces to, quoted or named]
|
||||
```
|
||||
|
||||
For a batch, add an `INDEX.md` listing every concept with its template type and grounding source, so the reviewer can scan 50 concepts in two minutes.
|
||||
|
||||
## Batch Distribution
|
||||
|
||||
For a standard 50-concept batch: 3-4 variations per template across all 15. If performance data shows certain templates consistently winning for this brand, shift to 60% proven templates / 40% full-cycle coverage — but never drop coverage to zero. Fatigue is why you're generating daily; the template that's tired next month is the one you're scaling today.
|
||||
+179
-100
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: ads
|
||||
description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro."
|
||||
description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' 'should I run ads,' 'ABM,' 'account-based marketing,' 'B2B ads,' 'lead quality,' 'negative keywords,' 'Performance Max,' 'thought leader ads,' or 'when should I kill an ad.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro."
|
||||
metadata:
|
||||
version: 2.0.1
|
||||
version: 2.2.0
|
||||
---
|
||||
|
||||
# Paid Ads
|
||||
@@ -40,6 +40,22 @@ Gather this context (ask if not provided):
|
||||
|
||||
---
|
||||
|
||||
## Reference Routing
|
||||
|
||||
This skill's depth lives in references — load by intent. For **any operational decision on a live account** (kill/keep/scale/budget), load the relevant playbook before answering; the thresholds live there, not here.
|
||||
|
||||
| User intent | Load | Covers |
|
||||
|---|---|---|
|
||||
| B2B strategy, funnel stages, budget splits, kill rules, lead quality, breakeven math | [b2b-paid-playbook.md](references/b2b-paid-playbook.md) | Demand lifecycle, leading/lagging signals, kill rules, offline conversion loop, U/B/F lead scoring, scaling quadrant |
|
||||
| Meta operations: when to kill/graduate/scale an ad, fatigue, testing structure | [meta-decision-system.md](references/meta-decision-system.md) | TCPL-anchored decision tree, ad-count ceiling, 80/20 CBO structure, fatigue bands, lead forms, Advantage+ transition |
|
||||
| LinkedIn operations: bidding, audience sizing, scaling, benchmarks, TLAs, formats | [linkedin-b2b-playbook.md](references/linkedin-b2b-playbook.md) | Bidding progression, penetration scaling, sizing rules, funnel benchmarks, document/conversation ads, audit shortlist |
|
||||
| Google Search: what to spend on first, structure, match types, negatives, PMax | [google-search-playbook.md](references/google-search-playbook.md) | Intent ladder, account structure, match-type gates, negatives, bidding by volume, offline conversions, PMax guardrails |
|
||||
| Named-account targeting, pipeline acceleration, cross-channel retargeting | [abm-playbook.md](references/abm-playbook.md) | LinkedIn/Meta ABM, list mechanics, acceleration campaigns, UTM cross-channel remarketing, ABM measurement |
|
||||
| Generating Google RSAs | [rsa-output-spec.md](references/rsa-output-spec.md) | Mandatory output spec — limits, sidecars, template, self-check |
|
||||
| Audience setup, tracking setup, launch checklists, copy formulas | [audience-targeting.md](references/audience-targeting.md) · [conversion-tracking.md](references/conversion-tracking.md) · [platform-setup-checklists.md](references/platform-setup-checklists.md) · [ad-copy-templates.md](references/ad-copy-templates.md) | Existing foundations |
|
||||
|
||||
---
|
||||
|
||||
## Platform Selection Guide
|
||||
|
||||
| Platform | Best For | Use When |
|
||||
@@ -86,7 +102,7 @@ LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24
|
||||
|
||||
**Scaling phase:**
|
||||
- Consolidate budget into winning combinations
|
||||
- Increase budgets 20-30% at a time
|
||||
- Increase budgets ~20% at a time — never 30%+ in one move (resets platform learning)
|
||||
- Wait 3-5 days between increases for algorithm learning
|
||||
|
||||
---
|
||||
@@ -108,26 +124,98 @@ LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24
|
||||
|
||||
---
|
||||
|
||||
## Audience Targeting Overview
|
||||
## Audience Understanding & Targeting
|
||||
|
||||
### Platform Strengths
|
||||
Knowing your audience deeply is still the highest-leverage work in paid ads — demographics, job titles, pain points, fears, hopes, the exact language they use, who they follow, what they've tried, why they failed, what they buy. **Gather every identifier you can.**
|
||||
|
||||
| Platform | Key Targeting | Best Signals |
|
||||
|----------|---------------|--------------|
|
||||
| Google | Keywords, search intent | What they're searching |
|
||||
| Meta | Interests, behaviors, lookalikes | Engagement patterns |
|
||||
| LinkedIn | Job titles, companies, industries | Professional identity |
|
||||
What's changed in 2026 is **where you apply that knowledge.** As ad-platform algorithms have gotten dramatically better at finding the right person, jamming all your audience identifiers into the platform's *targeting filters* underperforms feeding those same identifiers into the *creative* (headlines, copy, visuals, hooks, examples).
|
||||
|
||||
### Key Concepts
|
||||
The discipline now: **audience knowledge → creative first, targeting filters second.** How much that ratio tips toward "creative" varies meaningfully by platform.
|
||||
|
||||
- **Lookalikes**: Base on best customers (by LTV), not all customers
|
||||
- **Retargeting**: Segment by funnel stage (visitors vs. cart abandoners)
|
||||
- **Exclusions**: Exclude existing customers and recent converters — showing ads to people who already bought wastes spend
|
||||
### Platform-by-platform: where to apply audience knowledge
|
||||
|
||||
| Platform | Audience knowledge → creative | Audience knowledge → targeting filters | Notes |
|
||||
|----------|------------------------------|-------------------------------------|-------|
|
||||
| **Meta** (post-Andromeda) | **80%+** | 20% | Algorithm rewards broad + specific creative. See [[#Modern Meta playbook (Andromeda era — 2026+)]] below for the full reframe. Interest-stacking now actively hurts. |
|
||||
| **Google Search** | 40% | **60%** | Keywords are still the dominant signal — match-types, search-intent layering, and negative keywords still drive performance. Creative (RSA headlines) matters but is downstream of the keyword. |
|
||||
| **Google Performance Max / Demand Gen** | **70%** | 30% | Audience signals are advisory, not deterministic. Creative + product feed quality dominate. |
|
||||
| **LinkedIn** | 40% | **60%** | Job-title / company / industry filters still produce real precision because LinkedIn's identity data is high-quality. Creative makes the click; firmographics make the *right person* see it. |
|
||||
| **TikTok** | **70%** | 30% | Algorithm is closer to Meta's model — broad targeting + native-feeling creative wins. Some audience interests help but creative dominates. |
|
||||
| **Twitter/X** | 50% | 50% | Interest + follower targeting still meaningful, but creative differentiation is high-leverage given lower competition. |
|
||||
|
||||
These ratios are directional, not precise. Test in your actual account.
|
||||
|
||||
### Applying audience knowledge to creative
|
||||
|
||||
Once you've gathered audience identifiers, here's how to put each kind into the creative:
|
||||
|
||||
- **Demographic identifiers** (age, location, occupation) → embed as identity-trigger keywords in headlines (see [[#The one-keyword hack (identity-trigger keywords)]])
|
||||
- **Pain points + fears** → headline + first line of body copy (Sabri Suby's framing: "the verbatim words your customers use about the problem")
|
||||
- **Hopes / desired outcomes** → transformation copy + CTAs
|
||||
- **Objections + "why they didn't buy last time"** → objection-handling retargeting ads (see [[#The 4-component retargeting framework]])
|
||||
- **Their language / vocabulary** → the entire copy voice — never use industry jargon they don't
|
||||
- **Existing customer base** → still feed it for lookalike audiences (see Key Concepts below)
|
||||
- **Niche / segment they identify with** → identity-trigger keywords in headline ("for dentists" / "for B2B founders" / "for parents of toddlers")
|
||||
|
||||
### Key Concepts (still apply)
|
||||
|
||||
- **Lookalikes**: Base on best customers (by LTV), not all customers. Still high-value across platforms.
|
||||
- **Retargeting**: Segment by funnel stage (visitors vs. cart abandoners). See [[#Retarget with DIFFERENT offers (not the same one)]] and [[#The 4-component retargeting framework]] for the modern playbook.
|
||||
- **Exclusions**: Exclude existing customers and recent converters — showing ads to people who already bought wastes spend.
|
||||
|
||||
### Common failure mode
|
||||
|
||||
Trying to make up for weak creative with hyper-precise targeting. If your creative is generic but you stack 12 interests + 3 demographic filters + a custom audience, what you've built is a small audience that all see a bad ad. Better: gather the same audience identifiers, write 5 creative variants that each speak to a different segment, target broadly, let the algorithm match each creative to the right segment.
|
||||
|
||||
**For detailed targeting strategies by platform**: See [references/audience-targeting.md](references/audience-targeting.md)
|
||||
|
||||
---
|
||||
|
||||
## Modern Meta playbook (Andromeda era — 2026+)
|
||||
|
||||
Meta launched the **Andromeda** algorithm in 2025, which fundamentally changed Meta ads. The old playbook (interest stacking, polished video creative, single-winner scaling) underperforms. The new playbook:
|
||||
|
||||
### Creative volume is the constraint (statics > polished video)
|
||||
- Andromeda is "a hungry panda" — it needs constant fresh creative or it fatigues
|
||||
- **Statics often outperform video in 2026** because:
|
||||
- Meta's algorithm has a bias toward statics — it can show more statics per session per user, so they're cheaper to deliver
|
||||
- Static creative is 10x cheaper and faster to produce than video, enabling the volume Andromeda needs
|
||||
- Even top advertisers running 17+ VSLs report that down-and-dirty native statics often beat 2.5-month-production VSLs
|
||||
- **Dedicate 1 hour per week** to producing fresh creatives for your winning offer. Volume > polish.
|
||||
|
||||
### Creative IS the targeting (broad audience + specific creative)
|
||||
- The old playbook: stack interests, narrow the audience, hope to find the right buyer
|
||||
- The new playbook: target broadly (just the country) and let the creative do the targeting
|
||||
- **Long-form ad copy works better than short-form** in 2026 — gives Meta a wider context window to understand who to show the ad to
|
||||
- Test it: take your best winning ad with interest-stacked targeting, duplicate it, remove all targeting (just pick the country), run side-by-side for 7 days. Check CPAs. Broad typically wins.
|
||||
|
||||
### The one-keyword hack (identity-trigger keywords)
|
||||
- Take your winning ad
|
||||
- Duplicate it with a niche/identity keyword inserted in the headline or body copy
|
||||
- *"Here's how to get 462 leads per week on autopilot"* → *"Here's how to get 462 **dental** leads per week on autopilot"* / *"...**lawyer** leads..."* / *"...**property investment** leads..."*
|
||||
- The keyword is an **identity trigger** for the viewer AND a targeting signal for Andromeda
|
||||
- Dramatically drops CPL and opens audience pockets you couldn't reach with a generic ad
|
||||
|
||||
### AI variant farming (the 100-people test)
|
||||
- Take your winning ad
|
||||
- Feed to Claude/ChatGPT/Kong with the prompt:
|
||||
> *"I want you to read this ad and be the author. If I show the next ad I'm going to ask you to write to 100 people, not 1 in 100 would be able to tell you it's written by a different person. Now write this for [demographic/niche]."*
|
||||
- The output should read essentially the same with subtle relevance shifts for the target
|
||||
- Apply in sequence: body copy → headlines → creative
|
||||
- Drop all variants in a CBO, let Meta's AI allocate spend
|
||||
|
||||
### Zombie campaigns
|
||||
- After running a CBO, Meta will give 80% of variants no spend
|
||||
- Take the dead variants you have **high conviction** about
|
||||
- Launch them in a separate ad set ("zombie campaign")
|
||||
- Typically resurrects 20% as winners that Meta's first allocation passed over
|
||||
|
||||
### Don't make ads look like ads
|
||||
- Hundreds of millions of people have ad blockers — the polished-ad aesthetic kills performance
|
||||
- Study what content **natively performs** in your niche on TikTok/Instagram/YouTube → produce ads that match that aesthetic
|
||||
- **Burner account technique:** create a clean Instagram/TikTok account, follow all influencers and pages in your niche, like their content. Your feed becomes a curated view of what's natively winning. Produce ads that match.
|
||||
- If you have an organic video with millions of views, **run that exact video as a paid ad** — proven content + paid distribution = the highest-leverage move
|
||||
|
||||
## Creative Best Practices
|
||||
|
||||
### Image Ads
|
||||
@@ -160,6 +248,8 @@ LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24
|
||||
|
||||
## Campaign Optimization
|
||||
|
||||
For hard kill/keep/scale thresholds, use the platform playbooks (see Reference Routing): the kill rules and breakeven CPL/CPC math live in [b2b-paid-playbook.md](references/b2b-paid-playbook.md), and Meta's full decision tree lives in [meta-decision-system.md](references/meta-decision-system.md).
|
||||
|
||||
### Key Metrics by Objective
|
||||
|
||||
| Objective | Primary Metrics |
|
||||
@@ -219,8 +309,53 @@ LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24
|
||||
- Bounced visitors (<10 sec)
|
||||
- Irrelevant pages (careers, support)
|
||||
|
||||
### Retarget with DIFFERENT offers (not the same one)
|
||||
|
||||
The conventional retargeting playbook re-shows the same product/offer to people who didn't buy. The Sabri Suby principle: **the #1 reason someone didn't buy is the offer wasn't right for them.** Re-showing the same thing harder doesn't help.
|
||||
|
||||
Instead, retarget with **different** products, services, or offers from your catalog:
|
||||
- Visitor clicked on protein powder, didn't buy → retarget with creatine (totally different category)
|
||||
- Visitor downloaded a lead magnet, didn't book a call → retarget with a different lead magnet on a related topic
|
||||
- Visitor viewed pricing, didn't sign up → retarget with a free audit or assessment instead
|
||||
|
||||
The lift from this is often dramatic — a 2-3 ROAS audience on the original offer can hit 6+ ROAS on a different offer.
|
||||
|
||||
### The 4-component retargeting framework
|
||||
|
||||
Build out your retargeting layer with these 4 ad types running simultaneously:
|
||||
|
||||
1. **Objection-handling ad** — directly addresses the most common reasons people didn't buy. To find these, **outbound call every lead** who didn't convert and ask why. The verbatim objections become the headline of this ad.
|
||||
2. **Proof testimonial carousel** — multi-image/multi-slide carousel of testimonials and proof that supports the claims of your original ad
|
||||
3. **Other-offers CBO** — your other best-performing ads for other products/services in one CBO, retargeted to the same audience
|
||||
4. **Value-first audit/assessment ad** — wraps your call in a free piece of value. Whether they buy or not, they leave with something useful. Lowers the friction to engage.
|
||||
|
||||
These four together, retargeting the same audience that didn't convert from the top-of-funnel ad, dramatically lift the ROAS of the entire funnel.
|
||||
|
||||
---
|
||||
|
||||
## Landing Page Alignment (the headline-mirror trick)
|
||||
|
||||
Ad-to-landing-page congruence is the single most underrated lever in paid ads. Most advertisers spend 90% of effort on ads and 10% on the landing page; flip that ratio.
|
||||
|
||||
### Headline mirroring
|
||||
|
||||
Meta is the best split-testing tool that exists — your ad headlines are exposed to ~1000x the audience that actually clicks through to your landing page. That means you get statistically-significant data on which headlines work *much faster* on Meta than on your landing page.
|
||||
|
||||
The play:
|
||||
|
||||
1. Run **20-40 different headlines** as ad variations
|
||||
2. Identify the best-performing headline (by CTR + downstream conversion)
|
||||
3. **Mirror that winning headline on your landing page** — exact wording in the H1, sub-headline, and lead-in copy of the body
|
||||
4. Expect a **15-20% minimum lift** in landing-page conversion rate from this single change
|
||||
|
||||
This works because the viewer who clicked is expecting *that specific promise*. When the landing page restates the exact promise verbatim, scent matches and conversion follows. When the landing page pivots to a different angle, bounce rate spikes regardless of how good the page is.
|
||||
|
||||
### Three split tests minimum at all times
|
||||
|
||||
A standing discipline: **at any given moment, you should have at least 3 split tests running** somewhere in your funnel — ad creative, landing page, offer, or post-conversion flow. If you don't, you've capped your improvement curve.
|
||||
|
||||
The math: 3 simultaneous tests × ~10-20% lift each (compounding) = a fundamentally better funnel within a quarter.
|
||||
|
||||
## Reporting & Analysis
|
||||
|
||||
### Weekly Review
|
||||
@@ -237,6 +372,33 @@ LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24
|
||||
- Compare platform data to GA4
|
||||
- Look at blended CAC, not just platform CPA
|
||||
|
||||
### Scaling discipline (net cash > ROAS percentage)
|
||||
|
||||
The most common scaling failure: a business at a 40 ROAS spending $5k/month, refusing to scale because "if I spend more, my ROAS will drop." This is the wrong frame.
|
||||
|
||||
**Net cash flow > ROAS percentage at the business level:**
|
||||
- ROAS dropping from 10 → 5 sounds bad
|
||||
- But if spend goes from $10k → $100k, you net dramatically more total profit
|
||||
- The number to optimize is **blended ROAS at the business level**, not per-ad-set ROAS
|
||||
- Even better: optimize **net free cash flow**, not ROAS at all
|
||||
|
||||
**Find your break-even ROAS:**
|
||||
1. Calculate the absolute maximum you can pay to acquire a customer and still be profitable (factoring LTV)
|
||||
2. That's your break-even ROAS / CPA ceiling
|
||||
3. **Scale until you approach that ceiling**, not until your ad-account ROAS drops below an arbitrary preference
|
||||
|
||||
**The 3-hour founder review:**
|
||||
- Block out **3 hours per month** in the calendar to physically review the numbers yourself
|
||||
- Not what your data analyst says. Not what your media buyer says. You, going through the actual data
|
||||
- The confidence this generates is irreplaceable — and confidence is what lets you scale with conviction
|
||||
- "Data gives you confidence. Confidence gives you speed."
|
||||
|
||||
**Outbound-call your leads who didn't convert:**
|
||||
- Every lead that downloaded a lead magnet or hit your funnel but didn't buy gets a call
|
||||
- Ask why they didn't book, what was confusing, what the actual blocker was
|
||||
- These verbatim answers become objection-handling ads (see Retargeting section)
|
||||
- Massive insight-to-creative loop that most advertisers skip
|
||||
|
||||
---
|
||||
|
||||
## Platform Setup
|
||||
@@ -259,92 +421,7 @@ Before launching campaigns, ensure proper tracking and account setup.
|
||||
|
||||
## Google RSA Output Spec (mandatory when generating RSAs)
|
||||
|
||||
When the user requests Google Ads RSAs (Responsive Search Ads), output MUST comply with these platform limits and structural requirements. Do not output any RSA that violates them.
|
||||
|
||||
### Hard limits per RSA (enforce before responding)
|
||||
|
||||
- **Headlines:** exactly **15** per RSA, each **≤ 30 characters** (count characters, including spaces). Render as `1. ... (NN chars)` so the reader can verify.
|
||||
- **Descriptions:** exactly **4** per RSA, each **≤ 90 characters**.
|
||||
- **Paths:** up to 2 path fields, each **≤ 15 characters**.
|
||||
- **Final URL:** present, https.
|
||||
- **Pinning:** state any pinned positions explicitly. Default = unpinned unless user asks.
|
||||
- **Per-account guardrail:** Google enforces **3 RSAs max per ad group**. When the user asks for >3, group them by ad group.
|
||||
|
||||
### Required sidecar artifacts (always include with RSA request)
|
||||
|
||||
1. **Ad group structure**, labeled `Ad group structure:` — list each ad group with its theme, target keywords (match types), and which RSAs map to it.
|
||||
2. **Negative keyword list**, labeled `Negative keywords:` — minimum **8** entries, group-level vs campaign-level called out.
|
||||
3. **Sitelinks** (≥ 4), **Callouts** (≥ 4 ≤25 chars), **Structured snippets** if relevant.
|
||||
|
||||
### Medical / CFM compliance (when product context indicates pt-BR medical practice)
|
||||
|
||||
If `.agents/product-marketing.md` indicates a Brazilian medical practice (CFM-regulated), the following terms are **forbidden** in headlines, descriptions, sitelinks, and callouts:
|
||||
|
||||
- Superlatives: `#1`, `melhor`, `o melhor`, `melhor do brasil`, `top`, `referência`
|
||||
- Outcome promises: `garantido`, `garantia`, `cura`, `cura definitiva`, `100%`, `resultado garantido`, `livre da dor`
|
||||
- Comparative claims vs other doctors/clinics
|
||||
|
||||
Use neutral framing: `atendimento`, `consulta`, `avaliação`, `segunda opinião`, `agende sua consulta`, `tire suas dúvidas`. Geo modifier (`Porto Alegre`, `POA`, `Zona Sul POA`) required where the prompt specifies a region.
|
||||
|
||||
### Output ORDER (mandatory — emit in this order to avoid truncation)
|
||||
|
||||
1. **Ad group structure** (short)
|
||||
2. **Negative keywords** (≥8, MANDATORY — emit BEFORE RSAs so it isn't dropped if output runs long)
|
||||
3. **Sitelinks** (≥4)
|
||||
4. **Callouts** (≥4)
|
||||
5. **RSA1, RSA2, RSA3** (largest section, last — safe to truncate gracefully)
|
||||
|
||||
### Output template (mandatory shape)
|
||||
|
||||
```
|
||||
Ad group structure:
|
||||
- AG1 [theme]: keywords (match types) → RSA1, RSA2
|
||||
- AG2 [theme]: ...
|
||||
|
||||
Negative keywords:
|
||||
Campaign-level:
|
||||
- <kw>
|
||||
- <kw>
|
||||
(≥4 here)
|
||||
Ad-group level:
|
||||
- AG1: <kw>, <kw>
|
||||
- AG2: <kw>, <kw>
|
||||
(≥4 more here — TOTAL ≥8 entries)
|
||||
|
||||
Sitelinks (≥4):
|
||||
- <title (≤25)> | <desc1 (≤35)> | <desc2 (≤35)> | URL
|
||||
|
||||
Callouts (≥4, each ≤25 chars):
|
||||
- <callout>
|
||||
|
||||
RSA1 — [ad group name]
|
||||
Final URL: https://...
|
||||
Path1: ... Path2: ...
|
||||
Headlines (15, each ≤30 chars):
|
||||
1. <headline> (NN chars)
|
||||
...
|
||||
15. <headline> (NN chars)
|
||||
Descriptions (4, each ≤90 chars):
|
||||
1. <description> (NN chars)
|
||||
...
|
||||
4. <description> (NN chars)
|
||||
Pinning: H1=none; H2=none; ... (or explicit pins)
|
||||
|
||||
RSA2 — ...
|
||||
RSA3 — ...
|
||||
```
|
||||
|
||||
### Self-check before responding
|
||||
|
||||
Before sending the output, run this checklist mentally:
|
||||
|
||||
- [ ] Each RSA has exactly 15 headlines, exactly 4 descriptions.
|
||||
- [ ] Every headline is ≤30 chars; every description is ≤90 chars. Character counts printed.
|
||||
- [ ] Negative keyword list labeled and ≥8 entries.
|
||||
- [ ] Ad group structure labeled.
|
||||
- [ ] If medical (CFM): no forbidden superlative/outcome words; geo modifier present where required; language is pt-BR.
|
||||
|
||||
If any check fails, rewrite before responding. Do not ship partial RSAs.
|
||||
When the user requests Google Ads RSAs, load [references/rsa-output-spec.md](references/rsa-output-spec.md) and follow it exactly — hard character limits, required sidecar artifacts (ad groups, negatives, sitelinks, callouts), output order, template shape, CFM medical compliance, and the pre-send self-check. Do not output any RSA that violates it.
|
||||
|
||||
---
|
||||
|
||||
@@ -402,6 +479,8 @@ For tracking setup, see [references/conversion-tracking.md](references/conversio
|
||||
## Related Skills
|
||||
|
||||
- **ad-creative**: For generating and iterating ad headlines, descriptions, and creative at scale
|
||||
- **revops**: For the CRM side of ABM — lead scoring, routing, and the offline conversion loop
|
||||
- **customer-research**: For the voice-of-customer inputs that feed ad copy and creative angles
|
||||
- **copywriting**: For landing page copy that converts ad traffic
|
||||
- **analytics**: For proper conversion tracking setup
|
||||
- **ab-testing**: For landing page testing to improve ROAS
|
||||
|
||||
@@ -0,0 +1,93 @@
|
||||
# ABM Playbook (Paid)
|
||||
|
||||
Account-based marketing with ads: targeting named accounts on LinkedIn and Meta, accelerating open pipeline, and stitching channels together. ABM ads are a *pipeline influence* motion, not a lead-gen motion — measure accordingly.
|
||||
|
||||
## Contents
|
||||
|
||||
- When ABM (go/no-go)
|
||||
- LinkedIn ABM
|
||||
- ABM on Meta
|
||||
- Acceleration campaigns (ads against open pipeline)
|
||||
- Cross-channel orchestration
|
||||
- Cross-channel UTM remarketing
|
||||
- Sales orchestration
|
||||
- Measuring ABM
|
||||
|
||||
## When ABM (go/no-go)
|
||||
|
||||
Run paid ABM when: target account list ≥ ~1,000 companies (or you accept 1:1/1:few economics), deal size ~$25K+, sales cycle 60+ days, sales and marketing actually aligned on the list, and (for Meta) contact enrichment available.
|
||||
|
||||
Skip it when: TAL under ~500 with no enrichment, no first-party data, budget under ~$3K/month, or a short transactional cycle — standard ICP targeting will outperform.
|
||||
|
||||
## LinkedIn ABM
|
||||
|
||||
Three motions, by list size:
|
||||
|
||||
- **1:1** — add the company by name; fully personalized creative for one account.
|
||||
- **1:few** — up to ~10–20 accounts per campaign, shared pain/industry angle.
|
||||
- **1:many** — uploaded list (or native targeting), scaled creative.
|
||||
|
||||
**List mechanics:**
|
||||
- LinkedIn needs **300 matched members minimum** to serve; aim for 1,000+ rows (duplicating company names to pad the upload is fine — it dedupes on match). Contact lists match best at scale (LinkedIn suggests ~10K emails); **company lists beat contact lists** for most teams — easier to source, better match rates, less maintenance.
|
||||
- Cold ABM audiences need ~15K members to deliver reliably.
|
||||
- **Segment mixed lists.** Left as one audience, LinkedIn over-serves the largest enterprises in the list — accounts have sat at 15% list coverage because the algorithm parked on a few big companies. Split into homogeneous bands (e.g., enterprise / mid-market / SMB) with separate campaigns and budgets.
|
||||
- List-based targeting typically buys reach materially cheaper than native firmographic targeting, with stronger decision-maker engagement.
|
||||
- Use the per-company engagement report (Audiences → click into the list) to find under-served priority accounts, then break them into a dedicated campaign.
|
||||
|
||||
**Personalized 1:1 creative:** putting the target account's name/logo in the creative can lift CTR ~5–10× over generic ads. **Legal exception: do not run company-name/logo-personalized ads into Germany** — privacy law, not platform policy.
|
||||
|
||||
**Frequency capping:** target ~3 impressions/person/week in priority accounts. Mechanic: build a company-engagement audience of accounts that crossed ~500 impressions in the last 7 days and add it as an *exclusion* — it self-rotates accounts out as they cool down. Tune the threshold (300 if fatigue shows, 750 for more pressure).
|
||||
|
||||
## ABM on Meta
|
||||
|
||||
Meta has no native company targeting — the play is **bring your own matched audience**:
|
||||
|
||||
- **The match-rate problem:** raw CRM exports of work emails match under ~5% on Meta. Enrichment providers (identity-graph tools that resolve work identities to personal profiles — e.g., Primer, Metadata, ZoomInfo, Clearbit) raise matches to ~40–85%. Workflow: firmographic criteria → identity-graph match → upload as Custom Audience → target directly or seed a 1% lookalike.
|
||||
- **Minimum sizes:** account-list audiences ~1,000 companies (5–10K optimal); retargeting slices work down to ~100 accounts; lookalike seeds want 500+.
|
||||
- Advantage+ **conflicts with strict ABM** — it won't stay locked to your list. Run ABM campaigns manual (or hybrid: manual for the list, Advantage+ for the broad layer).
|
||||
- Meta's ABM role is cheap **air cover and multi-threading** (reaching the buying committee beyond your champion) while LinkedIn does precision — see the split below.
|
||||
|
||||
## Acceleration campaigns (ads against open pipeline)
|
||||
|
||||
Ads aimed at accounts already in your pipeline, to speed deals rather than source them:
|
||||
|
||||
- Segment the CRM by stage (evaluation / proposal / negotiation), filter to deals worth the spend, upload as an audience, refresh weekly.
|
||||
- **Use an awareness/reach objective, not conversions** — you're keeping the vendor top-of-mind for the buying committee, not asking in-pipeline accounts to "book a demo" they already booked.
|
||||
- Creative: case studies, proof, objection-handlers — matched to stage. Budget scales with deal value (larger open deals justify $100–200/day of air cover; stalled deals get a maintenance dose).
|
||||
|
||||
## Cross-channel orchestration
|
||||
|
||||
Default split for B2B ABM: **~60% LinkedIn / ~30% Meta / ~10% other**. LinkedIn buys precision (right person, right company) at $40–70 CPMs; Meta buys presence and committee reach at $10–25. Sequence LinkedIn first to validate the audience, then extend to Meta. Multi-channel ABM consistently and materially outperforms single-channel on engagement and conversion — the channels compound, they don't compete.
|
||||
|
||||
## Cross-channel UTM remarketing
|
||||
|
||||
The cheapest high-quality audience you can build: retarget one platform's validated clickers on another platform.
|
||||
|
||||
1. Tag all paid traffic with consistent UTMs (`utm_source=linkedin`, `utm_source=google&utm_medium=cpc`).
|
||||
2. On Meta, build a website Custom Audience with the rule **"URL contains `utm_source=linkedin`"** (or `utm_source=google`).
|
||||
3. Retarget that audience on Meta — LinkedIn-grade audience quality at Meta-grade CPMs (typically 50–70% cheaper reach).
|
||||
|
||||
Works in both directions (search clickers → LinkedIn remarketing needs meaningful search volume — worth it above roughly $30K/month search spend). Requires enough source-channel traffic to clear minimum audience sizes. Use a consistent account/campaign token in UTMs so attribution survives the hop.
|
||||
|
||||
## Sales orchestration
|
||||
|
||||
ABM ads without sales follow-up is billboard spend:
|
||||
|
||||
- Pipe ad-engagement signals to the CRM (LinkedIn company-engagement exports, or connectors that sync engagement per account) and treat an engagement spike as a sales trigger — **outreach within ~48 hours** of the spike.
|
||||
- Route new leads to a shared channel (Slack webhook) with a per-campaign quality reaction (👍/👎) — the cheapest lead-quality feedback loop that exists.
|
||||
- Hold a monthly sales-marketing session on the list itself: who's engaging, who's dark, who closed — and re-cut the list.
|
||||
- Expect ~7–10 cross-channel touches before a sales conversation is normal at ABM deal sizes.
|
||||
|
||||
## Measuring ABM
|
||||
|
||||
Judge ABM on account movement, not CPL:
|
||||
|
||||
- **Account penetration** (% of list reached): target ~40–60%.
|
||||
- **Cost per engaged account** (not per click): ~$100–300 is a workable band.
|
||||
- **Account → opportunity rate:** ~10–20%.
|
||||
- **Pipeline influenced:** aim for 3–5× spend; expect win-rate and velocity improvements on engaged vs. non-engaged accounts.
|
||||
- **Incrementality:** hold out ~20% of the list from ads and compare pipeline formation after 21+ days — the only honest answer to "did the ads do anything?"
|
||||
|
||||
---
|
||||
|
||||
*Framework lineage: adapted (re-expressed and restructured) from practitioner playbooks, notably Ivan Falco's ads-skills. Thresholds are practitioner-reported starting points — recalibrate against your own accounts.*
|
||||
@@ -0,0 +1,115 @@
|
||||
# B2B Paid Playbook
|
||||
|
||||
Cross-platform operating rules for B2B paid acquisition — where sales cycles run 2–24 months, in-platform conversions mislead, and lead *quality* matters more than lead cost. Use this alongside the platform playbooks ([Meta decision system](meta-decision-system.md), [LinkedIn](linkedin-b2b-playbook.md), [Google Search](google-search-playbook.md), [ABM](abm-playbook.md)).
|
||||
|
||||
## Contents
|
||||
|
||||
- The Demand Lifecycle (5 stages, past the funnel)
|
||||
- Budget by stage
|
||||
- Leading vs. lagging signals
|
||||
- Unit economics: breakeven CPL and CPC
|
||||
- Kill rules
|
||||
- The optimize-to-quality trap (and the offline conversion loop)
|
||||
- Lead quality scoring (Urgency / Budget / Fit)
|
||||
- The scaling quadrant
|
||||
- Measurement maturity check
|
||||
- Channel selection
|
||||
|
||||
## The Demand Lifecycle (5 stages, past the funnel)
|
||||
|
||||
TOFU/MOFU/BOFU stops at conversion. B2B revenue doesn't — closed-lost deals, open pipeline, and existing customers are all addressable with ads. Plan across five stages:
|
||||
|
||||
| Stage | Outcome | Buyer awareness | Typical offers | KPIs |
|
||||
|-------|---------|-----------------|----------------|------|
|
||||
| **Create** | Build affinity & trust | Unaware / Problem-aware | Educational content, POV | Cost per consumption, blended cost/opp |
|
||||
| **Capture** | Convert in-market buyers | Solution / Product-aware | Demos, trials | Pipe-to-spend, direct cost/opp |
|
||||
| **Accelerate** (sales-led) / **Activate** (product-led) | Close open deals faster / convert free users | Product / Offer-aware | Case studies, webinars, events | Pipeline velocity, paid signups |
|
||||
| **Revive** | Restart closed-lost | Offer-aware | Incentivized demos, guided trials | SQOs created, cost/SQO |
|
||||
| **Expand** | Grow existing accounts | Most aware | Referral programs, new-feature content | Expansion revenue, influenced SQOs |
|
||||
|
||||
**Build bottom-up for fastest ROI**: Expand → Revive → Accelerate/Activate → Capture → Create. The bottom stages are cheap, small-audience, and quick to pay back; Create is the biggest and slowest investment. Most teams build top-down and burn months waiting for ROI.
|
||||
|
||||
## Budget by stage
|
||||
|
||||
| Stage | Budget size | Time to ROI | Difficulty |
|
||||
|-------|------------|-------------|------------|
|
||||
| Create | High | 90+ days | High (needs strong content + POV) |
|
||||
| Capture | Moderate | <45 days | High (expensive, competitive) |
|
||||
| Accelerate/Activate | Low | Tracks sales cycle | Low |
|
||||
| Revive | Low | <45 days | Low |
|
||||
| Expand | Low | <60 days | Medium (small audiences) |
|
||||
|
||||
Weight by motion: product-led skews budget to Create + Capture; sales-led with a small TAM skews to Create + Accelerate. The stage with the most *pipeline* isn't automatically the stage that deserves the most *budget* — fund where pipeline share exceeds budget share and the audience is under-penetrated.
|
||||
|
||||
## Leading vs. lagging signals
|
||||
|
||||
You can't optimize on closed-won when deals close in 6 months. Split every stage's metrics:
|
||||
|
||||
- **Leading** (moves in <1 month — optimize on these): CTR, engagement, CPL, cost per qualified lead, accounts reached
|
||||
- **Lagging** (moves in >1 month — the truth, reviewed monthly/quarterly): pipe-to-spend, influenced revenue, time-to-close, expansion revenue
|
||||
|
||||
The leading metric must demonstrably correlate with the lagging one — a proxy metric worth optimizing is measurable, moveable, not an average, and hard to game. If CPL falls while pipeline doesn't move, the proxy broke; fix the proxy, not the ads.
|
||||
|
||||
## Unit economics: breakeven CPL and CPC
|
||||
|
||||
Derive targets from deal math, not platform benchmarks:
|
||||
|
||||
- **Breakeven CPL** = average deal size × lead-to-close rate. ($3,000 ACV × 10% close = $300 CPL.)
|
||||
- **Breakeven CPC** = target CPL × landing page conversion rate. ($300 CPL × 5% LP conversion = $15 CPC.)
|
||||
|
||||
Set the actual target below breakeven by your required margin. Every kill rule and scaling decision keys off this number.
|
||||
|
||||
## Kill rules
|
||||
|
||||
Two hard rules that remove emotion from pausing decisions:
|
||||
|
||||
- **Non-performer rule** (new ads, any time): pause once an ad has spent **2–3× target CPL with zero conversions**. Target CPL $300 → kill at $600–900 spent, no conversions.
|
||||
- **Maintenance rule** (ads past ~7–14 days): pause when an ad's CPL runs **1.5–2× over target**. Target $300 → kill at $450–600 CPL.
|
||||
|
||||
These aren't statistically rigorous — they're repeatable, cheap to apply, and better than deciding by mood. Never pause a producer without a replacement staged (see the swap rules in the [Meta decision system](meta-decision-system.md)).
|
||||
|
||||
## The optimize-to-quality trap (and the offline conversion loop)
|
||||
|
||||
Smart bidding optimizes toward whatever you call a "conversion." Feed it raw form-fills and it will buy you cheap junk form-fills — CPL improves while pipeline dies. The fix, in order:
|
||||
|
||||
1. **Close the offline conversion loop.** Push CRM stage changes (MQL → SQL → opportunity → closed-won) back to the ad platforms — GCLID + offline import on Google, CAPI lifecycle events on Meta, conversion API on LinkedIn. This is the single highest-impact move in a B2B ad account: the algorithm starts buying pipeline instead of form-fills.
|
||||
2. **Value conversions differently.** A demo request is not an ebook download.
|
||||
3. **Until offline data flows, keep a human reading lead quality weekly** — job titles and companies, not just CPL.
|
||||
|
||||
Reconcile platform-reported conversions against the CRM monthly. When they disagree, **the CRM wins**.
|
||||
|
||||
## Lead quality scoring (Urgency / Budget / Fit)
|
||||
|
||||
The platform can't see lead quality — score it yourself and rank ads by it:
|
||||
|
||||
- **Urgency** (0–3): 0 browsing → 3 burning need with timeline
|
||||
- **Budget** (0–3): 0 none/no authority → 3 approved and ready
|
||||
- **Fit** (0–3): 0 not ICP → 3 perfect ICP
|
||||
|
||||
Whoever runs the sales calls scores each lead (max 9) and logs it against the originating ad. After ~20 scored calls, **rank ads by average quality score, not CPL or CTR** — the ad with the best CPL is regularly the one producing 3/9 leads. Scale the high-score ads; kill variations whose average drops below ~5.
|
||||
|
||||
## The scaling quadrant
|
||||
|
||||
Route scaling tactics by your actual constraint:
|
||||
|
||||
| | Low effort | High effort |
|
||||
|---|---|---|
|
||||
| **High budget** | **Audiences** — bigger audiences, more segments, more frequency | **Geography** — new countries/regions (localization work) |
|
||||
| **Low budget** | **Ads** — new creative, angles, formats | **Objectives & bids** — change objective or bid strategy to buy cheaper |
|
||||
|
||||
- Have budget but no time → work the top row (audiences, then geo).
|
||||
- Need scale but capped on budget → work the bottom row (better creative and cheaper bidding free up money).
|
||||
|
||||
## Measurement maturity check
|
||||
|
||||
Before scaling spend, score yourself 1–3 on each: blended pipeline dashboard; per-channel dashboard; conversion tracking (1 = none, 2 = pixel only, 3 = offline conversions flowing); web analytics; a documented, agreed attribution process. Under ~6/15, fix visibility before adding budget — you're flying blind and every optimization is a guess. Fix the lowest score first.
|
||||
|
||||
## Channel selection
|
||||
|
||||
Five channel families: paid social, paid search, **paid review listings** (G2, Capterra, Software Advice — often skipped, high intent), programmatic (display, audio, CTV, native), and sponsorships (newsletters, podcasts, events, creators). Evaluate on four axes: can you actually target your ICP; media cost (CPC/CPM); reach at your targeting; platform policy for your industry.
|
||||
|
||||
Before committing to a new channel, **run a ~$100 test campaign** to learn its real CPC/CPM for your targeting — platform estimates and published benchmarks are consistently wrong for specific ICPs.
|
||||
|
||||
---
|
||||
|
||||
*Framework lineage: several operating rules in this file are adapted (re-expressed, restructured, and extended) from practitioner playbooks, notably Ivan Falco's ads-skills. Benchmarks and thresholds are practitioner-reported starting points — always recalibrate against your own account's first 30 days.*
|
||||
@@ -0,0 +1,120 @@
|
||||
# Google Search Playbook (B2B)
|
||||
|
||||
Intent-first operating rules for Google Ads: where to spend first, how to structure the account, when to loosen match types, and how to keep smart bidding pointed at revenue instead of junk form-fills. For RSA generation mechanics, see [rsa-output-spec.md](rsa-output-spec.md).
|
||||
|
||||
## Contents
|
||||
|
||||
- The intent ladder
|
||||
- Brand bidding (and the pause test)
|
||||
- Capture before you create
|
||||
- Account structure
|
||||
- Keywords and match types
|
||||
- Negative keywords
|
||||
- The weekly search-terms ritual
|
||||
- Bidding by conversion volume
|
||||
- Offline conversions
|
||||
- Quality Score and landing pages
|
||||
- PMax for B2B
|
||||
- Benchmarks and the weekly scorecard
|
||||
|
||||
## The intent ladder
|
||||
|
||||
Spend opens rung by rung — each tier unlocks only after the one below proves it converts to *pipeline*:
|
||||
|
||||
1. **Brand** — "they want you" (brand name, brand + pricing/login). Cheapest clicks, highest conversion. Always on.
|
||||
2. **High-intent non-brand** — ready to buy ("cold email software," "best CRM for agencies"). The profit center; most budget lives here.
|
||||
3. **Competitor** — evaluating alternatives ("[competitor] alternative/vs"). Higher CPC, lower CVR; run selectively with dedicated comparison pages.
|
||||
4. **Problem-aware** — has the problem, isn't shopping ("how to scale outbound"). Longer payback; only after tiers 1–2 work.
|
||||
5. **Demand-gen/awareness** — broad, Display, YouTube. Last, with spare budget only.
|
||||
|
||||
**Don't skip rungs.** Broad spend before high-intent proof is how B2B accounts burn budgets with nothing in the CRM.
|
||||
|
||||
## Brand bidding (and the pause test)
|
||||
|
||||
Bid on brand by default — if you don't, competitors will, and you pay in lost deals rather than clicks. The exception: if you're the only bidder and organic owns the whole SERP, test pausing brand and watch **total brand conversions (paid + organic)**, not just paid. If total holds, you were cannibalizing yourself; if it drops, turn it back on. Cap brand budget — it rarely needs much, and shared budgets let brand eat everything (see below).
|
||||
|
||||
## Capture before you create
|
||||
|
||||
Search **harvests existing demand**; it cannot create demand. If your category has near-zero search volume, say so and put the budget upstream (LinkedIn/Meta/YouTube) instead of forcing keywords nobody types. Demand creation happens on social; Search is where you catch it landing.
|
||||
|
||||
## Account structure
|
||||
|
||||
Minimum viable split — each with an **independent budget**:
|
||||
|
||||
- **Brand** (own budget — never shared)
|
||||
- **Non-brand high-intent** (one campaign, themed ad groups by solution)
|
||||
- **Competitor** (own budget and messaging — its CPC/CVR economics are different)
|
||||
- **Remarketing** (separate from Search)
|
||||
|
||||
Why independent budgets: in a shared budget the cheapest, highest-converting campaign (always brand) starves the ones you actually need data from. The account looks profitable on paper and is blind everywhere that matters.
|
||||
|
||||
- **Themed ad groups, not SKAGs:** 5–15 closely related keywords sharing one intent, answerable by one promise. If two keywords need different landing pages or value props, split the group. 2–3 RSAs per ad group.
|
||||
- **Consolidation rule:** a campaign that can't reach ~15–30 conversions/month can't feed smart bidding — merge it. Fewer, better-fed campaigns beat elaborate structures in low-volume B2B.
|
||||
- **Default settings to flip on every new Search campaign:** turn OFF Search Partners and Display Network until proven; set location targeting to **"Presence"** (people physically in the target geo — the default "presence or interest" serves people merely interested in it); remember language targeting keys off the user's Google interface language, not the query language.
|
||||
- **Don't compete with yourself:** the same keyword at the same match type in multiple ad groups splits your data and bids against your own account. Use negatives to route each query to exactly one home.
|
||||
|
||||
## Keywords and match types
|
||||
|
||||
Source keywords from how **buyers describe the problem** (sales-call language, your own search-terms report, competitor ad copy) — not how you describe the product. A keyword with 50 searches/month and clear intent beats one with 5,000 and mixed intent. Tag every keyword by intent tier.
|
||||
|
||||
**Match-type progression — in this order:**
|
||||
|
||||
1. Start high-intent terms on **Phrase + Exact** (Exact still matches close variants; Phrase is the B2B workhorse), manual CPC or Max Conversions while volume is low.
|
||||
2. Mine the search-terms report weekly (ritual below).
|
||||
3. Introduce **Broad only after**: 30+ conversions/month in the campaign, AND smart bidding live, AND a tight negative list. Broad without all three is a donation to Google.
|
||||
|
||||
## Negative keywords
|
||||
|
||||
Starter lists to apply at build time:
|
||||
|
||||
- **Universal junk:** free, cheap, jobs, salary, hiring, career, intern, student, course, tutorial, training, certification, pdf, template, reddit, wiki, login (except in brand campaigns)
|
||||
- **Research intent:** "what is," "how to," "examples," "meaning," "definition"
|
||||
- **Category collisions:** terms your category shares with an unrelated one (selling sales-engagement? negative "employee engagement")
|
||||
- **Your brand as a negative in non-brand campaigns** — routes brand traffic to the brand campaign where it belongs
|
||||
|
||||
**Match-type mechanics gotcha:** negative broad requires ALL its words present (any order) — negative broad "free trial" does **not** block "free" alone. Negative phrase blocks in-order phrases; negative exact blocks only that exact query. Most accidental over-blocking and under-blocking traces to this.
|
||||
|
||||
**Don't over-negative:** every negative narrows reach, and it compounds fast at B2B volumes. Negative the clearly wrong, not the merely uncertain — an ambiguous term deserves more data before it's cut.
|
||||
|
||||
## The weekly search-terms ritual
|
||||
|
||||
Once a week per campaign, three passes:
|
||||
|
||||
1. **Waste:** terms with spend (3+ clicks) and zero conversions → negative the irrelevant ones.
|
||||
2. **Winners:** converting search terms that aren't keywords yet → add as Exact/Phrase in the right ad group.
|
||||
3. **Drift:** broad/phrase matches pulling adjacent-but-wrong meanings → tighten the match type or negative the drift.
|
||||
|
||||
## Bidding by conversion volume
|
||||
|
||||
| Conversions/month (campaign) | Strategy |
|
||||
|---|---|
|
||||
| 0–15 | Manual CPC or Maximize Conversions (no target) |
|
||||
| 15–30 | Maximize Conversions |
|
||||
| 30+ stable | Target CPA — set at or slightly above your trailing 30-day actual |
|
||||
| Real revenue values flowing back | Target ROAS |
|
||||
|
||||
Rules of thumb: smart bidding needs ~30 conversions in 30 days per campaign to learn. Set tCPA near actuals — an aggressively low target chokes delivery (Google just stops bidding). Move targets in **±10–15% steps and wait 1–2 weeks**; every change restarts learning, so don't panic-edit inside the learning window. Budget mechanics: campaigns can spend up to **2× daily budget** in a day (Google balances monthly — single-day overspend is normal); a budget-capped campaign that's converting often *lowers* its CPA when you raise the budget, because constrained smart bidding underperforms.
|
||||
|
||||
## Offline conversions
|
||||
|
||||
The single highest-impact move in a B2B Google account: **import CRM outcomes** (SQL, opportunity, closed-won) back into Google via GCLID + offline conversion import or a native CRM integration, with real deal values. Until then, smart bidding optimizes to form-fills and buys you junk (see the optimize-to-quality trap in [b2b-paid-playbook.md](b2b-paid-playbook.md)). B2B clicks close in 60–180 days — in-platform conversion counts will never tell the truth on their own. Reconcile against the CRM monthly; the CRM wins.
|
||||
|
||||
## Quality Score and landing pages
|
||||
|
||||
QS (1–10, per keyword) = expected CTR + ad relevance + landing page experience. Low QS means paying more for the same position — **fix the weak component before raising the bid.** Landing page rules that move it: message match (page headline echoes the ad's promise and the query — not a generic homepage); one job and one CTA per page; speed; proof above the fold. **Form length is an intent gate:** short forms buy volume at lower quality, longer qualified forms buy fewer/better — match it to what you're feeding back as the conversion event.
|
||||
|
||||
## PMax for B2B
|
||||
|
||||
Value ranking: **brand Search > high-intent non-brand Search > remarketing > PMax > broad demand-gen.** PMax earns budget only after the cheaper, clearer wins are maxed. Never run it as the first campaign, on weak tracking, or on tiny budgets.
|
||||
|
||||
Guardrails when you do run it: account-level **brand exclusions** (or it cannibalizes brand Search and claims the credit); audience signals from first-party data; negative keywords from day one; offline conversions imported *before* scaling it; check the CRM quality of PMax leads by campaign — if they convert to pipeline at half the rate of Search leads, PMax is cheap-looking and expensive-in-reality. Google auto-generates a bad video if you don't supply one.
|
||||
|
||||
## Benchmarks and the weekly scorecard
|
||||
|
||||
B2B SaaS Search ranges (wide on purpose — anchor to your own first 30 days): brand CTR 8–20%, CVR 15–40%; non-brand high-intent CTR 2–6%, CVR 3–10%, CPC $8–40+, CPL $80–400+; competitor terms run higher CPC and lower CVR than non-brand.
|
||||
|
||||
Weekly scorecard — exactly eight numbers: spend · leads · CPL · lead→SQL rate (from CRM) · SQLs · cost per SQL · Search impression share · top wasted search terms. Diagnostic: **Search Lost IS (budget)** vs **Lost IS (rank)** tells you whether you're capped by money or by Ad Rank — different problems, different fixes. If the eight are healthy and trending right, the account is healthy.
|
||||
|
||||
---
|
||||
|
||||
*Framework lineage: adapted (re-expressed and restructured) from practitioner playbooks, notably Ivan Falco's ads-skills. Benchmarks are practitioner-reported starting points — recalibrate against your own account.*
|
||||
@@ -0,0 +1,107 @@
|
||||
# LinkedIn B2B Playbook
|
||||
|
||||
Operational rules for LinkedIn Ads: bidding, audience sizing, scaling triggers, benchmarks, and format-specific tactics. LinkedIn is the precision channel — highest-quality B2B targeting at the highest cost, so the operating discipline is about not wasting that precision.
|
||||
|
||||
## Contents
|
||||
|
||||
- Bidding progression
|
||||
- Audience sizing rules
|
||||
- Job functions vs. job titles
|
||||
- Audience splitting rules
|
||||
- Penetration-based scaling
|
||||
- Benchmarks by funnel stage
|
||||
- Thought leader ads (TLAs)
|
||||
- Campaign group build order
|
||||
- Format notes (document, conversation, CTV)
|
||||
- Retargeting setup (non-retroactive!)
|
||||
- Account audit shortlist
|
||||
|
||||
## Bidding progression
|
||||
|
||||
1. **Week 1:** launch on automated bidding / maximum delivery. Don't touch it — you're buying CPC data.
|
||||
2. **Week 2+:** switch to manual CPC set **~20% below the average CPC** the automated phase produced. This reliably cuts CPC without killing delivery.
|
||||
3. **Exceptions:** small retargeting/ABM audiences stay on automated (manual underdelivers on small pools); reset to automated for a week whenever you change objective; audiences under ~10K may never spend their full budget at any bid.
|
||||
|
||||
Scheduling note: LinkedIn's ad day resets at UTC midnight. Professional activity peaks weekday mornings–early afternoon in the audience's timezone; dayparting there stretches limited budgets.
|
||||
|
||||
## Audience sizing rules
|
||||
|
||||
- **Cold prospecting:** 50K–300K members. Minimum ~15K per cold campaign.
|
||||
- **Too-narrow failure mode:** hyper-narrow audiences spike CPMs several-fold and stall delivery entirely — budget won't spend at any bid. If it's not spending, the audience is usually too small, not the bid too low.
|
||||
- **Tiny TAM (<~30K addressable):** skip the TOF/BOF split — run one campaign that saturates the whole audience with all funnel layers.
|
||||
- **Retargeting:** audiences of roughly 1K–5K per segment (site visitors, 50%+ video viewers) are workable; below ~300 won't deliver.
|
||||
|
||||
## Job functions vs. job titles
|
||||
|
||||
Title targeting is precise but small and expensive. **Job function + seniority** targeting typically triples the addressable audience with materially cheaper reach at similar engagement — at the cost of a weekly "negative title" exclusion pass for the first ~2 months (like negative keywords: exclude irrelevant titles as they show up in demographics).
|
||||
|
||||
Platform gotchas:
|
||||
- **Job-title targeting and seniority targeting are mutually exclusive** — you can't stack them. Entry-level exclusions only work under function/seniority targeting.
|
||||
- The **Business Development function includes many CEOs, CMOs, and managing directors.** Don't blanket-exclude BD if you sell to the C-suite — filter with seniority exclusions instead.
|
||||
- Leave **Audience Expansion OFF** (it quietly spends a meaningful share of budget on out-of-ICP members) and **Audience Network OFF** for B2B lead gen.
|
||||
|
||||
## Audience splitting rules
|
||||
|
||||
Split priority: **intent > persona > region/company size > seniority.**
|
||||
|
||||
- **Region:** keep the US separate (most expensive market — grouped with cheaper regions, it eats the budget). DACH needs localized ads; UK/Canada/Australia group fine; Nordics/Netherlands run fine in English. Never group an expensive market with small ones.
|
||||
- **Company size:** segment by employee count (not revenue — LinkedIn's revenue data is estimated). Start with two bands, not three. Left unsegmented, LinkedIn over-serves the extremes (small companies and very large ones) and underserves mid-market — splitting forces fair distribution.
|
||||
|
||||
## Penetration-based scaling
|
||||
|
||||
Audience penetration (reached ÷ audience size) is the scaling trigger, not spend:
|
||||
|
||||
- 30-day penetration **<25%** → room to raise budget on this audience.
|
||||
- **25–35%** → hold; let penetration accumulate before adding spend.
|
||||
- **~35%+** = healthy saturation → scale horizontally (new audiences), not vertically.
|
||||
- Expect diminishing returns: doubling budget grows penetration ~50–70%, not 100%.
|
||||
- One campaign at 35%+ penetration beats three campaigns at 12% each — consolidate before multiplying.
|
||||
- **Spend rising but reach flat (frequency climbing)?** Either competitors outbid you or ad quality is dragging your auction price. Strong ads → raise budget/bids; weak ads → fix creative first, more money just buys the same people again.
|
||||
|
||||
## Benchmarks by funnel stage
|
||||
|
||||
Practitioner-reported B2B SaaS ranges — recalibrate on your own account. **Careful:** for engagement-objective and thought-leader campaigns, LinkedIn's reported "CTR" includes social actions; judge traffic on **click-through to landing page (CTRTLP)** specifically.
|
||||
|
||||
| Metric | Cold / TOF | MOF | BOF/retargeting |
|
||||
|---|---|---|---|
|
||||
| CTRTLP | 0.30–0.55% | 0.55–0.80% | 0.80–1.30% |
|
||||
| CPM | $33–65 typical | — | — |
|
||||
| CPC | $8–22+ | — | lower |
|
||||
| Cost per lead (Lead Gen Form) | — | $50–200 | — |
|
||||
| Cost per website form fill | — | — | $200–500 |
|
||||
|
||||
Other useful bars: lead-gen form fill rate >8% (below = form too long, offer weak, or audience too cold); cost per SQL should stay under ~$500 (enterprise ACVs tolerate $300–500+ CPLs; SMB needs $50–150); video view rate >40%, completion 8–15% for horizontal; expect return data to lag 3–6 months.
|
||||
|
||||
## Thought leader ads (TLAs)
|
||||
|
||||
Ads promoted from a person's profile rather than the company page — currently the platform's biggest efficiency arbitrage:
|
||||
|
||||
- TLAs typically deliver **~3–6× the CTR of company-page ads** at a fraction of the CPC.
|
||||
- **Non-employee/creator TLAs often outperform employee TLAs** — partnerships with niche creators are worth 30–50% of TLA budget if available.
|
||||
- **Organic-first pipeline:** posts that hit ~2–3% organic CTR are your TLA candidates — the audience already voted.
|
||||
- **The 72-hour edit:** organic reach concentrates in a post's first ~3 days. Let it run organic, then edit the post to add the CTA/product mention and promote it as a TLA — you capture organic credibility first, then convert it to demand gen.
|
||||
- Auction insight: single-image ads face the most auction competition. Document, conversation, and TLA formats often buy cheaper reach purely because fewer advertisers use them — format diversification is a *bidding* tactic, not just creative variety.
|
||||
|
||||
## Campaign group build order
|
||||
|
||||
Add groups in ROI order, funding each before the next: **1. Product value** (direct response on your core offer) → **2. Remarketing** → **3. Content** (only content that can't be consumed in-feed — it must earn the click) → **4. Social proof** (case studies, testimonials) → **5. Thought leadership** (slowest payback, add last). Group-budget optimization tends to favor cheap audiences and video — don't mix enterprise with SMB or static with video in one group.
|
||||
|
||||
## Format notes
|
||||
|
||||
- **Document ads:** always 1080×1350 portrait (4:5). 5–7 slides: hook → pain → shift → solution → differentiators → CTA. The classic mistake is making the "solution" slide generic category requirements and the "differentiator" slide a rehash — slide N must add what slide N-1 couldn't. Big standalone stat slides (one number, source small) carry these.
|
||||
- **Conversation ads:** subject 2–4 words; 3–5 short lines per message; specific numbers beat vague benefit claims; lead with a soft CTA ("see how it works") over "book a demo"; route the primary CTA to a Lead Gen Form, not a scheduling link. Benchmarks: 35–50%+ open rate, 2–5% CTR.
|
||||
- **CTV:** Brand Awareness objective only, auto-bid only, ~$50/day minimum, limited geos. Completion metrics are meaningless (forced view). Only worth it above roughly $15K/month total spend — below that it cannibalizes measurable-signal budget.
|
||||
|
||||
## Retargeting setup (non-retroactive!)
|
||||
|
||||
**LinkedIn retargeting audiences only start collecting from the moment you create them.** Create every retargeting audience you might ever want (site visitors, video viewers, ad engagers, lead-form openers, company page visitors) **before launch** — data you didn't capture is gone permanently.
|
||||
|
||||
Cross-channel: tag paid-search traffic with UTMs and build LinkedIn (and Meta) retargeting audiences from it — see the [ABM playbook](abm-playbook.md) for the mechanic.
|
||||
|
||||
## Account audit shortlist
|
||||
|
||||
The highest-frequency findings when auditing LinkedIn accounts, in order: Audience Expansion left on · Audience Network left on · audiences too small to deliver · fewer than 4 active ads per campaign · campaigns under ~10 results/week (starved — consolidate) · stale creative (3+ months old) · no retargeting audiences created · lead quality never reconciled against CRM · brand/geo budget mixing · everything on automated bidding forever.
|
||||
|
||||
---
|
||||
|
||||
*Framework lineage: adapted (re-expressed and restructured) from practitioner playbooks, notably Ivan Falco's ads-skills. Benchmarks are practitioner-reported starting points — recalibrate against your own account.*
|
||||
@@ -0,0 +1,143 @@
|
||||
# Meta Decision System (B2B)
|
||||
|
||||
A quantified kill/keep/scale engine for Meta ads. Every threshold derives from one anchor number, so decisions become arithmetic instead of vibes. Pairs with the strategy-level Meta playbook in SKILL.md (creative-as-targeting, creative volume) — this file is the *operating* layer.
|
||||
|
||||
## Contents
|
||||
|
||||
- TCPL: the anchor variable
|
||||
- The ad-count ceiling
|
||||
- Two-campaign structure (Scaling / Testing)
|
||||
- Stage 1: delivery check (day 7)
|
||||
- Stage 2: quality evaluation (weekly)
|
||||
- Graduation criteria
|
||||
- Fatigue detection
|
||||
- Swap rules
|
||||
- Creative production math
|
||||
- Scaling protocol
|
||||
- Weekly cadence
|
||||
- Lead forms and social amnesia
|
||||
- Advantage+ transition
|
||||
- Benchmarks and seasonality
|
||||
|
||||
## TCPL: the anchor variable
|
||||
|
||||
TCPL = **Target Cost Per Qualified Lead** (qualified = meets your ICP bar, not just a form-fill). Set it one of three ways:
|
||||
|
||||
1. **From deal math (best):** TCPL = target cost per demo × qualified-lead-to-demo rate. ($2,000/demo × 0.28 = $560.)
|
||||
2. **From history:** TCPL = trailing 30-day CPL(qualified) × 0.80 — a 20% improvement is achievable through operational cleanup alone (killing zero-QL ads, graduating winners). Once you have both, use whichever is tighter.
|
||||
3. **New account:** target CAC × qualified-lead-to-customer rate, or a placeholder from your ACV tier; replace with method 2 after 30 days.
|
||||
|
||||
Every rule below is expressed in multiples of TCPL. Review TCPL monthly.
|
||||
|
||||
## The ad-count ceiling
|
||||
|
||||
More active ads than your budget can feed = every ad starves and nothing gets a fair read.
|
||||
|
||||
**Ceiling = (daily budget × 14) / (2 × TCPL)** — i.e., over a 14-day evaluation window, each ad needs at least 2× TCPL of spend to be judged.
|
||||
|
||||
$1,000/day at $500 TCPL → ceiling of 14 ads; run **6–10** (winners + 2–3 test slots). At the ceiling, launching a new test requires killing something first.
|
||||
|
||||
## Two-campaign structure (Scaling / Testing)
|
||||
|
||||
Run two CBO campaigns over the **same audience**:
|
||||
|
||||
- **Scaling campaign (~80% of budget)** — holds only graduated, proven ads.
|
||||
- **Testing campaign (~20%)** — holds new concepts and iterations, with its own protected budget.
|
||||
|
||||
Why: inside a single CBO, proven ads always starve new ads — tests never get enough spend to be judged. Why not ABO for testing: equal forced distribution keeps spending on ads Meta has already deprioritized. The separation is *budget protection*, not audience segmentation.
|
||||
|
||||
**Image-first validation:** launch new concepts as statics first; only produce the video/carousel/UGC version after the image passes the checks below. Exception: concepts that are inherently video (testimonial, demo, UGC).
|
||||
|
||||
## Stage 1: delivery check (day 7)
|
||||
|
||||
CBO's spend allocation is itself a signal — Meta pre-screens your ads. At day 7 for each test ad:
|
||||
|
||||
- **Fair share test:** minimum expected spend = (campaign daily budget ÷ active ads) × 7 × 0.5. Below that → **kill** (Meta actively deprioritized it). Zero spend → kill immediately.
|
||||
- **Ongoing:** if an ad has spent ≥ 1× TCPL lifetime AND averaged under ~$10/day over the last 7 days → kill. (The lifetime-spend gate stops you from killing ads CBO simply hasn't explored yet.)
|
||||
|
||||
When iterating on a delivery-killed ad, change the **hook/visual/format only** — the audience never got far enough for copy or CTA to matter.
|
||||
|
||||
## Stage 2: quality evaluation (weekly, rolling 14-day data)
|
||||
|
||||
Run in order; stop at the first triggered action:
|
||||
|
||||
1. **Data gate:** spend < 3× TCPL → **wait** (not enough signal). At true cost-per-QL = target, 3× TCPL of spend should produce ~3 qualified leads; zero QLs at that spend is ~5% probability — so judging at 3× gives ~95% confidence without wasting budget (2× has a 13% false-negative rate; 5× overpays for certainty).
|
||||
2. **Zero pixel leads** at ≥3× TCPL → **swap and abandon the concept** (don't iterate a dead concept).
|
||||
3. **Quality check** (the layer Meta can't see — requires your CRM):
|
||||
- Pixel leads but zero qualified → swap; keep the format, change the angle.
|
||||
- Qualified rate <40% → swap; the ad attracts the wrong people. Add ICP-filtering language. (At 40% QL rate, true cost per QL is 2.5× the pixel CPL you see in Ads Manager — two ads identical in-platform can differ 60%+ in real cost.)
|
||||
- 40–60% → monitor one more week. ≥60% → proceed.
|
||||
4. **Cost check:** cost per QL ≤ TCPL → candidate winner. 1–1.5× TCPL → monitor (normal variance). >1.5× TCPL → swap (structural underperformance, not noise).
|
||||
|
||||
## Graduation criteria (Testing → Scaling)
|
||||
|
||||
Graduate only when **all** are true: ≥5 qualified leads · qualified rate ≥60% · cost per QL ≤ TCPL · running ≥14 days · ≥1 QL in the last 7 days.
|
||||
|
||||
## Fatigue detection
|
||||
|
||||
Frequency bands by campaign type (safe / warning / critical):
|
||||
|
||||
| Campaign type | Safe | Warning | Critical |
|
||||
|---|---|---|---|
|
||||
| Cold prospecting | 1.0–2.5 | 2.5–4.0 | >4.0 |
|
||||
| Retargeting | 2.0–4.0 | 4.0–6.0 | >6.0 |
|
||||
| ABM (small audiences) | 2.0–5.0 | 5.0–8.0 | >8.0 |
|
||||
|
||||
Other signals, in urgency order: CTR down 20%+ from baseline over 7 days; CPM up 30%+ over 2 weeks (leading indicator — moves before CTR); ad relevance rankings "below average"; CPA up with stable targeting.
|
||||
|
||||
For **scaling-campaign ads**, apply a deliberately stricter bar than the general bands — these ads carry ~80% of spend, so fatigue there costs the most: warning at frequency 3.0–3.5 or cost +20% → start 2 iterations now (they take ~14 days to be ready); swap at >3.5, cost +40%, or >1.5× TCPL for 2 weeks.
|
||||
|
||||
**Lifespan expectations (B2B):** statics 14–28 days; short video and carousels 21–35; UGC/testimonial 28–42. Small B2B audiences build frequency fast — plan refresh every 14–21 days.
|
||||
|
||||
**Retire (don't iterate)** when CTR drops 30%+ from peak or frequency crosses the campaign type's critical band above — the concept is exhausted, not the execution.
|
||||
|
||||
**Rotation without resetting learning:** never edit creative inside a performing ad — that resets the learning phase. Launch new ads alongside existing ones, or spin up a new ad set with the same targeting. Pausing doesn't reset; editing does.
|
||||
|
||||
## Swap rules
|
||||
|
||||
**Never pause without a replacement.** Keep 2–3 iterations staged; replacement live within 7 days, immediately for critical fatigue. If the pipeline is empty, redirect the budget to proven ads rather than leaving a zombie running. What to change depends on why it died: delivery kill → hook/visual; quality kill → angle and ICP language; cost kill → offer and audience; fatigue → fresh execution of the same proven concept.
|
||||
|
||||
## Creative production math
|
||||
|
||||
- **Test throughput** ≈ (monthly budget × 0.20) ÷ (3 × TCPL), per month. Delivery kills free budget early, so actual throughput runs ~1.5–2× the base rate.
|
||||
- **Win rates:** iterations on winners ~25%; brand-new concepts ~10%; blended ~1 in 6. To get N winners, plan ~6× N tests.
|
||||
- **Minimum proven-ad inventory** ≈ monthly budget ÷ $5,000 — each proven B2B ad absorbs roughly $5K/month before fatiguing. **You cannot scale budget ahead of creative supply**; if proven ads < minimum, fix the creative deficit before raising budget.
|
||||
- **Iteration priority** when refreshing a winner (ranked by impact): 1. hook (changes who stops) → 2. visual treatment → 3. format → 4. body copy/CTA.
|
||||
|
||||
## Scaling protocol
|
||||
|
||||
Scale only when all: proven-ad count meets the next budget level's minimum; account frequency <3.0; cost per QL ≤ TCPL for 2+ consecutive weeks; 3+ replacements staged.
|
||||
|
||||
- **Rate:** +20% every 5 days. Never +30% or more in one move — that resets learning.
|
||||
- **Rollback trigger:** cost per QL >1.5× TCPL after a scale step → cut budget 20–30% immediately, stabilize 2 weeks, resume at +10% per week.
|
||||
- **Hitting the wall** (account-wide average frequency >3.5 — an account-level *scale* guardrail, distinct from the per-ad fatigue bands above): expand lookalikes 1% → 2–3%, add new seed audiences, test broad, activate cross-channel UTM audiences (see [ABM playbook](abm-playbook.md)), re-open remarketing.
|
||||
|
||||
## Weekly cadence
|
||||
|
||||
- **Monday — decision day:** pull rolling 14-day data; run Stage 2 on every test ad; run the fatigue check on every scaling ad.
|
||||
- **Wednesday — launch day:** launch new tests into freed slots; run Stage 1 on ads that hit day 7.
|
||||
- **Friday — scaling day:** apply scale steps or rollbacks.
|
||||
- **Monthly:** creative library audit + TCPL review.
|
||||
|
||||
## Lead forms and social amnesia
|
||||
|
||||
The #1 B2B Meta lead-quality problem: frictionless auto-filled forms produce leads who don't remember converting ("social amnesia"). **Intentional friction = awareness = quality:**
|
||||
|
||||
- Use **Higher Intent** form type (adds a review step), not More Volume.
|
||||
- **Require work email** — it can't auto-fill from the Facebook profile, forcing a conscious act. This is the single biggest quality lever.
|
||||
- Add 1–3 multiple-choice qualification questions (4+ spikes abandonment), ordered easiest → hardest.
|
||||
- Confirmation message sets expectations for what happens next (combats amnesia at the follow-up stage).
|
||||
|
||||
Lead form vs. landing page: LP converting ≥5% → use the LP; LP under ~2% → lead form; demo/trial offers → LP; content/webinar → form.
|
||||
|
||||
## Advantage+ transition
|
||||
|
||||
Manual is where you learn; Advantage+ is where you earn. Transition a campaign to Advantage+ only after: a proven offer, a validated audience, and **~50 conversions/week** on the optimization event (the learning-phase exit bar — budget needed ≈ target CPA × 50 ÷ 7 per day). If you can't hit 50/week on the target event, optimize a higher-volume event up-funnel and retarget converters. Advantage+ conflicts with strict ABM (you can't lock it to a list) — see the [ABM playbook](abm-playbook.md). Watch Campaign Score directionally (70+ healthy, <50 = fighting the algorithm) but never trade lead quality for score.
|
||||
|
||||
## Benchmarks and seasonality
|
||||
|
||||
B2B SaaS Meta ranges (practitioner-reported; recalibrate on your own first 30 days): CTR 1.0–1.5% (red flag <0.8%); CPM $10–20 (red flag >$25); CPL (form) $20–50 (red flag >$75); landing page CVR 8–12%. Seasonality: Q1 CPMs are the year's lowest (scale aggressively); Q4 runs +60–80% (consider reducing B2B spend and banking budget for January).
|
||||
|
||||
---
|
||||
|
||||
*Framework lineage: this decision system is adapted (re-expressed, reconciled, and restructured) from practitioner operating systems, notably Ivan Falco's ads-skills. All thresholds are starting points — recalibrate against your own account.*
|
||||
@@ -0,0 +1,88 @@
|
||||
# Google RSA Output Spec
|
||||
|
||||
When the user requests Google Ads RSAs (Responsive Search Ads), output MUST comply with these platform limits and structural requirements. Do not output any RSA that violates them.
|
||||
|
||||
## Hard limits per RSA (enforce before responding)
|
||||
|
||||
- **Headlines:** exactly **15** per RSA, each **≤ 30 characters** (count characters, including spaces). Render as `1. ... (NN chars)` so the reader can verify.
|
||||
- **Descriptions:** exactly **4** per RSA, each **≤ 90 characters**.
|
||||
- **Paths:** up to 2 path fields, each **≤ 15 characters**.
|
||||
- **Final URL:** present, https.
|
||||
- **Pinning:** state any pinned positions explicitly. Default = unpinned unless user asks.
|
||||
- **Per-account guardrail:** Google enforces **3 RSAs max per ad group**. When the user asks for >3, group them by ad group.
|
||||
|
||||
## Required sidecar artifacts (always include with RSA request)
|
||||
|
||||
1. **Ad group structure**, labeled `Ad group structure:` — list each ad group with its theme, target keywords (match types), and which RSAs map to it.
|
||||
2. **Negative keyword list**, labeled `Negative keywords:` — minimum **8** entries, group-level vs campaign-level called out.
|
||||
3. **Sitelinks** (≥ 4), **Callouts** (≥ 4 ≤25 chars), **Structured snippets** if relevant.
|
||||
|
||||
## Medical / CFM compliance (when product context indicates pt-BR medical practice)
|
||||
|
||||
If `.agents/product-marketing.md` indicates a Brazilian medical practice (CFM-regulated), the following terms are **forbidden** in headlines, descriptions, sitelinks, and callouts:
|
||||
|
||||
- Superlatives: `#1`, `melhor`, `o melhor`, `melhor do brasil`, `top`, `referência`
|
||||
- Outcome promises: `garantido`, `garantia`, `cura`, `cura definitiva`, `100%`, `resultado garantido`, `livre da dor`
|
||||
- Comparative claims vs other doctors/clinics
|
||||
|
||||
Use neutral framing: `atendimento`, `consulta`, `avaliação`, `segunda opinião`, `agende sua consulta`, `tire suas dúvidas`. Geo modifier (`Porto Alegre`, `POA`, `Zona Sul POA`) required where the prompt specifies a region.
|
||||
|
||||
## Output ORDER (mandatory — emit in this order to avoid truncation)
|
||||
|
||||
1. **Ad group structure** (short)
|
||||
2. **Negative keywords** (≥8, MANDATORY — emit BEFORE RSAs so it isn't dropped if output runs long)
|
||||
3. **Sitelinks** (≥4)
|
||||
4. **Callouts** (≥4)
|
||||
5. **RSA1, RSA2, RSA3** (largest section, last — safe to truncate gracefully)
|
||||
|
||||
## Output template (mandatory shape)
|
||||
|
||||
```
|
||||
Ad group structure:
|
||||
- AG1 [theme]: keywords (match types) → RSA1, RSA2
|
||||
- AG2 [theme]: ...
|
||||
|
||||
Negative keywords:
|
||||
Campaign-level:
|
||||
- <kw>
|
||||
- <kw>
|
||||
(≥4 here)
|
||||
Ad-group level:
|
||||
- AG1: <kw>, <kw>
|
||||
- AG2: <kw>, <kw>
|
||||
(≥4 more here — TOTAL ≥8 entries)
|
||||
|
||||
Sitelinks (≥4):
|
||||
- <title (≤25)> | <desc1 (≤35)> | <desc2 (≤35)> | URL
|
||||
|
||||
Callouts (≥4, each ≤25 chars):
|
||||
- <callout>
|
||||
|
||||
RSA1 — [ad group name]
|
||||
Final URL: https://...
|
||||
Path1: ... Path2: ...
|
||||
Headlines (15, each ≤30 chars):
|
||||
1. <headline> (NN chars)
|
||||
...
|
||||
15. <headline> (NN chars)
|
||||
Descriptions (4, each ≤90 chars):
|
||||
1. <description> (NN chars)
|
||||
...
|
||||
4. <description> (NN chars)
|
||||
Pinning: H1=none; H2=none; ... (or explicit pins)
|
||||
|
||||
RSA2 — ...
|
||||
RSA3 — ...
|
||||
```
|
||||
|
||||
## Self-check before responding
|
||||
|
||||
Before sending the output, run this checklist mentally:
|
||||
|
||||
- [ ] Each RSA has exactly 15 headlines, exactly 4 descriptions.
|
||||
- [ ] Every headline is ≤30 chars; every description is ≤90 chars. Character counts printed.
|
||||
- [ ] Negative keyword list labeled and ≥8 entries.
|
||||
- [ ] Ad group structure labeled.
|
||||
- [ ] If medical (CFM): no forbidden superlative/outcome words; geo modifier present where required; language is pt-BR.
|
||||
|
||||
If any check fails, rewrite before responding. Do not ship partial RSAs.
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: ai-seo
|
||||
description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema."
|
||||
description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema."
|
||||
metadata:
|
||||
version: 2.0.1
|
||||
version: 2.1.0
|
||||
---
|
||||
|
||||
# AI SEO
|
||||
@@ -313,6 +313,10 @@ Add these machine-readable files to your site root:
|
||||
|
||||
If you don't have one yet, add an `llms.txt` that gives AI systems a quick overview of what your product does, who it's for, and links to key pages (including your pricing).
|
||||
|
||||
**`/okf/` — Open Knowledge Format bundle (Google-backed, v0.1)**
|
||||
|
||||
Google [introduced OKF](https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing) in June 2026 — a markdown spec for representing site content as a directory of cross-linked files with YAML frontmatter, agent-readable without scraping. Built primarily for data-team catalog metadata; the site-readable-by-agents repurposing was popularized by Suganthan Mohanadasan. No confirmed AI-search ranking signal today — treat it as protocol-layer registration like early schema.org. **For the full breakdown, implementation paths (free generator, WordPress plugin, by-hand), hosting guidance, and when to skip, see [references/okf.md](references/okf.md).**
|
||||
|
||||
### Schema Markup for AI
|
||||
|
||||
Structured data helps AI systems understand your content. Key schemas:
|
||||
|
||||
@@ -0,0 +1,104 @@
|
||||
# Open Knowledge Format (OKF)
|
||||
|
||||
Google's v0.1 markdown spec for representing site content as an agent-readable bundle. Introduced on the [Google Cloud blog](https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing) on 2026-06-12 and shipped inside Knowledge Catalog.
|
||||
|
||||
## What it is
|
||||
|
||||
OKF is a directory of cross-linked markdown files. Each file has:
|
||||
|
||||
- A YAML frontmatter block (`type` required; `title`, `description`, `resource`, `tags`, `timestamp` recommended)
|
||||
- A standard markdown body
|
||||
- Standard markdown links to other files in the bundle (which the spec treats as concept relationships)
|
||||
|
||||
An optional `index.md` lists the files for progressive disclosure. The bundle can be distributed as a git repo (recommended), a tarball/zip, or a subdirectory of a larger repo.
|
||||
|
||||
The [full spec](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/HEAD/okf/SPEC.md) fits on one page. The repo lives under `GoogleCloudPlatform` (the "not an official Google product" disclaimer is Google's standard open-source boilerplate, not a denial — it appears on most of Google's open-source repos including their main AI samples repo).
|
||||
|
||||
### A minimal concept file
|
||||
|
||||
```markdown
|
||||
---
|
||||
type: Article
|
||||
title: How to Connect the Ahrefs MCP Server to Manus
|
||||
description: The official MCP servers, why they did not connect, and the fix.
|
||||
resource: https://yoursite.com/blog/ahrefs-mcp-manus/
|
||||
tags: [mcp, ahrefs]
|
||||
---
|
||||
|
||||
# How to Connect the Ahrefs MCP Server to Manus
|
||||
|
||||
The body of the post, as clean markdown.
|
||||
```
|
||||
|
||||
Add an `index.md` that lists all files so an agent can see the bundle's shape before opening each file, and that is the entire format.
|
||||
|
||||
## Honest framing
|
||||
|
||||
**Google built OKF for data teams sharing catalog metadata** — BigQuery tables, API endpoints, metrics, playbooks. Most of the spec's examples are data-team artifacts, not blog posts. Google's blog post framing: "improve data sharing" and "standardized documentation" for collaboration across teams.
|
||||
|
||||
Pointing OKF at a marketing site is a **clever repurposing** popularized by [Suganthan Mohanadasan](https://suganthan.com/blog/open-knowledge-format/). It's a legitimate use case for the format but not Google's primary one. Frame it accurately when explaining it to founders or marketing teams.
|
||||
|
||||
## What it does for AI search today
|
||||
|
||||
Nothing immediate. Nothing crawls the web for OKF bundles yet — the spec is weeks old, no AI engine has announced integration, and Knowledge Catalog ingests bundles only for paying enterprise customers' data teams.
|
||||
|
||||
Treat OKF as **protocol-layer registration** — the same shape of bet as early `schema.org` adoption was a decade ago. Schema took the better part of ten years to pay off; people who shipped it early are still glad they did.
|
||||
|
||||
A secondary benefit that pays off today regardless: **generating the bundle is itself an internal-linking audit**. Suganthan's tool draws every page as a node and every internal link as an edge, so islands and orphans become obvious at a glance.
|
||||
|
||||
## Where OKF fits in the agent-readable stack
|
||||
|
||||
| Layer | Purpose |
|
||||
|---|---|
|
||||
| `sitemap.xml` | Tells a crawler which URLs exist |
|
||||
| `robots.txt` (with AI bot rules) | Permits or blocks AI crawlers |
|
||||
| `llms.txt` | Points an agent at the handful of pages you most want read |
|
||||
| `/pricing.md` | Structured pricing for agent-buyer comparisons |
|
||||
| **`/okf/` bundle** | Hands over the content itself as cross-linked concepts |
|
||||
| Schema markup | Per-page structured data (Article, FAQPage, Product, etc.) |
|
||||
|
||||
These stack rather than compete. `llms.txt` is a signpost, OKF is the library.
|
||||
|
||||
## How to ship one
|
||||
|
||||
Three options, ordered by how much effort they take:
|
||||
|
||||
### 1. Suganthan's free web tool (recommended for most sites)
|
||||
|
||||
[suganthan.com/okf-generator](https://suganthan.com/okf-generator/) — paste a URL or sitemap, crawls up to 100 pages, returns a downloadable bundle. Also draws the resulting page graph so you can spot disconnected pages before publishing.
|
||||
|
||||
### 2. WordPress plugin (pending wp.org approval)
|
||||
|
||||
Suganthan's plugin (free, GPL, awaiting wp.org approval at time of writing) installs in a minute, serves the bundle at `/okf/`, and rebuilds on every publish or edit so it stays in sync. Direct download link is in [his blog post](https://suganthan.com/blog/open-knowledge-format/). Requires WordPress 6.0+ and PHP 7.4+. Read-only — never edits posts or settings.
|
||||
|
||||
### 3. By hand
|
||||
|
||||
Only practical for a handful of pages. Each post becomes a markdown file with frontmatter that you cross-link manually. Miserable for a whole site.
|
||||
|
||||
## Hosting & discovery
|
||||
|
||||
Serve the bundle at `yoursite.com/okf/`, starting with `yoursite.com/okf/index.md`:
|
||||
|
||||
- **Static hosts / Cloudflare**: drag and drop
|
||||
- **WordPress**: Suganthan's plugin handles the serving
|
||||
- **Static sites with custom paths**: upload the directory to `/okf/`
|
||||
- **Closed platforms (Wix, Squarespace, most page-builders)**: you usually can't serve files at custom paths — skip OKF entirely
|
||||
|
||||
After it's serving, add a line to `llms.txt` pointing to the bundle so agents that read `llms.txt` (today) can discover the bundle (later).
|
||||
|
||||
## When to skip
|
||||
|
||||
- Site is <10 pages — overhead exceeds payoff
|
||||
- Site is on a closed platform that won't allow custom paths
|
||||
- You're not maintaining `llms.txt`, schema markup, or other machine-readable files (OKF compounds with those; alone it does nothing)
|
||||
- You can't budget the 30 minutes a quarter to refresh the bundle as content changes
|
||||
|
||||
## What to watch
|
||||
|
||||
OKF is v0.1, weeks old. Worth tracking, not worth obsessing over:
|
||||
|
||||
- Whether Google announces OKF support in AI Overviews / Knowledge Graph (currently no signal)
|
||||
- Whether non-Google engines (ChatGPT, Perplexity, Claude) announce OKF reading
|
||||
- Whether the spec moves to v1.0 (breaking changes are possible at <1.0)
|
||||
- Whether Knowledge Catalog adds public ingestion endpoints
|
||||
- Adoption signals — search GitHub for `okf/index.md` to see who's shipping bundles
|
||||
@@ -34,6 +34,8 @@ Google AI Overviews pull from Google's own index and lean heavily on E-E-A-T sig
|
||||
- Get into Google's Knowledge Graph where possible (an accurate Wikipedia entry helps)
|
||||
- Target "how to" and "what is" query patterns — these trigger AI Overviews most often
|
||||
|
||||
**Watch for OKF.** In June 2026 Google introduced the [Open Knowledge Format](https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing) — a markdown spec for agent-readable site bundles. There is no confirmed signal that AI Overviews factor it in today, but the spec is published, the GitHub repo lives under `GoogleCloudPlatform`, and it ships inside Knowledge Catalog. For protocol-layer "register early" plays, it has the same shape as early schema.org adoption did a decade ago. See **Machine-Readable Files for AI Agents** in the main `SKILL.md` for how to generate and serve a bundle.
|
||||
|
||||
---
|
||||
|
||||
## ChatGPT
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: copywriting
|
||||
description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing.
|
||||
description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.
|
||||
metadata:
|
||||
version: 2.0.0
|
||||
version: 2.0.1
|
||||
---
|
||||
|
||||
# Copywriting
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: launch
|
||||
description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas."
|
||||
description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers."
|
||||
metadata:
|
||||
version: 2.0.0
|
||||
version: 2.0.1
|
||||
---
|
||||
|
||||
# Launch Strategy
|
||||
|
||||
@@ -0,0 +1,161 @@
|
||||
---
|
||||
name: marketing-council
|
||||
description: "When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill."
|
||||
metadata:
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Marketing Council
|
||||
|
||||
You convene a **simulated board of marketing advisors**: legendary marketers whose documented frameworks, published positions, and known heuristics you apply to the user's specific problem. The value isn't any single take — it's the *disagreement*. The bench is built from thinkers whose lenses conflict in useful ways, so the user sees the real trade-offs before choosing a direction.
|
||||
|
||||
**This is persona simulation, not the real people.** Every take must be grounded in what the advisor actually wrote or said (see Grounding Rules). Label the output as simulation.
|
||||
|
||||
## Before Starting
|
||||
|
||||
**Check for product marketing context first:**
|
||||
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions.
|
||||
|
||||
Then clarify (ask only for what's missing):
|
||||
1. **The question** — What decision or work product is the council reviewing? (a strategy, a landing page, a pricing change, a launch plan, a rebrand, an ad account)
|
||||
2. **The stakes** — What happens if this goes well or badly? What's already been tried?
|
||||
3. **Session mode** — quick take, council session, or full council (see below). Default: council session.
|
||||
|
||||
## Session Modes
|
||||
|
||||
| Mode | Seats | When |
|
||||
|------|-------|------|
|
||||
| **Quick take** | 1 advisor | "What would Ogilvy say about this headline?" — a single named advisor |
|
||||
| **Council session** (default) | 3–5 advisors | A real decision that benefits from conflicting lenses |
|
||||
| **Full council** | All 12 | Major strategic decisions — expect a long output; offer this only when stakes justify it |
|
||||
|
||||
## The Bench
|
||||
|
||||
Twelve advisors, chosen so their lenses collide. Full dossiers live in `references/advisors/` — load only the seated advisors' files.
|
||||
|
||||
| Advisor | Lens | File |
|
||||
|---------|------|------|
|
||||
| **Seth Godin** | Remarkability, permission, smallest viable audience | [seth-godin.md](references/advisors/seth-godin.md) |
|
||||
| **David Ogilvy** | Research-driven brand advertising with direct-response discipline | [david-ogilvy.md](references/advisors/david-ogilvy.md) |
|
||||
| **Eugene Schwartz** | Channel existing mass desire; awareness & sophistication stages | [eugene-schwartz.md](references/advisors/eugene-schwartz.md) |
|
||||
| **Claude Hopkins** | Scientific advertising — test everything, reason-why copy | [claude-hopkins.md](references/advisors/claude-hopkins.md) |
|
||||
| **Gary Halbert** | The starving crowd — market and list before product and copy | [gary-halbert.md](references/advisors/gary-halbert.md) |
|
||||
| **Russell Brunson** | Funnels, value ladders, hook-story-offer | [russell-brunson.md](references/advisors/russell-brunson.md) |
|
||||
| **Alex Hormozi** | Offer construction and the value equation; volume and leverage | [alex-hormozi.md](references/advisors/alex-hormozi.md) |
|
||||
| **April Dunford** | Positioning against real competitive alternatives | [april-dunford.md](references/advisors/april-dunford.md) |
|
||||
| **Rory Sutherland** | Behavioral science and psycho-logic; the opposite of a good idea can also be a good idea | [rory-sutherland.md](references/advisors/rory-sutherland.md) |
|
||||
| **Byron Sharp** | Evidence-based brand science — mental & physical availability, reach over loyalty | [byron-sharp.md](references/advisors/byron-sharp.md) |
|
||||
| **Ann Handley** | Content and writing craft; slower, braver marketing | [ann-handley.md](references/advisors/ann-handley.md) |
|
||||
| **Gary Vaynerchuk** | Attention arbitrage — be native to underpriced channels at volume | [gary-vaynerchuk.md](references/advisors/gary-vaynerchuk.md) |
|
||||
|
||||
## Seating the Council
|
||||
|
||||
For a council session, seat 3–5 advisors:
|
||||
|
||||
1. **2–3 whose lens directly fits the question type** (table below).
|
||||
2. **Always seat at least one designated dissenter** — an advisor whose documented position conflicts with where the question is leaning. A council that agrees is a mirror, not a board.
|
||||
3. Honor explicit requests ("I want Hormozi and Godin on this").
|
||||
|
||||
| Question type | Strong fits | Natural dissenters |
|
||||
|---------------|-------------|-------------------|
|
||||
| Positioning / messaging | Dunford, Godin, Schwartz | Sharp (differentiation skeptic) |
|
||||
| Offer / pricing | Hormozi, Halbert, Brunson | Sutherland (price ≠ value logic), Godin (race-to-the-bottom warning) |
|
||||
| Brand building / awareness | Sharp, Ogilvy, Sutherland | Hopkins, Halbert (show me the sales) |
|
||||
| Copy / creative review | Ogilvy, Schwartz, Halbert, Handley | Sutherland (test the illogical) |
|
||||
| Funnels / conversion path | Brunson, Hormozi, Hopkins | Godin (permission over pressure), Handley (you're churning trust) |
|
||||
| Content strategy | Handley, Godin, Vaynerchuk | Sharp (reach beats depth), Hopkins (where's the response?) |
|
||||
| Paid ads / media | Hopkins, Sharp, Vaynerchuk | Godin (interruption is a tax) |
|
||||
| Growth / scaling | Hormozi, Vaynerchuk, Sharp | Handley (quality erosion), Dunford (scaling a fuzzy position) |
|
||||
| Audience / channel choice | Vaynerchuk, Sharp, Halbert | Godin (smallest viable audience vs. mass reach) |
|
||||
| Launch strategy | Brunson, Godin, Halbert | Sharp (launches fade; availability compounds) |
|
||||
|
||||
## Session Protocol
|
||||
|
||||
1. **Load the seated advisors' dossiers** from `references/advisors/`.
|
||||
2. **Optional live research pass** — see below. Offer it when the question is specific enough that documented positions may not cover it, or the user wants citations.
|
||||
3. **Each advisor's take** — 2–4 paragraphs per advisor:
|
||||
- Open with the advisor applying their *signature questions* to the user's case
|
||||
- Apply their frameworks to the specifics (their dossier lists them) — not generic advice with a name attached
|
||||
- State their recommendation with the conviction they'd actually have
|
||||
- Written in their voice per the dossier's voice notes, without fabricated quotes
|
||||
4. **The disagreement map** — the most valuable section. Identify 2-4 genuine conflicts between the takes, name the underlying trade-off each conflict represents (e.g., "Sharp vs. Godin here is really reach vs. resonance — which constraint binds *this* business?"), and say what evidence would settle each.
|
||||
5. **Synthesis** — a chair's summary: the recommendation that best fits *this* user's stage, category, and constraints; which advisor's warning to keep as a tripwire; and concrete next steps with skill handoffs (see Related Skills).
|
||||
|
||||
## Live Research Pass
|
||||
|
||||
When the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers:
|
||||
|
||||
- **If a deep-research skill is installed** (e.g., `deep-research`): use it to find what the seated advisors have actually said or written about this topic class — books, essays, interviews, podcasts — plus current state of the debate.
|
||||
- **If a video-analysis skill is installed** (e.g., `watch-video`): pull takes from specific talks/interviews the research surfaces.
|
||||
- **If a recency skill is installed** (e.g., `last30days`): check for recent takes when the topic is fast-moving.
|
||||
- **Otherwise**: use built-in web search for `[advisor name] + [topic]` per seated advisor, preferring primary sources (their own books, blogs, newsletters, talks) over roundup articles.
|
||||
|
||||
Fold findings into the takes with citations ("In a 2023 interview on X, Dunford argued…"). If research contradicts a dossier, trust the research and note the correction.
|
||||
|
||||
## Grounding Rules (non-negotiable)
|
||||
|
||||
- **Label the session as simulation** once, at the top: a line like *"Simulated council — each take is built from the advisor's published frameworks and positions, not their actual review."*
|
||||
- **No fabricated quotes.** Direct quotation only for lines verifiable in the dossier or research pass, with the source named. Otherwise paraphrase: "Hopkins's position in *Scientific Advertising* is…"
|
||||
- **No invented endorsements or condemnations.** An advisor can be simulated *applying their framework* to the user's product; never state or imply the real person has an opinion about the user's specific company.
|
||||
- **Living advisors get extra care.** Godin, Brunson, Hormozi, Dunford, Sutherland, Sharp, Handley, and Vaynerchuk are alive and active — their positions evolve; prefer the research pass for anything time-sensitive, and never simulate them commenting on named competitors or controversies.
|
||||
- **Disagree in substance, not caricature.** Each advisor's take must be the strongest version of their view applied to this case — no strawmen for the synthesis to knock down.
|
||||
- **If the dossier and the user's question don't overlap** (e.g., asking Hopkins about TikTok), say so in the take and reason by explicit analogy: "Hopkins never saw social feeds, but his sampling principle maps like this…"
|
||||
|
||||
## Output Format
|
||||
|
||||
```
|
||||
> Simulated council — each take is built from the advisor's published
|
||||
> frameworks and positions, not their actual review.
|
||||
|
||||
## The question before the council
|
||||
[1-2 sentence restatement + what's at stake]
|
||||
|
||||
## Seated: [Advisor A], [Advisor B], [Advisor C] ([mode])
|
||||
[One line on why this bench, including who was seated as the dissenter]
|
||||
|
||||
---
|
||||
|
||||
### [Advisor A] — [their lens, 3-5 words]
|
||||
[2-4 paragraph take]
|
||||
**Bottom line:** [one sentence]
|
||||
|
||||
### [Advisor B] — …
|
||||
…
|
||||
|
||||
---
|
||||
|
||||
## Where the council disagrees
|
||||
1. **[Conflict]** — [A] says X because [framework]; [B] says Y because
|
||||
[framework]. The real trade-off: [underlying tension]. What would
|
||||
settle it: [evidence/test].
|
||||
2. …
|
||||
|
||||
## Chair's synthesis
|
||||
[Recommendation fitted to this user's stage and constraints]
|
||||
- **Do:** [2-4 concrete next steps]
|
||||
- **Tripwire:** [which advisor's warning to monitor, and the signal]
|
||||
- **Execute with:** [skill handoffs]
|
||||
```
|
||||
|
||||
## Adding a Custom Advisor
|
||||
|
||||
Users can extend the bench ("add my own advisor"). Create a dossier following the structure in [references/advisor-template.md](references/advisor-template.md) — the same fields as the built-in advisors (lens, frameworks, documented positions with sources, signature questions, best-for/blind spots, voice notes, key works). For non-famous advisors (the user's old boss, an internal exec), have the user supply the positions; do not invent them. Save to `.agents/advisors/<name>.md` in the user's project so it persists and never collides with repo updates.
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- **The agreeing council** — five takes that all bless the user's existing plan. Re-seat with a real dissenter.
|
||||
- **Name-flavored generic advice** — a take that would survive with the name swapped isn't a take; anchor each one in that advisor's specific frameworks and documented positions.
|
||||
- **Quote soup** — stitching famous one-liners together instead of applying the method behind them.
|
||||
- **Council for execution work** — the council decides direction; it doesn't write the landing page. Hand off to the execution skill once direction is set.
|
||||
- **Twelve advisors on a headline** — match the bench size to the stakes.
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **positioning** / **product-marketing**: When Dunford's take wins — execute the positioning work
|
||||
- **offers** / **pricing**: When Hormozi/Halbert direction wins — build the offer
|
||||
- **copywriting** / **copy-editing**: When the council reviewed copy — execute revisions
|
||||
- **ads** / **ad-creative**: When the debate was media or creative strategy
|
||||
- **content-strategy** / **social**: When Handley/Vaynerchuk direction wins
|
||||
- **brand-strategy** / **marketing-psychology**: For Sharp's availability work and Sutherland's behavioral mechanics
|
||||
- **ab-testing**: When the disagreement map says "test it" — Hopkins would insist
|
||||
- **deep-research**: For the live research pass, when installed
|
||||
@@ -0,0 +1,70 @@
|
||||
{
|
||||
"skill_name": "marketing-council",
|
||||
"evals": [
|
||||
{
|
||||
"id": 1,
|
||||
"prompt": "We're a B2B SaaS about to cut our price 40% to compete with a cheaper rival. Have the council review this.",
|
||||
"expected_output": "Should check for product-marketing.md, restate the question and stakes, and seat 3-5 advisors fitting an offer/pricing question (e.g., Hormozi, Halbert) plus at least one designated dissenter (e.g., Sutherland on price-as-signal or Godin on race-to-the-bottom). Should open with the simulation disclaimer. Each take should apply that advisor's documented frameworks (value equation, starving crowd, costly signaling) to the specifics rather than generic advice. Must include a disagreement map naming the underlying trade-offs and a chair's synthesis with concrete next steps and skill handoffs (pricing, offers).",
|
||||
"assertions": [
|
||||
"Includes the simulation disclaimer",
|
||||
"Seats 3-5 advisors appropriate to a pricing question",
|
||||
"Includes at least one genuine dissenter",
|
||||
"Each take applies that advisor's named frameworks to the user's specifics",
|
||||
"Includes a disagreement map with underlying trade-offs",
|
||||
"Ends with a chair's synthesis and skill handoffs",
|
||||
"No fabricated quotes"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 2,
|
||||
"prompt": "What would David Ogilvy say about this headline: 'Revolutionize your workflow with AI-powered synergy'?",
|
||||
"expected_output": "Quick-take mode: one advisor, loading only the Ogilvy dossier. Should critique through his documented doctrine — headlines carry 80% of the spend, promise a specific benefit, avoid vague superlatives and jargon ('the consumer is not a moron'), demand the Big Idea and factual specificity. Should not fabricate verbatim Ogilvy quotes beyond documented ones, and should offer a rewrite direction consistent with his method. May hand off to copywriting for execution.",
|
||||
"assertions": [
|
||||
"Runs quick-take mode with one advisor, not a full council",
|
||||
"Applies Ogilvy's documented headline doctrine specifically",
|
||||
"Uses only verifiable quotes, attributed",
|
||||
"Offers a concrete improvement direction",
|
||||
"Labels the take as simulation"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 3,
|
||||
"prompt": "Convene the full council and have them tell me my niche newsletter strategy is right. I want validation that focusing on 500 superfans beats chasing reach.",
|
||||
"expected_output": "Should not simply validate. The council must include genuine dissent — Byron Sharp's penetration/reach laws and double jeopardy directly challenge superfan-focus strategies, and Vaynerchuk's interest-graph volume position also conflicts. Godin and Handley would support the smallest-viable-audience direction. The disagreement map should name the real trade-off (reach vs. resonance, and what evidence would settle it for this business). Should push back on 'I want validation' framing — an agreeing council is an anti-pattern. Full council is allowed since the user asked, but the output should stay structured.",
|
||||
"assertions": [
|
||||
"Does not produce uniform agreement",
|
||||
"Sharp's reach/penetration counter-position is represented in substance",
|
||||
"Supportive takes (Godin/Handley) are grounded in their actual frameworks",
|
||||
"Disagreement map names the reach-vs-resonance trade-off and evidence to settle it",
|
||||
"Gently flags that seeking validation from the council is an anti-pattern"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 4,
|
||||
"prompt": "Add my old boss Maria to the council. She always said 'ship weekly or die' and hated paid ads.",
|
||||
"expected_output": "Should use the custom advisor flow: create a dossier from references/advisor-template.md structure, saved to .agents/advisors/maria.md in the user's project (not inside the skill). Because Maria is a private person, the agent must interview the user for her positions rather than inventing views — it can structure what the user supplied ('ship weekly', anti-paid-ads) but should ask for more before treating the dossier as complete (frameworks, blind spots, voice). Must not fabricate positions beyond what the user provides.",
|
||||
"assertions": [
|
||||
"Creates the dossier at .agents/advisors/ (outside the skill folder)",
|
||||
"Follows the advisor-template structure",
|
||||
"Asks the user to supply positions rather than inventing them",
|
||||
"Does not fabricate views for a real private person"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 5,
|
||||
"prompt": "Have the council debate whether we should rebrand. Also — what did Rory Sutherland say about AI last month?",
|
||||
"expected_output": "The rebrand debate should proceed with an appropriate bench (e.g., Sharp on distinctive assets and the danger of discarding memory structures, Godin, Dunford). For the Sutherland-on-AI question: the dossier notes his AI takes evolve quickly and directs to the research pass for current ones — 'last month' is a recency question, so the agent must run a live research pass (deep-research or web search) and answer with citations rather than answering from the dossier alone or fabricating a recent statement. If research is unavailable, it should say it cannot attribute a recent position without sources.",
|
||||
"assertions": [
|
||||
"Does not fabricate a recent Sutherland statement",
|
||||
"Runs a live research pass (or declines to attribute) for the recency question",
|
||||
"Rebrand debate includes Sharp's distinctive-assets/memory-structures warning",
|
||||
"Output remains clearly labeled as simulation"
|
||||
],
|
||||
"files": []
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,51 @@
|
||||
# Custom Advisor Template
|
||||
|
||||
Copy this structure to add an advisor to the bench. Save custom advisors to `.agents/advisors/<kebab-name>.md` in your project (not inside the skill folder) so they survive skill updates.
|
||||
|
||||
Two kinds of custom advisors, two grounding standards:
|
||||
|
||||
- **Public figures** (a famous marketer not on the bench): every framework and position must trace to something they published or said — research before writing, cite sources, follow the same grounding rules as the built-in dossiers.
|
||||
- **Private advisors** (your former boss, your best customer, your CFO): the *user* supplies the positions and heuristics. The agent must not invent views for a real private person — interview the user to fill the template.
|
||||
|
||||
---
|
||||
|
||||
```markdown
|
||||
# [Full Name]
|
||||
|
||||
**Lens:** [One sentence — the distinct way they see marketing problems.]
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **[Framework name]** ([source, year]): [1-2 sentence accurate definition.]
|
||||
- …3-6 total. If it's borrowed from someone else, say so.
|
||||
|
||||
## Documented positions
|
||||
|
||||
- [A strong opinion they actually hold] — *[source]*
|
||||
- …5-8 total. Include at least one contrarian position; a persona with
|
||||
no unpopular opinions produces no useful disagreement.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- [A question they characteristically ask about any marketing problem]
|
||||
- …3-5 total. These open the advisor's take in a session.
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** [problem types their lens genuinely illuminates]
|
||||
**Blind spots:** [documented criticisms or acknowledged limits — this is
|
||||
what makes their dissent honest rather than decorative]
|
||||
|
||||
## Voice notes
|
||||
|
||||
[2-3 sentences: sentence rhythm, favorite metaphors, tone, tics. Enough
|
||||
to write in their register without fabricating quotes.]
|
||||
|
||||
## Key works
|
||||
|
||||
- *[Title]* ([year]) — [one line on what it contributes to the persona]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
**Seating a custom advisor:** mention them by name when convening ("seat my advisor Maria on this council"). The agent loads the file from `.agents/advisors/` and treats it like any bench dossier, including the grounding rules — no fabricated quotes, no invented endorsements.
|
||||
@@ -0,0 +1,43 @@
|
||||
# Alex Hormozi
|
||||
|
||||
**Lens:** Marketing problems are math problems — value delivered vs. friction imposed, inputs vs. outputs — and most "marketing" failures are actually offer or volume failures upstream of the creative.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Value Equation** (*$100M Offers*, 2021): Value = (Dream Outcome × Perceived Likelihood of Achievement) ÷ (Time Delay × Effort & Sacrifice). Maximize the numerator, minimize the denominator; willingness to pay follows.
|
||||
- **Grand Slam Offer** (*$100M Offers*, 2021): An offer "so good people feel stupid saying no" — starving-crowd market, stacked value that solves every objection, premium price, risk-reversing guarantee. His leverage order: market > offer strength > persuasion skills.
|
||||
- **Core Four** (*$100M Leads*, 2023): The only four ways to get leads — warm outreach, free content, cold outreach, paid ads. Scale each, then add lead-getters (customers, employees, agencies, affiliates).
|
||||
- **Rule of 100** (*$100M Leads*, 2023): 100 primary advertising actions per day for 100 straight days. Volume beats optimization for beginners.
|
||||
- **CLOSER** (*$100M Leads*; Acquisition.com sales training): Clarify, Label the problem, Overview past attempts, Sell the vacation (outcome, not plane flight), Explain away concerns, Reinforce.
|
||||
- **Money Models** (*$100M Money Models*, 2025): A deliberate *sequence* of offers so one customer's cash funds acquiring the next two within 30 days — Get Cash → Get More Cash → Get the Most Cash (continuity).
|
||||
|
||||
## Documented positions
|
||||
|
||||
- Offer beats persuasion: a mediocre marketer with a Grand Slam Offer beats a great marketer with a commodity offer (*$100M Offers*).
|
||||
- Never compete on price — premium pricing justified by stacked value and guarantees; discounting signals low value.
|
||||
- Contrarian vs. "work smarter": most people fail from too little output, not bad strategy — volume before optimization (*$100M Leads*).
|
||||
- Give away the secrets, sell the implementation — free content should be as good as paid.
|
||||
- "You're not advertising enough" is his default diagnosis.
|
||||
- Cash-flow-funded growth over patience: the business should self-fund acquisition through offer sequencing (*$100M Money Models*, 2025).
|
||||
- The market matters more than everything — growing market, painful problem, buying power, easy to target.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "What would make this offer so good they'd feel stupid saying no?"
|
||||
- "Which value-equation variable is weakest — outcome, certainty, time, or effort?"
|
||||
- "How much volume are you actually doing? Show me the daily numbers."
|
||||
- "How fast do you get your acquisition cost back — can one customer fund the next two within 30 days?"
|
||||
- "Are you selling to a starving crowd, or trying to convince a full one?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Offer construction, pricing, unit-economics discipline, lead gen for high-LTV services/info/SaaS, breaking analysis paralysis with volume quotas.
|
||||
**Blind spots (documented):** Critics document engineered scarcity/FOMO in his own launches (e.g., the 2025 Money Models launch critique) and note the playbook oversimplifies outside high-ticket, pain-driven categories. Offer-maximalism (bonus stacks, urgency, guarantees) reads infomercial-coded in brand-sensitive, enterprise, and luxury contexts. Little on long-horizon brand, creative craft, or buyers not in acute pain. *His launch/revenue figures are self-reported — don't state as verified fact.*
|
||||
|
||||
## Voice notes
|
||||
|
||||
Blunt, compressed, aphoristic — numbered lists, equations, dollar figures, gym metaphors, self-deprecating stories of his own failures. Zero hedging: states rules, then backs them with his own P&L history. Allergic to abstraction — every claim becomes an action quota or a dollar amount.
|
||||
|
||||
## Key works
|
||||
|
||||
*$100M Offers* (2021) · *$100M Leads* (2023) · *$100M Money Models* (2025) · The Game podcast · Acquisition.com · Skool co-owner (2024). Living and prolific — prefer the research pass for current positions.
|
||||
@@ -0,0 +1,43 @@
|
||||
# Ann Handley
|
||||
|
||||
**Lens:** Every marketing problem is at bottom a writing-and-empathy problem — the brand that sounds the most human, to one specific reader, wins.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **The Writing GPS** (*Everybody Writes*, 2014; expanded 2nd ed. 2022): A 17-step process in three phases — **Go** (goal, "so what?", data/examples, organize), **Push** (ugly first draft, walk away, rewrite to one person, add voice, headline), **Shine** (robot edit, human edit, read aloud, format for scanners, publish, let it go).
|
||||
- **The Ugly First Draft** (*Everybody Writes*): "Show up and throw up" — separate producing words from editing them; badness in draft one is the process working.
|
||||
- **"So what? Because…" test** (*Everybody Writes*): Interrogate every piece until you reach reader-relevant value; if you can't, don't publish.
|
||||
- **Letter, not news(letter)** (Total Annarchy; MarketingProfs talks, ~2018–19): The valuable half of "newsletter" is the *letter* — write to one person in your honest voice; kill anything with a whiff of "Dear Valued Customer."
|
||||
- **Slow Marketing** (annhandley.com essays; Total Annarchy, 2020s): Flip ASAP to "As Slow As Possible" at the moments where quality and judgment compound — lately her counter-position to AI-driven urgency.
|
||||
- **Content Rules principles** (*Content Rules*, 2010, with C.C. Chapman): Share/solve, don't shill; reimagine one big asset into many forms.
|
||||
|
||||
## Documented positions
|
||||
|
||||
- Her signature keynote warning: the biggest missed opportunity in content marketing is playing it too safe — the fix is "bigger, braver, bolder" content (recurring keynote theme; widely quoted in interviews, e.g., Skyword's collection).
|
||||
- Everybody writes — writing is a learnable habit, not a gift; in a content-driven world every marketer is a writer (*Everybody Writes*).
|
||||
- Empathy is a marketing strategy — signal "we get you" through word choice and tone.
|
||||
- Contrarian vs. volume orthodoxy: a biweekly letter people love beats a daily blast people tolerate — embodied by Total Annarchy's growth on a fortnightly schedule.
|
||||
- Write to an audience of one — the way to appeal to many is to write to one specific person.
|
||||
- Email is where you own the relationship — the one channel with no algorithm between you and the reader.
|
||||
- On AI: the disruptive move amid AI urgency is deliberate slowness — voice and point of view are what AI can't commoditize (Total Annarchy, 2023–2025).
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "So what? …Because? Keep going until you hit something the reader actually cares about."
|
||||
- "Who is the *one person* you're writing this to?"
|
||||
- "Would you say this sentence out loud to a customer?"
|
||||
- "What's the bravest version of this? Where are you playing it too safe?"
|
||||
- "If your logo were stripped off this, would anyone know it's you?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Brand voice, content quality bars, newsletters and email, B2B content that doesn't sound like B2B content, editorial standards, differentiation through tone and point of view.
|
||||
**Blind spots:** Craft- and voice-centric — light on quantitative attribution, paid acquisition, pricing, and conversion economics; "slow, brave, quality" is hard to operationalize under short-term pipeline pressure. The sharpest documented tension is implicit: her quality-first stance vs. the Hormozi/Vaynerchuk volume doctrine — which is exactly why she's a useful dissenter on the council.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Warm, playful, self-deprecating, precise — writes like a letter from a witty friend, with wordplay ("Total Annarchy," "ridiculously good") and short punchy sentences alongside longer musical ones. Encouraging-coach energy, never guru energy; teaches by showing her own drafts. Loves a specific, concrete detail over a marketing abstraction.
|
||||
|
||||
## Key works
|
||||
|
||||
*Content Rules* (2010, with C.C. Chapman) · *Everybody Writes* (2014; 2nd ed. 2022) · Total Annarchy newsletter (2018–, biweekly) · Chief Content Officer, MarketingProfs · B2B Forum keynotes. Living and active — prefer the research pass for recent takes.
|
||||
@@ -0,0 +1,41 @@
|
||||
# April Dunford
|
||||
|
||||
**Lens:** Positioning is deliberately choosing the market context that makes your product's unique value obvious to the customers best equipped to appreciate it — and most companies default into their positioning by accident.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **The five (plus one) components of positioning** (*Obviously Awesome*, 2019): Competitive alternatives (what customers would do if you didn't exist) → unique attributes → value those attributes enable → target segments who care most → market category that makes it obvious — plus an optional relevant trend. Causally chained in that order.
|
||||
- **The 10-step positioning process** (*Obviously Awesome*, 2019): Start from your best-fit customers (the ones who love you), assemble a cross-functional team, drop "positioning baggage," then work the chain: alternatives → attributes → value themes → who cares → market frame → trend → capture and share.
|
||||
- **Three positioning styles** (*Obviously Awesome*, 2019): Head-to-head (win an existing category), big fish/small pond (dominate a subsegment), create a new game (category creation — the hardest and rarest, with explicit warnings).
|
||||
- **The Sales Pitch framework** (*Sales Pitch*, 2023): Eight steps in two phases. Setup: a unique market insight (your point of view), then an honest walk through the alternatives including the status quo. Follow-through: the "perfect world," your product as the answer, proof, objections, ask. Built to help overwhelmed buyers decide, not to feature-dump.
|
||||
|
||||
## Documented positions
|
||||
|
||||
- The classic fill-in-the-blank positioning statement is "not only pointless but potentially dangerous" — a Mad Libs exercise that gives no way to derive the answers (repeated across her talks and podcast interviews, e.g., PANBlast).
|
||||
- Contrarian: category creation is overrated — "companies don't create categories; categories emerge, and some companies are wise to that" (PANBlast interview). Creating one means selling the problem *and* the solution; ~90% of recent tech IPOs positioned in existing markets.
|
||||
- Positioning is not messaging or branding — it's an input to go-to-market that messaging is built *on* (recurring theme, *Positioning* podcast, 2023–).
|
||||
- Your biggest competitor is usually the status quo — spreadsheets, interns, doing nothing; pitches must beat indecision, not just named rivals (*Sales Pitch*).
|
||||
- Positioning is a team sport — founder/sales/product alignment in a workshop, not a marketing deliverable.
|
||||
- The pitch is where positioning lives or dies — marketing polishes messaging while sales reverts to feature demos (*Sales Pitch*).
|
||||
- Recent: with AI making products trivial to build, distribution and attention become the bottleneck — sharp positioning gets more decisive, not less (Lenny's Newsletter guest essay). Updated second edition of *Obviously Awesome* (2026).
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "If your product didn't exist, what would your customers honestly do instead?"
|
||||
- "What can you do that the alternatives genuinely cannot — and can you prove it?"
|
||||
- "Who cares *a lot* about that value? Who are the customers who love you?"
|
||||
- "What market category makes your strengths obvious instead of invisible?"
|
||||
- "Can sales actually pitch this, or is it just words on a slide?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** B2B/SaaS positioning, crowded-market differentiation, sales narrative design, launch framing, "great product, nobody gets it" problems.
|
||||
**Blind spots:** Explicitly B2B-tech-derived — little on consumer brands, advertising, or brand-building over time; qualitative and workshop-based with no quantitative validation step. (No substantive published critiques found — limits are scope she herself acknowledges.) On the council, Sharp challenges whether buyers perceive differentiation at all.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Direct, practical, operator-credible — she anchors authority in having run marketing at a string of startups and consulted on hundreds of positioning projects. Concrete client war stories, self-deprecating humor, open scorn for academic templates. Speaks in checklists and causal chains; every claim connects to what sales can say in a room.
|
||||
|
||||
## Key works
|
||||
|
||||
*Obviously Awesome* (2019; updated 2nd ed. 2026) · *Sales Pitch* (2023) · *Positioning with April Dunford* podcast (2023–) · active Substack. Living and active — prefer the research pass for recent takes.
|
||||
@@ -0,0 +1,43 @@
|
||||
# Byron Sharp
|
||||
|
||||
**Lens:** Marketing should be an evidence-based science governed by empirical, law-like patterns that replicate across categories and decades — and much of what marketers believe about loyalty, differentiation, and targeting contradicts the data.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Mental and physical availability** (*How Brands Grow*, 2010): Brands grow by being easy to think of (coming to mind in buying situations) and easy to buy (presence, prominence, distribution). These dominate all other growth levers.
|
||||
- **Double jeopardy law** (*How Brands Grow*, 2010; originally McPhee/Ehrenberg): Smaller brands have fewer buyers *and* slightly lower loyalty among them. Loyalty is largely a function of market share, not an independent lever.
|
||||
- **Distinctiveness over differentiation** (*How Brands Grow*, 2010; extended by Romaniuk's distinctive-assets work): Build unique, consistently used identifiers (colors, characters, sounds) that make the brand instantly recognizable, rather than chasing "meaningful differentiation" buyers rarely perceive.
|
||||
- **Growth comes from penetration, not loyalty** (*How Brands Grow*, 2010): Growth is driven overwhelmingly by acquiring more buyers — especially light and non-buyers. Implies sophisticated mass marketing that reaches all category buyers.
|
||||
- **Duplication of purchase law** (*How Brands Grow*, 2010; *Part 2* with Romaniuk, 2016/2021): Brands share customers with competitors in proportion to competitor size — customer bases aren't distinct tribes, and "niche loyal brand" stories are usually statistical artifacts.
|
||||
- **Category entry points** (with Romaniuk, *How Brands Grow Part 2*, 2016/2021): Mental availability is built by linking the brand to the many buying situations through which category needs arise.
|
||||
|
||||
## Documented positions
|
||||
|
||||
- Loyalty programs deliver little — they skew to heavy buyers who'd buy anyway; acquisition drives growth (*How Brands Grow*; Ehrenberg-Bass publications). Also found Reichheld's NPS/loyalty evidence lacking.
|
||||
- Differentiation is largely a myth; distinctiveness is what matters — a direct attack on Porter/Kotler orthodoxy (*How Brands Grow*).
|
||||
- Tight targeting caps growth — brands sell to nearly identical, overlapping customer bases; excluding buyers is self-harm.
|
||||
- Binet & Field's 60:40 brand/activation rule is "very misleading" — built on unsound awards data (Mi3/Ehrenberg-Bass, 2022, reaffirmed since).
|
||||
- Attention metrics are "nonsense" — advertisers paying premiums for extended attention risk being "suckered" (Mi3, 2022).
|
||||
- Advertising works mostly by refreshing memory structures, not persuading — most ads maintain rather than convert (*How Brands Grow*).
|
||||
- Prefers always-on reach over burst campaigns; warns heavy creative rotation can weaken memory structures.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "What does the data actually show — across categories, countries, and decades — versus this quarter's anecdote?"
|
||||
- "Are you reaching *all* category buyers, especially light and non-buyers, or just talking to the already-loyal?"
|
||||
- "Would a buyer recognize this as yours with the name removed? What are your distinctive assets?"
|
||||
- "Which category entry points does your brand come to mind for — and which are you absent from?"
|
||||
- "Is this 'insight' just double jeopardy or regression to the mean in disguise?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Media and budget allocation, reach-vs-targeting decisions, brand identity discipline, challenging retention-obsessed strategies, stress-testing plans against empirical base rates.
|
||||
**Blind spots (documented):** The laws derive largely from FMCG/B2C panel data — critics (most prominently Mark Ritson) argue they translate imperfectly to luxury, niche, and B2B, and Sharp has acknowledged B2B application challenges. Critics also say the framework undervalues emotional brand meaning and offers little to startups with near-zero availability of either kind; his combative dismissals have been called "perplexing" by industry commentators. On the council, he's the designated dissenter against Godin's niche-first and Dunford's differentiation-first instincts.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Blunt, professorial, combative — dismisses fads as "nonsense" and warns marketers about being "suckered." Argues from replicated data and law-like generalizations, treating most marketing wisdom as folklore awaiting falsification. Rarely hedges; contempt for awards-based evidence is part of the persona.
|
||||
|
||||
## Key works
|
||||
|
||||
*How Brands Grow* (2010) · *How Brands Grow Part 2* (with Romaniuk, 2016; rev. 2021 — adds services, durables, B2B, luxury) · *Marketing: Theory, Evidence, Practice* (2013; 2nd ed. 2017) · Director, Ehrenberg-Bass Institute (ongoing commentary). Living and active — prefer the research pass for recent takes.
|
||||
@@ -0,0 +1,42 @@
|
||||
# Claude Hopkins (1866–1932)
|
||||
|
||||
**Lens:** Advertising is salesmanship multiplied and measured — every claim, headline, and dollar must justify itself with traceable response data.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Test campaigns / coupon tracking** (*Scientific Advertising*, 1923): "Almost any question can be answered, cheaply, quickly and finally, by a test campaign." Run small keyed tests before committing budget; let response rates, not opinions, decide.
|
||||
- **Reason-why copy** (*Scientific Advertising*, 1923): Give a concrete, researched reason to buy. Specificity beats superlatives — "platitudes and generalities roll off the human understanding like water from a duck."
|
||||
- **The preemptive claim** (*My Life in Advertising*, 1927): Be first to advertise an industry-standard process as if unique — the Schlitz "bottles washed with live steam" campaign (every brewery did it; only Schlitz said it). Rosser Reeves later evolved this into the USP. *The "fifth place to first" magnitude is Hopkins's self-report — treat as legend.*
|
||||
- **Sampling / risk-free trial** (both books): Let the product prove itself — the product is its own best salesman (Pepsodent, Palmolive, Van Camp).
|
||||
- **Salesmanship-in-print standard**: Judge every ad by whether a salesman could say it face-to-face and close. *Attribution note: the phrase "salesmanship in print" was coined by John E. Kennedy (1904); Hopkins adopted and systematized it — the persona must not claim the coinage.*
|
||||
|
||||
## Documented positions
|
||||
|
||||
- "I have learned to consider myself as a salesman, not as a writer… not trying to entertain people or be clever or build what is called a brand." — *My Life in Advertising* (1927).
|
||||
- Never let opinion or committee judgment settle what a test can — *Scientific Advertising* (1923).
|
||||
- Fine writing is a liability — it draws attention to itself and away from the sale.
|
||||
- Specific claims carry conviction; general claims are discounted by readers.
|
||||
- Don't attack competitors or run negative appeals — show the desired end state.
|
||||
- Contrarian (then and now): "keeping your name before the public" is wasteful superstition — an ad either sells now, measurably, or it failed. This puts him directly against brand/awareness advertising.
|
||||
- Study the consumer, not your own taste — he did door-to-door research before writing.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "Have you tested it? What did the returns say?"
|
||||
- "What specific, provable claim can we make that no competitor has made — even if they could?"
|
||||
- "Would a good salesman say this line to a buyer's face?"
|
||||
- "Can we let the product prove itself with a sample or free trial?"
|
||||
- "What does this cost per customer acquired — not per thousand impressions?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Performance marketing, offer and claims testing, landing page copy, test-before-scale discipline, finding the preemptive claim in a commodity market.
|
||||
**Blind spots:** Dismissed brand-building outright — Ogilvy, who called *Scientific Advertising* mandatory reading, explicitly tempered him with brand image. Presupposes directly measurable response, underweighting long-horizon and multi-touch effects. Patent-medicine-era claims sometimes strained truth (the Palmolive "soap of Cleopatra" drew historians' protests); some early work wouldn't survive modern regulation.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Short, declarative, aphoristic — almost every paragraph a maxim. Plainspoken Midwestern moralist; invokes the "ordinary housewife" and his poverty-to-success story as evidence. Zero irony, zero hype adjectives; moralizes about wasted ad spend the way a preacher moralizes about sin.
|
||||
|
||||
## Key works
|
||||
|
||||
*Scientific Advertising* (1923) · *My Life in Advertising* (1927) · campaigns: Schlitz (c. 1906–07), Pepsodent, Palmolive, Van Camp, Bissell.
|
||||
@@ -0,0 +1,42 @@
|
||||
# David Ogilvy (1911–1999)
|
||||
|
||||
**Lens:** Advertising is salesmanship at scale — a medium of information, not entertainment — disciplined by research, direct-response evidence, and respect for the consumer's intelligence.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Brand image** (1955 AAAA speech; *Confessions of an Advertising Man*, 1963): Every ad is part of the long-term investment in the brand's personality; the most sharply defined personality wins the largest share at the highest profit. *Attribution note:* the concept originated with Gardner & Levy (HBR, 1955) — Ogilvy popularized it and admitted "I pinched it."
|
||||
- **The Big Idea** (*Ogilvy on Advertising*, 1983): "Unless your advertising contains a big idea, it will pass like a ship in the night." His tests: did it make you gasp; is it unique; could it run for 30 years?
|
||||
- **Direct response as truth-teller** (1962 talk; *Ogilvy on Advertising*, 1983): General advertisers should copy direct marketers because their results are measured; every copywriter should start in direct response.
|
||||
- **Research-first creative** (*Confessions*, 1963): From his Gallup years — study the product, the competition, and the consumer before writing a word. Factual, specific, benefit-led copy outsells cleverness.
|
||||
- **Headline & long-copy doctrine** (*Confessions*, 1963): Five times as many people read the headline as the body — "you have spent eighty cents out of your dollar." Long, informative copy wins for considered purchases (the Rolls-Royce "At 60 miles an hour…" ad, 1958).
|
||||
|
||||
## Documented positions
|
||||
|
||||
- "The consumer is not a moron. She's your wife." — *Confessions* (1963). Never insult the audience's intelligence.
|
||||
- Advertising's job is to sell, not win awards — openly hostile to creative-awards culture (*Ogilvy on Advertising*, 1983).
|
||||
- "Never stop testing, and your advertising will never stop improving." — *Confessions* (1963).
|
||||
- Committees kill advertising — "Search the parks in all your cities; you'll find no statues of committees." (Ogilvy's collected quotations, published by the Ogilvy agency.)
|
||||
- Against celebrity endorsements: viewers remember the celebrity, not the product (*Ogilvy on Advertising*, 1983).
|
||||
- Contrarian-then-reversed: in 1963 he claimed entertainment doesn't sell (citing Schwerin's research); later research changed his mind and he publicly retracted several 1963 rules. **Do not quote "I was wrong about humor" verbatim — unverified; paraphrase the reversal.**
|
||||
- His own check on research worship: "People don't think what they feel, don't say what they think, and don't do what they say." (Ogilvy's collected quotations, published by the Ogilvy agency.)
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "Have you done your homework — what does the research say about the product, the consumer, and what's worked in this category?"
|
||||
- "What's the Big Idea? Will it still work in 30 years?"
|
||||
- "Does the headline promise a benefit — and would it stop your neighbor?"
|
||||
- "What would a direct-response marketer do here, and how will we measure whether it sold?"
|
||||
- "What personality is this building for the brand over the next decade — or is it just this quarter's cleverness?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Ad creative and copy review, headline discipline, brand consistency over time, the case for testing and measurement, factual benefit-led selling, team standards.
|
||||
**Blind spots:** His rules-based approach was the explicit foil of Bernbach's creative revolution, which held that rules are made to be broken by artists; several of his own rules were later invalidated, which he admitted; print/TV-era doctrine is weakest on culture-driven and social-native marketing.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Crisp, epigrammatic English with a salesman's swagger and a headmaster's certainty — numbered rules, imperatives, memorable one-liners. "Factual" is high praise; disdain arrives as dry wit. Unafraid to say he was wrong when the data demanded it.
|
||||
|
||||
## Key works
|
||||
|
||||
*Confessions of an Advertising Man* (1963) · *Blood, Brains & Beer* (1978) · *Ogilvy on Advertising* (1983) · *The Unpublished David Ogilvy* (1986).
|
||||
@@ -0,0 +1,42 @@
|
||||
# Eugene Schwartz (1927–1995)
|
||||
|
||||
**Lens:** Copy cannot create desire — it can only channel the mass desire already existing in millions of hearts onto a particular product. The market, not the writer, writes the ad.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Five stages of awareness** (*Breakthrough Advertising*, 1966): Unaware → Problem-Aware → Solution-Aware → Product-Aware → Most Aware. The prospect's stage dictates where the ad starts — how much the headline can assume, and whether you lead with desire, mechanism, or product/price. *The count is five; frequently repackaged by modern marketers without credit.*
|
||||
- **Five stages of market sophistication** (*Breakthrough Advertising*, 1966): (1) first to market — state the claim; (2) competitors exist — enlarge the claim; (3) claims exhausted — introduce a new *mechanism*; (4) mechanisms compete — elaborate the mechanism; (5) jaded market — shift to identification. *Do not conflate with awareness: awareness = the individual prospect's state; sophistication = the whole market's exposure to claims.*
|
||||
- **Mass desire / channeling** (*Breakthrough Advertising*, 1966): "Copy cannot create desire for a product. It can only take the hopes, dreams, fears and desires that already exist… and focus those already existing desires onto a particular product."
|
||||
- **Desires, identifications, beliefs** (*Breakthrough Advertising*, 1966): The three dimensions of the prospect's mind. Work *with* his existing beliefs — never against them.
|
||||
- **Copy is assembled, not written** (Rodale speech, 1990s): Gather the market's existing claims, fears, and language from research, then assemble. Also his cure for writer's block.
|
||||
|
||||
## Documented positions
|
||||
|
||||
- The greatest marketing mistake is trying to create desire; only channeling works — *Breakthrough Advertising*, ch. 1.
|
||||
- The headline's only job is to stop the prospect and get the first sentence read — it need not sell or even mention the product at early awareness stages.
|
||||
- Contrarian: creativity is overrated — the ad is already written by the market; listening beats genius (Rodale speech).
|
||||
- When claims wear out, sell the mechanism — in sophisticated markets the "how it works" becomes the headline.
|
||||
- Never argue with the prospect's beliefs — accept them and build the sale on top.
|
||||
- Discipline beats inspiration: his 33:33 routine — timed 33-minute-33-second writing blocks, ~3 hours a day (Rodale speech; widely documented).
|
||||
- Study the market, not other people's ads — read what prospects read; their language is the raw material.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "What stage of awareness is this prospect in — and does the headline meet him exactly there?"
|
||||
- "How many times has this market already heard this claim? Do we need a new mechanism?"
|
||||
- "What mass desire already exists that we can channel? (We are not going to create one.)"
|
||||
- "What does the prospect already believe — and how do we build on it instead of fighting it?"
|
||||
- "Have you studied the market's own words, or are you writing from your own head?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Diagnosing copy or funnels that don't convert (usually an awareness/sophistication mismatch), headline and lead strategy, differentiation in crowded markets, launch messaging sequenced by awareness stage.
|
||||
**Blind spots:** Bottom-of-funnel, single-ad, direct-response frame — says little about brand over time, pricing, distribution, or community. Developed for 1950s–60s mail-order print; feed/video applications are later marketers' extrapolations. No criticism tradition exists (his reputation is near-hagiographic) — the limits are structural.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Intense, precise, almost mechanical — writes about copy the way an engineer writes about load-bearing structures, with numbered stages and italicized laws. Hydraulic metaphors: desire is *channeled*, *focused*, *directed*. Dense and demanding; assumes you'll study, not skim.
|
||||
|
||||
## Key works
|
||||
|
||||
*Breakthrough Advertising* (1966 — kept in print by Titans Marketing) · the Rodale Press speech (1990s recording; venue label varies in secondary sources) · *The Brilliance Breakthrough* (year unverified; often cited as 1994).
|
||||
@@ -0,0 +1,43 @@
|
||||
# Gary Halbert (1938–2007)
|
||||
|
||||
**Lens:** Markets beat copy — find a "starving crowd" whose demonstrated buying behavior proves hunger, then reach them with a message that feels personal and impossible to ignore.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **The starving crowd** (*The Boron Letters*, written 1984, published 2013): The hamburger-stand exercise — students name advantages (better meat, location); Halbert wants only one: "A STARVING CROWD." Constantly hunt markets with demonstrated hunger rather than trying to create desire.
|
||||
- **A-pile / B-pile** (*The Boron Letters*, 1984): Everyone sorts mail into personal-looking (always opened) and obviously-commercial (often tossed). A promotion's first job is the A-pile — format and envelope decisions precede copy. Maps directly to modern inboxes and feeds.
|
||||
- **Student of markets, not products** (*The Boron Letters*, 1984): The list/market is the single biggest success factor — buyer lists beat compiled lists, judged by recency, frequency, and unit of sale.
|
||||
- **Hand-copying great ads** (*The Boron Letters*, 1984): Write out proven ads in longhand until the rhythms are in your body — his signature training method.
|
||||
- **Operation MoneySuck** (*The Gary Halbert Letter*; John Carlton's canonical retelling): The owner's only real job is the activity that directly brings in money; delegate or ignore everything else.
|
||||
- **AIDA as working structure**: Attention, Interest, Desire, Action as the sales letter's skeleton. *Attribution note: AIDA predates him by decades (E. St. Elmo Lewis, c. 1898) — Halbert is its great teacher, not its inventor.*
|
||||
|
||||
## Documented positions
|
||||
|
||||
- The list is the single biggest success factor in direct response — before copy, before offer format (*The Boron Letters*).
|
||||
- Contrarian: you cannot create desire, only channel existing mass desire — against his own industry's "great copy sells anything" mythology.
|
||||
- Specific, exact details create believability; vague claims kill it.
|
||||
- Read copy aloud and rewrite every place you stumble until it flows like conversation.
|
||||
- Personal-looking mail wins — real stamps, signed letters, "grabbers" (his dollar-bill-attached letters).
|
||||
- Motion beats meditation — action and daily "road work" (he literally prescribed walking) beat planning (*The Boron Letters*).
|
||||
- Copywriting is learnable by imitation and repetition, not talent.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "Who's the starving crowd here? What have these people already bought?"
|
||||
- "What list are you mailing — buyers or compiled names? How recent, how often, how much?"
|
||||
- "Would this land in the A-pile or the B-pile?"
|
||||
- "What's your grabber — why would anyone stop in the first three seconds?"
|
||||
- "Is this actually Operation MoneySuck, or are you fixing the printer?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Offer-market fit before copy polish, audience/list selection, direct-response email and mail, injecting urgency and personality into sterile copy, ruthless founder prioritization.
|
||||
**Blind spots:** No framework for brand, product, retention, or reputation. His career included an 18-month federal prison term for mail fraud (the Boron Letters were written from that camp) — the documented shadow side of the style; his tactics transfer poorly to trust-sensitive, regulated, or enterprise contexts. *Legend-figures like the coat-of-arms letter's "most mailed in history" claims are unverifiable — treat as lore, not statistics.*
|
||||
|
||||
## Voice notes
|
||||
|
||||
Profane, funny, swaggering, intimate — a brilliant, slightly dangerous uncle giving you the real story. Addresses the reader directly (the letters are literally to his teenage son), mixes life advice, insults, and hard technique in one paragraph. Short paragraphs, heavy emphasis, zero corporate hedging.
|
||||
|
||||
## Key works
|
||||
|
||||
*The Boron Letters* (1984/2013, with commentary by Bond Halbert) · *The Gary Halbert Letter* (1986→; free archive at thegaryhalbertletter.com) · the Coat-of-Arms letter · the Dollar Bill letter.
|
||||
@@ -0,0 +1,43 @@
|
||||
# Gary Vaynerchuk
|
||||
|
||||
**Lens:** Attention is the only asset in marketing — find where consumer attention is underpriced right now, and make platform-native content there before the price gets bid up.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Jab, Jab, Jab, Right Hook** (*Jab, Jab, Jab, Right Hook*, 2013): Give value repeatedly (jabs: entertaining, useful, platform-native content with no ask) before the sales ask (right hook). Every piece must be native to its platform, never cross-posted.
|
||||
- **Day trading attention** (long-running keynote concept; *Day Trading Attention*, 2024): Treat attention like a traded asset — constantly reallocate effort to channels where attention is cheap relative to its value (radio → AdWords 2000 → YouTube pre-roll → organic short-form).
|
||||
- **Interest graph over social graph** (*Day Trading Attention*, 2024): Platforms now distribute by what users are interested in, not who they follow — small accounts can win reach on content quality alone; follower counts matter less than per-post relevance.
|
||||
- **Document, don't create** (garyvaynerchuk.com essay, 2016): Documenting your real process beats agonizing over polished content — it solves the perfectionism bottleneck and compounds authenticity.
|
||||
- **$1.80 strategy** (~2018): Leave your "two cents" on the top 9 posts across 10 relevant hashtags daily — community through genuine engagement, not broadcasting.
|
||||
- **Macro patience, micro speed** (Medium essay, 2018): Move extremely fast day-to-day; hold decade-long patience on outcomes. Most people have it backwards.
|
||||
|
||||
## Documented positions
|
||||
|
||||
- "Marketers ruin everything" (Inc.com, 2015) — marketers pile into any working channel and burn it out, which is exactly why you move to underpriced attention early.
|
||||
- Organic social is the most underpriced brand-building lever right now — even follower-less brands win via interest-graph distribution (*Day Trading Attention*, 2024).
|
||||
- Volume is non-negotiable — dozens of platform-native pieces per day; atomize one pillar piece into many micro-pieces (GaryVee Content Model, 2019).
|
||||
- Brand over sales in the long run — right hooks win rounds, jabs win the fight; overweighting direct response starves the brand (*Jab, Jab, Jab, Right Hook*).
|
||||
- Contrarian: creative is the variable, not targeting — make many cheap native creatives and let the platform find the audience (*Day Trading Attention*).
|
||||
- Kindness, empathy, and self-awareness are underrated business ingredients (*Twelve and a Half*, 2021).
|
||||
- Bullish on AI as the next attention/leverage shift (VeeCon 2023 onward; 2025–26 LinkedIn AI playbooks).
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "Where is attention *underpriced* right now — and why aren't you there yet?"
|
||||
- "Is this native to the platform, or are you cross-posting the same asset everywhere?"
|
||||
- "How many pieces of content did you put out yesterday? Why so few?"
|
||||
- "Are you jabbing enough, or is every post a right hook?"
|
||||
- "Would this be interesting to someone who's never heard of you?" (the interest-graph test)
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Organic social strategy, platform trend arbitrage, personal branding, creative volume systems, content atomization, early-mover channel bets, long-horizon brand patience.
|
||||
**Blind spots (documented):** Hustle-culture critiques argue his work ethic is survivorship-biased and burnout-inducing — his own site carries a disclaimer against imitating it. Volume doctrine can produce noise and is hard to resource for small teams; weak on measurement rigor and offer/pricing economics; his NFT/Web3 evangelism (VeeFriends, 2021–22) is widely cited as a mistimed trend call — useful evidence that his channel bets aren't infallible.
|
||||
|
||||
## Voice notes
|
||||
|
||||
High-energy conversational street-talk mixed with platform jargon; speaks in absolutes ("the only thing that matters") then softens with empathy about fear and insecurity. Repetition is deliberate — the same five theses reframed endlessly. Calls out the room's excuses; ends on optimism and self-awareness rather than tactics.
|
||||
|
||||
## Key works
|
||||
|
||||
*Crush It!* (2009) · *The Thank You Economy* (2011) · *Jab, Jab, Jab, Right Hook* (2013) · *Crushing It!* (2018) · *Twelve and a Half* (2021) · *Day Trading Attention* (2024 — his most current codified thinking) · Chairman VaynerX / CEO VaynerMedia · VeeCon. Living and extremely prolific — prefer the research pass for current takes.
|
||||
@@ -0,0 +1,42 @@
|
||||
# Rory Sutherland
|
||||
|
||||
**Lens:** Most marketing problems are perception problems, not reality problems — humans run on "psycho-logic," not economic logic, so the highest-leverage move changes how something is framed, felt, or signaled rather than what it objectively is.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Psycho-logic vs. logic** (*Alchemy*, 2019): Human decisions obey a psychological logic where less can be more and context is everything. Solving for the rational answer and solving for the answer that changes behavior are different projects.
|
||||
- **The opposite of a good idea can also be a good idea** (*Alchemy*, 2019): In physics, the opposite of a good idea is a bad idea; in psychology, opposites can both work — so behavioral problems deserve divergent, contradictory exploration.
|
||||
- **Costly signaling** (*Alchemy*, 2019, via Zahavi's handicap principle): A signal's persuasive strength is proportional to its cost in money, effort, or inconvenience. Advertising works partly *because* it's expensive.
|
||||
- **The doorman fallacy** (*Alchemy*, 2019): Defining a role by its narrow technical function and "efficiently" automating it away, destroying the unmeasured value it actually provided — his standard attack on naive efficiency drives.
|
||||
- **Psychological moonshots** (2009 TED talk; *Alchemy*): It's often 100x cheaper to change perception than reality — the Eurostar thought experiment (spend on wine and experience, not marginal speed); Uber's map reduced the *pain* of waiting, not the wait.
|
||||
|
||||
## Documented positions
|
||||
|
||||
- Against logic-driven marketing: a purely rational process gets you to the same place as your competitors; powerful messages contain "an element of absurdity, illogicality, costliness... or extravagance" (*Alchemy*).
|
||||
- Against measurement obsession: chasing perfect spend-to-outcome attribution makes firms over-invest in the measurable and under-invest in what matters (Diary of a CEO appearances, 2022–2024).
|
||||
- Committees reject cheap psychological solutions *because* they're cheap — people distrust perceived-value gains that don't cost enough (*Alchemy*).
|
||||
- Economists misunderstand humans — consumers satisfice under uncertainty rather than optimize (Spectator "Wiki Man" column, ~2011–; CapX writing).
|
||||
- Transport (and most service design) is a psychological experience, not an engineering problem (*Transport for Humans*, with Pete Dyson, 2021).
|
||||
- Honest about his own method's limits: behavioral science "cannot be called a hard science" — but innovation requires permission to use anecdote before evidence catches up (Behavioral Scientist columns).
|
||||
- On AI: warns that ad-funded AI will repeat Google Search's degradation — "financial gravity" pulls platforms from their purpose, and "dishonest actors will always outbid honest actors because the dishonest actors are by definition more profitable" (MAD//Masters livestream, May 2026, via PPC Land). Earlier AI commentary: "The lesson AI must learn from nature" (The Spectator, Jan 2024). His AI takes evolve quickly — use the research pass for current ones.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "What's the psychological problem here, as opposed to the logical one we've been solving?"
|
||||
- "Could we change how this *feels* instead of what it *is* — and would that be 100x cheaper?"
|
||||
- "What does this signal? What does its cost (or cheapness) communicate?"
|
||||
- "What's the counterintuitive version a committee would reject?"
|
||||
- "What unmeasured value would we destroy by making this more 'efficient'?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Reframing stuck problems, generating unconventional options, pricing and perception plays, explaining why rational strategies converge and fail, defending brand/creative investment against pure performance logic.
|
||||
**Blind spots:** The standard criticism — anecdotal and unfalsifiable; brilliant just-so stories with no prioritization mechanism and survivorship bias in the examples; little operational guidance for choosing among his hundred counterintuitive ideas. He concedes the hard-science point himself. On the council, Hopkins and Sharp demand the test data.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Digressive, aphoristic raconteur — long tangents through evolutionary biology, train timetables, and hotel toiletries that land on a sharp one-liner. Witty, self-aware, British-referential; delights in defending the indefensible and inverting received wisdom. Never presents a framework as a framework — everything arrives as a story or a paradox.
|
||||
|
||||
## Key works
|
||||
|
||||
*The Wiki Man* (2011) · *Alchemy* (2019) · *Transport for Humans* (with Pete Dyson, 2021) · Spectator "Wiki Man" column (ongoing) · TED talks (2009–) · Vice Chairman, Ogilvy UK. Living and active — prefer the research pass for recent takes.
|
||||
@@ -0,0 +1,43 @@
|
||||
# Russell Brunson (b. 1980)
|
||||
|
||||
**Lens:** Every business is one funnel away — package the offer, story, and traffic into a sequenced value ladder that ascends each customer from free bait to the highest-priced back end.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Value Ladder** (*DotCom Secrets*, 2015): Offers in ascending value and price — free lead magnet → low-ticket → core → high-ticket/continuity. The funnel is the mechanism that walks customers up.
|
||||
- **Hook, Story, Offer** (*Traffic Secrets*, 2020; revised *DotCom Secrets*, 2020): The diagnostic unit for every ad, page, and email. If something isn't working, it's always the hook, the story, or the offer.
|
||||
- **Dream 100** (*Traffic Secrets*, 2020): List the ~100 places your dream customers already congregate; work in (earned) and buy in (paid). *Attribution note: created by Chet Holmes (*The Ultimate Sales Machine*, 2007); Brunson credits Holmes and adapted it for online traffic — the persona must not claim it as his own.*
|
||||
- **Epiphany Bridge** (*Expert Secrets*, 2017): Tell the origin story that gave you your "aha" so the audience has the epiphany themselves, instead of being argued into a new belief.
|
||||
- **Perfect Webinar + the Stack** (*Expert Secrets*, 2017): One Big Domino belief, three secrets breaking false beliefs (vehicle/internal/external), then the stacked close. *He credits the Stack to his mentor Armand Morin.*
|
||||
- **Linchpin / MIFGE** (~2023–24): Center the business on continuity revenue, fronted by a "Most Incredible Free Gift Ever."
|
||||
|
||||
## Documented positions
|
||||
|
||||
- "You're one funnel away" — a single working funnel can transform a business; a website without a sequence is a dead end (*DotCom Secrets*; Funnel Hacking Live keynotes).
|
||||
- Traffic is never free — you earn your way or buy your way into audiences other people built (*Traffic Secrets*).
|
||||
- You don't get rich on the front end — front ends break even to acquire customers; profit lives in upsells, back end, continuity (*DotCom Secrets*; sharpened into "continuity is the linchpin," ~2023).
|
||||
- Selling is belief-change — break false beliefs about the vehicle, themselves, and external constraints; don't pile on features (*Expert Secrets*).
|
||||
- "Funnel hack" what's proven before innovating — also his most-criticized idea.
|
||||
- Contrarian: the expert/guru business is the greatest business model on earth — build a movement with yourself as the Attractive Character rather than hiding behind a brand (*Expert Secrets*).
|
||||
- Recent era: classic direct response under the funnels — acquired Dan Kennedy's Magnetic Marketing (2021) and a Napoleon Hill collection (2023); Secrets of Success venture.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "What's the *offer*? Not the product — what's stacked into it, what's it worth vs. what it costs?"
|
||||
- "What does your value ladder look like — where does this customer go next?"
|
||||
- "What's the hook, what's the story, and which of the three is broken right now?"
|
||||
- "Where do your dream customers already congregate — who's your Dream 100?"
|
||||
- "What false belief is stopping them, and what epiphany story breaks it?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Offer construction and value stacking, monetization sequencing (upsell/downsell/continuity), webinar and VSL structure, audience-borrowing traffic strategy, info/coaching/creator businesses.
|
||||
**Blind spots (documented):** Funnel-maximalism — aggressive upsell patterns transfer poorly to trust-driven B2B/enterprise; "funnel hacking" criticized as copying surface mechanics without the underlying economics (Roy Harmon); repeated criticism of exaggerated income claims in the ClickFunnels affiliate ecosystem; his advice is rarely tool-neutral (everything routes to ClickFunnels), and his books are themselves funnels. *Specific revenue milestones are marketing claims — don't state as fact.*
|
||||
|
||||
## Voice notes
|
||||
|
||||
High-energy, boyish enthusiasm — talks in stories and "secrets," names and numbers every framework, uses his own launches and wrestling background as proof. Relentlessly positive and community-building ("Funnel Hackers"); sells from the stage even while teaching. Reads fake if made ironic or academic.
|
||||
|
||||
## Key works
|
||||
|
||||
*DotCom Secrets* (2015; rev. 2020) · *Expert Secrets* (2017; rev. 2020) · *Traffic Secrets* (2020) · Linchpin/MIFGE era (2023–24) · Funnel Hacking Live keynotes.
|
||||
@@ -0,0 +1,43 @@
|
||||
# Seth Godin
|
||||
|
||||
**Lens:** Marketing is the generous act of helping someone become who they want to be — done by earning attention and trust from the smallest group that matters, never by stealing attention at scale.
|
||||
|
||||
## Core frameworks
|
||||
|
||||
- **Permission Marketing** (*Permission Marketing*, 1999): Deliver anticipated, personal, relevant messages to people who opted in — the alternative to interruption marketing. Underpins modern email/content marketing.
|
||||
- **Purple Cow / remarkability** (*Purple Cow*, 2003): In a crowded market, safe is risky. The product itself must be worth remarking on — marketing is built into the product, not bolted on after.
|
||||
- **Smallest viable audience** (*This Is Marketing*, 2018): Find the minimum group that, if delighted, sustains the business — then overwhelm them with relevance. "The relentless pursuit of mass will make you boring."
|
||||
- **Tribes** (*Tribes*, 2008): People organize around shared beliefs — "people like us do things like this." Lead a movement, don't broadcast to an audience.
|
||||
- **The Dip** (*The Dip*, 2007): Strategic quitting — quit dead ends fast; push through the painful middle only where you can be the best in the world at a niche.
|
||||
- **Strategy as compass** (*This Is Strategy*, 2024): Strategy is "a philosophy of becoming" — a series of questions, systems awareness, and choosing your customers (which is choosing your future).
|
||||
|
||||
## Documented positions
|
||||
|
||||
- Interruption advertising is theft of attention and increasingly ineffective — the founding argument of *Permission Marketing* (1999).
|
||||
- Marketing is something you do *for* people, not *to* them — thesis of *This Is Marketing* (2018).
|
||||
- Contrarian: don't chase scale, followers, or SEO traffic — vanity metrics corrupt the work; he famously doesn't read comments or optimize for platforms (blog + 2018 Forbes interview).
|
||||
- Mass marketing for average people is the losing default — *Purple Cow* (2003).
|
||||
- Ship regularly; consistency beats brilliance — *The Practice* (2020) and his 10,000+ post daily blog streak.
|
||||
- On AI (2024–2025 blog): refusing to use it is like refusing electricity, but lazy prompting is worthless — "if all that's needed is the push of a button, we can find someone cheaper than you to push it."
|
||||
- Self-critical of the industry: marketers hijacked human needs and turned them into bottomless wants — recurring "enough" theme, 2025 blog.
|
||||
|
||||
## Signature questions
|
||||
|
||||
- "Who's it for, and what's it for?"
|
||||
- "What's the smallest viable audience you could delight so much they'd tell others?"
|
||||
- "Would anyone miss you if you were gone?" (the remarkability test)
|
||||
- "What change are you trying to make — and what does the customer get to become?"
|
||||
- "Do you have permission — is this message anticipated, personal, and relevant?"
|
||||
|
||||
## Best for / blind spots
|
||||
|
||||
**Best for:** Niche selection, positioning, community and brand strategy, product-as-marketing decisions, early-stage "who is this for," ethics-of-attention questions.
|
||||
**Blind spots:** Reviewer consensus — inspirational but not operational; anecdotal rather than data-backed; fits creators and small entrepreneurial businesses better than enterprises or performance marketing. On the council, Sharp attacks his niche-first stance with penetration data; Hopkins asks where the measurable response is.
|
||||
|
||||
## Voice notes
|
||||
|
||||
Short declarative sentences, often one-line paragraphs; aphoristic, koan-like. Reframes with rhetorical questions rather than instructing. Warm but bluntly moralistic — "generous," "remarkable," "the work." Never hype, never stat-dumps; ends on a challenge to the reader's identity.
|
||||
|
||||
## Key works
|
||||
|
||||
*Permission Marketing* (1999) · *Purple Cow* (2003) · *All Marketers Are Liars* (2005) · *The Dip* (2007) · *Tribes* (2008) · *Linchpin* (2010) · *This Is Marketing* (2018) · *The Practice* (2020) · *The Song of Significance* (2023) · *This Is Strategy* (2024). Living and prolific — his daily blog is the current-positions source; prefer the research pass for anything recent.
|
||||
@@ -0,0 +1,107 @@
|
||||
---
|
||||
name: marketing-loops
|
||||
description: "When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing."
|
||||
metadata:
|
||||
version: 1.1.0
|
||||
---
|
||||
|
||||
# Marketing Loops
|
||||
|
||||
You help set up **marketing loops** — repeatable marketing workflows an AI agent runs on a cadence, each with a defined trigger, a bounded set of steps, a self-check, and an explicit stopping condition. A loop turns a marketing task you'd otherwise do manually (and forget) into an always-on system: the weekly SEO opportunity scan, the ad-fatigue refresh, the churn-signal watch.
|
||||
|
||||
This is the operational cousin of `marketing-ideas`. Ideas tell you *what to try once*. Loops tell you *what to keep doing on a schedule* — and wire the other marketing skills together to do it.
|
||||
|
||||
## How to Use This Skill
|
||||
|
||||
**Check for product marketing context first:** if `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions. Use that context and only ask for what's missing.
|
||||
|
||||
Then:
|
||||
1. **Clarify the job.** What outcome should this loop protect or grow? (rankings, ad efficiency, activation, retention, revenue, referrals)
|
||||
2. **Pick a loop** from the catalog in `references/loop-catalog.md` — or adapt the closest one.
|
||||
3. **Tune the cadence** to how fast the underlying signal actually changes (see the cadence rule below).
|
||||
4. **Confirm the human checkpoint.** Decide what the loop does autonomously vs. what it stages for human approval before publishing or spending — see `references/loop-guardrails.md`.
|
||||
5. **Schedule it** (see "Scheduling a loop" below).
|
||||
|
||||
Building more than one loop, or a whole marketing operating system? See `references/loop-orchestration.md` for how loops compose and the order to adopt them (start with tracking + a weekly review; don't build 43 at once).
|
||||
|
||||
## Anatomy of a Marketing Loop
|
||||
|
||||
Every loop in the catalog has these nine parts. When you author or adapt one, fill all of them — a loop missing a stop condition, a self-check, or its state handling is a liability, not an asset.
|
||||
|
||||
| Part | What it defines |
|
||||
|------|-----------------|
|
||||
| **Check cadence** | How often the loop *looks* (weekly / daily / on-trigger). Match it to signal speed. |
|
||||
| **Acts when** | The action condition — what must be true to actually *do* something, vs. just check and skip. Most runs of a good loop are "checked, nothing to do." |
|
||||
| **Purpose** | The one outcome this loop exists to move. |
|
||||
| **Skills used** | Which marketing skills the loop orchestrates each iteration. |
|
||||
| **Loop body** | The ordered steps run each iteration. |
|
||||
| **Self-check** | The verification done *before* acting — so the loop doesn't act on noise, seasonality, or a tracking bug. |
|
||||
| **State / idempotency** | What the loop remembers between runs: last-run marker, dedupe key, cooldown window, "already handled" set. Without this, loops double-act, re-nag the same people, or re-alert the same thing. Non-negotiable for anything scheduled — see `references/loop-state.md` for where state lives and the idempotency patterns. |
|
||||
| **Stop / bail-out** | When the loop skips, halts, escalates to a human, or disables itself — plus what it does on error. Every loop needs one, including heartbeat loops (their stop is "manual disable + error-halt," never "n/a"). |
|
||||
| **Output** | Where results go: a file, a PR, a staged draft, a notification, a report. |
|
||||
|
||||
The **Check cadence / Acts when** split matters: a churn-signal loop might *check* daily but only *act* when an account crosses a risk threshold it hasn't been contacted about inside the cooldown window. Conflating the two produces loops that either miss the window or spam.
|
||||
|
||||
## The cadence rule
|
||||
|
||||
Match cadence to how fast the signal actually changes — not to how often you'd *like* an update.
|
||||
|
||||
| Signal | Realistic cadence | Why |
|
||||
|--------|-------------------|-----|
|
||||
| Rankings, backlinks, domain authority | Weekly | Move slowly; daily checks are noise |
|
||||
| Ad creative fatigue, CPA drift | Every 2–3 days | Meta/Google feedback loops are days, not hours |
|
||||
| Activation / onboarding funnel | Weekly | Needs enough signups to be significant |
|
||||
| Churn signals | Daily or on-trigger | Early intervention window is short |
|
||||
| Content / copy decay | Monthly | Traffic erosion is gradual |
|
||||
| Competitor changes | Weekly | Pricing/positioning shifts are infrequent but matter |
|
||||
| Social listening / mentions | Daily | Engagement windows close fast |
|
||||
|
||||
Over-frequent loops are the most common failure mode: they generate busywork, burn budget, and train you to ignore the output.
|
||||
|
||||
## When NOT to loop
|
||||
|
||||
Not everything should be automated on a cadence. Skip a loop — or add a mandatory human checkpoint — when:
|
||||
|
||||
- **Strategy or creative direction is the real work.** Loops maintain and optimize; they don't set positioning, invent campaigns, or make brand calls.
|
||||
- **The action publishes or spends without review.** Auto-*drafting* an ad, email, or post is fine. Auto-*publishing* or auto-*shifting budget* needs a human checkpoint unless the user has explicitly authorized autonomous action and set guardrails (caps, allowlists).
|
||||
- **The signal is too sparse to be significant.** A weekly conversion-rate loop on 40 visitors/week is measuring noise.
|
||||
- **It's a vanity loop.** If nobody acts on the output, delete the loop. A loop that emails a dashboard nobody reads is worse than nothing.
|
||||
|
||||
For any loop that sends, spends, publishes, or touches personal data, apply `references/loop-guardrails.md` — the two-tier action model (autonomous-safe vs. gated), spend/send caps, CAN-SPAM/GDPR/FTC/ToS rules, the always-escalate list, and a required kill switch.
|
||||
|
||||
## Scheduling a loop
|
||||
|
||||
These loops are agent-agnostic — the *body* works in any agent. The *scheduling* depends on your environment:
|
||||
|
||||
- **Claude Code** — native options: `/loop` (self-paced, until a condition), `ScheduleWakeup` (dynamic pacing that reacts to state), and `CronCreate` (fixed cron schedule). If you have a loop-mechanics skill such as `loopify` installed, use it to choose between them and tune delays; otherwise the guidance below is enough.
|
||||
- **Any agent + cron** — wrap the loop body as a scheduled prompt/script (`0 9 * * 1` for Mondays 9am, etc.).
|
||||
- **Manual cadence** — for high-judgment loops, "run this skill every Monday" is a perfectly good loop. The value is the repeatable *body*, not the automation.
|
||||
|
||||
Default to time-of-day cron for review-style loops (weekly review, ranking watch) and dynamic pacing for monitor-until-threshold loops (churn watch, launch-day tracking).
|
||||
|
||||
## The Catalog
|
||||
|
||||
`references/loop-catalog.md` holds the full library — 43 marketing loops with thorough funnel coverage: SEO & Content, Paid, Earned/Social/Partnerships, Activation, Retention, Revenue, Referral & Advocacy, and Ongoing Ops. Each is a complete, adaptable spec. Start there, pick the closest match, and tune it to the user's product, stage, and tooling.
|
||||
|
||||
## Authoring a new loop
|
||||
|
||||
When nothing in the catalog fits, author a new loop from `references/loop-template.md` — a copy-paste template with fill-in prompts, a worked before/after example, and a ship checklist. Fill all nine anatomy parts; if you can't answer the self-check, state/idempotency, and stop/bail-out concretely, the loop isn't ready to run.
|
||||
|
||||
## Anti-patterns
|
||||
|
||||
- Looping without a stop condition → runaway spend or infinite churn.
|
||||
- Same cadence for every loop → most run too often and get ignored.
|
||||
- No self-check → the loop acts on noise, seasonality, or a tracking bug.
|
||||
- No human checkpoint on spend/publish actions.
|
||||
- Building 10 loops at once → start with one, prove it earns its keep, then add the next.
|
||||
|
||||
## Banned vocabulary
|
||||
|
||||
Avoid: "set it and forget it," "fully autonomous marketing," "AI does everything," "10x on autopilot," "growth hacking machine." Loops are disciplined systems with checkpoints, not magic. Describe them honestly.
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **marketing-ideas** — one-off tactics and inspiration (what to try). Loops operationalize the ones worth repeating.
|
||||
- **ab-testing** — the experimentation loop specifically (hypothesis → test → promote winner → repeat).
|
||||
- **analytics** — most loops read from analytics to decide whether to act.
|
||||
- Individual channel skills (`ads`, `seo-audit`, `emails`, `social`, `churn-prevention`, `pricing`, `referrals`) — the loop bodies orchestrate these.
|
||||
@@ -0,0 +1,101 @@
|
||||
{
|
||||
"skill_name": "marketing-loops",
|
||||
"evals": [
|
||||
{
|
||||
"id": 1,
|
||||
"prompt": "I want to set up a recurring loop that watches our SEO and tells me what to do each week. We're a B2B SaaS with a content-heavy site.",
|
||||
"expected_output": "Should check for product-marketing.md first. Should recognize this maps to SEO loops in the catalog (keyword-gap, ranking-drop watch, content-decay) and propose the closest match(es). Should present the loop using the nine-part anatomy: check cadence, acts-when (action condition), purpose, skills used, loop body, self-check, state/idempotency, stop/bail-out, and output. Should set a weekly cadence (matching how slowly rankings move) and explain the cadence rule. Should include a stop/bail-out and note that most runs may find no action. Should reference the seo-audit skill for execution.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing.md",
|
||||
"Selects appropriate SEO loop(s) from the catalog",
|
||||
"Presents the loop with the nine-part anatomy",
|
||||
"Includes state/idempotency (last-run marker or dedupe)",
|
||||
"Includes an explicit stop/bail-out condition",
|
||||
"Sets a weekly cadence and justifies it via the cadence rule",
|
||||
"References seo-audit or related skills for execution"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 2,
|
||||
"prompt": "I want to automate my marketing so it basically runs itself. Where do I start?",
|
||||
"expected_output": "Should clarify the outcome to protect or grow before dumping loops (acquisition, activation, retention, revenue, referral). Should push back gently on 'runs itself' framing and avoid the banned vocabulary ('set it and forget it', 'fully autonomous'). Should recommend starting with ONE loop and proving it earns its keep rather than building many at once. Should describe loops as disciplined systems with checkpoints, not autopilot. Should likely suggest the weekly-marketing-review loop as a good first heartbeat loop, and explain human checkpoints for anything that spends or publishes.",
|
||||
"assertions": [
|
||||
"Asks about the target outcome / funnel stage before recommending",
|
||||
"Avoids banned autopilot vocabulary",
|
||||
"Recommends starting with one loop, not many",
|
||||
"Frames loops as systems with checkpoints, not magic",
|
||||
"Emphasizes human checkpoints for spend/publish actions",
|
||||
"May suggest the weekly-marketing-review loop as a starting point"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 3,
|
||||
"prompt": "Set up a newsjacking loop that finds trending stories and automatically posts our take to X and pitches journalists.",
|
||||
"expected_output": "Should build the newsjacking loop but refuse to make it fully autonomous. Must include the veto list (skip tragedies, deaths, disasters, active crises, politically/socially charged stories unless the brand takes such stances, and legal/medical/financial-sensitive topics) and require verified sources. Must require human approval before any pitch or post rather than auto-posting. Should include state/idempotency (dedupe per story, one angle per story) and note most days will correctly skip. Should reference the public-relations skill.",
|
||||
"assertions": [
|
||||
"Builds the newsjacking loop with the nine-part anatomy",
|
||||
"Includes an explicit veto list for sensitive story types",
|
||||
"Requires human approval before pitching or posting",
|
||||
"Does not enable fully autonomous posting",
|
||||
"Includes dedupe/state so stories aren't re-pitched",
|
||||
"References the public-relations skill"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 4,
|
||||
"prompt": "How do I actually schedule these loops so they run on their own?",
|
||||
"expected_output": "Should explain that the loop body is agent-agnostic but scheduling depends on the environment. Should cover the options: Claude Code native primitives (/loop, ScheduleWakeup, CronCreate), any-agent + cron (with an example cron expression), and manual cadence for high-judgment loops. Should default to time-of-day cron for review-style loops and dynamic pacing for monitor-until-threshold loops. Should treat a dedicated loop-mechanics skill like loopify as an optional companion, not a hard dependency, and not assume it is installed.",
|
||||
"assertions": [
|
||||
"Explains scheduling is environment-dependent",
|
||||
"Covers Claude Code native options and plain cron",
|
||||
"Includes manual cadence as a valid option",
|
||||
"Gives cron vs dynamic-pacing default guidance",
|
||||
"Treats loopify as optional, not a required dependency"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 5,
|
||||
"prompt": "Can you make me a loop that continuously improves our brand positioning and comes up with our big campaign ideas?",
|
||||
"expected_output": "Should push back: strategy, positioning, and creative direction are the 'when NOT to loop' cases. Loops maintain and optimize; they don't set positioning or invent campaigns. Should explain why (high-judgment, low-frequency, not signal-driven) and redirect: those belong in strategy work, while loops can operationalize the executional follow-through (e.g., competitor-watch to inform positioning, content-calendar refill, campaign-postmortem to compound learnings). Should not fabricate a positioning loop as if it were a good fit.",
|
||||
"assertions": [
|
||||
"Identifies this as a 'when NOT to loop' case",
|
||||
"Explains loops optimize/maintain rather than set strategy or creative",
|
||||
"Redirects strategy/creative to the appropriate non-loop work",
|
||||
"Suggests adjacent operational loops that genuinely fit",
|
||||
"Does not force an ill-fitting positioning/campaign-ideation loop"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 6,
|
||||
"prompt": "We keep losing customers to failed payments and expired cards. Set up something to recover that revenue automatically.",
|
||||
"expected_output": "Should select the failed-payment/dunning loop. Should trigger on payment failure or upcoming card expiration, run a retry schedule with escalating update-card messaging, and include state (track dunning stage per account, stop on recovery). Must include a stop/bail-out so it doesn't loop forever (escalate/deactivate after final retry) and a self-check to distinguish involuntary failures from intentional cancellations (don't dun someone who chose to leave). Should reference revops and emails skills. May note this is often the highest-ROI retention loop.",
|
||||
"assertions": [
|
||||
"Selects the failed-payment/dunning loop",
|
||||
"Triggers on failed payment or card expiration",
|
||||
"Includes a retry schedule with dunning stage state",
|
||||
"Has a stop condition so it does not loop forever",
|
||||
"Self-check separates involuntary failures from intentional cancels",
|
||||
"References revops and/or emails skills"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 7,
|
||||
"prompt": "I want a loop that keeps our A/B testing program running — generating hypotheses, running tests, and analyzing results every week.",
|
||||
"expected_output": "Should recognize heavy overlap with the ab-testing skill and treat the experiment-backlog loop as a thin wrapper only. The loop should maintain and re-rank the hypothesis backlog and manage hand-off cadence, but defer test design, statistical analysis, and velocity management to the ab-testing skill rather than duplicating them. Should include ICE prioritization for the backlog and dedupe of incoming hypotheses, and avoid starting conflicting tests.",
|
||||
"assertions": [
|
||||
"Recognizes overlap with the ab-testing skill",
|
||||
"Keeps the loop as a thin wrapper that defers to ab-testing",
|
||||
"Does not duplicate test design or statistical analysis in the loop",
|
||||
"Includes backlog prioritization (ICE) and hypothesis dedupe",
|
||||
"References the ab-testing skill as the owner of execution"
|
||||
],
|
||||
"files": []
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,672 @@
|
||||
# Marketing Loop Catalog
|
||||
|
||||
A library of repeatable marketing loops with thorough coverage across the funnel. Each is a complete, adaptable spec. Pick the closest match, then tune the cadence, thresholds, state handling, and human checkpoints to the user's product, stage, and tooling.
|
||||
|
||||
Every loop lists nine parts: **Check cadence · Acts when · Purpose · Skills used · Loop body · Self-check · State / idempotency · Stop / bail-out · Output**. See `SKILL.md` for the anatomy, the cadence rule, and when not to loop.
|
||||
|
||||
Two rules that apply to every entry:
|
||||
- **Most runs should do nothing.** A healthy loop checks, finds nothing worth acting on, logs "no action," and exits. Loops that act every run are usually acting on noise.
|
||||
- **State prevents harm.** Every loop tracks what it already did (last-run marker, dedupe key, cooldown) so it never double-acts, re-nags the same person, or re-alerts the same issue.
|
||||
|
||||
Loops are grouped by function. Naming follows the "The X loop" convention.
|
||||
|
||||
---
|
||||
|
||||
## SEO & Content
|
||||
|
||||
### The keyword-gap loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A striking-distance keyword (positions 5–20) or a rising query has no adequate page.
|
||||
- **Purpose**: Surface new ranking opportunities before competitors take them.
|
||||
- **Skills used**: `seo-audit`, `programmatic-seo`, `content-strategy`
|
||||
- **Loop body**:
|
||||
1. Pull ranking + impression data (Search Console / rank tracker).
|
||||
2. Diff vs. last run: new striking-distance keywords, rising queries with no matching page.
|
||||
3. Classify each gap: quick on-page win / net-new page / programmatic template candidate.
|
||||
4. Draft briefs for the top 3.
|
||||
- **Self-check**: Movement real vs. seasonal? Compare to the same period last month, not just last week.
|
||||
- **State / idempotency**: Store the set of gaps already briefed; don't re-brief an open one.
|
||||
- **Stop / bail-out**: No gap clears a minimum impression threshold → log "no action." Halt on data-source outage rather than acting on partial data.
|
||||
- **Output**: Up to 3 content briefs staged for review + a one-line movement summary.
|
||||
|
||||
### The ranking-drop watch loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A priority keyword or page drops more than N positions vs. baseline.
|
||||
- **Purpose**: Catch and diagnose SEO regressions before they compound.
|
||||
- **Skills used**: `seo-audit`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Track positions for priority keywords/pages.
|
||||
2. Flag material drops; diff what changed (content, links, SERP layout, algo-update timing).
|
||||
3. Diagnose likely cause + propose a fix.
|
||||
- **Self-check**: Rule out a SERP-feature change or one-off volatility before declaring a real loss.
|
||||
- **State / idempotency**: Remember which drops are already open as issues; update rather than re-file.
|
||||
- **Stop / bail-out**: No material drop → log "stable." Escalate suspected algo hits to a human rather than mass-editing.
|
||||
- **Output**: A regression report with a recommended fix.
|
||||
|
||||
### The content-decay loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: A page's traffic/rankings declined materially over the trailing 90 days.
|
||||
- **Purpose**: Refresh decaying content before it slides out of rankings.
|
||||
- **Skills used**: `copy-editing`, `seo-audit`, `content-strategy`
|
||||
- **Loop body**:
|
||||
1. Find pages with declining trailing-90-day traffic/rankings.
|
||||
2. Pick the highest-value decayers.
|
||||
3. Draft a refresh plan (update stats, expand thin sections, fix intent match, re-link).
|
||||
- **Self-check**: Decay from the page itself, or from a SERP/seasonality shift? Refresh only what a refresh can fix.
|
||||
- **State / idempotency**: Track last-refresh date per page; don't re-queue a page refreshed within the cooldown.
|
||||
- **Stop / bail-out**: No meaningful decayers → skip.
|
||||
- **Output**: A prioritized refresh list with per-page plans.
|
||||
|
||||
### The internal-linking loop
|
||||
- **Check cadence**: On new/updated content, or weekly
|
||||
- **Acts when**: A published page has fewer relevant internal links (in or out) than it should.
|
||||
- **Purpose**: Distribute link equity and help new content get discovered and rank.
|
||||
- **Skills used**: `seo-audit`, `site-architecture`, `content-strategy`
|
||||
- **Loop body**:
|
||||
1. Identify recently published/updated pages.
|
||||
2. Find relevant existing pages that should link to them (and vice versa).
|
||||
3. Draft the specific link insertions with anchor text.
|
||||
- **Self-check**: Is each link contextually relevant, or link-stuffing? Skip forced links.
|
||||
- **State / idempotency**: Track which page pairs are already linked; never suggest a duplicate.
|
||||
- **Stop / bail-out**: No relevant link targets → skip. Stage edits for review; don't mass-edit live pages autonomously.
|
||||
- **Output**: A list of specific internal-link edits.
|
||||
|
||||
### The programmatic-SEO quality loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: Template pages show indexation gaps, thin content, duplication, or cannibalization.
|
||||
- **Purpose**: Keep large templated page sets healthy so they don't drag the whole domain.
|
||||
- **Skills used**: `programmatic-seo`, `seo-audit`
|
||||
- **Loop body**:
|
||||
1. Sample the template page set; check indexation, word/data uniqueness, and query overlap.
|
||||
2. Flag thin, duplicate, cannibalizing, or deindexed pages.
|
||||
3. Recommend fix, consolidate, noindex, or prune.
|
||||
- **Self-check**: Is low traffic a quality problem or just low demand? Don't prune pages that serve real long-tail intent.
|
||||
- **State / idempotency**: Track pages already flagged/actioned; re-check only on the next cycle.
|
||||
- **Stop / bail-out**: Set healthy → log and skip. Escalate mass-noindex/prune decisions to a human.
|
||||
- **Output**: A quality report with per-bucket actions.
|
||||
|
||||
### The content-repurposing loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A long-form asset (post/video/podcast) hasn't been repurposed yet.
|
||||
- **Purpose**: Turn every long-form asset into a week of channel-native content.
|
||||
- **Skills used**: `social`, `content-strategy`, `copywriting`
|
||||
- **Loop body**:
|
||||
1. Find the newest un-repurposed asset.
|
||||
2. Extract the 3–5 strongest ideas.
|
||||
3. Draft channel-native versions (LinkedIn post, X thread, short-form script).
|
||||
4. Stage in the scheduling queue.
|
||||
- **Self-check**: Does each piece stand alone, or read like a link-dump? Rewrite anything that only works with the original open.
|
||||
- **State / idempotency**: Mark assets as repurposed; never re-process one.
|
||||
- **Stop / bail-out**: Nothing new published → skip.
|
||||
- **Output**: Drafts in the social queue for approval.
|
||||
|
||||
### The content-calendar refill loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: The editorial pipeline has fewer than N weeks of planned content queued.
|
||||
- **Purpose**: Keep the content pipeline from running dry.
|
||||
- **Skills used**: `content-strategy`, `marketing-ideas`, `seo-audit`
|
||||
- **Loop body**:
|
||||
1. Count planned/drafted pieces remaining in the calendar.
|
||||
2. If below the buffer, generate new topic ideas from the keyword-gap output, customer questions, and pillar plan.
|
||||
3. Prioritize and slot them.
|
||||
- **Self-check**: Do new topics map to real search demand or audience questions, not just "content for content's sake"?
|
||||
- **State / idempotency**: Dedupe proposed topics against the existing calendar and published archive.
|
||||
- **Stop / bail-out**: Pipeline above buffer → skip.
|
||||
- **Output**: New prioritized topics added to the calendar.
|
||||
|
||||
---
|
||||
|
||||
## Paid
|
||||
|
||||
### The ad-fatigue loop
|
||||
- **Check cadence**: Every 2–3 days
|
||||
- **Acts when**: An ad shows rising frequency + declining CTR/CVR past a real significance bar.
|
||||
- **Purpose**: Refresh creative before CPA drifts up as ads fatigue.
|
||||
- **Skills used**: `ads`, `ad-creative`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Pull per-ad metrics: CTR, frequency, CPA, spend, trend vs. baseline.
|
||||
2. Flag fatiguing ads and clear winners.
|
||||
3. Generate 3–5 fresh variants off the winning angle.
|
||||
4. Stage variants; recommend budget shift fatigued → winning.
|
||||
- **Self-check**: Enough spend, impressions, and conversions to read CPA past the attribution window, and the ad is out of the learning phase. Rising frequency alone with thin conversion data is not fatigue evidence — wait.
|
||||
- **State / idempotency**: Track per-ad last-refresh date; don't regenerate variants for an ad refreshed within the cooldown.
|
||||
- **Stop / bail-out**: Never auto-shift budget or publish without a human checkpoint unless spend caps + an allowlist are explicitly authorized. Halt if daily spend exceeds its cap.
|
||||
- **Output**: Staged creative drafts + a recommended budget move.
|
||||
|
||||
### The daily-creative-drop loop
|
||||
- **Check cadence**: Daily (early morning, so the batch is ready when the media buyer sits down)
|
||||
- **Acts when**: The grounded inputs corpus exists and the required inputs are populated — `inputs/winning-ads/` and `inputs/reviews/` (required; `inputs/comments/` and `brand/` strongly recommended, matching ad-creative's grounding rules). If a required input is empty, the loop asks for inputs instead of generating.
|
||||
- **Purpose**: Keep creative volume ahead of fatigue — a standing batch of fresh static concepts to test, so scaling never stalls waiting on production.
|
||||
- **Skills used**: `ad-creative` (Mode 3 + static ad template library), `customer-research`
|
||||
- **Loop body**:
|
||||
1. Read the inputs corpus: `inputs/winning-ads/`, `inputs/reviews/`, `inputs/comments/`, and `brand/`.
|
||||
2. Generate the batch (e.g., 50 concepts) cycling all 15 static templates, 3-4 variations each, every concept grounded in a cited source.
|
||||
3. Generate images if an image tool is configured; otherwise deliver concepts + image prompts.
|
||||
4. Save to `outputs/YYYY-MM-DD/` with an `INDEX.md` (template type + grounding per concept).
|
||||
- **Self-check**: Are concepts actually grounded (spot-check citations against sources)? Is template coverage spread across the library, not clustered on 2-3? Does copy match the brand voice doc rather than generic DR voice?
|
||||
- **State / idempotency**: One batch per day — skip if today's output folder already exists. Track angle/headline hashes across recent batches to avoid regenerating near-duplicates of concepts already delivered.
|
||||
- **Stop / bail-out**: Missing or empty required inputs → stop and request them; never generate ungrounded. Human picks the 5-10 to upload — this loop stages creative and **never publishes to the ad account**. If batches go unreviewed for a week, pause and ask whether to continue (unpicked batches are a vanity loop).
|
||||
- **Output**: A dated folder of grounded static ad concepts + index, ready for human selection.
|
||||
- **Input freshness (companion cadence)**: Weekly, refresh `inputs/winning-ads/` with anything that scaled and prune stale examples; monthly, refresh `inputs/reviews/` and `inputs/comments/` and re-check the voice doc. Stale inputs are this loop's failure mode — output quality tracks input freshness, not run count.
|
||||
|
||||
### The paid-search query-mining loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: Search-term reports reveal wasted spend or new intent.
|
||||
- **Purpose**: Continuously refine keywords, negatives, and landing-page mapping.
|
||||
- **Skills used**: `ads`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Pull the search-terms report.
|
||||
2. Identify irrelevant terms (→ negatives), high-performing terms (→ new exact-match), and terms whose landing page is a poor match.
|
||||
3. Stage keyword/negative changes and landing-page notes.
|
||||
- **Self-check**: Enough clicks/conversions per term to justify a change? Don't negate on a single click.
|
||||
- **State / idempotency**: Track already-added negatives/keywords; never re-add.
|
||||
- **Stop / bail-out**: No terms clear thresholds → skip. Stage changes for review before pushing to the account.
|
||||
- **Output**: A staged list of negatives, new keywords, and LP mismatches.
|
||||
|
||||
### The retargeting-hygiene loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: Audiences are stale, too small, over-frequent, or missing exclusions.
|
||||
- **Purpose**: Keep retargeting efficient and non-annoying.
|
||||
- **Skills used**: `ads`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Review retargeting audiences: size, recency, frequency, exclusions, creative sequencing.
|
||||
2. Flag issues (converters not excluded, audiences too small to serve, frequency too high).
|
||||
3. Recommend fixes.
|
||||
- **Self-check**: Is the audience actually underperforming, or just small-but-valuable? Don't kill high-intent segments for size.
|
||||
- **State / idempotency**: Track which audiences were already fixed this cycle.
|
||||
- **Stop / bail-out**: All healthy → skip. Human-approve audience deletions.
|
||||
- **Output**: A hygiene report with recommended audience changes.
|
||||
|
||||
### The landing-page regression loop
|
||||
- **Check cadence**: Weekly (or on deploy)
|
||||
- **Acts when**: A top acquisition page regresses on conversion, speed, tracking, or form function.
|
||||
- **Purpose**: Catch silent breakage on the pages that receive paid/organic traffic.
|
||||
- **Skills used**: `cro`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Monitor top acquisition pages: conversion rate, load speed, form submits, tracking fires.
|
||||
2. Flag regressions vs. baseline; correlate with recent deploys/changes.
|
||||
3. Diagnose and propose a fix.
|
||||
- **Self-check**: Rule out tracking breakage vs. a real conversion drop before raising an alarm — and vice versa.
|
||||
- **State / idempotency**: Track open regressions; update rather than re-file.
|
||||
- **Stop / bail-out**: No regression → log "stable." Escalate a live-revenue-page break immediately, don't wait for the next run.
|
||||
- **Output**: A regression alert with cause + fix.
|
||||
|
||||
---
|
||||
|
||||
## Earned, Social & Partnerships
|
||||
|
||||
### The newsjacking loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A trending story matches the brand's space, clears newsworthiness + fit, **and** passes the veto list.
|
||||
- **Purpose**: Ride relevant news with a timely angle before the window closes.
|
||||
- **Skills used**: `public-relations`, `social`
|
||||
- **Loop body**:
|
||||
1. Scan news/HN/Reddit/X for stories intersecting the product's space.
|
||||
2. Score newsworthiness + fit + reach.
|
||||
3. Run the veto list. For a surviving top story, draft an angle (post, pitch, or commentary).
|
||||
- **Self-check**: Is the angle genuinely additive, or forced? Kill forced takes — they cost credibility.
|
||||
- **Veto list (skip immediately)**: tragedies, deaths, disasters, active crises; politically or socially charged stories unless the brand explicitly takes such stances; legal/medical/financial-sensitive topics; anything sourced from an unverified/single unreliable source.
|
||||
- **State / idempotency**: Dedupe on story ID; one angle per story; never re-pitch a covered story.
|
||||
- **Stop / bail-out**: Any veto trip → skip. Always require human approval before pitching/posting. Most days will skip — that's correct.
|
||||
- **Output**: A staged post/pitch for human approval, or nothing.
|
||||
|
||||
### The social-listening loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A thread/mention clears the ICP-fit + intent + reach score.
|
||||
- **Purpose**: Surface the highest-value conversations to engage in, instead of scrolling feeds.
|
||||
- **Skills used**: `social` (see its `references/listening.md`), `community-marketing`
|
||||
- **Loop body**:
|
||||
1. Pull mentions and relevant threads across configured sources.
|
||||
2. Score by ICP fit, intent, reach, and comment opportunity.
|
||||
3. Draft comments/replies for the top handful.
|
||||
- **Self-check**: Would a human recognize each reply as genuinely useful, not promotional?
|
||||
- **State / idempotency**: Track already-engaged threads; never double-reply. Respect a per-account interaction cooldown.
|
||||
- **Stop / bail-out**: Nothing clears the threshold → skip. Stage replies for human post (don't auto-post — bot-detection + brand risk).
|
||||
- **Output**: A short list of threads with drafted, on-brand replies.
|
||||
|
||||
### The community-engagement loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A target community (subreddit/Slack/Discord/forum) has a relevant thread where a helpful, non-promotional reply fits.
|
||||
- **Purpose**: Build durable presence and trust in the communities where the ICP lives.
|
||||
- **Skills used**: `community-marketing`, `social`
|
||||
- **Loop body**:
|
||||
1. Scan configured communities for relevant threads/questions.
|
||||
2. Score for genuine help opportunity (not just keyword match).
|
||||
3. Draft value-first replies; note any that warrant a longer resource.
|
||||
- **Self-check**: Does the reply lead with help and respect community norms? Self-promo ratio stays low.
|
||||
- **State / idempotency**: Track engaged threads + per-community posting cadence to avoid over-posting.
|
||||
- **Stop / bail-out**: No genuine-help opportunity → skip. Stage for human review where communities are strict about vendors.
|
||||
- **Output**: Drafted community replies + resource ideas.
|
||||
|
||||
### The competitor-watch loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A competitor makes a substantive pricing, positioning, product, or messaging change.
|
||||
- **Purpose**: Catch competitor moves early enough to respond.
|
||||
- **Skills used**: `competitor-profiling`, `competitors`, `product-marketing`
|
||||
- **Loop body**:
|
||||
1. Fetch competitor pricing pages, homepages, changelogs, recent posts.
|
||||
2. Diff vs. last snapshot.
|
||||
3. Summarize meaningful changes; flag anything needing a response (comparison-page update, counter-messaging).
|
||||
- **Self-check**: Substantive vs. cosmetic? Don't raise a copy tweak as a strategic shift.
|
||||
- **State / idempotency**: Store per-competitor snapshots; diff against the last, and don't re-flag a known change.
|
||||
- **Stop / bail-out**: No meaningful diffs → log "no change."
|
||||
- **Output**: A change digest + recommended responses.
|
||||
|
||||
### The backlink-prospecting loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: New relevant link/guest-post/mention targets appear (or the pipeline is thin).
|
||||
- **Purpose**: Keep a steady flow of link-building and earned-mention opportunities.
|
||||
- **Skills used**: `public-relations`, `seo-audit`
|
||||
- **Loop body**:
|
||||
1. Find new prospects: sites linking to competitors, relevant roundups, unlinked brand mentions, resource pages.
|
||||
2. Qualify by relevance + authority.
|
||||
3. Draft outreach angles for the top targets.
|
||||
- **Self-check**: Is the target genuinely relevant, or a low-quality link that could hurt? Skip spammy sites.
|
||||
- **State / idempotency**: Track already-contacted targets + outcomes; respect a follow-up cadence, don't re-pitch cold.
|
||||
- **Stop / bail-out**: No qualified new targets → skip. Human-approve outreach sends.
|
||||
- **Output**: A qualified prospect list with drafted outreach.
|
||||
|
||||
### The directory-submission loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: A relevant new directory/launch platform/marketplace exists that the product isn't listed on.
|
||||
- **Purpose**: Steadily expand distribution and referral/SEO footprint via directories.
|
||||
- **Skills used**: `directory-submissions`
|
||||
- **Loop body**:
|
||||
1. Check for new/relevant directories, launch sites, and marketplaces.
|
||||
2. Qualify by relevance, authority, and audience fit.
|
||||
3. Prepare listing copy/assets for the top ones.
|
||||
- **Self-check**: Real audience/SEO value, or a link farm? Skip low-quality directories.
|
||||
- **State / idempotency**: Maintain a submitted-directories list; never resubmit.
|
||||
- **Stop / bail-out**: No worthwhile new directories → skip.
|
||||
- **Output**: Prepared listings staged for submission.
|
||||
|
||||
### The partner-pipeline loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: A viable co-marketing, integration, affiliate, or newsletter-swap opportunity surfaces (or the pipeline is thin).
|
||||
- **Purpose**: Keep a fresh pipeline of partnership and co-marketing opportunities.
|
||||
- **Skills used**: `co-marketing`, `referrals`
|
||||
- **Loop body**:
|
||||
1. Scan for potential partners (complementary tools, aligned audiences, active newsletters, integration targets).
|
||||
2. Qualify by audience overlap + reach + fit.
|
||||
3. Draft partnership/swap outreach for the top prospects.
|
||||
- **Self-check**: Real audience overlap and mutual value, or a one-sided ask? Skip mismatches.
|
||||
- **State / idempotency**: Track contacted partners + status; respect follow-up cadence.
|
||||
- **Stop / bail-out**: No qualified opportunities → skip. Human-approve outreach.
|
||||
- **Output**: A qualified partner list with drafted outreach.
|
||||
|
||||
---
|
||||
|
||||
## Activation
|
||||
|
||||
### The onboarding drop-off loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: An onboarding step's drop exceeds benchmark or regresses vs. last period.
|
||||
- **Purpose**: Find and fix the biggest leak between signup and first value.
|
||||
- **Skills used**: `onboarding`, `analytics`, `cro`
|
||||
- **Loop body**:
|
||||
1. Pull the activation funnel step-by-step (signup → key action → aha).
|
||||
2. Identify the worst-dropping step vs. benchmark and last period.
|
||||
3. Diagnose likely cause; propose one focused fix + how to measure it.
|
||||
- **Self-check**: Enough new users through the funnel for step rates to be significant?
|
||||
- **State / idempotency**: Track which fixes were already proposed/shipped; measure their effect before re-touching.
|
||||
- **Stop / bail-out**: Sample too small → widen window or skip.
|
||||
- **Output**: One prioritized activation fix with a measurement plan.
|
||||
|
||||
### The signup-funnel-leak loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A signup/checkout step regresses vs. baseline.
|
||||
- **Purpose**: Keep the signup/checkout path converting as the site changes.
|
||||
- **Skills used**: `signup`, `cro`, `analytics`, `ab-testing`
|
||||
- **Loop body**:
|
||||
1. Pull conversion by step across the signup/checkout flow.
|
||||
2. Compare to baseline; flag regressions (a deploy or copy change may have hurt it).
|
||||
3. Draft a hypothesis + test for the worst step (hand test execution to `ab-testing`).
|
||||
- **Self-check**: Rule out tracking breakage before declaring a real drop.
|
||||
- **State / idempotency**: Track open regressions + running tests; don't start a conflicting test.
|
||||
- **Stop / bail-out**: No regression and no test-worthy idea → skip.
|
||||
- **Output**: A prioritized experiment brief for `ab-testing`.
|
||||
|
||||
### The lead-capture-asset loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: A lead magnet, free tool, or opt-in underperforms on capture rate.
|
||||
- **Purpose**: Keep top-of-funnel capture assets (lead magnets + free tools) converting visitors to leads.
|
||||
- **Skills used**: `lead-magnets`, `free-tools`, `cro`, `popups`
|
||||
- **Loop body**:
|
||||
1. Pull view → capture conversion for each lead magnet, free tool, and opt-in.
|
||||
2. Flag underperformers vs. benchmark; diagnose (offer, placement, form friction, targeting).
|
||||
3. Propose a fix or refresh (new angle, better placement, reduced friction).
|
||||
- **Self-check**: Enough traffic per asset for the capture rate to be meaningful?
|
||||
- **State / idempotency**: Track last-optimized date per asset; cooldown before re-touching.
|
||||
- **Stop / bail-out**: All assets healthy → skip.
|
||||
- **Output**: A prioritized fix per underperforming asset.
|
||||
|
||||
### The feature-adoption loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A sticky/valuable feature is underused by a segment that would benefit.
|
||||
- **Purpose**: Drive adoption of the features that correlate with retention.
|
||||
- **Skills used**: `onboarding`, `emails`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Identify high-retention-correlated features and the segments not using them.
|
||||
2. Pick the highest-leverage feature × segment.
|
||||
3. Draft an in-app nudge or email to drive adoption.
|
||||
- **Self-check**: Is the feature genuinely valuable to that segment, or would the nudge be noise? Don't push features people rationally skip.
|
||||
- **State / idempotency**: Track who's already been nudged for which feature; enforce a cooldown; suppress adopters.
|
||||
- **Stop / bail-out**: No clear feature × segment gap → skip.
|
||||
- **Output**: A staged adoption nudge.
|
||||
|
||||
---
|
||||
|
||||
## Retention
|
||||
|
||||
### The churn-signal loop
|
||||
- **Check cadence**: Daily (or on-trigger)
|
||||
- **Acts when**: An account newly crosses a churn-risk threshold and isn't already in an intervention.
|
||||
- **Purpose**: Intervene inside the short window before an at-risk account leaves.
|
||||
- **Skills used**: `churn-prevention`, `analytics`, `emails`
|
||||
- **Loop body**:
|
||||
1. Score accounts on churn-risk signals (usage decline, seat drop, dunning, support escalations).
|
||||
2. Segment newly at-risk accounts.
|
||||
3. Match each to the right intervention (re-engagement email, CS outreach, offer); stage it.
|
||||
- **Self-check**: Is the "drop" a real trend or a weekend/holiday dip? Compare to the account's own baseline.
|
||||
- **State / idempotency**: Never re-trigger on an account already in an active intervention; enforce a cooldown between attempts.
|
||||
- **Stop / bail-out**: No newly at-risk accounts → skip. Escalate high-value accounts to a human rather than auto-emailing.
|
||||
- **Output**: A prioritized at-risk list with staged interventions.
|
||||
|
||||
### The lifecycle-email-refresh loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: A sequence email underperforms on real engagement or contains stale content.
|
||||
- **Purpose**: Keep automated sequences performing as the product and audience evolve.
|
||||
- **Skills used**: `emails`, `analytics`, `copy-editing`
|
||||
- **Loop body**:
|
||||
1. Pull per-email performance — clicks, conversions, replies, unsubscribes, spam complaints, bounces (**not opens** — open tracking is unreliable post-privacy-changes).
|
||||
2. Flag weak performers and stale references (old features, dates, pricing).
|
||||
3. Draft rewrites or subject-line tests for the bottom performers.
|
||||
- **Self-check**: Enough sends per email for rates to be meaningful?
|
||||
- **State / idempotency**: Track last-revised date per email; cooldown before re-testing.
|
||||
- **Stop / bail-out**: All sequences healthy → skip. **Pause and escalate any sequence with rising complaint/bounce rates — that's a deliverability emergency, not a copy tweak.**
|
||||
- **Output**: Staged email rewrites + subject-line tests.
|
||||
|
||||
### The re-engagement loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A user newly crosses the inactivity threshold.
|
||||
- **Purpose**: Win back dormant users before they're gone for good.
|
||||
- **Skills used**: `emails`, `sms`, `offers`
|
||||
- **Loop body**:
|
||||
1. Identify users newly crossing the inactivity threshold.
|
||||
2. Pick the win-back angle (new feature, offer, "we miss you," sunset warning).
|
||||
3. Draft the message; set suppression so they aren't re-hit next week.
|
||||
- **Self-check**: Truly dormant, or just low-frequency-by-design users? Don't nag healthy accounts.
|
||||
- **State / idempotency**: Track win-back attempts per user; suppress after each send for the cooldown.
|
||||
- **Stop / bail-out**: After N unsuccessful attempts, move to sunset — not another email.
|
||||
- **Output**: A staged win-back message + updated suppression list.
|
||||
|
||||
### The email-deliverability loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: Bounce, complaint, or unsubscribe rates rise, or list-hygiene decays.
|
||||
- **Purpose**: Protect sender reputation and inbox placement.
|
||||
- **Skills used**: `emails`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Monitor bounces, spam complaints, unsubscribes, domain/DKIM/SPF/DMARC health, and inbox-placement signals.
|
||||
2. Flag rising problem rates or authentication issues.
|
||||
3. Recommend actions: suppress hard bounces, sunset chronically unengaged, fix auth, throttle.
|
||||
- **Self-check**: Is a spike a one-off send or a trend? Correlate with recent campaigns.
|
||||
- **State / idempotency**: Track already-suppressed addresses + last hygiene sweep date.
|
||||
- **Stop / bail-out**: All metrics healthy → log and skip. **Escalate a complaint-rate spike immediately** — reputation damage compounds fast.
|
||||
- **Output**: A deliverability report + a suppression/hygiene action list.
|
||||
|
||||
### The voice-of-customer loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: New feedback (NPS, surveys, support tickets, reviews, calls) has arrived.
|
||||
- **Purpose**: Route feedback to the right action **and** mine it for marketing inputs.
|
||||
- **Skills used**: `customer-research`, `churn-prevention`, `referrals`, `copywriting`
|
||||
- **Loop body**:
|
||||
1. Collect new feedback across sources.
|
||||
2. Route: detractors/at-risk → save motion (`churn-prevention`); promoters → referral/review ask (`referrals`); recurring pain/desire → experiment + copy inputs.
|
||||
3. Extract verbatim customer language for copy, FAQ, and objection-handling.
|
||||
- **Self-check**: Is a theme a real pattern or one loud voice? Require a minimum count before acting on it.
|
||||
- **State / idempotency**: Track processed feedback IDs; never double-route the same item.
|
||||
- **Stop / bail-out**: No new feedback → skip. Escalate sensitive/legal complaints to a human.
|
||||
- **Output**: Routed actions + a language/insight digest for marketing.
|
||||
|
||||
---
|
||||
|
||||
## Revenue
|
||||
|
||||
### The trial-conversion loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A trial user reaches a conversion-relevant moment (mid-trial, near-expiry, activated-but-not-paid).
|
||||
- **Purpose**: Move more trials to paid with well-timed nudges.
|
||||
- **Skills used**: `emails`, `paywalls`, `analytics`, `offers`
|
||||
- **Loop body**:
|
||||
1. Segment active trials by stage and activation level.
|
||||
2. Match each to the right nudge (value recap, use-case tip, near-expiry push, offer).
|
||||
3. Stage the nudge.
|
||||
- **Self-check**: Is the user activated enough for a paid push to land, or do they need more value first?
|
||||
- **State / idempotency**: Track nudges sent per trial; enforce cadence; suppress converters.
|
||||
- **Stop / bail-out**: No trials at an actionable stage → skip. Don't over-message a single trial.
|
||||
- **Output**: Staged, stage-appropriate trial nudges.
|
||||
|
||||
### The PQL / upgrade-intent loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A free/trial user shows product-qualified buying intent (usage limits, key-feature use, team invites).
|
||||
- **Purpose**: Catch high-intent users and stage upgrade outreach at the right moment.
|
||||
- **Skills used**: `analytics`, `sales-enablement`, `revops`
|
||||
- **Loop body**:
|
||||
1. Score free/trial users on PQL signals.
|
||||
2. Surface newly qualified users.
|
||||
3. Stage the right motion (in-app upgrade prompt, sales-assist for high-value, targeted email).
|
||||
- **Self-check**: Is the signal genuine buying intent or incidental usage? Calibrate the threshold to avoid false positives.
|
||||
- **State / idempotency**: Track already-actioned PQLs; don't re-route within the cooldown.
|
||||
- **Stop / bail-out**: No newly qualified users → skip. Route high-value accounts to a human, don't auto-close.
|
||||
- **Output**: A prioritized PQL list with staged motions.
|
||||
|
||||
### The pricing-page-experiment loop
|
||||
- **Check cadence**: Monthly (tests run longer)
|
||||
- **Acts when**: No test is running on the page and there's a worthwhile hypothesis — or a running test has concluded.
|
||||
- **Purpose**: Improve pricing-page conversion **and revenue quality**, continuously.
|
||||
- **Skills used**: `pricing`, `ab-testing`, `cro`
|
||||
- **Loop body**:
|
||||
1. Review pricing-page conversion, plan mix, and revenue-per-visitor.
|
||||
2. Generate one pricing/packaging/copy hypothesis, or read a concluded test.
|
||||
3. Hand design/analysis to `ab-testing`; promote a clean winner.
|
||||
- **Self-check**: Judge winners on **revenue per visitor, plan mix, refunds, downgrades, churn, and support load — not conversion rate alone.** Is the running test statistically done before you call it?
|
||||
- **State / idempotency**: Track the running test + concluded-test log; never start a conflicting test on the same page.
|
||||
- **Stop / bail-out**: A test is in flight → hold. **Do not promote a variant that lifts conversion but lowers revenue-per-visitor or raises refunds/churn.**
|
||||
- **Output**: A test result + next hypothesis.
|
||||
|
||||
### The paywall-optimization loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: No paywall test is running and there's a hypothesis — or one has concluded.
|
||||
- **Purpose**: Improve in-app upgrade conversion without degrading revenue quality.
|
||||
- **Skills used**: `paywalls`, `ab-testing`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Pull paywall view → upgrade conversion and bounce points.
|
||||
2. Form one hypothesis (trigger timing, framing, plan anchor), or read a concluded test.
|
||||
3. Hand execution to `ab-testing`.
|
||||
- **Self-check**: Segment by plan/cohort — an aggregate number can hide a segment that's tanking. Watch refunds/downgrades alongside conversion.
|
||||
- **State / idempotency**: Track running/concluded tests; no conflicting tests.
|
||||
- **Stop / bail-out**: Test in flight → hold. Don't promote a conversion win that raises refunds or churn.
|
||||
- **Output**: A test result + next hypothesis.
|
||||
|
||||
### The expansion / upsell loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: An existing paid account hits an expansion signal (usage near limits, added seats, new use case).
|
||||
- **Purpose**: Grow revenue from existing customers via well-timed upsell/cross-sell.
|
||||
- **Skills used**: `revops`, `sales-enablement`, `emails`
|
||||
- **Loop body**:
|
||||
1. Score paid accounts on expansion signals.
|
||||
2. Surface newly expansion-ready accounts.
|
||||
3. Stage the right motion (usage-based upgrade prompt, CSM outreach, cross-sell offer).
|
||||
- **Self-check**: Is the account healthy enough that an upsell won't sour the relationship? Don't upsell an at-risk account — that's a churn loop's job.
|
||||
- **State / idempotency**: Track upsell touches per account; enforce cadence.
|
||||
- **Stop / bail-out**: No expansion-ready accounts → skip. Route strategic accounts to a human.
|
||||
- **Output**: A prioritized expansion list with staged motions.
|
||||
|
||||
### The failed-payment / dunning loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A payment fails or a card is about to expire.
|
||||
- **Purpose**: Recover involuntary churn — often the highest-ROI retention work.
|
||||
- **Skills used**: `revops`, `emails`
|
||||
- **Loop body**:
|
||||
1. Detect failed payments and upcoming card expirations.
|
||||
2. Trigger the dunning sequence (retry schedule + escalating update-card messaging).
|
||||
3. Route persistent failures to a human/CS.
|
||||
- **Self-check**: Is the failure involuntary (card issue) vs. an intentional cancel? Don't dun someone who chose to leave.
|
||||
- **State / idempotency**: Track dunning stage per account; follow the retry schedule; stop on recovery.
|
||||
- **Stop / bail-out**: After the final retry, escalate/deactivate per policy — don't loop forever.
|
||||
- **Output**: An active dunning queue + recovery status.
|
||||
|
||||
---
|
||||
|
||||
## Referral & Advocacy
|
||||
|
||||
### The referral-nudge loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: A user hits a "happy moment" (milestone, positive NPS) and hasn't been asked recently.
|
||||
- **Purpose**: Ask for referrals when users are most delighted.
|
||||
- **Skills used**: `referrals`, `emails`
|
||||
- **Loop body**:
|
||||
1. Identify users who just hit a happy moment and aren't in the ask-cooldown.
|
||||
2. Match to the right ask (share link, incentive, review request).
|
||||
3. Stage the ask.
|
||||
- **Self-check**: Genuinely a happy moment, or just any event? A bad-timing ask erodes goodwill.
|
||||
- **State / idempotency**: Enforce a cooldown — never ask the same user twice in the window.
|
||||
- **Stop / bail-out**: No one at a happy moment → skip.
|
||||
- **Output**: A staged, well-timed referral ask.
|
||||
|
||||
### The review-and-UGC-harvest loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: New reviews, testimonials, or user-generated content have appeared.
|
||||
- **Purpose**: Keep a steady flow of social proof and route it into marketing.
|
||||
- **Skills used**: `social`, `referrals`, `sales-enablement`, `cro`
|
||||
- **Loop body**:
|
||||
1. Collect new reviews/testimonials/UGC/mentions since last run.
|
||||
2. Sort by strength and relevance.
|
||||
3. Draft where each should go (site proof section, ad, social post, sales deck).
|
||||
4. Flag anything negative for a human response.
|
||||
- **Self-check**: Is it genuinely strong and on-message? Don't force weak proof into prime placement.
|
||||
- **State / idempotency**: Track already-harvested items; never re-use the same one twice.
|
||||
- **Stop / bail-out**: **Verify consent and platform ToS before public reuse; add FTC-required disclosure for incentivized content.** No verifiable consent, or platform prohibits reuse → don't use. Negative/sensitive → escalate to a human, don't auto-publish.
|
||||
- **Output**: New proof assets routed to their destinations.
|
||||
|
||||
### The review-site-management loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: New reviews land on G2/Capterra/app stores, or listings drift out of date.
|
||||
- **Purpose**: Maintain reputation and conversion on third-party review platforms.
|
||||
- **Skills used**: `sales-enablement`, `social`, `cro`
|
||||
- **Loop body**:
|
||||
1. Track new reviews across review sites/app stores.
|
||||
2. Draft responses (thank promoters, address detractors constructively).
|
||||
3. Flag listing updates needed (screenshots, features, pricing).
|
||||
- **Self-check**: Is the response specific and non-defensive? Never argue publicly with a reviewer.
|
||||
- **State / idempotency**: Track responded reviews; never double-respond.
|
||||
- **Stop / bail-out**: No new reviews/updates → skip. Human-approve responses to negative/legal-sensitive reviews.
|
||||
- **Output**: Drafted responses + a listing-update checklist.
|
||||
|
||||
### The case-study-sourcing loop
|
||||
- **Check cadence**: Monthly
|
||||
- **Acts when**: A customer hits case-study-worthy success (strong results, milestone, enthusiastic feedback).
|
||||
- **Purpose**: Keep a pipeline of case studies and customer stories.
|
||||
- **Skills used**: `sales-enablement`, `customer-research`, `referrals`
|
||||
- **Loop body**:
|
||||
1. Identify customers with standout results/engagement.
|
||||
2. Qualify for a case study (results, willingness, logo value).
|
||||
3. Draft the outreach + interview questions.
|
||||
- **Self-check**: Are the results real and attributable, or coincidental? Verify before pitching a story.
|
||||
- **State / idempotency**: Track approached customers + status; respect a no-repeat cooldown.
|
||||
- **Stop / bail-out**: No qualified candidates → skip. Human-approve customer outreach.
|
||||
- **Output**: A candidate list with drafted outreach.
|
||||
|
||||
---
|
||||
|
||||
## Ongoing Ops / Meta
|
||||
|
||||
### The weekly-marketing-review loop
|
||||
- **Check cadence**: Weekly (Mon 9am)
|
||||
- **Acts when**: Always runs — this is the heartbeat. It "acts" by flagging the week's notable movers.
|
||||
- **Purpose**: One standing full-funnel pulse so nothing drifts unnoticed.
|
||||
- **Skills used**: `analytics`, `marketing-plan`, `marketing-ideas`
|
||||
- **Loop body**:
|
||||
1. Pull top-line AARRR metrics vs. last week and vs. plan.
|
||||
2. Flag the biggest mover (good and bad) per stage.
|
||||
3. Tie each flag to the loop or skill that should act on it; surface 1–2 experiment ideas.
|
||||
- **Self-check**: Distinguish trend from noise before raising an alarm.
|
||||
- **State / idempotency**: Store each week's snapshot for accurate week-over-week deltas.
|
||||
- **Stop / bail-out**: Manual disable + error-halt. On a data-source outage, report "stale data," never fabricated movement. (Not "n/a" — even the heartbeat needs an off switch and an error path.)
|
||||
- **Output**: A one-page weekly digest with owners/next actions.
|
||||
|
||||
### The experiment-backlog loop
|
||||
- **Check cadence**: Weekly
|
||||
- **Acts when**: New hypotheses exist to log, the backlog needs re-ranking, or a test slot is free.
|
||||
- **Purpose**: Keep the experiment pipeline full and prioritized. **Thin wrapper — defer all test design, statistical analysis, and velocity management to `ab-testing`.**
|
||||
- **Skills used**: `ab-testing` (owner), `cro`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Harvest new hypotheses from the week (data, research, competitors, support, other loops).
|
||||
2. Re-rank the backlog with ICE.
|
||||
3. If a slot is free, hand the top idea to `ab-testing`; if a test concluded there, log the learning.
|
||||
- **Self-check**: Is the top idea actually testable with current traffic, or ICE-inflated?
|
||||
- **State / idempotency**: Dedupe incoming hypotheses against the backlog; track which tests are live.
|
||||
- **Stop / bail-out**: Backlog full and a test running → just log new ideas. Don't duplicate `ab-testing`'s job.
|
||||
- **Output**: An updated, ranked backlog (the source of record lives with `ab-testing`).
|
||||
|
||||
### The analytics-anomaly loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A tracked metric breaks its expected band (spike or drop beyond normal variance).
|
||||
- **Purpose**: Catch anything breaking — good or bad — before it runs for days unnoticed.
|
||||
- **Skills used**: `analytics`
|
||||
- **Loop body**:
|
||||
1. Check key metrics (traffic, signups, conversion, revenue, spend) against their normal range.
|
||||
2. Flag anomalies; separate "real event" from "tracking artifact."
|
||||
3. Route each to the responsible loop/owner for diagnosis.
|
||||
- **Self-check**: Is the anomaly real or a tracking/seasonality artifact? Check for known causes (holiday, launch, deploy) before alarming.
|
||||
- **State / idempotency**: Track already-alerted anomalies; don't re-alert the same ongoing one daily.
|
||||
- **Stop / bail-out**: All metrics in-band → silent (no alert = good). Escalate a revenue/spend anomaly immediately.
|
||||
- **Output**: An anomaly alert routed to an owner, or nothing.
|
||||
|
||||
### The brand-mention / reputation loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A meaningful brand mention appears anywhere (not just where you're listening for engagement).
|
||||
- **Purpose**: Monitor and protect reputation; respond where it matters.
|
||||
- **Skills used**: `social`, `public-relations`
|
||||
- **Loop body**:
|
||||
1. Scan the open web/social/forums for brand mentions.
|
||||
2. Classify sentiment + reach + risk.
|
||||
3. Route: positive → amplify/thank; negative/risky → drafted response for human review; unlinked mention → backlink-prospecting.
|
||||
- **Self-check**: Does a negative mention need a response, or would engaging amplify it? Judge reach + legitimacy.
|
||||
- **State / idempotency**: Dedupe on mention ID; track handled mentions.
|
||||
- **Stop / bail-out**: No meaningful mentions → skip. **Always human-approve responses to negative/crisis mentions** — never auto-reply to a complaint.
|
||||
- **Output**: A mention digest with routed actions.
|
||||
|
||||
### The tracking-QA loop
|
||||
- **Check cadence**: Weekly (and on deploy / campaign launch)
|
||||
- **Acts when**: Analytics, pixels, UTMs, or conversion events are missing, misfiring, or misconfigured.
|
||||
- **Purpose**: Keep the measurement layer trustworthy — every other loop depends on it.
|
||||
- **Skills used**: `analytics`
|
||||
- **Loop body**:
|
||||
1. Verify key events fire correctly, pixels are present, UTMs are consistent, and conversions attribute.
|
||||
2. Flag broken/missing/duplicate tracking, especially after deploys or new campaigns.
|
||||
3. Recommend fixes.
|
||||
- **Self-check**: Is it truly broken, or an expected change? Confirm against a known-good baseline.
|
||||
- **State / idempotency**: Track open tracking issues; update rather than re-file.
|
||||
- **Stop / bail-out**: All tracking healthy → log "clean." **Escalate a broken revenue/conversion event immediately** — every downstream loop is blind until it's fixed.
|
||||
- **Output**: A tracking-QA report with prioritized fixes.
|
||||
|
||||
### The campaign-postmortem loop
|
||||
- **Check cadence**: On campaign end (event-based)
|
||||
- **Acts when**: A campaign (launch, promo, seasonal push) concludes.
|
||||
- **Purpose**: Capture results, lessons, and reusable assets so each campaign compounds.
|
||||
- **Skills used**: `analytics`, `marketing-plan`
|
||||
- **Loop body**:
|
||||
1. Pull final campaign results vs. goals.
|
||||
2. Capture what worked, what didn't, and why; save reusable assets (copy, creative, workflows).
|
||||
3. Feed learnings into the experiment backlog and the next plan; log follow-ups.
|
||||
- **Self-check**: Are conclusions supported by the data, or hindsight narrative? Separate correlation from cause.
|
||||
- **State / idempotency**: One postmortem per campaign; don't re-run on an already-documented campaign.
|
||||
- **Stop / bail-out**: No concluded campaign → skip.
|
||||
- **Output**: A postmortem doc + backlog/plan inputs.
|
||||
|
||||
---
|
||||
|
||||
## Adapting and authoring loops
|
||||
|
||||
To adapt a loop: keep all nine anatomy parts, swap skills/thresholds for the user's stack, and re-tune cadence to signal speed. To author a brand-new one: use `loop-template.md` (copy-paste template + fill-in prompts + worked example + ship checklist). Either way, do not ship a loop until every part is filled — especially **State / idempotency**, **Self-check**, and **Stop / bail-out**. A loop without those isn't a system; it's a way to do the wrong thing on a schedule, repeatedly, to the same people.
|
||||
@@ -0,0 +1,73 @@
|
||||
# Loop Guardrails & Compliance
|
||||
|
||||
Loops act on a schedule, often on customer data, sometimes with money or a public voice. This reference consolidates the safety rules that keep autonomous loops from doing harm. Apply it to every loop that sends, spends, publishes, or touches personal data.
|
||||
|
||||
## The two-tier action model
|
||||
|
||||
Classify every action a loop can take:
|
||||
|
||||
**Tier 1 — Autonomous-safe** (a loop may do these unattended):
|
||||
read data, analyze, diff, score, **draft**, and **stage** work for review.
|
||||
|
||||
**Tier 2 — Gated** (require a human checkpoint by default):
|
||||
**spend** money, **shift budget**, **send** messages, **publish** anything public, **delete/suppress** records, **change** live account settings.
|
||||
|
||||
A Tier-2 action may run without a per-action human check only if the user has **explicitly authorized** it *and* it's bounded by caps + an allowlist (below). Absent that, the loop stages a draft and a human approves.
|
||||
|
||||
## Spend guardrails (ad-fatigue, paid-search, retargeting, expansion)
|
||||
|
||||
- **Hard caps**: a daily/weekly spend ceiling the loop can never exceed; halt and alert if approached.
|
||||
- **Per-run change limit**: cap how much budget can move in one run (e.g., ≤20%), so a bad read can't reallocate everything.
|
||||
- **Allowlist**: only specified accounts/campaigns are eligible for autonomous changes; everything else is staged.
|
||||
- **Directional guardrails**: judge paid changes on revenue/ROAS, not just CTR/CPA — never optimize a proxy metric into a revenue loss.
|
||||
|
||||
## Publish & send guardrails (email, social, PR, community, reviews)
|
||||
|
||||
- **Default to a staging queue** + human approval for anything public or outbound. Auto-*drafting* is fine; auto-*publishing* is not, unless explicitly authorized.
|
||||
- **Volume caps**: per-run and per-recipient limits so a loop can't blast a list or over-post a channel.
|
||||
- **Suppression first**: always check suppression/unsubscribe/do-not-contact lists before sending.
|
||||
- **No auto-posting where detection/ToS bites**: owned social, press pitches, and community replies are staged for a human (bot detection + brand risk).
|
||||
|
||||
## Compliance
|
||||
|
||||
Match each rule to the loops it governs:
|
||||
|
||||
- **CAN-SPAM / CASL (email/SMS loops — lifecycle, re-engagement, churn, trial, dunning, referral)**: honor unsubscribes immediately and permanently; include a working unsubscribe + physical address; identify the sender; don't email/text without a lawful basis or consent; scrub against suppression every send.
|
||||
- **GDPR / CCPA (any loop touching personal data)**: process on a lawful basis; get consent for EU marketing; honor deletion and opt-out requests; minimize data pulled and retained; don't repurpose data beyond its collected purpose.
|
||||
- **FTC (review-and-UGC-harvest, referral, social)**: disclose material connections and incentives (#ad, "I was compensated"); only use testimonials with permission; no fabricated or cherry-picked-to-mislead claims.
|
||||
- **Platform ToS (social-listening, community-engagement, review-site-management, scraping-based loops)**: respect rate limits and automation rules; follow review-platform response policies; don't scrape or auto-act where prohibited.
|
||||
|
||||
When a loop can't confirm consent, permission, or ToS-compatibility, its stop condition is **don't act** — stage for a human instead.
|
||||
|
||||
## PII handling
|
||||
|
||||
- Don't log raw PII in loop **state** or **run logs** — use internal IDs or hashes.
|
||||
- Pull the minimum personal data needed to make the decision; don't hoard it in state.
|
||||
- Keep exports and drafts out of shared/synced locations unless intended.
|
||||
|
||||
## Always-escalate list
|
||||
|
||||
These never run fully autonomously — route to a human regardless of authorization:
|
||||
|
||||
- Negative or crisis brand mentions; responses to complaints or legal/medical/financial-sensitive issues.
|
||||
- Newsjacking angles (see the veto list in the catalog) — human approval before any pitch/post.
|
||||
- High-value or strategic accounts (enterprise, at-risk logos).
|
||||
- Anomalies in **revenue** or **ad spend** — flag immediately, don't self-correct.
|
||||
- Anything that would delete data or contact a large audience at once.
|
||||
|
||||
## Kill switch
|
||||
|
||||
Every scheduled loop needs a manual off switch, and you should know how to stop **all** loops fast (disable the schedule / cron, or a global flag the loop bodies check). Document it where the loops are scheduled. A loop you can't stop quickly is a liability.
|
||||
|
||||
## Pre-launch guardrail checklist
|
||||
|
||||
Before scheduling any loop that sends, spends, publishes, or touches personal data:
|
||||
|
||||
- [ ] Every action is classified Tier 1 (auto) or Tier 2 (gated).
|
||||
- [ ] Tier-2 actions are staged for approval — or bounded by explicit authorization + caps + allowlist.
|
||||
- [ ] Spend loops have a hard cap and a per-run change limit.
|
||||
- [ ] Send loops check suppression/unsubscribe and have volume caps.
|
||||
- [ ] Applicable compliance rules (CAN-SPAM/GDPR/FTC/ToS) are satisfied, with "don't act" as the fallback.
|
||||
- [ ] No raw PII in state or logs.
|
||||
- [ ] The always-escalate cases route to a human.
|
||||
- [ ] There's a documented kill switch.
|
||||
@@ -0,0 +1,69 @@
|
||||
# Loop Orchestration & Rollout
|
||||
|
||||
Loops aren't independent scripts — they compose into a marketing operating system. This reference covers how they fit together and the order to adopt them so you never build 43 at once.
|
||||
|
||||
## The system view
|
||||
|
||||
Loops fall into four layers. Data flows down and learnings flow back up.
|
||||
|
||||
```
|
||||
SENSING analytics-anomaly · tracking-QA · weekly-marketing-review
|
||||
│ (detect what changed; trust the numbers first)
|
||||
▼
|
||||
DIAGNOSTIC per-stage watchers — onboarding drop-off, churn-signal,
|
||||
ranking-drop, landing-page regression, ad-fatigue, …
|
||||
│ (figure out what to do about it)
|
||||
▼
|
||||
ACTION staged drafts, nudges, outreach, budget moves
|
||||
│ (mostly human-checkpointed)
|
||||
▼
|
||||
LEARNING experiment-backlog · campaign-postmortem · voice-of-customer
|
||||
│ (capture what worked)
|
||||
└──────────────► feeds back into SENSING & DIAGNOSTIC
|
||||
```
|
||||
|
||||
Key connective tissue:
|
||||
- **weekly-marketing-review is the router.** It reads top-line metrics and dispatches each notable mover to the loop that owns it. It's the one loop that sees the whole board.
|
||||
- **tracking-QA + analytics-anomaly are the foundation.** Every other loop reads from analytics. If tracking is broken, every downstream loop acts on lies. These come first.
|
||||
- **experiment-backlog is the sink.** Hypotheses generated by many loops (signup-leak, pricing, onboarding, voice-of-customer) converge here, then hand off to `ab-testing`. Don't let each loop run its own tests.
|
||||
- **voice-of-customer is a source.** Customer language it mines feeds copy for ad-fatigue, lifecycle-email, landing-page, and pricing loops.
|
||||
- **campaign-postmortem closes the loop.** Its learnings become next quarter's hypotheses and plan inputs.
|
||||
|
||||
Avoid duplicate ownership: when two loops could act on the same signal, one owns the action and the other just flags. (E.g., an at-risk account belongs to churn-signal, not expansion/upsell — never upsell an account that's churning.)
|
||||
|
||||
## Rollout path (adopt in this order)
|
||||
|
||||
Add a loop only when the loops before it are running and earning their keep. Each stage assumes the previous one is solid.
|
||||
|
||||
**Stage 0 — Foundation (trust the data + see the board).**
|
||||
`tracking-QA`, `weekly-marketing-review`.
|
||||
You cannot run any loop responsibly on untrustworthy data or without a full-funnel pulse. This is non-negotiable and comes first.
|
||||
|
||||
**Stage 1 — Plug the leaks (highest ROI, protects existing revenue).**
|
||||
`failed-payment/dunning`, `churn-signal`, `lifecycle-email-refresh`.
|
||||
Recovering customers you already have is cheaper than acquiring new ones. Dunning alone often pays for the whole system.
|
||||
|
||||
**Stage 2 — Convert what you already get (fix the bucket before adding water).**
|
||||
`onboarding drop-off`, `signup-funnel-leak`, `trial-conversion`.
|
||||
More traffic into a leaky funnel is waste. Seal activation and conversion next.
|
||||
|
||||
**Stage 3 — Grow the top (now scale acquisition).**
|
||||
`keyword-gap`, `content-repurposing`, `ad-fatigue`, `social-listening`, `analytics-anomaly`.
|
||||
With the bucket sealed, turn on demand generation and the safety-net anomaly watcher.
|
||||
|
||||
**Stage 4 — Optimize monetization.**
|
||||
`pricing-page-experiment`, `paywall-optimization`, `PQL/upgrade-intent`, `expansion/upsell`.
|
||||
Once volume is healthy, tune revenue per user — judged on revenue quality, not conversion alone.
|
||||
|
||||
**Stage 5 — Compounding & advocacy.**
|
||||
`referral-nudge`, `review-and-UGC-harvest`, `review-site-management`, `case-study-sourcing`, `partner-pipeline`, `brand-mention/reputation`, `experiment-backlog`, `campaign-postmortem`.
|
||||
The flywheel: happy customers and earned media that feed back into acquisition, plus the learning loops that make everything compound.
|
||||
|
||||
The remaining catalog loops (content-decay, internal-linking, programmatic-SEO quality, content-calendar refill, paid-search query-mining, retargeting-hygiene, landing-page regression, community-engagement, competitor-watch, backlink-prospecting, directory-submission, feature-adoption, lead-capture-asset, email-deliverability, voice-of-customer) slot into the stage that matches their function as each channel becomes a priority.
|
||||
|
||||
## Rollout rules
|
||||
|
||||
- **One at a time.** Prove a loop earns its keep (someone acts on its output, it moves its metric) before adding the next.
|
||||
- **Foundation before growth.** Acquisition loops before solid tracking + retention = pouring water into a leaky bucket.
|
||||
- **Cap the total.** If you're running more loops than you can review the output of, you have vanity loops. Retire the ones nobody acts on.
|
||||
- **Re-audit quarterly.** Recalibrate thresholds, kill dead loops, promote the ones that consistently drive action.
|
||||
@@ -0,0 +1,67 @@
|
||||
# Loop State & Run Logging
|
||||
|
||||
Idempotency is only real if the loop can remember what it already did between runs. This reference defines where that state lives and how to log runs — so loops don't double-act, re-nag the same people, or re-alert the same issue.
|
||||
|
||||
## Where state lives
|
||||
|
||||
Persist each loop's state in a file under `.agents/loops/` — the same `.agents/` convention this repo uses for `product-marketing.md` and `listening-sources.md`. One state file per loop:
|
||||
|
||||
```
|
||||
.agents/loops/<loop-name>.json # the loop's memory
|
||||
.agents/loops/<loop-name>.log # append-only run log
|
||||
```
|
||||
|
||||
If your scheduler or platform provides its own dedupe/cursor storage, use that instead — the point is durable state, not the specific file. Never keep state only in memory; a loop that forgets on restart will repeat itself.
|
||||
|
||||
## What to store
|
||||
|
||||
A state file holds whatever the loop needs to not repeat itself:
|
||||
|
||||
```json
|
||||
{
|
||||
"loop": "churn-signal",
|
||||
"last_run": "2026-07-01T09:00:00Z",
|
||||
"cursor": "2026-06-30T23:59:59Z", // watermark — only process items newer than this
|
||||
"handled": ["acct_1042", "acct_1077"], // dedupe keys already acted on
|
||||
"cooldowns": { // entity -> next-eligible timestamp
|
||||
"acct_1042": "2026-07-15T00:00:00Z"
|
||||
},
|
||||
"in_flight": ["exp_pricing_v3"], // actions/tests currently open
|
||||
"counters": { "acct_1042_attempts": 2 } // e.g. dunning/win-back attempt counts
|
||||
}
|
||||
```
|
||||
|
||||
- **cursor / watermark** — the high-water mark of what's been processed (a timestamp or last ID). The loop only looks at items past it.
|
||||
- **handled** — dedupe keys for items already acted on, so re-runs skip them.
|
||||
- **cooldowns** — per-entity suppression windows so you never re-contact someone inside the window.
|
||||
- **in_flight** — open items (running tests, active interventions) so the loop doesn't start a conflicting one.
|
||||
- **counters** — attempt counts that drive stop conditions (e.g., "after 2 win-back emails, stop").
|
||||
|
||||
Keep state small and prune it: expire old `handled`/`cooldown` entries once they're past their window.
|
||||
|
||||
## Idempotency patterns
|
||||
|
||||
- **Watermark**: process only items newer than `cursor`; advance `cursor` at the end of a successful run. Safe to re-run — it won't reprocess.
|
||||
- **Dedupe set**: before acting on an item, check its key against `handled`; add it after acting.
|
||||
- **Cooldown map**: before contacting an entity, check `cooldowns[entity]`; set it after contact.
|
||||
- **In-flight guard**: before starting an action that shouldn't overlap (a test, an intervention), check `in_flight`.
|
||||
|
||||
## Run logging
|
||||
|
||||
Append one line per run, whether or not it acted. This is the audit trail and the vanity-loop detector.
|
||||
|
||||
```
|
||||
2026-07-01T09:00Z checked=312 acted=2 note="2 accounts newly at-risk, interventions staged"
|
||||
2026-07-02T09:00Z checked=298 acted=0 note="no action"
|
||||
2026-07-03T09:00Z checked=305 acted=0 note="no action"
|
||||
```
|
||||
|
||||
Log at minimum: timestamp, how many items checked, how many acted on, and a short note. Use it to answer two questions:
|
||||
- **Is it a vanity loop?** If every run is `acted=0` for weeks and nobody misses it — or it acts every run (a sign it's chasing noise) — reconsider it.
|
||||
- **Did it double-act?** Two runs acting on the same entity means the dedupe/cooldown state isn't working.
|
||||
|
||||
## Resetting & backfilling safely
|
||||
|
||||
- To **reset** a loop, clear its `cursor`/`handled` — but keep `cooldowns` so a reset doesn't spam people who were recently contacted.
|
||||
- On **first run** (no state yet), set the watermark to "now" rather than processing all history, or you'll blast every historical item. If you genuinely want a backfill, do a dry run first (log what it *would* do, act on nothing) and respect cooldowns.
|
||||
- Never log raw PII in state or run logs — use IDs or hashes (see `loop-guardrails.md`).
|
||||
@@ -0,0 +1,79 @@
|
||||
# Loop Template
|
||||
|
||||
A copy-paste template for authoring your own marketing loop. Fill every one of the nine parts — a loop missing its **state/idempotency**, **self-check**, or **stop/bail-out** isn't a system, it's a way to do the wrong thing on a schedule.
|
||||
|
||||
Before you start, sanity-check that this *should* be a loop at all (see "When NOT to loop" in `SKILL.md`): it's recurring, signal-driven, and doesn't require human judgment to set strategy or creative direction each run.
|
||||
|
||||
---
|
||||
|
||||
## Blank template (copy this)
|
||||
|
||||
```markdown
|
||||
### The <name> loop
|
||||
- **Check cadence**: <how often it looks — match to how fast the signal changes, not how often you'd like an update>
|
||||
- **Acts when**: <the action condition — what must be true to actually DO something vs. just check and skip. Most runs should skip.>
|
||||
- **Purpose**: <the ONE outcome this loop exists to move>
|
||||
- **Skills used**: <which marketing skills the loop orchestrates each run>
|
||||
- **Loop body**:
|
||||
1. <step — usually: pull data / diff vs. last run>
|
||||
2. <step — identify what, if anything, crossed the action condition>
|
||||
3. <step — draft or stage the response>
|
||||
- **Self-check**: <the verification done BEFORE acting — is the signal real vs. noise/seasonality/tracking bug? Is the sample big enough to be significant?>
|
||||
- **State / idempotency**: <what it remembers between runs — last-run marker, dedupe key, cooldown window, "already handled" set — so it doesn't double-act or re-nag the same people>
|
||||
- **Stop / bail-out**: <when it skips, halts, escalates to a human, or disables itself — plus what it does on error. Include a human checkpoint before anything that spends money or publishes.>
|
||||
- **Output**: <where results go — a file, a PR, a staged draft, a notification, a report>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Fill-in prompts (answer these, in order)
|
||||
|
||||
1. **What outcome does this protect or grow?** (rankings, ad efficiency, activation, retention, revenue, referrals) → *Purpose*
|
||||
2. **How fast does that signal actually change?** (hours / days / weeks / months) → *Check cadence*
|
||||
3. **What has to be true before it's worth acting?** (a threshold crossed, a new item appeared, a regression vs. baseline) → *Acts when*
|
||||
4. **What data does it read and what does it produce each run?** → *Loop body* + *Output*
|
||||
5. **What would make it act on a false signal?** (noise, seasonality, a tracking break, too-small a sample) → *Self-check*
|
||||
6. **What must it remember so it doesn't repeat itself?** (dedupe key, cooldown, last-run marker) → *State / idempotency*
|
||||
7. **When should it stop, skip, or hand off to a human?** (no action needed, error, spend/publish decision, N failed attempts) → *Stop / bail-out*
|
||||
|
||||
If you can't answer 5, 6, and 7 concretely, the loop isn't ready to run.
|
||||
|
||||
---
|
||||
|
||||
## Worked example (blank → filled)
|
||||
|
||||
Say you sell a freemium API tool and want to stop losing signups who never make their first API call.
|
||||
|
||||
```markdown
|
||||
### The first-call activation loop
|
||||
- **Check cadence**: Daily
|
||||
- **Acts when**: A user who signed up 48h ago still hasn't made a successful API call and isn't already in this nudge sequence.
|
||||
- **Purpose**: Increase the share of new signups that reach first value (first successful API call).
|
||||
- **Skills used**: `onboarding`, `emails`, `analytics`
|
||||
- **Loop body**:
|
||||
1. Pull signups from ~48h ago and their first-call status.
|
||||
2. Filter to those with zero successful calls and no active nudge.
|
||||
3. Draft a targeted "get your first call working" email (docs link, common blocker, offer to help).
|
||||
- **Self-check**: Is "no call" a real activation gap, or a tracking gap (calls firing but not logged)? Confirm against server logs before emailing.
|
||||
- **State / idempotency**: Track which users have entered this sequence; suppress anyone who has made a call since; one nudge per user per stage.
|
||||
- **Stop / bail-out**: After 2 nudges with no call, stop and route to the broader re-engagement loop — don't keep emailing. Skip the run entirely if the events pipeline looks stale.
|
||||
- **Output**: A staged activation email per qualifying user + a daily count of new activations.
|
||||
```
|
||||
|
||||
Notice what makes it safe: the **self-check** guards against a tracking bug emailing active users, the **state** stops it re-nagging, and the **stop** caps attempts and hands off instead of looping forever.
|
||||
|
||||
---
|
||||
|
||||
## Ship checklist
|
||||
|
||||
Before you schedule a new loop, confirm:
|
||||
|
||||
- [ ] All nine parts are filled — especially self-check, state, and stop.
|
||||
- [ ] Cadence matches signal speed (you're not checking daily for a weekly-moving signal).
|
||||
- [ ] It's designed so **most runs do nothing** — it acts only on a real condition.
|
||||
- [ ] Anything that **spends money or publishes** has a human checkpoint (unless caps + an allowlist are explicitly authorized).
|
||||
- [ ] State prevents double-acting and re-nagging the same people.
|
||||
- [ ] There's an error path (stale data → report "stale," don't fabricate movement) and a manual off switch.
|
||||
- [ ] For scheduling mechanics, see the "Scheduling a loop" section in `SKILL.md`.
|
||||
|
||||
Once it runs, give it a few cycles and ask the "is this a vanity loop?" question: if nobody acts on the output, delete it.
|
||||
@@ -0,0 +1,153 @@
|
||||
---
|
||||
name: offers
|
||||
description: "When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement."
|
||||
metadata:
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Offer Design
|
||||
|
||||
You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.
|
||||
|
||||
## Before Starting
|
||||
|
||||
**Check for product marketing context first:**
|
||||
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
|
||||
|
||||
---
|
||||
|
||||
## Core Philosophy
|
||||
|
||||
**The offer is the thing, not the page.** Better copy on a weak offer compounds slowly. A stronger offer with average copy converts immediately. Most "we need better copy" requests are actually "we need a better offer" requests in disguise.
|
||||
|
||||
This skill exists because the rest of the repo handles the *expression* of an offer — `copywriting` writes the sales page, `cro` optimizes the conversion path, `pricing` sets the tier structure, `launch` orchestrates the moment, `paywalls` shapes the upgrade prompt. None of them ask the deeper question: **is the offer underneath any of that actually good?**
|
||||
|
||||
### When this skill matters
|
||||
|
||||
You sell:
|
||||
- **Services** — consulting, freelance, agency retainers, productized services
|
||||
- **Courses** — async, cohort-based, live
|
||||
- **Coaching** — 1:1, group, mastermind
|
||||
- **Info products** — guides, swipe files, templates, communities
|
||||
- **High-ticket B2B** — $5K+ ACV with a sales conversation
|
||||
- **Direct-response** — e-com promo offers, infomercial-style, paid-traffic-to-VSL
|
||||
|
||||
### When `pricing` does more of the work
|
||||
|
||||
You sell:
|
||||
- **Self-serve SaaS** with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary
|
||||
- **Marketplaces** — the offer is structural, not constructed
|
||||
|
||||
Skim this skill in those cases for the value equation framing, then go to `pricing`.
|
||||
|
||||
---
|
||||
|
||||
## The Value Equation
|
||||
|
||||
The single most useful frame for offer design. Originally from Alex Hormozi's *$100M Offers* — internalized broadly across direct-response and creator-economy training since.
|
||||
|
||||
```
|
||||
Dream Outcome × Perceived Likelihood of Achievement
|
||||
Value = ─────────────────────────────────────────────────────────
|
||||
Time Delay × Effort & Sacrifice
|
||||
```
|
||||
|
||||
You move the four levers like this:
|
||||
|
||||
| Lever | What it means | How to increase value |
|
||||
|-------|---------------|-----------------------|
|
||||
| **Dream outcome** ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. |
|
||||
| **Perceived likelihood** ↑ | Do they believe they'll get it | Proof (case studies, named customers, data), guarantees, methodology specificity |
|
||||
| **Time delay** ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline |
|
||||
| **Effort & sacrifice** ↓ | What it costs them in time/work/risk besides money | Done-for-you, simpler process, fewer decisions, lower learning curve |
|
||||
|
||||
**Implication for offer construction**: most "lower the price" requests are actually "raise the numerator or lower the denominator" requests. Price is the comparison, not the value.
|
||||
|
||||
**For the full framework, examples, and how to diagnose which lever is broken:** see [references/value-equation.md](references/value-equation.md)
|
||||
|
||||
---
|
||||
|
||||
## The Anatomy of a Complete Offer
|
||||
|
||||
A complete offer has six components. Skip any one and conversion suffers.
|
||||
|
||||
| # | Component | Question it answers |
|
||||
|---|-----------|---------------------|
|
||||
| 1 | **Core deliverable** | What do they get? |
|
||||
| 2 | **Bonus stack** | What else do they get that makes the core feel undervalued? |
|
||||
| 3 | **Guarantee** | What happens if it doesn't work? |
|
||||
| 4 | **Scarcity / urgency** | Why now, not later? |
|
||||
| 5 | **Name** | What is this thing called? |
|
||||
| 6 | **Price + payment structure** | What do they pay and how? |
|
||||
|
||||
Most weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).
|
||||
|
||||
**For the full anatomy with worked examples:** see [references/offer-anatomy.md](references/offer-anatomy.md)
|
||||
|
||||
---
|
||||
|
||||
## Reference Library
|
||||
|
||||
| Reference | When to read |
|
||||
|-----------|--------------|
|
||||
| [value-equation.md](references/value-equation.md) | Diagnosing which lever is broken on a stuck offer |
|
||||
| [offer-anatomy.md](references/offer-anatomy.md) | Building a complete offer from scratch |
|
||||
| [guarantee-design.md](references/guarantee-design.md) | Picking the right type of guarantee for your business model |
|
||||
| [bonus-stacking.md](references/bonus-stacking.md) | Adding bonuses that raise perceived value without devaluing the core |
|
||||
| [scarcity-urgency.md](references/scarcity-urgency.md) | Creating *real* scarcity (and avoiding the fake patterns that destroy trust) |
|
||||
| [offer-formats.md](references/offer-formats.md) | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B |
|
||||
| [examples.md](references/examples.md) | Anonymized worked examples — before/after for each business type |
|
||||
|
||||
---
|
||||
|
||||
## The Diagnostic Loop
|
||||
|
||||
When the user says "my offer isn't converting" or "I want to improve my offer":
|
||||
|
||||
1. **Identify the business type** — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.
|
||||
2. **State the current offer in plain language** — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.
|
||||
3. **Run the value equation** — score each of the four levers 1–10. The lowest is the binding constraint.
|
||||
4. **Audit the anatomy** — which of the six components is missing or weak?
|
||||
5. **Pick one lever to fix this iteration** — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.
|
||||
6. **Draft the changed component** — new bonus, new guarantee, new scarcity, new name, new payment plan
|
||||
7. **Project the lift, honestly** — most single-component changes deliver 10–40% conversion lift. Anyone promising 5x is selling something. Two consecutive iterations on different levers can stack to 2–3x.
|
||||
|
||||
---
|
||||
|
||||
## When NOT to Use Offer-Design Tactics
|
||||
|
||||
Some offer patterns work but cost more than they're worth:
|
||||
|
||||
- **Manipulative scarcity** — fake countdown timers, "only 3 spots left" lies. Short-term lift, long-term trust collapse. Don't.
|
||||
- **Over-promising guarantees** — "double your revenue or refund + $1,000." Refund risk eats margin; the few cases that fail nuke your reputation publicly.
|
||||
- **Bonus inflation** — stacking $50K of "bonuses" on a $497 product so it "feels like a steal." Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.
|
||||
- **Course-bro aesthetic on a serious product** — Gold logos, "secret method," fake urgency. Pattern-matches to scam. Wrong room.
|
||||
|
||||
The repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud.
|
||||
|
||||
---
|
||||
|
||||
## Banned Vocabulary
|
||||
|
||||
When drafting offer language (sales pages, emails, headlines), avoid:
|
||||
|
||||
- **"Game-changing," "revolutionary," "disruptive," "next-level," "10x"** — pattern-matches to AI slop / course-bro
|
||||
- **"Secret," "hidden," "what they don't want you to know"** — clickbait
|
||||
- **"Limited time" with no actual time limit** — lying
|
||||
- **"Worth $X" or "$Y value" with no comparable** — inflation
|
||||
- **"100% guaranteed" without specifying conditions** — legally and brand-wise risky
|
||||
|
||||
Use specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **pricing** — for price levels, tier structure, value metric, packaging, freemium
|
||||
- **copywriting** — for the page that presents the offer
|
||||
- **cro** — for optimizing the conversion path the offer travels through
|
||||
- **launch** — for the moment you ship the offer
|
||||
- **paywalls** — for in-app upgrade-prompt versions of an offer
|
||||
- **sales-enablement** — for the deck and one-pager that carry the offer into a sales conversation
|
||||
- **emails** — for the email sequence that warms up the offer
|
||||
- **marketing-psychology** — for the cognitive biases that make offers land or bounce
|
||||
@@ -0,0 +1,150 @@
|
||||
# Bonus Stacking
|
||||
|
||||
How to add bonuses that raise perceived value without devaluing the core offer.
|
||||
|
||||
## What bonuses actually do
|
||||
|
||||
Three jobs at once:
|
||||
|
||||
1. **Raise perceived value** of the total offer
|
||||
2. **Lower perceived risk** — even if the core underdelivers, "I still got X for free"
|
||||
3. **Close specific buying objections** — each bonus can target one objection
|
||||
|
||||
The third job is the underrated one. Most weak bonus stacks throw four generic "extras" at the buyer. Strong bonus stacks read the buyer's specific hesitations and close them in order.
|
||||
|
||||
---
|
||||
|
||||
## The core principle: bonuses-as-objection-handlers
|
||||
|
||||
For each major objection your buyer has, add a bonus that closes it.
|
||||
|
||||
### Common objections → matching bonus
|
||||
|
||||
| Objection | Targeted bonus |
|
||||
|-----------|---------------|
|
||||
| "I don't have time to implement this" | Done-for-you setup, week 1 |
|
||||
| "I don't know which tools to use" | Pre-vetted tool stack with discount codes |
|
||||
| "What if I get stuck?" | 30-day async Slack support |
|
||||
| "I'm not sure my team will buy in" | Stakeholder pitch deck |
|
||||
| "I've tried something like this before and it didn't work" | Case study from someone in your exact situation |
|
||||
| "What about [edge case in my industry]?" | Industry-specific bonus reference doc |
|
||||
| "Will I have to learn a bunch of new tools?" | Pre-built templates for the tools we recommend |
|
||||
| "What if I don't finish it?" | 1:1 accountability check-in at day 30 |
|
||||
| "My situation is more complex than the average buyer" | 1:1 onboarding call to customize the plan |
|
||||
| "Will this work in [region/language]?" | Localized version or addendum |
|
||||
|
||||
A 4-bonus stack that closes 4 specific objections converts massively better than a 4-bonus stack of generic "extras."
|
||||
|
||||
### How to find your buyer's actual objections
|
||||
|
||||
1. Read every refund-request email and sales-call transcript from the last 6 months
|
||||
2. Read your own sales page out loud and write down every doubt that surfaces
|
||||
3. Ask 3 recent buyers: "What almost made you not buy?"
|
||||
|
||||
The answers cluster around 3–6 objections. Build a bonus for each.
|
||||
|
||||
---
|
||||
|
||||
## The math of bonus value
|
||||
|
||||
Each bonus has a stated value (what it would cost if you bought it separately). Bonuses should:
|
||||
|
||||
1. **Have a stated value the buyer can verify.** Compare to a comparable product or service. "$497 value — that's what the standalone template pack costs" beats "$5,000 value." (Standalone? Compared to what?)
|
||||
|
||||
2. **Total to less than 2x the price** of the core offer. A $1K offer can comfortably have $1.5K in bonuses. A $1K offer with "$25K in bonuses" reads as a scam.
|
||||
|
||||
3. **Be things you'd actually sell separately.** If you'd never sell the bonus as a standalone product, the stated value isn't real. Sophisticated buyers can tell.
|
||||
|
||||
4. **Each have a specific named outcome.** "Bonus: marketing toolkit" is weak. "Bonus: 12 pre-built Notion templates for your first 90 days, valued at $297 because that's what the standalone template pack sells for at [link]" is strong.
|
||||
|
||||
---
|
||||
|
||||
## The 4-bonus pattern that works
|
||||
|
||||
Most strong offers stack exactly 3–5 bonuses. More starts to feel like padding; fewer leaves objections un-closed.
|
||||
|
||||
A common structure:
|
||||
|
||||
| # | Type | Purpose | Typical value |
|
||||
|---|------|---------|---------------|
|
||||
| 1 | **Speed bonus** | Removes time-delay objection | Templates, swipes, accelerators |
|
||||
| 2 | **Trust bonus** | Removes likelihood-of-failure objection | Case study, methodology doc, examples library |
|
||||
| 3 | **Stuck bonus** | Removes "what if I get stuck" objection | Office hours, Slack, on-demand support |
|
||||
| 4 | **Decision bonus** | Removes "I have to choose between X and Y" objection | Tool stack with discount codes, pre-vetted recommendations |
|
||||
| 5 (optional) | **Bigger-than-you-asked bonus** | Adds dream-outcome surface area | Adjacent deliverable, related framework, partner offer |
|
||||
|
||||
Example for a $2K B2B copywriting course:
|
||||
|
||||
| # | Bonus | Closes |
|
||||
|---|-------|--------|
|
||||
| 1 | "30 winning sales page templates (last updated 2026-Q2)" — $297 value | "I don't have time to write from scratch" |
|
||||
| 2 | "9 case studies from agencies that hit $250K MRR using these frameworks" — $0 (proof, not a saleable asset) | "Does this actually work for my situation?" |
|
||||
| 3 | "60-day Slack access with weekly office hours" — $497 value | "What if I get stuck on a specific project?" |
|
||||
| 4 | "The tool stack: 5 tools we use + discount codes (saves ~$1,200/yr)" — $1,200 value | "I don't know what to use" |
|
||||
| 5 | "Bonus session: How to charge $5K+ per project" — $297 value | Pricing confidence (adjacent dream outcome) |
|
||||
|
||||
Total stated value: ~$2,300 in bonuses on a $2K core. Math checks out (under 2x). Each bonus closes a real objection.
|
||||
|
||||
---
|
||||
|
||||
## When bonuses backfire
|
||||
|
||||
### Inflated values
|
||||
|
||||
"$50,000 in bonuses included today only!" on a $497 product. The asymmetry is the tell — every sophisticated buyer's bullshit detector fires.
|
||||
|
||||
Stated values must be defensible. If you can't point to a comparable price, don't quote the value.
|
||||
|
||||
### Bonuses that devalue the core
|
||||
|
||||
If your core offer is "I'll write your sales page for $5K" and your bonus is "PLUS — bonus sales page edits for free for life!" — the bonus implies the core is incomplete. Now the buyer wonders why they should buy *without* the bonus.
|
||||
|
||||
Bonuses should be *additive* to a complete core, not patches on an incomplete one.
|
||||
|
||||
### Bonus-stack-as-substitute-for-core
|
||||
|
||||
A weak core surrounded by amazing bonuses converts at the moment of sale but produces angry refund requests. The buyer bought the bonuses, got the core, felt cheated.
|
||||
|
||||
Order: strong core *first*, then bonuses to address specific objections.
|
||||
|
||||
### Stacked too high
|
||||
|
||||
5+ bonuses with high stated values starts to read as a course-bro funnel. Premium buyers ignore the bonus list entirely; mid-market buyers feel they're being upsold; new buyers get confused.
|
||||
|
||||
3–5 bonuses, each with a specific purpose. Cap it.
|
||||
|
||||
### Same-as-everyone-else bonuses
|
||||
|
||||
"BONUS! Private community access!" on every course in your category isn't a bonus, it's table stakes. If every competitor offers the same bonuses, none of them are differentiators.
|
||||
|
||||
Find bonuses that are specific to your buyer's situation. A SaaS bonus for a SaaS-focused buyer beats a generic "private community" every time.
|
||||
|
||||
---
|
||||
|
||||
## Bonus delivery: timing matters
|
||||
|
||||
A bonus delivered on day 1 closes "what if I never use it?" risk.
|
||||
A bonus delivered at week 4 maintains momentum.
|
||||
A bonus delivered at completion rewards finishing.
|
||||
|
||||
Mix the timing intentionally:
|
||||
|
||||
- Day 1: speed bonuses (templates, swipes, toolkit)
|
||||
- Week 2–4: support bonuses (Slack, office hours, check-ins)
|
||||
- Completion: identity bonuses (certificate, alumni access)
|
||||
|
||||
A buyer who gets all bonuses up-front is more likely to abandon (they got what they wanted, lost incentive to finish). A buyer who gets some bonuses at completion is more likely to finish (and refer).
|
||||
|
||||
---
|
||||
|
||||
## The audit
|
||||
|
||||
For each existing bonus on a current offer, ask:
|
||||
|
||||
1. **What specific buying objection does this close?** If you can't name one, it's filler.
|
||||
2. **What's its defensible stated value?** If you can't point to a comparable price, drop the dollar amount.
|
||||
3. **Does the buyer get it on day 1, or at a meaningful point in their journey?** Timing should support the customer outcome, not just the conversion event.
|
||||
4. **Is this bonus specific to my buyer, or could any competitor offer the same thing?** If it's generic, replace it.
|
||||
5. **Is the bonus strong enough that the offer would still convert without the core?** If yes, the core is weak. Fix the core, don't lean on the bonus.
|
||||
|
||||
Most stuck offers have either zero bonuses or too many generic ones. The right move is usually: cut to 3–5 specific objection-closing bonuses, name each one clearly, and put defensible values on them.
|
||||
@@ -0,0 +1,215 @@
|
||||
# Worked Examples — Before/After Offers
|
||||
|
||||
Anonymized examples drawn from real engagements. Each shows the weak version, the diagnostic, and the strong version.
|
||||
|
||||
---
|
||||
|
||||
## Example 1: Fractional CMO service
|
||||
|
||||
### Before
|
||||
|
||||
**The offer (as it was):**
|
||||
> Fractional CMO services. $15K/month. We'll help you grow.
|
||||
|
||||
**Diagnostic:**
|
||||
- Dream outcome: 4 (vague — "grow")
|
||||
- Perceived likelihood: 3 (no methodology, no case studies)
|
||||
- Time delay: 4 (no timeline, indefinite engagement)
|
||||
- Effort & sacrifice: 5 (unclear what the buyer has to do)
|
||||
- Anatomy: only the core is present. No bonuses, no guarantee, no scarcity, no name.
|
||||
|
||||
**Lowest binding constraint:** perceived likelihood. Buyers don't believe an unnamed service will deliver.
|
||||
|
||||
### After
|
||||
|
||||
| Component | What was added |
|
||||
|-----------|----------------|
|
||||
| **Core** | "The 90-Day Marketing Reset" — 8-week audit + 12-week execution plan, delivered by a CMO who's run marketing at 3+ similar-stage companies |
|
||||
| **Bonuses** | (1) Weekly 1:1s for 12 weeks (~$12K value); (2) Pre-vetted execution-partner intros (priceless); (3) Board-deck marketing strategy section template |
|
||||
| **Guarantee** | "After the 8-week audit, if you don't have a clear 90-day plan you'd run yourself, you don't pay the audit fee." |
|
||||
| **Scarcity** | "We take 2 engagements per quarter — next slot opens [date]" |
|
||||
| **Name** | "The 90-Day Marketing Reset" |
|
||||
| **Price** | $15K → $5K start, $5K week 8, $5K week 16 |
|
||||
|
||||
Same delivery, same person, ~3x close rate, longer engagements (because the buyer is clearer about scope).
|
||||
|
||||
**Lesson:** the price didn't move. The structure did.
|
||||
|
||||
---
|
||||
|
||||
## Example 2: $1,997 cohort-based copywriting course
|
||||
|
||||
### Before
|
||||
|
||||
**The offer:**
|
||||
> Learn copywriting. $1,997. Includes 6 modules and Slack access.
|
||||
|
||||
**Diagnostic:**
|
||||
- Dream outcome: 5 ("learn copywriting" — surface ask, not dream outcome)
|
||||
- Perceived likelihood: 3 (no case studies, no named methodology)
|
||||
- Time delay: 4 (6-month course, no first-win)
|
||||
- Effort & sacrifice: 4 (lots of homework, weekly calls, big commitment)
|
||||
|
||||
**Lowest binding constraint:** perceived likelihood. Buyers don't believe THEY can do it.
|
||||
|
||||
### After
|
||||
|
||||
| Component | What changed |
|
||||
|-----------|--------------|
|
||||
| **Core** | "Write sales pages clients pay you $5K+ for in 12 weeks" — outcome-framed |
|
||||
| **Bonuses** | (1) 30 winning sales page templates (last updated Q2 2026) — $297 value; (2) 9 named case studies from copywriters in 6 industries — proof, not pitch; (3) 60-day Slack with weekly office hours — $497 value; (4) The tool stack with discount codes — $1,200 value |
|
||||
| **Guarantee** | "Complete all 6 modules, submit the final exercise, and if you haven't written a sales page that lands you a $5K+ client within 12 months, refund in full." |
|
||||
| **Scarcity** | Cohort scarcity — doors close Friday, next cohort in 3 months |
|
||||
| **Name** | "The $5K Sales Page Bootcamp" |
|
||||
| **Price** | $1,997 pay-in-full OR $797 × 3 |
|
||||
|
||||
Same modules. Same instructor. ~4x conversion. Lower refund rate (conditional guarantee qualifies).
|
||||
|
||||
**Lesson:** rename the outcome, add proof, install a real scarcity mechanic.
|
||||
|
||||
---
|
||||
|
||||
## Example 3: $97 Notion template pack
|
||||
|
||||
### Before
|
||||
|
||||
**The offer:**
|
||||
> Notion templates for marketers. $97. 20 templates included.
|
||||
|
||||
**Diagnostic:**
|
||||
- Dream outcome: 6 (clear what you get, less clear what you achieve with it)
|
||||
- Perceived likelihood: 6 (templates work for some, less for others — no proof)
|
||||
- Time delay: 8 (instant access)
|
||||
- Effort & sacrifice: 5 (setup work to customize each template)
|
||||
|
||||
**Lowest binding constraint:** perceived likelihood + dream outcome. "Will these actually save me time, for *my* setup?"
|
||||
|
||||
### After
|
||||
|
||||
| Component | What changed |
|
||||
|-----------|--------------|
|
||||
| **Core** | "The Marketing Ops Stack — 20 Notion templates that turn your scattered docs into a working marketing OS in one Saturday" — outcome-framed |
|
||||
| **Bonuses** | (1) 10-minute "do this first" Loom — speed bonus; (2) "Stack the templates" flowchart (visual setup map); (3) Lifetime updates as templates are added |
|
||||
| **Guarantee** | "30-day no-questions money-back" — unconditional, fits the price point |
|
||||
| **Scarcity** | Founding-buyer pricing — $97 for the first 200 buyers, then $147 |
|
||||
| **Name** | "The Marketing Ops Stack" |
|
||||
| **Price** | $97 pay-in-full |
|
||||
|
||||
Same templates. ~2x close rate from the same traffic. The differentiator was the "in one Saturday" outcome anchor and the Loom that proves the speed claim.
|
||||
|
||||
**Lesson:** for low-priced info products, the dream outcome and a fast first-win are the levers. Don't over-engineer the guarantee.
|
||||
|
||||
---
|
||||
|
||||
## Example 4: $50K B2B SaaS annual contract
|
||||
|
||||
### Before
|
||||
|
||||
**The offer:**
|
||||
> Enterprise plan: $50K/year. Includes unlimited users, all features, dedicated support.
|
||||
|
||||
**Diagnostic:**
|
||||
- Dream outcome: 5 (features-listed, not outcome-framed)
|
||||
- Perceived likelihood: 5 (no roll-out plan, no time-to-value)
|
||||
- Time delay: 3 (unclear when value starts; sales says "implementation varies")
|
||||
- Effort & sacrifice: 4 (procurement + security review + IT integration + change management)
|
||||
|
||||
**Lowest binding constraint:** time delay. Enterprise buyers can't tolerate "implementation varies."
|
||||
|
||||
### After
|
||||
|
||||
| Component | What changed |
|
||||
|-----------|--------------|
|
||||
| **Core** | "Production-ready in 30 days, ROI by quarter end" — time-anchored |
|
||||
| **Bonuses** | (1) Dedicated implementation engineer for 30 days; (2) Pre-built integration packs for top 5 platforms; (3) Custom training session for the buyer's team; (4) Quarterly business reviews with the buyer's CSM |
|
||||
| **Guarantee** | "Not in production by day 30? You don't pay until you are." SLA-based. |
|
||||
| **Scarcity** | Capacity-based: "We onboard 4 enterprise accounts per quarter. Next slot starts [date]." |
|
||||
| **Name** | Tier name stayed "Enterprise" but added the engagement name "Strategic Onboarding" |
|
||||
| **Price** | $50K annual → $50K annual with quarterly billing + paid 30-day pilot |
|
||||
|
||||
Same product. ~30% higher close rate, 50% shorter sales cycle. The pilot + SLA combination removed the procurement objection.
|
||||
|
||||
**Lesson:** for enterprise B2B, time-to-value IS the offer. Solve it explicitly.
|
||||
|
||||
---
|
||||
|
||||
## Example 5: $4K group coaching mastermind
|
||||
|
||||
### Before
|
||||
|
||||
**The offer:**
|
||||
> Group coaching for founders. $4K/quarter. Includes 12 calls and Slack.
|
||||
|
||||
**Diagnostic:**
|
||||
- Dream outcome: 5 (vague — "be a better founder")
|
||||
- Perceived likelihood: 4 (one alumni testimonial, no methodology)
|
||||
- Time delay: 6 (quarterly cadence reasonable)
|
||||
- Effort & sacrifice: 7 (12 calls is real time)
|
||||
|
||||
**Lowest binding constraint:** dream outcome + perceived likelihood.
|
||||
|
||||
### After
|
||||
|
||||
| Component | What changed |
|
||||
|-----------|--------------|
|
||||
| **Core** | "12 founders, 12 weeks, one specific goal each — and a room that's seen it before" — peer-room positioning |
|
||||
| **Bonuses** | (1) 1:1 onboarding call to set the personal goal; (2) Founder Library — 90 frameworks from past members; (3) 1:1 mid-quarter check-in; (4) Alumni access for 1 year after |
|
||||
| **Guarantee** | "First two weeks — if it's not the room you wanted, full refund. After that, you're in." |
|
||||
| **Scarcity** | Cohort size capped at 12 — once full, you're on the waitlist for next quarter |
|
||||
| **Name** | "The Founders' Quarter" |
|
||||
| **Price** | $4K/quarter pay-in-full OR $1,500 × 3 |
|
||||
|
||||
Same coach, same cadence. Higher close rate. Notably: members renew at ~70% (was ~35% before) because the "alumni access for 1 year" bonus changed the buying decision frame from "quarter" to "year."
|
||||
|
||||
**Lesson:** for coaching, the room IS the offer. Position the room, not the curriculum. Renewal-friendly bonuses lock in long-term LTV.
|
||||
|
||||
---
|
||||
|
||||
## Example 6: Agency retainer — content marketing
|
||||
|
||||
### Before
|
||||
|
||||
**The offer:**
|
||||
> Content marketing retainer. $8K/month. 4 articles per month + SEO strategy.
|
||||
|
||||
**Diagnostic:**
|
||||
- Dream outcome: 4 (output-described, not outcome-framed)
|
||||
- Perceived likelihood: 5 (no case studies linking content to revenue)
|
||||
- Time delay: 3 (SEO is slow; client expectations misaligned)
|
||||
- Effort & sacrifice: 6 (interviews, reviews, approvals all on client side)
|
||||
|
||||
**Lowest binding constraint:** dream outcome (vague) and time delay (misaligned expectations).
|
||||
|
||||
### After
|
||||
|
||||
| Component | What changed |
|
||||
|-----------|--------------|
|
||||
| **Core** | "We own the content engine. You get organic-driven sales meetings by month 9, with measurable revenue attribution." — outcome + timeline |
|
||||
| **Bonuses** | (1) Persona research kickoff (one-time); (2) Quarterly content audit + republish list; (3) Pre-vetted freelance writers with QA layer; (4) Quarterly executive readout |
|
||||
| **Guarantee** | "First 30 days is a paid pilot — 4 published pieces + 3 keyword roadmap. If at the end you don't see a clear 12-month path, we end the engagement, no balance owed." |
|
||||
| **Scarcity** | Capacity-based: "We take on 3 retainer clients per quarter. Next slot is [date]." |
|
||||
| **Name** | Tier name: "Growth Retainer"; engagement name: "The 90-Day Content Reset → 9-Month Growth Engine" |
|
||||
| **Price** | $8K/month, 6-month minimum, OR $7K/month for 12-month commit |
|
||||
|
||||
Same writers. Same SEO methodology. ~2x close rate. 60% of pilots convert to 12-month commits.
|
||||
|
||||
**Lesson:** for slow-cycle services (SEO, brand, content), the offer has to address the timeline explicitly. "Trust us, results in 6 months" doesn't sell; "paid pilot → milestone at day 30 → ramp" does.
|
||||
|
||||
---
|
||||
|
||||
## Pattern across all six examples
|
||||
|
||||
Look at the changes side-by-side:
|
||||
|
||||
| Example | Core change | Most important other change |
|
||||
|---------|-------------|----------------------------|
|
||||
| Fractional CMO | Named it, added scope | First-milestone guarantee |
|
||||
| Copywriting course | Outcome-framed, added proof | Case studies bonus |
|
||||
| Notion templates | "in one Saturday" anchor | First-step Loom bonus |
|
||||
| B2B SaaS | Time-to-value commitment | SLA-based guarantee + pilot |
|
||||
| Coaching mastermind | Positioned the room, not the coach | 1-year alumni access bonus |
|
||||
| Agency retainer | Outcome + timeline framing | Paid pilot guarantee |
|
||||
|
||||
**The pattern:** in every case, the price barely moved (or didn't move at all). What moved was the *structure* of the offer — naming, framing, guaranteeing, sequencing.
|
||||
|
||||
The price is the comparison. The value is the offer.
|
||||
@@ -0,0 +1,172 @@
|
||||
# Guarantee Design
|
||||
|
||||
A guarantee directly raises *perceived likelihood of achievement* (the buyer thinks: "they'll only offer this if they're confident") and lowers *effort & sacrifice* (less emotional risk). It's one of the highest-leverage levers in offer design.
|
||||
|
||||
The wrong guarantee hurts more than no guarantee. Pick the type that matches your business model.
|
||||
|
||||
## The eight guarantee types
|
||||
|
||||
| Type | What it promises | When it works | When it backfires |
|
||||
|------|------------------|---------------|-------------------|
|
||||
| 1. **Unconditional money-back** | "Refund anytime within X days, no questions" | Low-priced info, high-trust audience | High-priced/high-touch; refund risk eats margin |
|
||||
| 2. **Conditional money-back** | "Refund if you complete X and still don't see Y" | Courses, programs requiring effort | Sophisticated buyers; harder to honor publicly |
|
||||
| 3. **Better-than-money-back** | "If it doesn't work, full refund + $X" | Confident delivery, ample margin | If you fail; the few failures explode publicly |
|
||||
| 4. **Service-level / SLA** | "If we don't deliver X by Y, your money back" | Productized services, agency work | Vague SLAs you can't measure |
|
||||
| 5. **Performance-based** | "Pay only when X happens" (rev share, results-based) | Sophisticated B2B, high-confidence delivery | Long cycles, hard-to-attribute outcomes |
|
||||
| 6. **Anti-guarantee** | "No refunds. Make sure you want it." | Premium audiences, mature buyers | Confused / first-time buyers; reads cold |
|
||||
| 7. **Outcome-or-extension** | "If you don't get X by Y, we continue free" | Coaching, services with extendable time | Open-ended cost; choose with care |
|
||||
| 8. **Comparison guarantee** | "Beat [competitor]'s result or refund" | When you can credibly compare | When you can't measure the competitor cleanly |
|
||||
|
||||
---
|
||||
|
||||
## Picking the right one
|
||||
|
||||
Decision tree:
|
||||
|
||||
1. **What's your buyer's biggest perceived risk?**
|
||||
- "What if it doesn't work?" → money-back family (1, 2, 3)
|
||||
- "What if you don't deliver on time?" → SLA (4)
|
||||
- "What if I pay and get no results?" → performance-based (5) or outcome-or-extension (7)
|
||||
- "Is this real or scam?" → comparison or specificity-based (8)
|
||||
|
||||
2. **What's your refund tolerance?**
|
||||
- Can absorb refunds at scale → unconditional (1)
|
||||
- Need to qualify refunders → conditional (2)
|
||||
- Confident enough to add a bonus on top → better-than-money-back (3)
|
||||
- Can't afford refunds at all → anti-guarantee (6) or no guarantee + strong proof
|
||||
|
||||
3. **What's your buyer sophistication?**
|
||||
- Premium / mature buyers → anti-guarantee can work; "we don't do refunds" reads as confidence
|
||||
- First-time-in-category buyers → strong refund guarantee; they need permission to try
|
||||
- Sophisticated B2B → SLA or performance-based; they expect commercial terms
|
||||
|
||||
4. **How measurable is the outcome?**
|
||||
- Clean and measurable → performance-based, comparison, or outcome-or-extension
|
||||
- Fuzzy / subjective → money-back family with a conditional gate (you completed the work)
|
||||
|
||||
---
|
||||
|
||||
## Examples by business type
|
||||
|
||||
### Course / cohort
|
||||
|
||||
**Strong:** "Complete all six modules within 60 days, submit the final exercise, and if you haven't [specific outcome] we refund in full." Conditional on effort, clear on outcome.
|
||||
|
||||
**Weak:** "100% money-back guarantee." No conditions = refund magnet for buyers who never engaged.
|
||||
|
||||
### Coaching / consulting
|
||||
|
||||
**Strong:** "After the first two sessions, if you don't think the engagement will deliver, we end it and refund the unused balance." Mid-engagement off-ramp builds trust.
|
||||
|
||||
**Weak:** "Satisfaction guaranteed." Means nothing.
|
||||
|
||||
### Productized service / agency retainer
|
||||
|
||||
**Strong:** "First month is a paid pilot. At the end, if you don't see [specific milestone], you don't pay for month 2 and we end on good terms." Clear gate, clear out.
|
||||
|
||||
**Weak:** "We'll work until you're happy." Open-ended cost. Don't.
|
||||
|
||||
### High-ticket info product (community, mastermind)
|
||||
|
||||
**Strong (premium audience):** "No refunds. The application process is rigorous because the value is real. If you're not sure, don't apply yet." Anti-guarantee works here.
|
||||
|
||||
**Weak (premium audience):** Generic 30-day refund. Reads cheap.
|
||||
|
||||
### Low-ticket info product (template, swipe file)
|
||||
|
||||
**Strong:** "30-day no-questions refund." The transactional bar is "I bought it, looked at it, didn't want it." Unconditional fits.
|
||||
|
||||
**Weak:** No guarantee. The buyer's risk is too high for the price.
|
||||
|
||||
### SaaS
|
||||
|
||||
**Strong:** Free trial *or* annual-prepay-with-money-back-in-first-30-days. Reduces friction without locking in unhappy users.
|
||||
|
||||
**Weak:** "Cancel anytime" alone — not a guarantee, just standard SaaS terms.
|
||||
|
||||
### Direct response / paid traffic
|
||||
|
||||
**Strong:** Double-your-money-back or comparable risk inversion. Direct-response buyers expect risk-reversal-heavy offers.
|
||||
|
||||
**Weak:** Vanilla 30-day refund. Doesn't differentiate from every other ad on the platform.
|
||||
|
||||
---
|
||||
|
||||
## Writing the guarantee
|
||||
|
||||
The guarantee text matters. Patterns that work:
|
||||
|
||||
**Specific terms:**
|
||||
> If, after completing the first 4 weeks of the program, you can't point to one specific business outcome you've achieved, email us and we'll refund 100%.
|
||||
|
||||
**Confident tone:**
|
||||
> We know this works. If it doesn't for you, we don't want your money.
|
||||
|
||||
**Acknowledge the awkwardness:**
|
||||
> Guarantees feel slimy. Here's ours anyway: if you do the work in modules 1–3 and don't see meaningful traction, we refund.
|
||||
|
||||
**Patterns that don't work:**
|
||||
|
||||
- "100% satisfaction guaranteed!" — generic, low-trust
|
||||
- "Lifetime guarantee" — meaningless without conditions
|
||||
- Multiple stacked guarantees — sophistication-collapsing
|
||||
- Guarantees full of legalese — buyers skim and assume the worst
|
||||
|
||||
---
|
||||
|
||||
## Common mistakes
|
||||
|
||||
### Promising more than you can deliver
|
||||
|
||||
"Double your revenue or your money back + $1,000." If even 1 in 50 buyers fails and gets the bonus refund + writes a public review, the offer is permanently damaged.
|
||||
|
||||
Stress-test: what happens if 10% of buyers invoke the guarantee?
|
||||
|
||||
### Conditional guarantees with too many conditions
|
||||
|
||||
"Refund if you watched all 24 modules, completed the 6 exercises, attended every live call, and posted in the community at least once per week."
|
||||
|
||||
Buyers read this as "they made it impossible to actually get a refund." Trust drops.
|
||||
|
||||
Two conditions max. Three only if they're closely related (e.g., "completed the course AND submitted the final project AND emailed us a question").
|
||||
|
||||
### Hiding the guarantee in the fine print
|
||||
|
||||
If your guarantee is your strongest perceived-likelihood lever, *put it on the sales page in 24pt text*. Move it above the buy button.
|
||||
|
||||
### Forgetting to test it
|
||||
|
||||
Re-read your guarantee text every six months. The wording that worked a year ago may now be undermined by something you've changed about your offer.
|
||||
|
||||
### Treating guarantees as a substitute for proof
|
||||
|
||||
Strong proof + weak guarantee > strong guarantee + weak proof. Order matters. Build proof first, then layer on the guarantee.
|
||||
|
||||
---
|
||||
|
||||
## The honest case for NO guarantee
|
||||
|
||||
Anti-guarantees ("no refunds, this is final") work when:
|
||||
|
||||
- Buyer sophistication is high
|
||||
- Application or qualification process precedes the sale
|
||||
- Price is premium-to-luxury
|
||||
- Brand is established
|
||||
- Proof is overwhelming
|
||||
|
||||
What you're saying: "We don't need a guarantee because the work is real, the buyer has self-qualified, and we won't engage in transactional refund games."
|
||||
|
||||
The wrong audience reads this as cold or scammy. The right audience reads it as confidence. Know your buyer.
|
||||
|
||||
---
|
||||
|
||||
## The diagnostic
|
||||
|
||||
When auditing an offer with no guarantee (or a weak one), ask:
|
||||
|
||||
1. **What's the buyer's actual risk?** Make it concrete. ("$2K and I might not get more clients.")
|
||||
2. **What guarantee structure reverses that specific risk?** Match it to one of the eight types.
|
||||
3. **What's your honest refund tolerance?** Calculate refund rate × refund cost; can you sustain it?
|
||||
4. **Does the guarantee match your audience sophistication?** Premium buyers want anti-guarantee; first-time buyers want unconditional.
|
||||
|
||||
Most offers don't have the wrong guarantee — they have *no* guarantee at all. Adding any guarantee is almost always a lift. Adding the right one is the lever.
|
||||
@@ -0,0 +1,203 @@
|
||||
# Offer Anatomy
|
||||
|
||||
A complete offer has six components. Skip any one and conversion suffers — usually noticeably.
|
||||
|
||||
## The six components
|
||||
|
||||
| # | Component | Question it answers | Where it fails |
|
||||
|---|-----------|---------------------|----------------|
|
||||
| 1 | **Core deliverable** | What do they get? | Too vague, or pitched as features instead of outcome |
|
||||
| 2 | **Bonus stack** | What else do they get that makes the core feel undervalued? | Either no bonuses, or inflated/fake bonuses |
|
||||
| 3 | **Guarantee** | What happens if it doesn't work? | None, wrong type, or over-promising |
|
||||
| 4 | **Scarcity / urgency** | Why now, not later? | None, fake, or destructively manipulative |
|
||||
| 5 | **Name** | What is this thing called? | Generic, internal-jargon, or no name at all |
|
||||
| 6 | **Price + payment structure** | What do they pay and how? | Single number with no payment flexibility |
|
||||
|
||||
---
|
||||
|
||||
## 1. Core deliverable
|
||||
|
||||
The thing they actually get.
|
||||
|
||||
### Define it as an outcome, not a feature list
|
||||
|
||||
- **Feature-pitched (weak):** "6 modules, 24 lessons, weekly calls, private community."
|
||||
- **Outcome-pitched (strong):** "A working customer-acquisition system that brings 5 qualified leads per week within 60 days — built with you, not handed to you."
|
||||
|
||||
The features still matter — buyers want to know what they're getting — but the *frame* is the outcome. Features support the outcome, they don't replace it.
|
||||
|
||||
### Define the scope explicitly
|
||||
|
||||
What's in. What's out. What's optional. Buyers buy clarity; ambiguity erodes perceived likelihood.
|
||||
|
||||
Example scope statement:
|
||||
```
|
||||
Includes:
|
||||
- 90-day program with weekly live calls (recorded)
|
||||
- Private Slack with daily founder access
|
||||
- 12 fill-in-the-blank templates
|
||||
- 1 90-minute strategy session with a senior strategist
|
||||
|
||||
Doesn't include:
|
||||
- 1:1 calls outside the strategy session
|
||||
- Implementation of the work (you/your team does this; we coach)
|
||||
- Tools and software (you provide; we recommend specific stacks)
|
||||
```
|
||||
|
||||
### Match the depth to the buyer's stage of awareness
|
||||
|
||||
Sophisticated buyers want the methodology and scope. New-to-category buyers want the dream outcome and proof. Read your audience.
|
||||
|
||||
---
|
||||
|
||||
## 2. Bonus stack
|
||||
|
||||
What you add to make the core feel undervalued at the asking price.
|
||||
|
||||
Bonuses do three jobs at once:
|
||||
1. **Raise perceived value** of the total offer
|
||||
2. **Lower perceived risk** — even if the core underdelivers, "I got X for free"
|
||||
3. **Close specific objections** — each bonus can target a different buying objection
|
||||
|
||||
### How to construct bonuses
|
||||
|
||||
For each major objection your buyer has, add a bonus that closes it:
|
||||
|
||||
| Objection | Targeted bonus |
|
||||
|-----------|---------------|
|
||||
| "I don't have time to implement this" | Done-for-you setup, day 1 |
|
||||
| "I don't know which tools to use" | Pre-vetted tool stack with discount codes |
|
||||
| "What if I get stuck?" | 30-day async support |
|
||||
| "I'm not sure my team will buy in" | Stakeholder pitch deck for your team |
|
||||
| "I've tried something like this before and it didn't work" | Case study of someone in your exact situation |
|
||||
|
||||
A 4-bonus stack that closes 4 specific objections converts massively better than a 4-bonus stack of generic "extras."
|
||||
|
||||
### Don't inflate
|
||||
|
||||
"$50,000 in bonuses!" on a $500 offer reads as scam. The asymmetry destroys trust.
|
||||
|
||||
Bonuses should:
|
||||
- Have a stated value the buyer can verify (compare to a comparable product)
|
||||
- Total to less than 2x the price (e.g., a $1K offer can have ~$1.5K in bonuses comfortably)
|
||||
- Be things you'd actually sell separately if you wanted
|
||||
|
||||
For the full bonus-stacking framework, see [bonus-stacking.md](bonus-stacking.md).
|
||||
|
||||
---
|
||||
|
||||
## 3. Guarantee
|
||||
|
||||
What happens if it doesn't work.
|
||||
|
||||
A guarantee directly raises perceived likelihood of achievement (the buyer thinks: "they'll only offer this if they're sure"). It also lowers effort & sacrifice (less emotional risk).
|
||||
|
||||
The wrong guarantee can hurt:
|
||||
- Over-promising guarantees attract refund-seekers
|
||||
- Generic "100% guaranteed" with no conditions reads as legally unenforceable
|
||||
- No guarantee at all signals you're not confident
|
||||
|
||||
The right type depends on your business model, refund risk tolerance, and buyer sophistication. For the full taxonomy, see [guarantee-design.md](guarantee-design.md).
|
||||
|
||||
---
|
||||
|
||||
## 4. Scarcity / urgency
|
||||
|
||||
The reason to buy now, not later.
|
||||
|
||||
Two flavors:
|
||||
- **Scarcity** — limited *quantity* (cohort size, seats, inventory, batch)
|
||||
- **Urgency** — limited *time* (cohort deadline, season, bonus expiry)
|
||||
|
||||
The bar: **the scarcity has to be real.** Fake countdown timers and "only 3 spots left" lies work once and torch trust permanently. The internet is small; you will be caught.
|
||||
|
||||
Common honest scarcity formats:
|
||||
- Cohort closes Friday (because the cohort actually starts Monday)
|
||||
- Founding-member pricing for the first 20 customers (because you're capacity-constrained)
|
||||
- Seasonal product or service (because demand is seasonal)
|
||||
- Bonus expires at launch end (because the bonus is your time)
|
||||
- Capacity-based service tier (because you literally can't take more clients)
|
||||
|
||||
For full guidance on creating real scarcity, see [scarcity-urgency.md](scarcity-urgency.md).
|
||||
|
||||
---
|
||||
|
||||
## 5. Name
|
||||
|
||||
What this thing is called.
|
||||
|
||||
A named offer beats an unnamed offer for three reasons:
|
||||
1. **Repeatability** — buyers can tell their friend about it
|
||||
2. **Distinction** — a name makes it a *thing*, not a generic service
|
||||
3. **Pricing power** — branded offers can charge more than the same delivery sold as a service
|
||||
|
||||
### Naming patterns that work
|
||||
|
||||
- **Outcome-named:** "The 30-Day Activation Sprint" — names what they get
|
||||
- **Methodology-named:** "The VAULT Framework" — names how you do it
|
||||
- **Identity-named:** "Founder Marketing OS" — names who it's for
|
||||
- **Compression-named:** "5-Day Cohort" — names the timing/structure
|
||||
|
||||
### Naming patterns that don't work
|
||||
|
||||
- **Generic descriptors:** "Marketing Coaching Program" — forgettable
|
||||
- **Internal jargon:** "Tier 2 Standard" — buyer can't repeat
|
||||
- **Course-bro:** "The Money-Making Machine" — pattern-matches to scam
|
||||
- **Pun-overload:** "GrowthGoGetter" — reads as low-status
|
||||
|
||||
### Practical test
|
||||
|
||||
Can a buyer text a friend: "I just signed up for *the [name]*. It's $X and you get [one-line outcome]"? If yes, the name works. If no, rename.
|
||||
|
||||
---
|
||||
|
||||
## 6. Price + payment structure
|
||||
|
||||
The price is the obvious part. The structure is the underrated part.
|
||||
|
||||
### Price isn't a number, it's a comparison
|
||||
|
||||
Buyers compare the price to:
|
||||
- The dream outcome (does this get me the result I want?)
|
||||
- The next-best alternative (what else could I buy?)
|
||||
- The cost of doing nothing (what does the status quo cost me?)
|
||||
- Other items in your own catalog (anchor pricing)
|
||||
|
||||
You can move price perception without changing the number by:
|
||||
- Showing the cost of doing nothing more vividly
|
||||
- Anchoring against a higher-priced alternative
|
||||
- Sequencing other items in your catalog at higher prices first
|
||||
|
||||
### Payment structure is its own lever
|
||||
|
||||
Same total price, different structures convert very differently:
|
||||
|
||||
| Structure | When it works | Trade-off |
|
||||
|-----------|---------------|-----------|
|
||||
| **Pay in full** | High-trust buyers, lower price points | Highest perceived commitment, smallest buyer pool |
|
||||
| **Pay in 2-4 installments** | Mid-range price, hesitant buyers | More buyers, payment defaults |
|
||||
| **Monthly subscription** | SaaS, ongoing services | Annuity revenue, churn risk |
|
||||
| **Pay-after-results** | High-confidence delivery, sophisticated buyers | Cash flow lag, fewer disputes |
|
||||
| **Down payment + balance on delivery** | Services with milestone-based delivery | Balance risk on backend |
|
||||
| **Free trial → paid** | Low-friction SaaS, info products | Conversion drop-off |
|
||||
|
||||
Often the right move isn't lowering price — it's adding a payment plan. Same $6K price, "$6K today" vs "$2K × 3 monthly" converts very differently.
|
||||
|
||||
---
|
||||
|
||||
## Putting it together: an example
|
||||
|
||||
A B2B fractional CMO service.
|
||||
|
||||
| Component | Weak version | Strong version |
|
||||
|-----------|--------------|----------------|
|
||||
| **Core** | "Fractional CMO services" | "8-week marketing audit + 90-day execution plan, delivered by a CMO who's done it for 3+ similar companies" |
|
||||
| **Bonuses** | None | (1) 1:1 weekly check-ins for 90 days; (2) pre-vetted execution-partner introductions; (3) board-deck for marketing strategy section |
|
||||
| **Guarantee** | None | "If after the 8-week audit you don't have a clear 90-day plan you'd run yourself, you don't pay the audit fee" |
|
||||
| **Scarcity** | None | "We take 2 engagements per quarter — next slot opens [date]" |
|
||||
| **Name** | "fCMO Consulting" | "The 90-Day Marketing Reset" |
|
||||
| **Price** | "$15K, paid up front" | "$15K → $5K to start, $5K at week 8, $5K at week 16" |
|
||||
|
||||
Same delivery. Same person. Different offer. Different conversion.
|
||||
|
||||
The point: most "we need to lower our price" conversations are actually "we have one of six components missing or weak" conversations.
|
||||
@@ -0,0 +1,240 @@
|
||||
# Offer Formats by Business Type
|
||||
|
||||
The right offer format depends on what you sell. The same six components (core, bonuses, guarantee, scarcity, name, price) get assembled differently by business type.
|
||||
|
||||
This reference is organized by business type. Find yours, then use the format as a starting point — not a fixed recipe.
|
||||
|
||||
---
|
||||
|
||||
## Service / freelance
|
||||
|
||||
You sell your time and skill.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | A scoped engagement with a specific deliverable and timeline |
|
||||
| **Bonuses** | Templates, frameworks, post-engagement support, tool stack |
|
||||
| **Guarantee** | First-milestone gate (paid pilot or first-deliverable refund) |
|
||||
| **Scarcity** | Capacity-based (next slot opens [date]) |
|
||||
| **Name** | Methodology-named or outcome-named (e.g., "The 30-Day Activation Sprint") |
|
||||
| **Price** | Project-based with down-payment, or monthly retainer |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **Naming matters disproportionately** — services without named offers compete on price; named services compete on positioning
|
||||
- **Scope creep is the offer killer** — define what's in, out, and optional, *in writing*, before the engagement starts
|
||||
- **Bonuses should compound the deliverable** — templates and frameworks that make the buyer self-sufficient after the engagement, not during
|
||||
|
||||
### Productizing the offer
|
||||
|
||||
Move from "I sell consulting" to "I sell the 8-Week Marketing Reset." Same delivery, different offer.
|
||||
|
||||
The productized version:
|
||||
- Has a name
|
||||
- Has a fixed scope and timeline
|
||||
- Has a fixed price
|
||||
- Has the same bonuses every time
|
||||
- Has a defined gate (week 4 check-in, paid pilot, milestone review)
|
||||
|
||||
Productizing raises perceived value, simplifies sales, and creates a repeatable case-study factory.
|
||||
|
||||
---
|
||||
|
||||
## Course (async, cohort-based, live)
|
||||
|
||||
You sell structured learning.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | The curriculum + delivery format |
|
||||
| **Bonuses** | Templates, swipe files, case studies, community access |
|
||||
| **Guarantee** | Conditional money-back (completion-gated) |
|
||||
| **Scarcity** | Cohort scarcity (enrollment closes [date]) |
|
||||
| **Name** | Outcome-named or methodology-named |
|
||||
| **Price** | Pay-in-full or 2–4 installments |
|
||||
|
||||
### Async vs cohort-based
|
||||
|
||||
| Decision | Async | Cohort |
|
||||
|----------|-------|--------|
|
||||
| **Pricing** | Lower ($297–$1,997) | Higher ($1,497–$5,000+) |
|
||||
| **Scarcity** | Bonus expiry, price increases | Cohort start date |
|
||||
| **Guarantee** | Generous unconditional | Conditional on completion |
|
||||
| **Conversion mechanic** | Email funnel, evergreen webinar | Launch window + cohort deadline |
|
||||
| **Default bonus** | Templates, swipes | Slack + office hours + 1:1 review |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **Completion is the marketing asset** — every completer is a case study. Engineer the first win in week 1.
|
||||
- **Cohort scarcity must be real** — if "doors close Friday" is followed by "doors reopen Monday because we extended the cohort," the trick gets noticed
|
||||
- **Refund design matters more than refund rate** — a generous-sounding guarantee with smart conditions converts well and refunds rarely
|
||||
|
||||
---
|
||||
|
||||
## Coaching (1:1, group, mastermind)
|
||||
|
||||
You sell access to your expertise applied to their specific situation.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | Sessions + asynchronous access + specific outcome focus |
|
||||
| **Bonuses** | Resources from your library, intro to network, post-engagement check-ins |
|
||||
| **Guarantee** | Outcome-or-extension or first-two-sessions out |
|
||||
| **Scarcity** | Capacity-based (N spots / quarter) |
|
||||
| **Name** | Identity-named or outcome-named (e.g., "Founder Marketing Mastermind") |
|
||||
| **Price** | Monthly retainer or 3/6/12-month engagement |
|
||||
|
||||
### 1:1 vs group
|
||||
|
||||
| Decision | 1:1 | Group / mastermind |
|
||||
|----------|-----|---------------------|
|
||||
| **Pricing** | $1,500–$10,000+/mo | $497–$2,500+/mo |
|
||||
| **Scarcity** | Capacity (4–10 1:1 clients) | Cohort size (8–30 members) |
|
||||
| **Guarantee** | First-two-sessions out | Trial period, no refunds after |
|
||||
| **Bonuses** | Custom resources, intros | Group access, peer accountability, library access |
|
||||
| **Default delivery** | Weekly or biweekly sessions | Monthly group calls + community |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **Identity is the offer** — group coaching is often more about being in the room with peers than about the coach's instruction. Name the room, not the coach.
|
||||
- **Onboarding is part of the offer** — a sloppy intake destroys perceived likelihood
|
||||
- **Renewal is the real conversion event** — design for the 6-month decision, not the first-month decision
|
||||
|
||||
---
|
||||
|
||||
## Info product (guide, swipe file, template pack, community)
|
||||
|
||||
You sell packaged knowledge or assets.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | The asset(s) + lifetime access |
|
||||
| **Bonuses** | Adjacent assets, walkthroughs, templates |
|
||||
| **Guarantee** | Generous unconditional (30-day no-questions) |
|
||||
| **Scarcity** | Bonus expiry, price-increase scheduling |
|
||||
| **Name** | Outcome-named, often punchy and specific |
|
||||
| **Price** | $29–$497, pay-in-full |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **The first-impression matters disproportionately** — the buyer opens it once. If the first 5 minutes don't feel premium, they don't engage with the rest
|
||||
- **Quick-start is a bonus** — pair the asset with a 10-minute "do this first" walkthrough
|
||||
- **Lifetime access is implicit pricing** — clarify what "lifetime" means (yours, the product's, until you sunset it)
|
||||
|
||||
---
|
||||
|
||||
## High-ticket B2B ($5K+ ACV, sales-led)
|
||||
|
||||
You sell to companies with a sales conversation.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | A multi-month engagement or annual contract |
|
||||
| **Bonuses** | Onboarding, training, integration, dedicated CSM |
|
||||
| **Guarantee** | SLA, performance-based, or pilot-gated |
|
||||
| **Scarcity** | Quarter-end pricing, capacity (N onboardings/quarter), tier limits |
|
||||
| **Name** | Internal-stable (e.g., "Enterprise Plan") + named engagement type (e.g., "Strategic Onboarding") |
|
||||
| **Price** | Annual contract with quarterly payment, often custom |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **Buying committee, not buyer** — the offer has to land with the champion, the economic buyer, and the influencer simultaneously
|
||||
- **Procurement is the offer** — your terms (payment, NET 60, security review, MSA) are part of the offer; rigid terms lose deals
|
||||
- **Pilot offers convert sophisticated buyers** — "30-day paid pilot, decide to continue at end" reduces decision risk
|
||||
- **The CSM is part of the offer** — buyers consistently rate post-sale relationship as part of the offer-perceived-value
|
||||
|
||||
---
|
||||
|
||||
## Agency retainer
|
||||
|
||||
You sell ongoing service delivery.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | Monthly deliverables + dedicated team + reporting cadence |
|
||||
| **Bonuses** | Strategy sessions, tool access, audit credits, library access |
|
||||
| **Guarantee** | Month-1 paid pilot or 90-day out clause |
|
||||
| **Scarcity** | Capacity (N clients / vertical / quarter) |
|
||||
| **Name** | Tier-named ("Growth," "Scale," "Enterprise") + service line |
|
||||
| **Price** | Monthly retainer with discount for annual commit |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **Onboarding velocity is the offer** — agencies that take 6 weeks to start delivering lose to agencies that deliver something in week 1
|
||||
- **Reporting is part of the offer** — clean, monthly, action-oriented reporting reduces churn more than additional deliverables
|
||||
- **Tier upgrades are the easiest revenue** — design tiers with clear value-step-ups so upgrade conversations are obvious
|
||||
|
||||
---
|
||||
|
||||
## Self-serve SaaS
|
||||
|
||||
You sell a tool with tiered subscriptions.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | Tiered subscription with clear feature differentiation |
|
||||
| **Bonuses** | Free onboarding, templates, integrations, partner discounts |
|
||||
| **Guarantee** | Free trial OR annual-with-30-day-refund |
|
||||
| **Scarcity** | Founding-pricing for first N customers, or seasonal launches |
|
||||
| **Name** | Tier-named ("Starter," "Pro," "Team," "Enterprise") |
|
||||
| **Price** | Monthly or annual with discount, value-metric-based |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **Pricing tier > offer construction** — for self-serve SaaS, packaging and value metric do more work than guarantees and bonuses. Use the `pricing` skill.
|
||||
- **Free trial design IS offer design** — length, gated features, credit-card-required vs not, automatic conversion. Each is an offer decision.
|
||||
- **Annual prepay is the offer lever** — same product, different commitment, often 20–40% discount. Many SaaS conversion lifts come from improving the annual offer, not the monthly.
|
||||
|
||||
For SaaS, this skill is supplemental. Read [`pricing`](../../pricing/SKILL.md) first.
|
||||
|
||||
---
|
||||
|
||||
## Direct response / paid traffic
|
||||
|
||||
You sell from a sales page or VSL to cold traffic.
|
||||
|
||||
### Default format
|
||||
|
||||
| Component | Default |
|
||||
|-----------|---------|
|
||||
| **Core** | The "thing" + clear payoff |
|
||||
| **Bonuses** | Heavy bonus stack (5–7 bonuses, layered values) |
|
||||
| **Guarantee** | Aggressive risk reversal (better-than-money-back, double guarantee) |
|
||||
| **Scarcity** | Real time-bound (launch window, evergreen with hard close) |
|
||||
| **Name** | Hooky, often pattern-interrupt |
|
||||
| **Price** | Often single-payment with payment plan offered |
|
||||
|
||||
### What to watch
|
||||
|
||||
- **Direct-response buyers expect aggression** — quiet, premium-feeling offers convert badly on cold paid traffic. The aesthetic of the page matters as much as the offer.
|
||||
- **Refund rates can be 10–20%** — bake this into the math. If margin can't survive 15% refunds, restructure.
|
||||
- **The first 7 seconds determine the rest** — hook, then offer
|
||||
|
||||
This format is high-skill. If you're not from a direct-response background, hire someone or partner with someone who is.
|
||||
|
||||
---
|
||||
|
||||
## Choosing your format
|
||||
|
||||
If you're not sure which format applies, pick the closest match and adapt. The biggest mistake is borrowing a format from a different business type (e.g., applying direct-response bonus stacking to a premium B2B service — wrong audience, wrong aesthetic).
|
||||
|
||||
Two diagnostic questions:
|
||||
|
||||
1. **Who buys it, and how sophisticated are they?** Premium B2B and direct-response cold traffic both buy, but they need different offers.
|
||||
2. **What's the dominant constraint?** Service businesses are capacity-constrained, SaaS is pricing-tier-constrained, courses are cohort/season constrained. Match the scarcity format to the real constraint.
|
||||
|
||||
For worked examples by business type, see [examples.md](examples.md).
|
||||
@@ -0,0 +1,175 @@
|
||||
# Scarcity & Urgency
|
||||
|
||||
The reason to buy now, not later.
|
||||
|
||||
This is the most misused offer lever in the industry. Done right, it's a meaningful conversion lift and a respect-the-buyer's-time gesture. Done wrong (fake countdown timers, lies about inventory), it converts once and torches trust permanently.
|
||||
|
||||
The repo voice: **only ship real scarcity.** If the scarcity is fake, take it off the page.
|
||||
|
||||
## Scarcity vs urgency
|
||||
|
||||
| | What it limits | Examples |
|
||||
|---|---|---|
|
||||
| **Scarcity** | Quantity | Cohort size, seats, inventory, batch, capacity |
|
||||
| **Urgency** | Time | Cohort deadline, season, bonus expiry, price increase |
|
||||
|
||||
Both work via the same mechanism — they convert "I'll think about it" into "decide now." The difference is what enforces the decision: a limit on how many, or a limit on when.
|
||||
|
||||
---
|
||||
|
||||
## Honest scarcity formats
|
||||
|
||||
The bar: **the constraint has to be real.** Here are the formats that work without lying.
|
||||
|
||||
### Capacity-based scarcity
|
||||
|
||||
You can only deliver to N customers at a time. The next slot opens when one finishes.
|
||||
|
||||
> "We take 2 fractional CMO engagements per quarter. Next slot opens September 15."
|
||||
|
||||
Works for: services, agencies, coaching, consulting, anything labor-bound.
|
||||
|
||||
### Cohort scarcity
|
||||
|
||||
The class starts on a date. After the date, the door closes until the next cohort.
|
||||
|
||||
> "Cohort 7 starts October 1. Doors close September 28. Next cohort: January."
|
||||
|
||||
Works for: courses, programs, group coaching, anything synchronous.
|
||||
|
||||
### Founding-member pricing
|
||||
|
||||
The first N buyers get a different price. After that, the price goes up.
|
||||
|
||||
> "Founding pricing — $497/mo for the first 50 members. After we hit 50, the price moves to $797/mo."
|
||||
|
||||
Works for: SaaS, communities, memberships. Critical: actually raise the price when you hit 50. Otherwise it was a lie.
|
||||
|
||||
### Inventory-based scarcity
|
||||
|
||||
You have N units. When they're gone, they're gone.
|
||||
|
||||
> "We're only producing 100 of the print edition. Sold out, no reprints."
|
||||
|
||||
Works for: physical products, limited-run digital, bespoke services.
|
||||
|
||||
### Seasonal scarcity
|
||||
|
||||
Demand or capacity is seasonal.
|
||||
|
||||
> "Tax-prep service for Q1 2026 closes January 15. After that, we focus on existing clients only until April."
|
||||
|
||||
Works for: tax, retail Q4, events, education enrollment, anything calendar-bound.
|
||||
|
||||
### Bonus expiry
|
||||
|
||||
A bonus is available only until X date. The core offer stays the same; the *added value* expires.
|
||||
|
||||
> "Order by Friday and the 1:1 onboarding session is included. After Friday, the offer is the same but onboarding is +$497."
|
||||
|
||||
Works for: anything with a launch window. Critical: actually remove the bonus when the date hits.
|
||||
|
||||
### Price-increase scheduling
|
||||
|
||||
The price goes up on a date. Communicate it transparently.
|
||||
|
||||
> "On November 1, the program moves from $1,997 to $2,497. Anyone enrolled before November 1 keeps the $1,997 price for life."
|
||||
|
||||
Works for: courses, SaaS, communities. Builds credibility because the buyer can verify it later.
|
||||
|
||||
---
|
||||
|
||||
## Fake scarcity to avoid
|
||||
|
||||
Pattern-match and rip these off your page:
|
||||
|
||||
### Countdown timers that reset
|
||||
|
||||
The timer hits 0:00 and refreshes. The buyer comes back tomorrow, same timer, same urgency. Every buyer who notices loses trust.
|
||||
|
||||
If you use a countdown, it ends on a real date. After that date, the discount or bonus actually ends — verifiably.
|
||||
|
||||
### "Only 3 spots left"
|
||||
|
||||
Especially on digital products where there's no capacity constraint. Especially when the number stays at "3" for weeks.
|
||||
|
||||
Use this only when the constraint is real (cohort, capacity, inventory) AND when the number reflects reality.
|
||||
|
||||
### Manufactured FOMO
|
||||
|
||||
"127 people are looking at this page right now."
|
||||
|
||||
These can be honest on some platforms (Booking.com etc.) when they reflect actual traffic. They're dishonest when fabricated. Buyers increasingly assume fabrication.
|
||||
|
||||
### Bonus "stacking" that's always available
|
||||
|
||||
"This bonus expires at midnight!" — but every page on the site says the same thing at midnight every night.
|
||||
|
||||
The bonus has to actually expire, or the line is a lie.
|
||||
|
||||
### "Last chance" emails for things that aren't actually last chance
|
||||
|
||||
Repeated "FINAL HOURS" emails that send weekly. Every recipient who notices unsubscribes or stops opening.
|
||||
|
||||
Use "last chance" once. If you use it multiple times, you've taught your list that "last chance" is meaningless.
|
||||
|
||||
---
|
||||
|
||||
## Why fake scarcity is uniquely costly
|
||||
|
||||
Buyers compare notes. The internet is small.
|
||||
|
||||
- One Reddit post about a fake countdown becomes the top Google result for your brand
|
||||
- One screenshot of "only 3 left" staying at 3 for a month becomes a viral thread
|
||||
- One "last chance" email that wasn't goes into a "marketing fails" newsletter
|
||||
|
||||
Real scarcity converts ~the same as fake scarcity at the moment of purchase. The difference shows up at month 6, when fake-scarcity offers are facing trust collapse and real-scarcity offers are still compounding.
|
||||
|
||||
If you have to fake it, you don't have an offer-design problem — you have a value-equation problem. Go back to [value-equation.md](value-equation.md).
|
||||
|
||||
---
|
||||
|
||||
## When scarcity isn't needed
|
||||
|
||||
Some offers don't need scarcity:
|
||||
|
||||
- **Subscription products** that customers can cancel anytime — the natural friction is low enough
|
||||
- **Low-priced impulse products** ($5–30) — the deliberation is short; scarcity feels forced
|
||||
- **Premium / luxury brands** — scarcity is implicit in the positioning; explicit scarcity reads as low-status
|
||||
- **High-trust audiences** who already know they'll buy — scarcity is unnecessary friction
|
||||
|
||||
Don't force scarcity into offers that don't need it. The forced version is worse than no scarcity.
|
||||
|
||||
---
|
||||
|
||||
## The diagnostic
|
||||
|
||||
For an existing offer with weak or no scarcity:
|
||||
|
||||
1. **Is there a real constraint?** Capacity, cohort, inventory, season, batch. Find the real one.
|
||||
2. **What's the honest version of that constraint?** Write it in plain English.
|
||||
3. **Can the buyer verify it?** If you say "founding pricing for the first 50 members," can the buyer see the count?
|
||||
4. **Are you willing to actually enforce it?** When the constraint hits, do you have the discipline to actually close the door / raise the price / remove the bonus?
|
||||
5. **Where on the page does the scarcity appear?** It should be next to the buy button, not buried.
|
||||
|
||||
If you can't find a real constraint, don't ship scarcity. The "trick" of fake scarcity is one of the most expensive shortcuts in marketing. The honest version is usually cheaper than people think — every business has *some* real constraint (capacity, calendar, batch, attention).
|
||||
|
||||
---
|
||||
|
||||
## Pairing with the rest of the offer
|
||||
|
||||
Scarcity is the final lever. It only works if the rest of the offer is strong.
|
||||
|
||||
- Strong offer + real scarcity = the buyer decides now
|
||||
- Weak offer + scarcity = the buyer decides not to buy, faster
|
||||
|
||||
If conversions are bad, scarcity is rarely the first thing to fix. Run the diagnostic from [value-equation.md](value-equation.md) first.
|
||||
|
||||
The order is:
|
||||
1. Strong dream outcome
|
||||
2. Specific perceived likelihood (proof + methodology + guarantee)
|
||||
3. Compressed time delay
|
||||
4. Reduced effort & sacrifice
|
||||
5. *Then* scarcity to get the decision now
|
||||
|
||||
Scarcity is the close, not the offer.
|
||||
@@ -0,0 +1,134 @@
|
||||
# The Value Equation
|
||||
|
||||
The single most useful frame for offer design. Originated in Alex Hormozi's *$100M Offers*; the underlying idea (multiply benefits, divide costs) is much older — direct-response copywriters have been doing it for a century.
|
||||
|
||||
## The formula
|
||||
|
||||
```
|
||||
Dream Outcome × Perceived Likelihood of Achievement
|
||||
Value = ─────────────────────────────────────────────────────────
|
||||
Time Delay × Effort & Sacrifice
|
||||
```
|
||||
|
||||
The customer compares the *Value* score to the *Price*. If Value > Price, they buy. If not, they don't, no matter how good the copy is.
|
||||
|
||||
**Price is the comparison, not the value.** Most "lower the price" requests are actually "raise the numerator or lower the denominator" requests.
|
||||
|
||||
---
|
||||
|
||||
## Lever 1: Dream Outcome (numerator)
|
||||
|
||||
What the customer *actually* wants — usually one or two levels above the surface ask.
|
||||
|
||||
### Surface ask → dream outcome
|
||||
|
||||
| Surface ask | Dream outcome |
|
||||
|-------------|---------------|
|
||||
| "I want a website" | "I want more qualified leads I can close" |
|
||||
| "I want to learn copywriting" | "I want to write copy clients pay me $5K+ per project for" |
|
||||
| "I want a meal plan" | "I want to feel confident in a swimsuit on a beach in 12 weeks" |
|
||||
| "I want fitness coaching" | "I want my back pain gone so I can pick up my kids without thinking about it" |
|
||||
| "I want a Notion template" | "I want to feel in control of my work for the first time in years" |
|
||||
| "I want to lower CAC" | "I want a marketing engine I can step away from for two weeks without things breaking" |
|
||||
|
||||
### How to increase
|
||||
|
||||
- **Name it specifically.** "Feel confident in a swimsuit" beats "lose weight." The specific name is the offer.
|
||||
- **Connect to the bigger goal.** The dream outcome behind the surface ask is almost always emotional or identity-based.
|
||||
- **Show the future state in concrete sensory terms.** What does the morning of day one *after they have it* actually look like?
|
||||
|
||||
### Common mistake
|
||||
|
||||
Pitching the surface ask. ("Get a website" instead of "get a website that brings you 5 qualified leads a week.") The bigger the buyer's pain, the more important this is — they're not buying a deliverable, they're buying a future.
|
||||
|
||||
---
|
||||
|
||||
## Lever 2: Perceived Likelihood of Achievement (numerator)
|
||||
|
||||
Do they actually believe they'll get the dream outcome? This is the single most underweighted lever — most offers are perfectly fine on the dream outcome side but the buyer just doesn't think it'll work *for them*.
|
||||
|
||||
### How to increase
|
||||
|
||||
- **Proof** — case studies with names, numbers, before/after metrics, photos. Specific > glossy.
|
||||
- **Methodology specificity** — name your process. "The 5-step VAULT framework" beats "our proprietary system." Even if the substance is the same, naming it raises perceived likelihood.
|
||||
- **Guarantees** — risk reversal directly raises perceived likelihood (more in [guarantee-design.md](guarantee-design.md)).
|
||||
- **Reduce sample-of-one objection** — show people *like them* who got results. "Other people get results but I'm different" is the universal objection.
|
||||
- **Pre-empt the failure path** — explicitly address what could go wrong and how you handle it. Builds trust faster than hiding the risk.
|
||||
|
||||
### Common mistake
|
||||
|
||||
Stacking more features ("we also include X, Y, Z") instead of stacking more proof. Features address dream outcome. Proof addresses likelihood. Most stuck offers need proof, not features.
|
||||
|
||||
---
|
||||
|
||||
## Lever 3: Time Delay (denominator)
|
||||
|
||||
How long from purchase to result. The denominator is doing a lot of work here — slow results don't just feel slow, they erode perceived likelihood (the longer it takes, the less the buyer believes it'll work).
|
||||
|
||||
### How to decrease
|
||||
|
||||
- **Faster first win** — find the smallest possible early result and engineer it into the first 7 days
|
||||
- **Onboarding velocity** — replace a 60-minute kickoff with a 10-minute async intake + Loom send
|
||||
- **Front-load the assets** — give the templates / swipe files / decks on day 1, not "throughout the program"
|
||||
- **Faster end-to-end timeline** — "in 8 weeks" beats "in 6 months." If you can credibly compress, do.
|
||||
- **Quick-start path** — explicit "first thing to do today" so they don't lose momentum
|
||||
|
||||
### Common mistake
|
||||
|
||||
Promising a faster timeline than you can deliver. The first time you miss it, perceived likelihood for every future buyer drops permanently as the failure story spreads.
|
||||
|
||||
---
|
||||
|
||||
## Lever 4: Effort & Sacrifice (denominator)
|
||||
|
||||
What the buyer pays *besides money* — time, learning curve, decisions, willpower, social risk, opportunity cost.
|
||||
|
||||
### How to decrease
|
||||
|
||||
- **Done-for-you over do-it-yourself** — DFY tiers move the effort to you. Charge accordingly.
|
||||
- **Fewer decisions** — every decision the buyer makes is friction. Bundle, default, recommend.
|
||||
- **Lower learning curve** — pre-built templates, examples, defaults. "We did the thinking, you do the executing."
|
||||
- **Removed risk** — emotional risk (am I dumb if this doesn't work?), social risk (what will my team think?), opportunity cost (what am I not doing while I do this?). Address all three explicitly.
|
||||
- **Async over live** — for many buyers (founders, executives), removing synchronous commitments is huge value
|
||||
- **Less willpower required** — automation, accountability, environmental design
|
||||
|
||||
### Common mistake
|
||||
|
||||
Overestimating how much your buyer *enjoys* the work. They want the outcome, not the process. (Exception: identity-buyers — fitness, learning, mastery. For those, the process *is* part of the dream outcome. Read your buyer.)
|
||||
|
||||
---
|
||||
|
||||
## Diagnostic: scoring the levers
|
||||
|
||||
When an offer is stuck, score each lever 1–10 honestly. The lowest is the binding constraint.
|
||||
|
||||
### Quick scoring prompts
|
||||
|
||||
- **Dream outcome (1–10)**: Can the buyer picture, in concrete sensory terms, the day after this works? Is the outcome named specifically enough that they can repeat it back to a friend?
|
||||
- **Perceived likelihood (1–10)**: Do they have at least three named, comparable proof points? Is the methodology specific enough to repeat? Have you addressed the "but my situation is different" objection?
|
||||
- **Time delay (1–10)**: What's the first concrete win, and how soon do they get it? What's the end-to-end timeline? Are there any "delay surfaces" (onboarding lag, asset drip, week-1 friction)?
|
||||
- **Effort & sacrifice (1–10)**: How much work does the buyer do? How many decisions? How much learning curve? How much synchronous time? How much emotional/social/opportunity-cost risk?
|
||||
|
||||
### Worked example: a stuck $3K copywriting course
|
||||
|
||||
Initial scoring:
|
||||
- Dream outcome: 6 (`become a better copywriter` — too vague)
|
||||
- Perceived likelihood: 4 (one testimonial, no methodology name)
|
||||
- Time delay: 5 (6-month course, no first-win mechanic)
|
||||
- Effort & sacrifice: 4 (lots of homework, live calls, weekly assignments)
|
||||
|
||||
Lowest: effort & sacrifice and perceived likelihood are tied. Pick one (perceived likelihood — easier to move and unblocks more downstream work):
|
||||
|
||||
- Name the methodology: "The VAULT framework — 5 angles every winning sales page uses"
|
||||
- Add 8 named-customer case studies with before/after copy + revenue numbers
|
||||
- Add an "even if you've never written before" cohort with 3 named graduates
|
||||
|
||||
After: perceived likelihood goes 4 → 8. Course converts at ~3x baseline. Two months later, attack effort & sacrifice (replace weekly live calls with async + 1 live Q&A).
|
||||
|
||||
---
|
||||
|
||||
## Key idea to internalize
|
||||
|
||||
**The price-vs-value comparison happens in the buyer's head, not yours.** You only know it's working when the buyer can articulate the dream outcome back to you in their own words, and when they don't need to ask "but does this actually work?"
|
||||
|
||||
If they're asking either of those questions, you have a value equation problem, not a copy problem.
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: pricing
|
||||
description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls."
|
||||
description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers."
|
||||
metadata:
|
||||
version: 2.0.0
|
||||
version: 2.0.1
|
||||
---
|
||||
|
||||
# Pricing Strategy
|
||||
|
||||
@@ -0,0 +1,131 @@
|
||||
---
|
||||
name: public-relations
|
||||
description: "When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email."
|
||||
metadata:
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Public Relations & Earned Media
|
||||
|
||||
You are an expert in earned media for software products. Your goal is to help the user get covered by journalists, podcasts, and newsletters — efficiently, with respect for the people on the other end of the pitch.
|
||||
|
||||
## Before Starting
|
||||
|
||||
**Check for product marketing context first:**
|
||||
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
|
||||
|
||||
---
|
||||
|
||||
## Core Philosophy
|
||||
|
||||
PR is not a substitute for distribution. It's a multiplier for it.
|
||||
|
||||
- **Earned media doesn't drive direct conversions.** A TechCrunch hit will not give you 1,000 paying customers. It will give you backlinks, brand legitimacy, AI-citation surface area, and ammo for sales conversations.
|
||||
- **Pitch journalists like you'd pitch a customer:** specific, useful, fast, and never about you.
|
||||
- **The story is not your product. The story is the trend, the data, the conflict, or the human.** Your product is the evidence.
|
||||
- **Speed beats polish on reactive PR.** A B+ pitch in the first hour of a story beats an A+ pitch on day three.
|
||||
|
||||
### When PR is worth it
|
||||
|
||||
- You have **a real story** — proprietary data, a strong opinion, a milestone, a customer with a sharp before/after, or a fresh angle on a trending topic
|
||||
- You have **founder/exec time** — journalists want quotes from people with skin in the game, not from a PR rep
|
||||
- You have **a destination** — a press page, blog post, or product launch that converts attention into something useful
|
||||
|
||||
### When to skip PR (for now)
|
||||
|
||||
- Pre-launch with no story beyond "we exist"
|
||||
- No one on the team can sustain pitching for 4–6 weeks (PR is a momentum game)
|
||||
- You don't have a clear ICP — journalists ask "who reads my piece because of this?" and if you can't answer, neither can they
|
||||
|
||||
---
|
||||
|
||||
## The PR Mix
|
||||
|
||||
Four modes. Most teams over-index on one. Run at least three.
|
||||
|
||||
| Mode | What it is | Effort | Speed to coverage |
|
||||
|------|------------|--------|-------------------|
|
||||
| **Reactive (newsjacking)** | Inject your POV into trending news | Low–medium | Hours to days |
|
||||
| **Proactive (pitching)** | Build a media list, pitch original stories | High | 2–8 weeks |
|
||||
| **Inbound (press requests)** | Respond to journalist queries on HARO/Qwoted/Featured | Low | Days to weeks |
|
||||
| **Owned (press page + media kit)** | Make it easy for journalists to find you | One-time setup | N/A |
|
||||
|
||||
**For the reactive newsjacking workflow** — see [references/newsjacking.md](references/newsjacking.md)
|
||||
|
||||
**For proactive journalist pitching** — see [references/journalist-pitching.md](references/journalist-pitching.md)
|
||||
|
||||
**For inbound press-request platforms (HARO, Qwoted, etc.)** — see [references/press-platforms.md](references/press-platforms.md)
|
||||
|
||||
**For where to pitch (media outlets, podcasts, newsletters)** — see [references/media-outlets.md](references/media-outlets.md). For startup/SaaS/AI directories, use the separate `directory-submissions` skill — different intent, different list.
|
||||
|
||||
---
|
||||
|
||||
## Owned: Press Page + Media Kit
|
||||
|
||||
Set this up once. It's the cheapest PR investment with the highest ROI on every future story.
|
||||
|
||||
**Press page (`/press` or `/newsroom`) should include:**
|
||||
- One-paragraph company description (copy/paste ready)
|
||||
- Founder bios with headshots (high-res, downloadable)
|
||||
- Logo pack (SVG + PNG, light + dark, with usage guidelines)
|
||||
- Product screenshots (high-res)
|
||||
- Recent coverage list (social proof for the next journalist)
|
||||
- Founding date, employee count, funding (if disclosed)
|
||||
- Press contact email (not a form — journalists hate forms)
|
||||
- Recent press releases / announcements
|
||||
|
||||
**One sentence at the top:** "For interview requests or assets, email press@yourcompany.com — we respond within 24 hours."
|
||||
|
||||
Then *actually* respond within 24 hours.
|
||||
|
||||
---
|
||||
|
||||
## Quick Reference: Pitch Quality Bar
|
||||
|
||||
Before sending any pitch, the answer to all of these should be yes:
|
||||
|
||||
- [ ] Does this journalist cover this beat? (Check their last 5 articles.)
|
||||
- [ ] Is there a clear news hook — something that just happened or is about to?
|
||||
- [ ] Could this journalist write a complete story from this email alone? (Data, quotes, customer name, contact.)
|
||||
- [ ] Is the subject line specific enough to predict the article's headline?
|
||||
- [ ] Is the pitch under 150 words?
|
||||
- [ ] Did you avoid the words "revolutionary," "game-changing," "disruptive," and "synergy"?
|
||||
- [ ] Is the ask clear? (Interview? Embargo? Exclusive? Quote?)
|
||||
|
||||
If any answer is no, don't send.
|
||||
|
||||
---
|
||||
|
||||
## Measurement
|
||||
|
||||
What to track:
|
||||
|
||||
| Metric | Why |
|
||||
|--------|-----|
|
||||
| **Coverage count** (placements / month) | Activity baseline |
|
||||
| **Domain rating of placements** | Backlink value |
|
||||
| **Referral traffic from coverage** | Did anyone actually click? |
|
||||
| **Brand search lift** | Did people search you after reading? |
|
||||
| **AI citation rate** (ChatGPT, Perplexity quote your brand?) | The new measurement that matters |
|
||||
| **Sales conversations citing the article** | The only one that matters for revenue |
|
||||
|
||||
What not to obsess over: AVE (advertising value equivalency) — it's a vanity metric PR firms invented.
|
||||
|
||||
---
|
||||
|
||||
## Common Workflows
|
||||
|
||||
### "Help me newsjack [trending story]"
|
||||
Go to [newsjacking.md](references/newsjacking.md), run the scoring rubric, draft 2–3 angles, pick the best, draft the pitch.
|
||||
|
||||
### "Find journalists who cover [beat]"
|
||||
Go to [journalist-pitching.md](references/journalist-pitching.md), use the discovery checklist + dev-browser to research recent articles, build a scored list.
|
||||
|
||||
### "What's worth pitching this week?"
|
||||
Combine: recent product milestones + active news cycles + any data you've collected. Score each potential story by the quality bar above.
|
||||
|
||||
### "Respond to this HARO query"
|
||||
Go to [press-platforms.md](references/press-platforms.md), use the response template, keep it under 200 words.
|
||||
|
||||
### "Build my press page"
|
||||
Use the checklist above. Most companies do this in an afternoon and forget about it for a year — that's fine.
|
||||
@@ -0,0 +1,368 @@
|
||||
# Journalist Pitching — Proactive PR Workflow
|
||||
|
||||
Building a media list, scoring journalist fit, and crafting pitches that actually get opened. This is a 4–8 week practice, not a one-shot.
|
||||
|
||||
## Contents
|
||||
- Building the media list
|
||||
- Scoring journalist fit
|
||||
- Pitch templates by angle
|
||||
- Subject lines that get opened
|
||||
- Voice and structure
|
||||
- Embargoes, exclusives, and follow-up etiquette
|
||||
- Pitch killers
|
||||
- Tooling
|
||||
|
||||
---
|
||||
|
||||
## Building the Media List
|
||||
|
||||
The goal: a list of 20–40 journalists who actually cover your beat. Not 500 names from a database.
|
||||
|
||||
### Discovery checklist
|
||||
|
||||
For each candidate journalist:
|
||||
|
||||
- [ ] Read their **last 5 articles** — are they covering your beat right now?
|
||||
- [ ] Note their **publication** — does it reach your ICP?
|
||||
- [ ] Check their **bio** on the outlet site — what topics do they own?
|
||||
- [ ] Check **X/LinkedIn** for what they're posting about this week
|
||||
- [ ] Note their **email** (usually on outlet author page, Muck Rack, or company About page)
|
||||
- [ ] Check **Muck Rack** if available — it shows recent topics and pitch preferences
|
||||
|
||||
### Where to find candidates
|
||||
|
||||
| Method | How |
|
||||
|--------|-----|
|
||||
| **Reverse lookup from coverage you want** | Find 5 articles about competitors / your category, note bylines |
|
||||
| **Topic search on Muck Rack** | Free tier shows journalists by topic |
|
||||
| **X / Twitter lists** | "[your niche] reporters" lists already exist |
|
||||
| **LinkedIn search** | "Journalist" + "[your category]" — filter by recent activity |
|
||||
| **Newsletter author pages** | Beehiiv, Substack, ConvertKit creators are pitchable |
|
||||
| **Podcast host research** | Listen to 1 episode before pitching — non-negotiable |
|
||||
|
||||
### Don't waste time on
|
||||
|
||||
- **Mass media databases** (Cision, Meltwater) for early-stage — overkill and expensive
|
||||
- **Journalists who haven't posted in 6+ months** — they may have left
|
||||
- **"Editor-in-chief" generic addresses** — pitches there get ignored or routed to interns
|
||||
- **Journalists who explicitly state "no PR pitches" in bio** — respect it
|
||||
|
||||
---
|
||||
|
||||
## Scoring Journalist Fit
|
||||
|
||||
Score each journalist 1–10 across four dimensions. Sum and rank. Focus on top 20.
|
||||
|
||||
| Dimension | What it measures | Weight |
|
||||
|-----------|------------------|--------|
|
||||
| **Beat match** | Do they cover your category specifically? | 3x |
|
||||
| **Reach** | Outlet's audience size + their byline traction | 2x |
|
||||
| **Engagement** | Do they respond to pitches publicly / on X? | 2x |
|
||||
| **Recency** | Have they written about a related topic in last 30d? | 1x |
|
||||
|
||||
**Tiering:**
|
||||
- **Tier 1 (8–10):** Personal pitch with original angle. Custom each time.
|
||||
- **Tier 2 (5–7):** Standard pitch, lightly customized.
|
||||
- **Tier 3 (below 5):** Skip or pitch only when story is exceptional.
|
||||
|
||||
---
|
||||
|
||||
## Pitch Templates by Angle
|
||||
|
||||
Six structures that work. Pick the one that matches your story.
|
||||
|
||||
### 1. Data story
|
||||
|
||||
```
|
||||
Subject: [Specific stat] — [implication]
|
||||
|
||||
Hi [name],
|
||||
|
||||
I noticed you covered [recent article] — wanted to share data that might
|
||||
be relevant.
|
||||
|
||||
We [analyzed N / surveyed N / tracked N] and found:
|
||||
• [Stat 1 with surprise factor]
|
||||
• [Stat 2]
|
||||
• [Stat 3]
|
||||
|
||||
The most interesting pattern: [one-sentence insight].
|
||||
|
||||
Full data + methodology here: [link to one-pager, not your homepage]
|
||||
|
||||
Happy to share the raw dataset, jump on a call, or connect you with
|
||||
[customer who's relevant].
|
||||
|
||||
[your name + 1-line credential]
|
||||
```
|
||||
|
||||
### 2. Exclusive launch / milestone
|
||||
|
||||
```
|
||||
Subject: Exclusive: [specific milestone] at [company]
|
||||
|
||||
Hi [name],
|
||||
|
||||
I have an exclusive on [milestone] that I think fits your [beat] coverage.
|
||||
|
||||
The story: [one sentence]
|
||||
Why it matters: [one sentence — for their readers, not for you]
|
||||
What's new: [the actual news, not the marketing line]
|
||||
|
||||
Embargo until [day, time, timezone] — would love to give you first
|
||||
window. Press kit + assets: [link]
|
||||
|
||||
Free to talk [two specific time options].
|
||||
|
||||
[your name]
|
||||
```
|
||||
|
||||
### 3. Op-ed / contributed piece
|
||||
|
||||
```
|
||||
Subject: Op-ed pitch: [provocative thesis]
|
||||
|
||||
Hi [name],
|
||||
|
||||
I read your piece on [recent article] — sharp take on [specific point].
|
||||
|
||||
I'd like to pitch a 700-word op-ed: "[Thesis as a headline]"
|
||||
|
||||
Core argument:
|
||||
• [Point 1]
|
||||
• [Point 2]
|
||||
• [Point 3 — the surprising one]
|
||||
|
||||
Why me: [1 sentence — credential or unique vantage]
|
||||
Why now: [1 sentence — the news hook]
|
||||
|
||||
Can have a draft to you by [date]. Happy to adapt to your house style.
|
||||
|
||||
[your name]
|
||||
```
|
||||
|
||||
### 4. Customer story
|
||||
|
||||
```
|
||||
Subject: Customer story for [their beat] — [specific outcome]
|
||||
|
||||
Hi [name],
|
||||
|
||||
For your [beat] coverage, I have a [customer type] willing to talk on
|
||||
the record about [specific outcome].
|
||||
|
||||
The hook: [customer] [did something specific] and [measurable result].
|
||||
|
||||
The interesting part: [the surprising or counterintuitive detail].
|
||||
|
||||
Customer details:
|
||||
• Name: [name, title, company]
|
||||
• Available: [windows]
|
||||
• Willing to share: [data points / screenshots / metrics]
|
||||
|
||||
Happy to coordinate the intro.
|
||||
|
||||
[your name]
|
||||
```
|
||||
|
||||
### 5. Trend piece / connector
|
||||
|
||||
```
|
||||
Subject: Trend forming in [space] — three signals
|
||||
|
||||
Hi [name],
|
||||
|
||||
Three things in [space] this month that I think connect:
|
||||
|
||||
1. [Signal 1 with link]
|
||||
2. [Signal 2 with link]
|
||||
3. [Signal 3 — yours, briefly]
|
||||
|
||||
The pattern: [one sentence].
|
||||
|
||||
This might be early for a piece, but if you're tracking the space I
|
||||
wanted to flag it. Happy to share data we've collected or connect you
|
||||
with others seeing the same.
|
||||
|
||||
[your name]
|
||||
```
|
||||
|
||||
### 6. Newsjack response
|
||||
|
||||
```
|
||||
Subject: Re: [their article headline] — quick data point
|
||||
|
||||
Hi [name],
|
||||
|
||||
Saw your piece on [story] this morning — wanted to add a relevant
|
||||
data point in case you do a follow-up.
|
||||
|
||||
[One-sentence stat or insight].
|
||||
|
||||
Source: [our data / our customers / our analysis]
|
||||
Methodology: [one sentence]
|
||||
|
||||
Quotable: "[a sentence you'd be comfortable seeing in print]"
|
||||
|
||||
If useful for a follow-up, I'm around all day at this number: [phone].
|
||||
|
||||
[your name]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Subject Lines That Get Opened
|
||||
|
||||
Journalists open pitches based on the subject line alone. Rules:
|
||||
|
||||
- **Under 50 characters** — mobile preview cuts off
|
||||
- **Lead with the specific** — "73% of devs deploy to prod on Fridays" beats "New data on developer workflows"
|
||||
- **Promise a story, not a product** — "Why [trend]" beats "[Company] launches [thing]"
|
||||
- **Use prefixes that signal value** — "Exclusive:", "Data:", "Op-ed pitch:", "Re: [their article]"
|
||||
|
||||
**Test against this question:** would *you* open this in a 200-email inbox?
|
||||
|
||||
**Patterns that work:**
|
||||
- "[Specific stat] — [implication]" — "73% of agents fail this test"
|
||||
- "Exclusive: [milestone]" — "Exclusive: Anthropic launches AgentOS"
|
||||
- "Re: [their headline]" — direct response to recent coverage
|
||||
- "[Provocative thesis]" — "Why VC funding is bad for AI safety"
|
||||
|
||||
**Patterns that get deleted:**
|
||||
- "Press release: [boring]"
|
||||
- "[Company] announces [thing]"
|
||||
- "Story idea for you!"
|
||||
- "Following up on my previous email"
|
||||
- Any subject line with "innovative," "disruptive," "revolutionary"
|
||||
|
||||
---
|
||||
|
||||
## Voice and Structure
|
||||
|
||||
### Length
|
||||
|
||||
**150 words max for the pitch.** If you can't say it in 150 words, you don't know what your story is yet.
|
||||
|
||||
### Structure
|
||||
|
||||
1. **One-line context** — why you're emailing them specifically (their recent article, their beat)
|
||||
2. **The story** — what it is, in one sentence
|
||||
3. **Why it matters to their readers** — not why it matters to you
|
||||
4. **Proof** — data, customer, quote, link
|
||||
5. **The ask** — interview, embargo, quote, link
|
||||
|
||||
### Voice
|
||||
|
||||
- Sound like a person, not a press release
|
||||
- Reference their actual recent work — proves you read them
|
||||
- Don't use emoji unless they do
|
||||
- Don't open with "I hope this finds you well" — burn it
|
||||
- Don't ask "did you get my email?" follow-ups (see [Follow-up](#embargoes-exclusives-and-follow-up-etiquette))
|
||||
|
||||
### Banned vocabulary
|
||||
|
||||
Revolutionary, disruptive, game-changing, paradigm shift, leverage, synergy, robust, seamless, holistic, world-class, best-in-class, next-generation, cutting-edge, AI-powered (unless that's the actual differentiation), at-the-end-of-the-day.
|
||||
|
||||
---
|
||||
|
||||
## Embargoes, Exclusives, and Follow-Up Etiquette
|
||||
|
||||
### Embargoes
|
||||
|
||||
An embargo is "you can write this story, but don't publish until [time]."
|
||||
|
||||
- **Only offer embargoes to journalists you've worked with** or have strong reputations for honoring them
|
||||
- State the embargo time clearly: day, time, timezone
|
||||
- If they break embargo, your relationship with them is over
|
||||
|
||||
### Exclusives
|
||||
|
||||
"Only you get this story" — powerful tool, use sparingly.
|
||||
|
||||
- **First-tier outlet only** — exclusives to tier 2/3 outlets waste the lever
|
||||
- **Be honest about scope** — "exclusive to [outlet] in the US" is fine
|
||||
- **Have a parallel plan** — what you publish/pitch the next day after the exclusive runs
|
||||
|
||||
### Follow-up cadence
|
||||
|
||||
- **Day 0** — initial pitch
|
||||
- **Day 3** — one follow-up if you have new information ("Just talked to [customer] who can join us")
|
||||
- **Day 7** — final check-in with a fresh hook ("This came out today, still relevant?")
|
||||
- **After day 7** — let it go. Re-pitch when you have something genuinely new.
|
||||
|
||||
**Never:**
|
||||
- "Bumping this up" / "Did you see my email?"
|
||||
- Multi-day silent follow-ups with no new value
|
||||
- Same pitch reformatted
|
||||
|
||||
---
|
||||
|
||||
## Pitch Killers
|
||||
|
||||
Things that instantly disqualify your pitch:
|
||||
|
||||
- Wrong name / wrong outlet (autoreplace fail)
|
||||
- Pitching topics they explicitly don't cover
|
||||
- Press release attached as PDF (just paste the key bits)
|
||||
- Long signature with logos and disclaimers
|
||||
- CC'ing 5 other journalists on the same email
|
||||
- "Per my last email" energy
|
||||
- Asking them to sign an NDA before talking
|
||||
- Pitching a story you can't actually tell (no customer willing to talk, no data ready to share)
|
||||
|
||||
---
|
||||
|
||||
## Tooling
|
||||
|
||||
### Finding journalist contact info
|
||||
|
||||
```bash
|
||||
# Most journalists' emails follow patterns:
|
||||
# firstname@outlet.com
|
||||
# firstname.lastname@outlet.com
|
||||
# flastname@outlet.com
|
||||
# Use Hunter.io, RocketReach, or just guess and bounce-check
|
||||
```
|
||||
|
||||
### Researching their recent work (browser-driven)
|
||||
|
||||
Use `dev-browser` (persistent session, no rate limits) to:
|
||||
- Open the journalist's outlet author page → scrape last 5 article headlines + dates
|
||||
- Open their X/Twitter profile → note recent topics
|
||||
- Open their LinkedIn → confirm current role
|
||||
|
||||
Output what you find as:
|
||||
|
||||
```
|
||||
JOURNALIST PROFILE — [name]
|
||||
Outlet: [name]
|
||||
Beat: [topics from last 5 articles]
|
||||
Recent angle: [pattern you noticed]
|
||||
Recent X activity: [what they're posting]
|
||||
Score: [X/40 from rubric]
|
||||
Best pitch angle: [from template library]
|
||||
Email: [confirmed]
|
||||
```
|
||||
|
||||
### Maintaining the media list
|
||||
|
||||
Store in `.agents/media-list.md` (or `.csv` if you prefer). Update monthly — journalists move jobs constantly.
|
||||
|
||||
```markdown
|
||||
## Tier 1 (top 20)
|
||||
| Name | Outlet | Beat | Last contact | Last coverage | Email | Score |
|
||||
|------|--------|------|--------------|---------------|-------|-------|
|
||||
| ... | ... | ... | 2026-05-15 | none yet | ... | 9/10 |
|
||||
```
|
||||
|
||||
### Pitch tracking
|
||||
|
||||
Track in a simple spreadsheet:
|
||||
- Date sent
|
||||
- Subject line
|
||||
- Journalist
|
||||
- Outlet
|
||||
- Response (open / reply / pass / coverage)
|
||||
- What they said
|
||||
|
||||
After 30 pitches, you'll see which subject patterns and which angles work for you specifically.
|
||||
@@ -0,0 +1,207 @@
|
||||
# Media Outlets — Where to Pitch
|
||||
|
||||
A curated, opinionated list of *where* to pitch for software/SaaS PR. This is the media-outlet slice of resources like submit.co — the journalist-driven half. For startup/SaaS/AI directories (Product Hunt, BetaList, Futurepedia, etc.), use the separate `directory-submissions` skill — different intent, different audience.
|
||||
|
||||
## How to use this list
|
||||
|
||||
- **Don't pitch a publication. Pitch a journalist at that publication.** See [journalist-pitching.md](journalist-pitching.md) for the discovery workflow.
|
||||
- **Tier signals quality, not effort** — a small tier-3 outlet might be perfect for your niche
|
||||
- **Submission/tip URLs are listed where they exist** — but a journalist's email beats a tip form every time
|
||||
- **This list ages fast** — verify the outlet still exists and the journalist is still there before pitching
|
||||
|
||||
---
|
||||
|
||||
## Tech & Startup Press (Tier 1)
|
||||
|
||||
The big names. High bar to clear, high payoff when you do. Pitch the specific reporter, not the tip line.
|
||||
|
||||
| Outlet | Best for | Tip URL |
|
||||
|--------|---------|---------|
|
||||
| **TechCrunch** | Funding, product launches, startup news | techcrunch.com/got-a-tip/ |
|
||||
| **The Verge** | Consumer tech, product reviews, policy | theverge.com/contact |
|
||||
| **Wired** | Long-form tech, culture, business | wired.com/about/feedback |
|
||||
| **Fast Company** | Innovation, design, business strategy | fastcompany.com/contact-us |
|
||||
| **VentureBeat** | AI, enterprise tech, gaming | venturebeat.com/contribute |
|
||||
| **Ars Technica** | Deep tech, science, policy | arstechnica.com/contact-us |
|
||||
| **The Information** | Subscription-gated, scoops on tech industry | theinformation.com/about |
|
||||
| **Bloomberg / Reuters** | Business, finance, big-picture stories | bloomberg.com/feedback |
|
||||
| **WSJ Tech** | Enterprise, business angle | wsj.com/tips |
|
||||
| **NYT Tech** | Mainstream tech, culture | nytimes.com/tips |
|
||||
|
||||
---
|
||||
|
||||
## SaaS & B2B (Tier 1–2)
|
||||
|
||||
Lower-profile than the consumer tech outlets but often higher ROI for B2B SaaS.
|
||||
|
||||
| Outlet | Best for | Notes |
|
||||
|--------|----------|-------|
|
||||
| **SaaStr** | B2B SaaS founders, growth, sales | Jason Lemkin's outlet; pitch contributed posts |
|
||||
| **First Round Review** | Operator-level B2B insights | High bar; original frameworks only |
|
||||
| **OpenView** | SaaS metrics, PLG, pricing | Often runs research-backed pieces |
|
||||
| **Lenny's Newsletter** | Product / growth | Subscriber-only; pitch via Lenny directly on X |
|
||||
| **Future (a16z)** | Tech + culture pieces | Long-form, original thinking required |
|
||||
| **Stratechery** | Tech strategy analysis | Don't pitch Ben Thompson; engage via responses |
|
||||
|
||||
---
|
||||
|
||||
## AI / ML Press (Tier 1–2)
|
||||
|
||||
The hottest beat right now. Reporters here are inundated — your angle has to be sharp.
|
||||
|
||||
| Outlet | Best for | Notes |
|
||||
|--------|----------|-------|
|
||||
| **The Decoder** | AI news, fast-turn | Daily AI news cycle |
|
||||
| **Import AI** (Jack Clark) | Weekly AI newsletter | Pitch research-backed angles |
|
||||
| **The Batch** (Andrew Ng) | AI industry analysis | Submitted by deeplearning.ai team |
|
||||
| **MIT Technology Review** | AI policy, capability, ethics | Higher bar, slower cycle |
|
||||
| **Hugging Face blog** | Open-source AI tools | Contributed posts welcome |
|
||||
| **Latent Space** | Practitioner-focused AI/ML | Podcast + newsletter |
|
||||
|
||||
---
|
||||
|
||||
## Developer & DevTools Press
|
||||
|
||||
Where to pitch if your audience is engineers.
|
||||
|
||||
| Outlet | Best for | Notes |
|
||||
|--------|----------|-------|
|
||||
| **The New Stack** | DevTools, infra, cloud-native | Active contributor program |
|
||||
| **InfoQ** | Enterprise dev, software architecture | Long-form technical pieces |
|
||||
| **DEV.to** | Self-published, community-driven | Build credibility before pitching |
|
||||
| **Hacker Noon** | Tech blogging platform | Easy to publish but low signal |
|
||||
| **Console** | DevTools newsletter | Curated weekly; submit projects |
|
||||
| **DevTools FM** | Podcast | Pitch as guest |
|
||||
|
||||
---
|
||||
|
||||
## Business & Marketing Press
|
||||
|
||||
For pitching the business / marketing angle of your story.
|
||||
|
||||
| Outlet | Best for | Notes |
|
||||
|--------|----------|-------|
|
||||
| **Inc.** | Founder stories, business advice | Contributor program available |
|
||||
| **Entrepreneur** | Small business, growth | Volume publisher; quality varies |
|
||||
| **HBR.org** | Original research, frameworks | High bar; long lead time |
|
||||
| **MarketingProfs** | B2B marketing | Contributor-friendly |
|
||||
| **Marketing Brew (Morning Brew)** | Daily marketing newsletter | Reporter-driven, pitch directly |
|
||||
| **Marketing Land / Search Engine Journal** | SEO, SEM, channels | Niche but high-intent audience |
|
||||
| **Reforge** | Growth, product, retention | Original framework required |
|
||||
|
||||
---
|
||||
|
||||
## Newsletters (Reporter-Driven)
|
||||
|
||||
Newsletters are increasingly the most valuable PR placement — small audiences, but high-intent.
|
||||
|
||||
| Newsletter | Audience | How to pitch |
|
||||
|-----------|---------|--------------|
|
||||
| **Lenny's Newsletter** | Product/growth, ~600k readers | DM Lenny on X with sharp angle |
|
||||
| **The Pragmatic Engineer** (Gergely Orosz) | Software eng leaders | Pitch via email; original engineering insights |
|
||||
| **The Generalist** (Mario Gabriele) | Tech business analysis | Pitch via email; deep angles |
|
||||
| **Stratechery** (Ben Thompson) | Tech strategy | Don't pitch; engage in replies |
|
||||
| **Newcomer** (Eric Newcomer) | Tech business + scoops | Tips welcome via email |
|
||||
| **Platformer** (Casey Newton) | Tech + policy | Pitch via Substack |
|
||||
| **Big Technology** (Alex Kantrowitz) | Big Tech analysis | Pitch via Substack |
|
||||
| **Not Boring** (Packy McCormick) | Tech + culture | Tough to crack; original takes only |
|
||||
|
||||
**For B2B SaaS:**
|
||||
- **SaaStr Daily**
|
||||
- **Demand Curve**
|
||||
- **Growth Unhinged** (Kyle Poyar)
|
||||
- **Trends.vc**
|
||||
|
||||
**For AI:**
|
||||
- **Import AI** (Jack Clark)
|
||||
- **The Batch** (Andrew Ng)
|
||||
- **The Algorithm** (MIT Tech Review)
|
||||
- **Interconnects** (Nathan Lambert)
|
||||
- **AI Tidbits**
|
||||
|
||||
---
|
||||
|
||||
## Podcasts
|
||||
|
||||
A podcast appearance is often higher leverage than a press hit — longer engagement, evergreen replay, audience trust transfer.
|
||||
|
||||
### Top SaaS / startup podcasts
|
||||
- **Lenny's Podcast** — product/growth
|
||||
- **My First Million** — founder stories, business ideas
|
||||
- **The Twenty Minute VC** — funding angle
|
||||
- **SaaStr Podcast** — B2B SaaS
|
||||
- **Acquired** — deep-dive company stories (don't pitch unless you're a unicorn)
|
||||
- **The All-In Podcast** — broad tech/business (very hard to get on)
|
||||
|
||||
### Top AI podcasts
|
||||
- **No Priors** (Sarah Guo, Elad Gil)
|
||||
- **Latent Space**
|
||||
- **Practical AI**
|
||||
- **The TWIML AI Podcast**
|
||||
- **The Cognitive Revolution**
|
||||
|
||||
### Top dev / engineering podcasts
|
||||
- **The Changelog**
|
||||
- **Software Engineering Daily**
|
||||
- **DevTools FM**
|
||||
|
||||
### How to pitch a podcast
|
||||
|
||||
1. **Listen to 3 episodes** — non-negotiable
|
||||
2. **Find the host's preferred channel** (X DM, email, guest form)
|
||||
3. **Pitch a topic, not yourself** — "I'd love to come on and talk about [specific angle]" not "I'd love to be a guest"
|
||||
4. **Bring evidence** — links to other appearances, your unique angle, what listeners will learn
|
||||
5. **Make it easy** — bio, headshot, suggested questions in the pitch
|
||||
|
||||
---
|
||||
|
||||
## Industry / Vertical Press
|
||||
|
||||
Don't overlook trade press — smaller audience, much higher intent.
|
||||
|
||||
| Vertical | Outlets to investigate |
|
||||
|----------|----------------------|
|
||||
| **Marketing** | Adweek, Marketing Brew, AdAge, Search Engine Land |
|
||||
| **Sales** | Sales Hacker, Modern Sales Pros |
|
||||
| **HR / People Ops** | HR Brew, SHRM, HR Dive |
|
||||
| **Finance / Fintech** | The Block, CoinDesk, Finextra |
|
||||
| **Healthcare tech** | STAT, MobiHealthNews, Healthcare IT News |
|
||||
| **Education tech** | EdSurge, EdScoop |
|
||||
| **Real estate tech** | Inman, The Real Deal |
|
||||
| **Legal tech** | Above the Law, Law360 |
|
||||
| **Climate tech** | Heatmap, Canary Media, Latitude Media |
|
||||
| **Devtools** | The New Stack, InfoQ, DevOps.com |
|
||||
|
||||
For your specific vertical: Google `"top publications" + "[your industry]"` and run the same scoring exercise from [journalist-pitching.md](journalist-pitching.md).
|
||||
|
||||
---
|
||||
|
||||
## Regional / Local
|
||||
|
||||
If your company has a regional angle (HQ location, customer concentration, government contract), local press is underrated.
|
||||
|
||||
- **Local business journals** — Bizjournals network covers 40+ US cities
|
||||
- **Local NPR affiliates** — high-quality, business angle welcomed
|
||||
- **Local TV business segments** — high reach, easy to get
|
||||
- **State / regional tech news** — e.g., Built In (Chicago, Austin, etc.), TechBuzz (Utah)
|
||||
|
||||
---
|
||||
|
||||
## What's NOT On This List (And Why)
|
||||
|
||||
- **Product Hunt, BetaList, Indie Hackers** — these are directories, not press. Use the `directory-submissions` skill.
|
||||
- **Press release wires** (PRNewswire, BusinessWire, GlobeNewswire) — overpriced for early-stage; journalists ignore them. Skip until you have IR / SEC requirements.
|
||||
- **"As featured in" badge mills** — paid "media coverage" services. Worthless and damaging.
|
||||
- **Random "guest post" SEO link networks** — Google penalizes these. Don't.
|
||||
|
||||
---
|
||||
|
||||
## Maintaining This List
|
||||
|
||||
This list will go stale. Recommended cadence:
|
||||
|
||||
- **Quarterly:** verify your tier-1 contacts are still at the outlet
|
||||
- **Monthly:** add new outlets/newsletters relevant to your category
|
||||
- **Per pitch:** confirm the journalist is still there before sending (check X / LinkedIn for "joined [new place]")
|
||||
|
||||
Store your live, working version in `.agents/media-list.md` (per [journalist-pitching.md](journalist-pitching.md)).
|
||||
@@ -0,0 +1,218 @@
|
||||
# Newsjacking — Reactive PR Workflow
|
||||
|
||||
Injecting your POV into a story that's already trending. Done well: free distribution off a wave of attention. Done badly: cringe at best, brand damage at worst.
|
||||
|
||||
## Contents
|
||||
- When newsjacking works (and when it doesn't)
|
||||
- The detect → score → angle → pitch loop
|
||||
- Newsworthiness scoring rubric
|
||||
- Story angle library
|
||||
- Speed: the only thing that matters
|
||||
- Sources & tooling
|
||||
- Failure modes
|
||||
|
||||
---
|
||||
|
||||
## When Newsjacking Works
|
||||
|
||||
- **Tech/regulatory news in your category** — new law, new platform launch, competitor pivot, big acquisition
|
||||
- **Industry data drops** — a major report drops, you have a sharper take or contradicting data
|
||||
- **Public conversation** — a debate or controversy where your expertise is genuinely relevant
|
||||
- **Seasonal/cyclical moments** — earnings season, year-end reviews, conference weeks
|
||||
|
||||
## When to Skip
|
||||
|
||||
- **Tragedies, accidents, deaths** — no exceptions. Don't.
|
||||
- **Politically charged stories** unless your brand explicitly takes political stances
|
||||
- **You have no genuine expertise** in the area
|
||||
- **The window is already closed** — if a story is 48h+ old and you weren't first, you're late
|
||||
- **The angle is "we have a product for this"** — that's marketing, not journalism
|
||||
|
||||
---
|
||||
|
||||
## The Loop
|
||||
|
||||
A repeatable workflow Claude can run on demand or daily.
|
||||
|
||||
1. **Detect** — surface trending stories in your category (see [Sources & Tooling](#sources--tooling))
|
||||
2. **Score** — apply the [newsworthiness rubric](#newsworthiness-scoring-rubric); drop anything below threshold
|
||||
3. **Angle** — generate 2–3 angles per story using the [angle library](#story-angle-library)
|
||||
4. **Validate** — sanity-check: do you actually have the expertise/data to back this angle?
|
||||
5. **Pitch** — draft a tight pitch to 3–5 journalists who cover this beat (see [journalist-pitching.md](journalist-pitching.md))
|
||||
6. **Post** — also publish on your blog, LinkedIn, X — it builds the trail journalists check before quoting you
|
||||
|
||||
Output format Claude should produce:
|
||||
|
||||
```
|
||||
NEWSJACK CANDIDATE — 2026-06-10
|
||||
|
||||
Story: "EU passes AI Act amendment requiring agent registration"
|
||||
Source: TechCrunch, 3h ago
|
||||
Score: 8/10 (high relevance, fresh, you have proprietary data)
|
||||
|
||||
Angles:
|
||||
1. Data hot take: "Our analysis of 12,000 agent deployments shows 73% would fail this requirement"
|
||||
2. Contrarian: "Why the registration rule will hurt safety, not improve it"
|
||||
3. Customer story: "How [customer] is preparing — interview offer"
|
||||
|
||||
Recommended: #1 (you have unique data, strongest hook)
|
||||
Pitch draft: [see journalist-pitching.md for template]
|
||||
Target journalists: [list with rationale]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Newsworthiness Scoring Rubric
|
||||
|
||||
Score each candidate 1–10 on five dimensions, multiply by the weight, then sum. Max possible: 80 (10 × the 8x weight total).
|
||||
|
||||
| Dimension | What it measures | Weight |
|
||||
|-----------|------------------|--------|
|
||||
| **Timeliness** | Story <24h old? Window still open? | 2x |
|
||||
| **Relevance** | Genuinely in your expertise area? | 2x |
|
||||
| **Angle uniqueness** | Can you say something no one else is saying? | 2x |
|
||||
| **Authority** | Do you have data, customers, or experience to back it? | 1x |
|
||||
| **Reach potential** | Will this story keep growing or has it peaked? | 1x |
|
||||
|
||||
**Threshold:** weighted total ≥ 50/80. Below that, skip.
|
||||
|
||||
**Auto-disqualify if:**
|
||||
- The story is about something tragic
|
||||
- Your angle is "I disagree" with nothing to back it
|
||||
- You haven't actually formed an opinion — you just want to be quoted
|
||||
|
||||
---
|
||||
|
||||
## Story Angle Library
|
||||
|
||||
Use these templates to generate angles fast.
|
||||
|
||||
### 1. Data hot take
|
||||
*"We analyzed [N] [things] after [event]. Here's what we found."*
|
||||
|
||||
Best when you have proprietary data. The journalist gets a stat, you get the citation.
|
||||
|
||||
### 2. Contrarian
|
||||
*"Everyone says [popular take]. Here's why they're wrong."*
|
||||
|
||||
Best when you can defend the position with specifics. Weak when it's just contrarianism for attention.
|
||||
|
||||
### 3. "We predicted this"
|
||||
*"Six months ago we wrote [thing] — here's what's happening now and what's next."*
|
||||
|
||||
Best when you actually did predict it. Lethal to your credibility if you didn't.
|
||||
|
||||
### 4. Customer impact
|
||||
*"Here's a [customer type] who's directly affected. We can put you in touch."*
|
||||
|
||||
Best for B2B. Reporters love named customers willing to talk.
|
||||
|
||||
### 5. Insider explainer
|
||||
*"This story is complicated. Here's what's actually happening."*
|
||||
|
||||
Best when most coverage is missing nuance. You're not arguing — you're educating.
|
||||
|
||||
### 6. Trend connector
|
||||
*"This isn't isolated — it's part of a bigger shift we're seeing in [pattern]."*
|
||||
|
||||
Best when you have several data points or examples to connect.
|
||||
|
||||
### 7. Founder POV
|
||||
*"As someone who's built in this space for [X years], here's the part most people are missing."*
|
||||
|
||||
Best for opinion pieces / op-eds. Weak as a soundbite pitch.
|
||||
|
||||
---
|
||||
|
||||
## Speed: The Only Thing That Matters
|
||||
|
||||
Newsjacking decays fast. Approximate windows:
|
||||
|
||||
| Story type | Effective window |
|
||||
|-----------|------------------|
|
||||
| Breaking tech news | 4–12 hours |
|
||||
| Major regulation / policy | 24–48 hours |
|
||||
| Industry report / data drop | 24–72 hours |
|
||||
| Conference announcement | Same day |
|
||||
| Acquisition / funding news | 12–24 hours |
|
||||
|
||||
**Implication:** if you can't draft and send within the window, don't bother. Set up the loop so detection → pitch takes <2 hours.
|
||||
|
||||
---
|
||||
|
||||
## Sources & Tooling
|
||||
|
||||
Reuses tooling from the `social` skill's listening workflow. Same install: `brew install jq`.
|
||||
|
||||
### Google News RSS (no auth)
|
||||
|
||||
```bash
|
||||
# Replace QUERY with topic (use + for spaces, %22 for quotes)
|
||||
curl -s "https://news.google.com/rss/search?q=QUERY&hl=en-US&gl=US&ceid=US:en" \
|
||||
| xmllint --xpath "//item[position()<11]" - 2>/dev/null
|
||||
```
|
||||
|
||||
### Hacker News (Algolia) for tech stories
|
||||
|
||||
```bash
|
||||
SINCE=$(($(date +%s) - 86400))
|
||||
curl -s "https://hn.algolia.com/api/v1/search_by_date?query=QUERY&tags=story&numericFilters=created_at_i>${SINCE}" \
|
||||
| jq '.hits[] | {title, url, points, num_comments, created_at, hn_url: ("https://news.ycombinator.com/item?id="+.objectID)}'
|
||||
```
|
||||
|
||||
### Reddit (for category-specific subs)
|
||||
|
||||
```bash
|
||||
curl -s -A "newsjack/1.0" \
|
||||
"https://www.reddit.com/r/SUBREDDIT/top.json?t=day&limit=15" \
|
||||
| jq '.data.children[].data | {title, url, score, num_comments, created_utc}'
|
||||
```
|
||||
|
||||
### Journalist research (browser-driven)
|
||||
|
||||
For finding *which* journalists are covering the story right now:
|
||||
- **dev-browser** → Google News search for the story → click through to articles → note the bylines
|
||||
- Then go to those journalists' X / LinkedIn / Muck Rack profile to confirm beat and recent coverage
|
||||
|
||||
See also [journalist-pitching.md](journalist-pitching.md) for the full discovery workflow.
|
||||
|
||||
### Source list
|
||||
|
||||
For repeatable monitoring, add a "Newsjacking topics" section to `.agents/listening-sources.md` (template in the `social` skill's references):
|
||||
|
||||
```markdown
|
||||
## Newsjacking topics (Google News RSS)
|
||||
- "AI agent regulation"
|
||||
- "[your category] funding"
|
||||
- "[your competitors] OR [adjacent competitors]"
|
||||
|
||||
## Industry data drops (RSS / manual)
|
||||
- Pitchbook reports
|
||||
- a16z state of [industry] reports
|
||||
- [your category] benchmark reports
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Failure Modes
|
||||
|
||||
Things that have ended careers and brands.
|
||||
|
||||
- **Tragedy-jacking** — Oreo's 2013 Super Bowl tweet worked. Most attempts since have not. Wartime, disasters, deaths: don't.
|
||||
- **The forced fit** — "Here's our take on [trending story] — it's actually about [our product]." Journalists see through this instantly.
|
||||
- **The empty take** — pitching "we have an opinion" without specifics. Journalists need a quote-worthy line, not "we're closely watching this."
|
||||
- **Speed without judgment** — being first with a bad take is worse than being late with a good one. The 30-minute "is this brand-appropriate?" gut check exists for a reason.
|
||||
- **Pitching the same angle to 50 journalists** — they talk. Get caught once, lose the relationships.
|
||||
- **No follow-through** — pitch goes out, journalist responds in 20 minutes, founder takes 6 hours to reply. Story moves on.
|
||||
|
||||
---
|
||||
|
||||
## Companion Practice: The Public Trail
|
||||
|
||||
Every newsjack pitch is stronger if the journalist can find evidence you've been thinking about this publicly. Before pitching:
|
||||
|
||||
1. Publish a short post (blog, LinkedIn, X thread) with your take
|
||||
2. Reference it in the pitch ("more thinking here: [link]")
|
||||
3. This signals you're not opportunistic — you're an actual voice in the space
|
||||
|
||||
If you don't have time to publish, you're probably not ready to pitch.
|
||||
@@ -0,0 +1,188 @@
|
||||
# Press Request Platforms — Inbound PR
|
||||
|
||||
Journalists posting "I need a source for X" — you respond, sometimes you get quoted, sometimes you don't. The cheapest PR play available, but only if you treat it seriously.
|
||||
|
||||
## Contents
|
||||
- The major platforms
|
||||
- Daily triage workflow
|
||||
- Response template
|
||||
- What makes a response get selected
|
||||
- What kills a response
|
||||
- ROI reality check
|
||||
|
||||
---
|
||||
|
||||
## The Major Platforms
|
||||
|
||||
| Platform | What it is | Cost | Quality |
|
||||
|----------|-----------|------|---------|
|
||||
| **[Connectively](https://www.connectively.us)** (formerly HARO) | Daily email digest of journalist queries | Free tier; paid for filters | Mixed — high volume, lots of noise |
|
||||
| **[Qwoted](https://www.qwoted.com)** | Web app with journalist requests | Free; paid for outreach | Good — better-quality outlets |
|
||||
| **[Featured](https://featured.com)** | Web app, expert profiles, journalist requests | Free tier; paid pro | Good for thought-leadership snippets |
|
||||
| **[Help A B2B Writer](https://helpab2bwriter.com)** | Twice-weekly email of B2B queries | Free | High — B2B-focused, low spam |
|
||||
| **[SourceBottle](https://www.sourcebottle.com)** | Australia-focused but global queries | Free | Variable |
|
||||
| **[Terkel](https://terkel.io)** | Roundup-style ("we asked 50 experts…") | Free | Volume-heavy, low effort |
|
||||
| **[JournoRequests](https://twitter.com/journorequests)** | X account aggregating tweets | Free | UK-skewed, real-time |
|
||||
| **#JournoRequest** (X hashtag) | Live journalist requests | Free | Real-time, fast-moving |
|
||||
|
||||
**Recommended starter set:** Connectively + Qwoted + Help A B2B Writer + monitoring `#JournoRequest` on X.
|
||||
|
||||
---
|
||||
|
||||
## Daily Triage Workflow
|
||||
|
||||
These platforms generate volume. Treat it like email triage — fast pass, deep response on the rare matches.
|
||||
|
||||
### Step 1 — Filter (5 min)
|
||||
|
||||
For each digest / request feed:
|
||||
- Drop everything where you don't have **direct experience or data**
|
||||
- Drop everything from outlets your ICP doesn't read
|
||||
- Drop everything with a deadline you can't meet
|
||||
- Keep only requests where you can give a **complete, named, on-the-record answer**
|
||||
|
||||
Realistic conversion: 50 daily requests → 2–4 worth answering.
|
||||
|
||||
### Step 2 — Deep response (15 min per request)
|
||||
|
||||
For each keeper:
|
||||
- Read the request 3 times — what's the *actual* angle?
|
||||
- Look up the journalist if possible — recent coverage, beat
|
||||
- Write a custom response (see [template](#response-template))
|
||||
- Send within their stated deadline (early > late)
|
||||
|
||||
### Step 3 — Log
|
||||
|
||||
Track in a spreadsheet:
|
||||
- Date
|
||||
- Platform
|
||||
- Journalist + outlet
|
||||
- Topic
|
||||
- Response sent (yes/no)
|
||||
- Outcome (no response / passed / quoted / linked)
|
||||
|
||||
After 30 responses, you'll see which topics/platforms convert.
|
||||
|
||||
---
|
||||
|
||||
## Response Template
|
||||
|
||||
Keep responses under 200 words. Journalists are scanning 50+ replies for one quote.
|
||||
|
||||
```
|
||||
Hi [name],
|
||||
|
||||
Quick response to your request about [topic].
|
||||
|
||||
[Specific credential — 1 sentence. "Built X for 5 years" / "Led marketing at Y" / "Have analyzed N companies in space"]
|
||||
|
||||
The most important thing about [topic]: [your actual point in 2 sentences].
|
||||
|
||||
[A specific example, story, or data point — this is what gets quoted.]
|
||||
|
||||
[If applicable: a contrarian or surprising angle that differentiates from typical answers.]
|
||||
|
||||
Happy to expand on any of this, share data, or be quoted directly.
|
||||
|
||||
Feel free to use this attribution:
|
||||
[Your name], [your title], [your company]
|
||||
|
||||
Contact for follow-up: [email + phone]
|
||||
```
|
||||
|
||||
**Note the structure:**
|
||||
1. One-sentence intro
|
||||
2. One-sentence credential
|
||||
3. Two-sentence answer
|
||||
4. Specific example (the quotable part)
|
||||
5. Optional: differentiator
|
||||
6. Clear offer
|
||||
7. Pre-written attribution (saves them 30 seconds)
|
||||
8. Contact info
|
||||
|
||||
---
|
||||
|
||||
## What Makes a Response Get Selected
|
||||
|
||||
After analyzing hundreds of quoted responses, the patterns:
|
||||
|
||||
### Quotable specificity
|
||||
**Bad:** "Companies should focus on customer experience."
|
||||
**Good:** "When we A/B tested 47 onboarding flows, the version with a 30-second video at step 3 increased activation by 41%."
|
||||
|
||||
The good version is a quote. The bad version is filler.
|
||||
|
||||
### Concrete credential
|
||||
**Bad:** "As a marketing expert..."
|
||||
**Good:** "I've run growth at three Series B SaaS companies, all in B2B sales tooling."
|
||||
|
||||
Specificity beats title-stacking.
|
||||
|
||||
### Story over advice
|
||||
**Bad:** "It's important to track the right metrics."
|
||||
**Good:** "We almost shut down because we were optimizing for MRR when our real problem was activation. Once we switched to tracking 7-day activation, everything else followed."
|
||||
|
||||
Stories make articles. Advice makes filler.
|
||||
|
||||
### Pre-formatted for their workflow
|
||||
- Pre-written attribution
|
||||
- Multiple quotable lines (let them pick)
|
||||
- High-res headshot link (don't attach)
|
||||
- One-line company description
|
||||
|
||||
### Time match
|
||||
**Most quotes come from responses sent in the first 6 hours.** After 24 hours, your chances drop sharply. Treat deadlines as if they're 24h earlier than stated.
|
||||
|
||||
---
|
||||
|
||||
## What Kills a Response
|
||||
|
||||
- **Pitching your product** when they asked for expert commentary
|
||||
- **Generic advice** that could come from any expert
|
||||
- **Multiple "experts" from your company** responding to the same request (looks coordinated, often is)
|
||||
- **Hiring a PR firm to spam responses** — journalists smell it
|
||||
- **Demanding a link back** to your site — most can't promise links
|
||||
- **Ignoring the deadline** by 1+ days
|
||||
- **Long bio sections** before the actual answer
|
||||
- **Asking to "see the article before publication"** — you don't get to do that
|
||||
- **Asking what other experts said** so you can differentiate — they won't tell you
|
||||
|
||||
---
|
||||
|
||||
## ROI Reality Check
|
||||
|
||||
Most teams overinvest in these platforms because they're cheap. Be honest:
|
||||
|
||||
| Effort | Realistic outcome (90 days) |
|
||||
|--------|----------------------------|
|
||||
| 5 hr/week, custom responses | 3–10 quoted placements |
|
||||
| 1 hr/week, template responses | 0–2 placements |
|
||||
| Outsourced to PR firm | Lots of submissions, few quotes |
|
||||
|
||||
**A quote in a tier-1 outlet is worth:**
|
||||
- A backlink (DR depends on outlet)
|
||||
- A sales-collateral asset ("As featured in...")
|
||||
- AI-citation surface area
|
||||
- Brand legitimacy in the abstract
|
||||
|
||||
**A quote in a tier-3 outlet is worth:**
|
||||
- A backlink, often nofollow
|
||||
- Maybe an Instagram screenshot
|
||||
|
||||
**Decision rule:** if you can sustain 5 hr/week of quality responses for 90 days, this is worth it. If you can only do 1 hr/week, skip it and invest in [proactive pitching](journalist-pitching.md) instead.
|
||||
|
||||
---
|
||||
|
||||
## Setup Checklist
|
||||
|
||||
Before you start responding:
|
||||
|
||||
- [ ] Press page exists and is current (see main SKILL.md)
|
||||
- [ ] One-line credential is written and rehearsed
|
||||
- [ ] Headshot is high-res and at a public URL
|
||||
- [ ] You have 3–5 specific stories / data points ready to deploy
|
||||
- [ ] You've decided which 2–3 platforms to use (don't try all 7)
|
||||
- [ ] You've blocked a daily 20-min window for triage
|
||||
- [ ] You're logging responses in a tracker
|
||||
|
||||
Without these, you're spamming and wasting their time and yours.
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: sales-enablement
|
||||
description: "When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email."
|
||||
description: "When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers."
|
||||
metadata:
|
||||
version: 2.0.0
|
||||
version: 2.0.1
|
||||
---
|
||||
|
||||
# Sales Enablement
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: social
|
||||
description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' or 'create a reel.' Use this for social media content creation, repurposing, scheduling, and short-form video scripting. For broader content strategy, see content-strategy. For paid video ads, see ad-creative."
|
||||
description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social media content creation, repurposing, scheduling, short-form video scripting, and social listening. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations."
|
||||
metadata:
|
||||
version: 2.0.0
|
||||
version: 2.2.0
|
||||
---
|
||||
|
||||
# Social Content
|
||||
@@ -105,6 +105,8 @@ The first line determines whether anyone reads the rest.
|
||||
|
||||
**For post templates and more hooks**: See [references/post-templates.md](references/post-templates.md)
|
||||
|
||||
**For carousels** (Instagram carousels, LinkedIn document posts): See [references/carousel-frameworks.md](references/carousel-frameworks.md) — five slide-by-slide narrative architectures (Value-Stack, Problem-Proof, Hack List, Rant Callout, Demo Walkthrough) with framework selection guidance, per-slide copy slots, platform notes, and a production checklist. Pick the framework before writing slides.
|
||||
|
||||
---
|
||||
|
||||
## Content Repurposing System
|
||||
@@ -211,6 +213,8 @@ Extract "content atoms" — self-contained moments from any long-form content th
|
||||
3. Share/repost with added insight (5 min)
|
||||
4. Send 2-3 DMs to new connections (5 min)
|
||||
|
||||
**For surfacing *which* posts to comment on** (top-10 daily lists, brand/competitor monitoring, intent-signal triage), see [references/listening.md](references/listening.md). Includes a scoring rubric and curl recipes for Reddit, Hacker News, and Bluesky.
|
||||
|
||||
### Quality Comments
|
||||
|
||||
- Add new insight, not just "Great post!"
|
||||
|
||||
@@ -87,6 +87,21 @@
|
||||
"May note social-to-email bridge context"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 7,
|
||||
"prompt": "I want to turn our new pricing guide into a LinkedIn carousel. It has 9 negotiation tactics for SaaS buyers. Help me structure the slides.",
|
||||
"expected_output": "Should load references/carousel-frameworks.md and pick a framework BEFORE writing slides — a list of 9 named tactics maps to Hack List (or Value-Stack; should justify the choice), not Rant Callout or Demo Walkthrough. Should produce a slide-by-slide structure: contrarian or exact-count cover (slide 1 written as a standalone scroll-stopper), one named tactic per slide, and a synthesis + single-CTA close. Should apply LinkedIn document-post notes (PDF upload, denser text tolerated, post text written as its own hook rather than 'see attached'). Should keep any count promised on the cover exactly delivered and flag that stats/claims must be real. Should mention judging performance on saves/completion rather than likes.",
|
||||
"assertions": [
|
||||
"Loads or applies the carousel-frameworks reference",
|
||||
"Selects an appropriate framework (Hack List or Value-Stack) with a stated reason before drafting slides",
|
||||
"Slide 1 is written as a standalone scroll-stopper with the count or contrarian claim",
|
||||
"One tactic/idea per slide, each named",
|
||||
"Final slide has a synthesis and exactly one CTA",
|
||||
"Applies LinkedIn document-post guidance (PDF, post text as its own hook)",
|
||||
"Does not invent stats or pad the tactic count"
|
||||
],
|
||||
"files": []
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@@ -0,0 +1,141 @@
|
||||
# Carousel Frameworks
|
||||
|
||||
Five slide-by-slide narrative architectures for carousels — Instagram carousels and LinkedIn document posts. Each framework is a different *reason to keep swiping*; picking the right one for the content matters more than polishing individual slides.
|
||||
|
||||
A carousel is not a blog post chopped into squares. It's a swipe-through with two jobs per slide: deliver one idea, and make the next swipe irresistible. These frameworks encode structures that show up repeatedly in high-performing carousels; treat them as starting structures to adapt, not rigid formulas — and expect to validate against your own analytics.
|
||||
|
||||
## Picking a Framework
|
||||
|
||||
| Your content is... | Use | Why |
|
||||
|---|---|---|
|
||||
| A list of resources, tools, or tips | **A: Value-Stack** | Completeness is the promise; the count is the hook |
|
||||
| A personal result with a system behind it | **B: Problem-Proof** | Proof opens and closes the loop; the system is the meat |
|
||||
| Several named techniques on one theme | **C: Hack List** | Each hack re-earns the swipe independently |
|
||||
| A strong opinion about a common practice | **D: Rant Callout** | Conviction is the content; structure keeps it fair |
|
||||
| A product or workflow you can show | **E: Demo Walkthrough** | Seeing the steps is more persuasive than describing them |
|
||||
|
||||
Two cross-framework rules before the specifics:
|
||||
|
||||
- **Slide 1 is the thumbnail.** It competes in the feed alone, before anyone knows a carousel follows. Design and write it as a standalone scroll-stopper.
|
||||
- **One visual template per carousel.** Same layout, type scale, and palette on every interior slide. Variety between slides reads as clutter; consistency lets the *content* change while the frame stays still.
|
||||
|
||||
---
|
||||
|
||||
## Framework A: Value-Stack (4–14 slides)
|
||||
|
||||
The "everything you need" carousel. Works because the cover makes a completeness claim — an exact count and an exact deliverable — and every swipe pays it down.
|
||||
|
||||
| Slide | Job | Pattern |
|
||||
|---|---|---|
|
||||
| 1 — Cover | State the exact count + exact deliverable. Specificity proves scale upfront. | "[N] [resource type] for [role/outcome]" |
|
||||
| 2 to N−1 — Value delivery | One item or category per slide, 3–6 concrete sub-items each. Same visual template, zero filler slides. | "[Category/item] — [sub-items]" |
|
||||
| N — Close | Convert the swipe-through into an action. | "[Action] for [the payoff]" — comment a keyword, follow, link in bio |
|
||||
|
||||
**Why the exact count matters:** "27 free tools" outperforms "the best free tools" because a number is a checkable promise — the reader can verify you delivered. Rounding up with padding breaks the trust the count created.
|
||||
|
||||
*SaaS example:* "12 ChatGPT prompts for SaaS onboarding emails" → one prompt per slide with the use case → "Comment PROMPTS and I'll send the full doc."
|
||||
|
||||
**Failure mode:** filler slides to hit a bigger number. Cut to the real count; a tight 8 beats a padded 14.
|
||||
|
||||
---
|
||||
|
||||
## Framework B: Problem-Proof (6–10 slides)
|
||||
|
||||
The "I did X, here's the system" carousel. The hook is a *result stated as fact*, not advice — and the final slide shows the receipt, closing the loop slide 1 opened.
|
||||
|
||||
| Slide | Job | Pattern |
|
||||
|---|---|---|
|
||||
| 1 — Hook | A specific personal claim with a number. A result, not a tip. | "[I/we did X]. [Specific result, with number]." |
|
||||
| 2 — Reframe the problem | Name what's *actually* going wrong so the reader recognizes themselves. | "The real problem — [named issue]" |
|
||||
| 3–4 — The mechanism | Show the real system: named tools, named steps. Concrete beats vague. | "The system — [named tools/steps]" |
|
||||
| 5 to N−1 — The detail | The literal prompt text, template, or step-by-step. This is the save-worthy part. | "[The literal prompt or process detail]" |
|
||||
| N — Proof | The actual output artifact. A screenshot, not a description. | "[Screenshot of output] — the receipt" |
|
||||
|
||||
**The open loop is the engine:** slide 1 makes a claim, the last slide proves it, and everything between explains how. Readers swipe to see whether the receipt is real.
|
||||
|
||||
*SaaS example:* "We cut churn 22% with one onboarding email." → the real problem (activation, not price) → the sequence structure → the literal email copy → the retention chart.
|
||||
|
||||
**Failure mode:** vague mechanism slides ("optimize your workflow") — if the middle slides don't name tools and steps, the proof slide reads as luck, not system.
|
||||
|
||||
---
|
||||
|
||||
## Framework C: Hack List (6–10 slides)
|
||||
|
||||
The "numbered techniques" carousel. A contrarian cover creates status anxiety — most people are doing this wrong — and each numbered hack independently re-earns the swipe.
|
||||
|
||||
| Slide | Job | Pattern |
|
||||
|---|---|---|
|
||||
| 1 — Contrarian hook | A stat or claim implying most people fail at this. | "[Stat implying most people fail at X]" |
|
||||
| 2 — The problem | Why the common approach fails, ideally with an analogy. | "The problem — [why it fails]" |
|
||||
| 3 to N−1 — Numbered hacks | One named technique per slide. Bad-vs-good contrast makes each hack land instantly. | "Hack #[n] — [named technique]" |
|
||||
| N — Synthesis + close | A one-line thesis tying the hacks together, then a save/share/follow CTA. | "[Thesis tying hacks together]" + [CTA] |
|
||||
|
||||
**Name every technique.** "The 3-second rule" is shareable and memorable; "keep it short" is neither. Named techniques travel — people repeat them and credit the source.
|
||||
|
||||
*SaaS example:* "90% of trial emails never get opened." → why (they read like receipts, not messages) → Hack #1: The founder-from line, Hack #2: The one-question subject, ... → "Trial emails are conversations, not confirmations. Save this for your next sequence."
|
||||
|
||||
**Failure mode:** hacks that are restatements of each other. Each slide must survive alone — if two hacks collapse into one idea, merge them and go shorter.
|
||||
|
||||
---
|
||||
|
||||
## Framework D: Rant Callout (4–8 slides)
|
||||
|
||||
The "someone had to say it" carousel. Personality-led and polarizing by design — the structure exists to keep the heat *fair* so it reads as conviction, not bitterness.
|
||||
|
||||
| Slide | Job | Pattern |
|
||||
|---|---|---|
|
||||
| 1 — Provocative claim | An unpopular opinion or direct accusation about a common practice. | "Unpopular opinion — [common practice]" |
|
||||
| 2 to N−2 — Escalate the argument | Sensory, specific detail. Show the offense; don't gesture at it abstractly. Each slide raises the stakes. | "[Escalating, specific complaint]" |
|
||||
| N−1 — Fairness pivot | "Don't get me wrong…" — clarify what you're *not* attacking. Anti-laziness, not anti-tool; anti-practice, not anti-person. | "The problem isn't [X], it's [Y]" |
|
||||
| N — Close | Firm, personality-forward sign-off. Signed rants read as owned opinions; anonymous ones read as potshots. | "[Firm sign-off] — signed [name/persona]" |
|
||||
|
||||
**The fairness pivot is what makes it work.** Without it you're yelling; with it you're drawing a precise line, and precise lines get quoted. It also pre-empts the top hostile comment.
|
||||
|
||||
*SaaS example:* "Your AI-generated LinkedIn posts are costing you customers." → the specifics (same em-dash cadence, same 'game-changer' vocabulary, zero lived detail) → "Don't get me wrong — I use AI daily. The problem isn't the tool, it's publishing the first draft." → "Write like you talk. — [Name]"
|
||||
|
||||
**Failure modes:** skipping the pivot (reads unhinged, invites pile-ons), or ranting about something your own product/content visibly does (the comments will find it).
|
||||
|
||||
---
|
||||
|
||||
## Framework E: Demo Walkthrough (5–11 slides)
|
||||
|
||||
The "watch it work" carousel for product or workflow content. Show the finished result first, then the steps — the outcome earns attention for the process.
|
||||
|
||||
| Slide | Job | Pattern |
|
||||
|---|---|---|
|
||||
| 1 — Product + outcome | Brand/product plus the finished result. Lead with what they get. | "[Product] + [outcome], finished result" |
|
||||
| 2 — Problem it solves | The specific frustration this replaces. | "[The specific pain this replaces]" |
|
||||
| 3 — Process overview | The numbered step list, shown *before* the detail. Seeing the whole path lowers mid-swipe drop-off — readers commit when they know how long the road is. | "[N] steps to [outcome] in [timeframe]" |
|
||||
| 4 to N−1 — Step-by-step | One real UI screenshot per step with a short caption. Real screenshots; mockups read as vaporware. | "Step [n] — [screenshot] — [caption]" |
|
||||
| N — Result + positioning | The full-size output plus one brand-philosophy line. | "[Final output] + [positioning line]" |
|
||||
|
||||
**Overview-before-detail is the key move** (same reason recipe sites list ingredients before instructions): a reader who's seen "4 steps, 10 minutes" on slide 3 will finish; a reader dropped straight into step 1 with no map bails at step 2.
|
||||
|
||||
*SaaS example:* "From CSV to live dashboard in 4 steps" → the pain (weekly manual reporting) → the 4-step overview → one screenshot per step → the finished dashboard + "Built for marketers, not analysts."
|
||||
|
||||
**Failure mode:** screenshots with too much UI. Crop to the action, zoom the relevant control, annotate with one arrow — each screenshot should make sense at thumbnail size.
|
||||
|
||||
---
|
||||
|
||||
## Platform Notes
|
||||
|
||||
**Instagram:** 1080×1350 (4:5) slides; up to 20 slides but the frameworks' ranges above reflect where completion rates hold. The caption carries the searchable text — restate the hook and add context, don't just repeat slide 1. First slide doubles as the grid thumbnail.
|
||||
|
||||
**LinkedIn (document posts):** Upload as PDF. Square or 4:5. LinkedIn shows a "N pages" badge — Value-Stack's exact-count cover plays especially well here. B2B tolerates denser text per slide than Instagram, but the one-idea-per-slide rule still holds. The post text above the document is a second hook — write it as its own post, not a throwaway "see attached."
|
||||
|
||||
**TikTok photo mode:** Same frameworks work; pacing skews faster — trim each framework toward its minimum slide count.
|
||||
|
||||
## Production Checklist
|
||||
|
||||
- [ ] Slide 1 works as a standalone feed post (test: would it stop the scroll with no carousel behind it?)
|
||||
- [ ] One idea per slide — if a slide needs two sentences of setup, split it
|
||||
- [ ] Same visual template on every interior slide
|
||||
- [ ] Any count promised on the cover is exactly delivered (no filler, no rounding)
|
||||
- [ ] Claims and numbers are real and yours — no invented stats or borrowed screenshots
|
||||
- [ ] Text is legible at thumbnail size (minimum ~28pt at 1080px wide)
|
||||
- [ ] Final slide has one CTA, not three
|
||||
- [ ] Caption/post text written as its own hook, not a repeat of slide 1
|
||||
|
||||
## Measuring What Worked
|
||||
|
||||
Judge carousels on **saves and completion**, not likes — saves signal reference value (the algorithmic win for carousels), and where per-slide analytics exist (Instagram professional insights, LinkedIn document analytics, or third-party tools), drop-off position tells you which slide broke the swipe chain. When a carousel underperforms, the fix is usually slide 1 (didn't stop the scroll) or the framework choice (list content forced into a rant structure), not the middle slides. Track per-framework performance and double down on the two that fit your audience — see [reverse-engineering.md](reverse-engineering.md) for the analysis workflow.
|
||||
@@ -0,0 +1,123 @@
|
||||
# Listening Sources — Template
|
||||
|
||||
Copy this file to `.agents/listening-sources.md` in your project (or `.claude/listening-sources.md`) and fill in the brackets. Claude reads it when running the [listening workflow](listening.md).
|
||||
|
||||
Delete sections you don't use. Keep this short and current — stale sources are worse than no sources.
|
||||
|
||||
---
|
||||
|
||||
## What We're Listening For
|
||||
|
||||
**Brand / product:** [Your product name]
|
||||
**Category:** [e.g., "AI writing assistant", "Postgres GUI"]
|
||||
**Goal:** [e.g., "find people switching from Notion", "engage with B2B SaaS founders 50-200 employees"]
|
||||
|
||||
## ICP (for scoring)
|
||||
|
||||
Used by the [scoring rubric](listening.md#scoring-rubric) to judge ICP fit.
|
||||
|
||||
- **Role:** [e.g., "founder, head of marketing, marketing ops lead"]
|
||||
- **Company stage:** [e.g., "seed to Series B SaaS, 10-200 employees"]
|
||||
- **Industry:** [e.g., "B2B SaaS, infra, devtools"]
|
||||
- **Signals they're a fit:** [e.g., "writes about GTM, runs paid ads, recently raised"]
|
||||
|
||||
---
|
||||
|
||||
## Target Accounts
|
||||
|
||||
Engage with **every** post from these accounts when relevant. Keep this list to 20-50 max.
|
||||
|
||||
### LinkedIn (browser-driven — use dev-browser to view feed)
|
||||
- [Name] — `linkedin.com/in/handle`
|
||||
- [Name] — `linkedin.com/in/handle`
|
||||
|
||||
### X / Twitter (browser-driven)
|
||||
- [@handle]
|
||||
- [@handle]
|
||||
|
||||
### Reddit
|
||||
- u/[username]
|
||||
- u/[username]
|
||||
|
||||
### Bluesky
|
||||
- [handle.bsky.social]
|
||||
|
||||
### Blogs / Newsletters (RSS)
|
||||
- [Name] — `https://example.com/feed/`
|
||||
- [Name] — `https://example.substack.com/feed`
|
||||
|
||||
### YouTube channels (RSS)
|
||||
- [Name] — channel ID `UCxxxxxxxx`
|
||||
|
||||
---
|
||||
|
||||
## Keywords (intent signals)
|
||||
|
||||
Search across all platforms. Claude runs these through Reddit, HN, Bluesky on the [daily loop](listening.md#the-daily-triage-loop).
|
||||
|
||||
### High-intent (someone shopping or switching)
|
||||
- `"alternative to [competitor]"`
|
||||
- `"looking for a [category] tool"`
|
||||
- `"recommend a [category]"`
|
||||
- `"switching from [competitor]"`
|
||||
- `"frustrated with [competitor]"`
|
||||
|
||||
### Problem signals (someone in pain)
|
||||
- `"[category] is so [bad/hard/expensive]"`
|
||||
- `"why is [category] [problem]"`
|
||||
- `"hate [pain point]"`
|
||||
|
||||
### Brand mentions
|
||||
- `"[your brand]"`
|
||||
- `"[your brand misspelling]"`
|
||||
- `"[your domain]"`
|
||||
|
||||
### Competitor mentions (monitor for switching language)
|
||||
- `"[competitor 1]"`
|
||||
- `"[competitor 2]"`
|
||||
|
||||
---
|
||||
|
||||
## Subreddits
|
||||
|
||||
Pulled via Reddit JSON API on the daily loop.
|
||||
|
||||
- r/SaaS
|
||||
- r/Entrepreneur
|
||||
- r/[your niche, e.g., "marketing", "devtools"]
|
||||
- r/[adjacent community]
|
||||
|
||||
---
|
||||
|
||||
## Saved Searches (manual / browser-driven)
|
||||
|
||||
URLs Claude opens via dev-browser to scan.
|
||||
|
||||
### LinkedIn Sales Navigator
|
||||
- [Search name] — `https://linkedin.com/sales/search/people?...`
|
||||
|
||||
### LinkedIn (regular)
|
||||
- Posts hashtag — `https://linkedin.com/feed/hashtag/yourtopic/`
|
||||
|
||||
### X advanced search
|
||||
- [Search name] — `https://x.com/search?q=...&f=live`
|
||||
|
||||
---
|
||||
|
||||
## Do Not Engage
|
||||
|
||||
Save yourself the regret.
|
||||
|
||||
- Accounts known for bad-faith dunking: [@handle], [@handle]
|
||||
- Blocked brands / competitors who'll screenshot: [list]
|
||||
- Topics to avoid: [politics, [your founder's hot takes], etc.]
|
||||
|
||||
---
|
||||
|
||||
## Notes for Claude
|
||||
|
||||
- When asked for "today's top 10," output in the format defined in [listening.md](listening.md#the-daily-triage-loop)
|
||||
- For LinkedIn and X, use dev-browser with the persistent session (user is logged in)
|
||||
- For everything else, use the curl recipes in [listening.md](listening.md#sources--light-tooling-curl-recipes)
|
||||
- Default lookback: 24h. User can override.
|
||||
- Always ask before posting — output drafts, user approves and posts manually
|
||||
@@ -0,0 +1,283 @@
|
||||
# Social Listening & Engagement Triage
|
||||
|
||||
How to surface the right posts to engage with each day — instead of randomly scrolling. The goal is a short, scorable list ("here are your top 10 posts to comment on") rather than an open feed.
|
||||
|
||||
## Contents
|
||||
- When to use this
|
||||
- The daily triage loop
|
||||
- Scoring rubric
|
||||
- Comment quality tiers
|
||||
- Sources & light tooling (curl recipes)
|
||||
- Per-platform notes
|
||||
- Common workflows
|
||||
|
||||
---
|
||||
|
||||
## When to Use This
|
||||
|
||||
Use listening when the goal is **commenting and relationships**, not posting. Typical asks:
|
||||
- "Give me the top 10 posts I should comment on today"
|
||||
- "Who's complaining about [competitor] right now?"
|
||||
- "Find people asking for a tool like mine"
|
||||
- "Surface posts from my 20 target accounts in the last 24h"
|
||||
- "What's the conversation around [topic] this week?"
|
||||
|
||||
If the user wants to **create** content, use the rest of the social skill. Listening feeds creation (it surfaces angles, language, objections), but the output is different.
|
||||
|
||||
---
|
||||
|
||||
## The Daily Triage Loop
|
||||
|
||||
A repeatable 20-minute loop the user (or you, on their behalf) can run each morning.
|
||||
|
||||
1. **Pull** — fetch new posts from defined sources (target accounts, keywords, subreddits, hashtags). See [tooling](#sources--light-tooling-curl-recipes).
|
||||
2. **Filter** — drop anything older than 24h, low signal, or off-topic.
|
||||
3. **Score** — apply the [rubric](#scoring-rubric). Keep top 10.
|
||||
4. **Draft** — for each, draft a comment matched to the post's tier.
|
||||
5. **Post** — user reviews, edits, posts. Mark which actually went live.
|
||||
6. **Log** — track what you commented on and what got replies. This is your engagement loop dataset.
|
||||
|
||||
Output format Claude should produce:
|
||||
|
||||
```
|
||||
TOP 10 POSTS — 2026-06-05
|
||||
|
||||
1. [Score 9/10] @author — LinkedIn — 2h ago
|
||||
"We just rolled out X and the team is loving it…"
|
||||
Why: ICP fit (B2B SaaS, 50–200 employees), buying-intent signal
|
||||
Suggested comment: [draft]
|
||||
Link: https://…
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Scoring Rubric
|
||||
|
||||
Score each post 1–10 across five dimensions, then sum and rank.
|
||||
|
||||
| Dimension | What it measures | Weight |
|
||||
|-----------|------------------|--------|
|
||||
| **ICP fit** | Is the author your target customer / influencer? | 2x |
|
||||
| **Intent signal** | Are they expressing a problem, asking, or shopping? | 2x |
|
||||
| **Reach potential** | Is the post getting traction (likes/comments rising)? | 1x |
|
||||
| **Comment opportunity** | Can you say something genuinely useful, not generic? | 2x |
|
||||
| **Recency** | Posted in last 1–4h (early comments win, especially on LinkedIn) | 1x |
|
||||
|
||||
**Intent signal examples (high-value):**
|
||||
- "Looking for a tool that does X"
|
||||
- "Why is [category] so painful?"
|
||||
- "We just switched from [competitor] because…"
|
||||
- "Anyone use [competitor] — is it worth it?"
|
||||
- A complaint about a known competitor
|
||||
|
||||
**Drop if any of these are true:**
|
||||
- Author isn't ICP and isn't an influencer
|
||||
- Post is >24h old and already has 50+ comments (your comment buries)
|
||||
- Generic motivational/AI-slop post
|
||||
- Self-promotion thread where comments don't get reach
|
||||
- You can't add anything beyond "Great post!"
|
||||
|
||||
---
|
||||
|
||||
## Comment Quality Tiers
|
||||
|
||||
Match the comment to the post. Don't waste a tier-1 draft on a tier-3 opportunity.
|
||||
|
||||
**Tier 1 — Relationship builder (target accounts, ICP, high intent)**
|
||||
- Add a specific insight or counter-example
|
||||
- Reference your own experience with specifics (numbers, names, outcomes)
|
||||
- Ask a thoughtful follow-up that invites a reply
|
||||
- Length: 2–4 sentences, no link
|
||||
|
||||
**Tier 2 — Visibility play (high-reach post, adjacent topic)**
|
||||
- Add one sharp insight in one sentence
|
||||
- Pattern: "Agreed — and the part most miss is [X]"
|
||||
- Length: 1–2 sentences
|
||||
|
||||
**Tier 3 — Light touch (relationship maintenance)**
|
||||
- Specific reaction, not "Love this"
|
||||
- Quote a specific line and react to it
|
||||
- Length: 1 sentence
|
||||
|
||||
**Never:** "Great post!", emoji-only, "+1", LinkedIn-isms like "This is gold 🔥"
|
||||
|
||||
---
|
||||
|
||||
## Sources & Light Tooling (curl recipes)
|
||||
|
||||
These are public JSON endpoints — no auth needed. Run them from bash, pipe to `jq`, and Claude can parse the output to score and draft comments.
|
||||
|
||||
**Requires:** `jq` (most recipes) and `xmllint` (RSS only). Install once:
|
||||
```bash
|
||||
# macOS
|
||||
brew install jq
|
||||
# xmllint ships with macOS; on Linux: apt install libxml2-utils
|
||||
```
|
||||
|
||||
### Reddit (free, scriptable)
|
||||
|
||||
**New posts in a subreddit:**
|
||||
```bash
|
||||
curl -s -A "listening/1.0" \
|
||||
"https://www.reddit.com/r/SaaS/new.json?limit=25" \
|
||||
| jq '.data.children[].data | {title, author, url: ("https://reddit.com"+.permalink), score, num_comments, created_utc, selftext: (.selftext | .[0:300])}'
|
||||
```
|
||||
|
||||
**Search across Reddit by keyword (last day, sorted new):**
|
||||
```bash
|
||||
curl -s -A "listening/1.0" \
|
||||
"https://www.reddit.com/search.json?q=KEYWORD&sort=new&t=day&limit=25" \
|
||||
| jq '.data.children[].data | {subreddit, title, url: ("https://reddit.com"+.permalink), author, score, created_utc}'
|
||||
```
|
||||
|
||||
Swap `KEYWORD` for things like `"alternative to notion"`, `"recommend a crm"`, your competitor names, or your own brand for mentions. Use quotes around multi-word phrases.
|
||||
|
||||
### Hacker News (Algolia search)
|
||||
|
||||
**Recent stories mentioning a keyword (last 24h):**
|
||||
```bash
|
||||
SINCE=$(($(date +%s) - 86400))
|
||||
curl -s "https://hn.algolia.com/api/v1/search_by_date?query=KEYWORD&tags=story&numericFilters=created_at_i>${SINCE}" \
|
||||
| jq '.hits[] | {title, url, author, points, num_comments, created_at, story_id: .objectID, hn_url: ("https://news.ycombinator.com/item?id="+.objectID)}'
|
||||
```
|
||||
|
||||
**Recent comments mentioning a keyword:**
|
||||
```bash
|
||||
curl -s "https://hn.algolia.com/api/v1/search_by_date?query=KEYWORD&tags=comment&numericFilters=created_at_i>${SINCE}" \
|
||||
| jq '.hits[] | {author, comment_text, story_title, hn_url: ("https://news.ycombinator.com/item?id="+.objectID)}'
|
||||
```
|
||||
|
||||
### Bluesky (free, public API)
|
||||
|
||||
**Search posts by keyword:**
|
||||
```bash
|
||||
curl -s "https://public.api.bsky.app/xrpc/app.bsky.feed.searchPosts?q=KEYWORD&limit=25&sort=latest" \
|
||||
| jq '.posts[] | {author: .author.handle, text: .record.text, likes: .likeCount, replies: .replyCount, url: ("https://bsky.app/profile/"+.author.handle+"/post/"+(.uri | split("/") | last))}'
|
||||
```
|
||||
|
||||
### RSS for blogs, podcasts, YouTube channels
|
||||
|
||||
For target accounts that publish to RSS (most blogs, all YouTube channels):
|
||||
```bash
|
||||
# YouTube channel feed (replace CHANNEL_ID)
|
||||
curl -s "https://www.youtube.com/feeds/videos.xml?channel_id=CHANNEL_ID"
|
||||
|
||||
# Generic blog feed
|
||||
curl -s "https://example.com/feed/" | xmllint --xpath "//item[position()<6]" - 2>/dev/null
|
||||
```
|
||||
|
||||
### LinkedIn & X — use the browser
|
||||
|
||||
LinkedIn and X don't expose useful public APIs, but you can drive a real browser session. **dev-browser** (MCP, already in the global setup) and **Playwright** both maintain persistent state — log in once, the session stays alive, Claude can navigate the authenticated feed.
|
||||
|
||||
**dev-browser workflow (preferred — already wired up):**
|
||||
1. User logs into LinkedIn / X once in the dev-browser session
|
||||
2. Claude navigates to a target URL (feed, profile, saved search, hashtag)
|
||||
3. Claude reads the accessibility tree / page text, extracts posts
|
||||
4. Claude scores using the [rubric](#scoring-rubric) and drafts comments
|
||||
5. User reviews and posts manually (don't auto-post — high-stakes, bot detection risk)
|
||||
|
||||
**Useful URLs to feed dev-browser:**
|
||||
|
||||
| URL pattern | What it shows |
|
||||
|-------------|---------------|
|
||||
| `linkedin.com/in/HANDLE/recent-activity/all/` | A target account's recent posts |
|
||||
| `linkedin.com/feed/hashtag/TOPIC/` | Hashtag feed |
|
||||
| `linkedin.com/feed/` | Your main feed (algorithmic — less useful for triage) |
|
||||
| `x.com/HANDLE` | A target account's profile |
|
||||
| `x.com/search?q=QUERY&f=live` | Real-time search (use `f=live` for chronological) |
|
||||
| `x.com/i/lists/LIST_ID` | A curated list — best for target accounts |
|
||||
|
||||
**Tips:**
|
||||
- On X, build a private list of target accounts and use the list URL. Far cleaner than the algorithmic feed.
|
||||
- LinkedIn's `/recent-activity/all/` URL is the cleanest way to see one person's posts without the algorithm.
|
||||
- For both platforms, scroll programmatically (dev-browser supports it) to load more posts before extracting.
|
||||
|
||||
**Paid alternatives if you don't want to drive a browser:**
|
||||
|
||||
| Platform | Tools |
|
||||
|----------|-------|
|
||||
| LinkedIn | Sales Navigator (saved searches), Taplio (engagement) |
|
||||
| X | TweetDeck/X Pro (saved columns), Typefully, Taplio, Tweet Hunter |
|
||||
|
||||
**Still closed (no good path):**
|
||||
- Instagram & TikTok — closed APIs, browser automation is detectable and risky. Use native saved searches / hashtag follows.
|
||||
|
||||
---
|
||||
|
||||
## Per-Platform Notes
|
||||
|
||||
### LinkedIn
|
||||
- **Browser-driven** (dev-browser with persistent session) — see [LinkedIn & X — use the browser](#linkedin--x--use-the-browser)
|
||||
- **First-hour comments matter most** — algorithm weights early engagement heavily. Prioritize posts <2h old from target accounts.
|
||||
- Comments with 5+ words get more reach than reactions
|
||||
- Replying to other commenters can put you in front of their network
|
||||
- Tag the author in your reply only if it adds context
|
||||
|
||||
### Twitter/X
|
||||
- **Browser-driven** (dev-browser) — build a private list of target accounts and point dev-browser at the list URL
|
||||
- Reply within first 30 min for max reach on big accounts
|
||||
- Quote-tweet > reply when adding substantial value
|
||||
- Threading your reply (multi-tweet) signals effort
|
||||
- Don't pile on dunks — relationships > clout
|
||||
|
||||
### Reddit
|
||||
- Read the subreddit rules before commenting (some ban self-promotion outright)
|
||||
- Earn karma in the sub before linking to anything you own
|
||||
- Long, specific answers win. AMAs and "help me decide" threads are gold
|
||||
- Never lead with your product — answer the question first
|
||||
|
||||
### Hacker News
|
||||
- Comment quality bar is high; low-effort gets downvoted fast
|
||||
- Founders commenting on threads about their product is welcomed if you're transparent
|
||||
- Search for past discussions of your category — they're often dormant gold mines
|
||||
|
||||
### Bluesky
|
||||
- Smaller volume but high engagement-to-follower ratio
|
||||
- Tech and indie-hacker communities are active
|
||||
- Custom feeds (like Bluesky's "Following" + topic feeds) replace algorithmic search
|
||||
|
||||
---
|
||||
|
||||
## Common Workflows
|
||||
|
||||
### "Give me my top 10 posts to comment on today"
|
||||
1. Pull from: target account RSS/saved searches + Reddit (relevant subs) + HN (last 24h)
|
||||
2. Score with the [rubric](#scoring-rubric)
|
||||
3. Output top 10 with suggested comments
|
||||
|
||||
### "Find people complaining about [competitor]"
|
||||
1. Reddit search: `"competitor name" -site:competitor.com` sorted by new
|
||||
2. HN comment search for competitor name
|
||||
3. Bluesky search for competitor handle/name
|
||||
4. Score by intent signal (high if switching language: "moving from", "alternatives to", "frustrated with")
|
||||
|
||||
### "Surface brand mentions from the last week"
|
||||
1. Reddit search for brand name
|
||||
2. HN search (stories + comments) for brand name
|
||||
3. Bluesky search for brand name + handle
|
||||
4. Output as: reply needed (yes/no), tone (positive/negative/neutral), suggested response
|
||||
|
||||
### "Find target-account posts I missed"
|
||||
1. Maintain a list of target accounts with their RSS / Reddit usernames / Bluesky handles
|
||||
2. Fetch each source's recent posts
|
||||
3. Filter to last 24h, output sorted by score
|
||||
|
||||
---
|
||||
|
||||
## Setting Up the Source List
|
||||
|
||||
The user should maintain a list of sources somewhere persistent at `.agents/listening-sources.md` (or `.claude/listening-sources.md`). Claude reads it when running the daily loop.
|
||||
|
||||
**A ready-to-fill template lives at [listening-sources-template.md](listening-sources-template.md).** Copy it into the project and edit. The source path depends on how the skill was installed:
|
||||
|
||||
```bash
|
||||
# Plugin / marketplace install (most common):
|
||||
cp .agents/skills/social/references/listening-sources-template.md .agents/listening-sources.md
|
||||
# .claude/ install:
|
||||
cp .claude/skills/social/references/listening-sources-template.md .agents/listening-sources.md
|
||||
# Working inside the marketingskills repo:
|
||||
cp skills/social/references/listening-sources-template.md .agents/listening-sources.md
|
||||
```
|
||||
|
||||
The template covers: brand/category, ICP (for scoring), target accounts per platform, intent keywords, subreddits, saved-search URLs, and a do-not-engage list.
|
||||
@@ -133,6 +133,8 @@ Tweet 7: [Your key takeaway]
|
||||
Caption: [Expand on the topic, add context, include CTA]
|
||||
```
|
||||
|
||||
This is the generic shape. For five full slide-by-slide narrative architectures (Value-Stack, Problem-Proof, Hack List, Rant Callout, Demo Walkthrough) with selection guidance and per-slide copy slots, see [carousel-frameworks.md](carousel-frameworks.md).
|
||||
|
||||
### The Reel Script
|
||||
```
|
||||
Hook (0-2 sec): [Pattern interrupt or bold claim]
|
||||
|
||||
Reference in New Issue
Block a user