::play 01 · Subject-Line A/B/C/D Lab
Claude (voice fidelity) or ChatGPT (volume)
Generate four subject-line variants that test distinct psychological angles, not four versions of the same angle in different words
You are running a subject-line lab for [BRAND NAME]. Brand voice primer is attached. The email is going to [SEGMENT — e.g., active trial users on day 5 who have not yet imported data]. The email body is: [PASTE BODY]. The single goal of this email is [GOAL — e.g., get them to book a 15-min onboarding call]. Produce FOUR subject lines, each testing a distinct angle: (A) Curiosity gap — implies missing information. (B) Specific benefit — names the concrete outcome. (C) Loss framing — names the cost of inaction. (D) Pattern interrupt — unexpected phrasing or formatting. For each, give: subject line (under 50 chars), preview text (under 90 chars), the angle being tested, and one risk (e.g., 'might read as clickbait to enterprise buyers'). Do not produce four variations of the same angle. Use the brand voice primer strictly — no exclamation points unless the primer allows them, no emoji unless the primer allows them.
::what to notice · Whether the four variants actually test different angles or whether the model collapsed into four variations of the same idea. If they collapsed, push back — that means the model is averaging, not generating.
::trap · Letting the model pick the 'winner' — it cannot. Only your open and click data can. Ship all four to small cohorts, then scale the winner.
::play 02 · Brand-Voice Consistency Check
Claude (better at nuanced voice work)
Audit a draft against your documented brand voice before it ships, flagging exact phrases that drift toward beige
Attached is the [BRAND NAME] brand voice primer (tone, banned phrases, signature rhythms, approved register). Below is a draft of [ASSET — e.g., a launch announcement, a Twitter thread, a sales page section]. Audit the draft against the primer. For each section, identify: (1) phrases that match the brand voice — quote them and say why. (2) phrases that drift toward generic/beige — quote them, say what's wrong, propose a voice-locked replacement. (3) banned phrases (per the primer) that appear — flag and replace. (4) signature rhythms (per the primer) that are missing where they should appear. Do not rewrite the whole draft. Surgical edits only. End with a one-sentence verdict: 'ship as edited' / 'one more pass needed' / 'voice is too far off, restart.' Draft: [PASTE DRAFT]
::what to notice · Whether the model finds drift you missed. If it finds nothing, either your draft is genuinely tight or your primer is too vague to be useful — both are signals.
::trap · Treating this as a green-light step. The check is diagnostic, not approving. You still ship the final call.
::play 03 · Ad Creative Variant Batch
ChatGPT (volume) or Claude (voice)
Produce a batch of paid-social ad copy variants across distinct hook structures, each ready to pair with a creative
I'm running [PLATFORM — Meta/LinkedIn/TikTok] ads for [PRODUCT] targeting [AUDIENCE — be specific: role, company size, pain]. The single conversion event is [EVENT — free trial / demo book / lead magnet download]. Brand voice primer is attached. Produce 8 ad copy variants in 4 hook categories (2 per category): (1) Problem-aware — names the pain in their language. (2) Outcome-aware — names the after-state they want. (3) Mechanism-aware — explains the unique-how. (4) Social-proof — anchors on real customer evidence. For each variant: hook (first 125 chars — what shows above the fold), body (under 200 chars), CTA. Flag any variant that makes a quantitative claim (percentages, dollar amounts, timeframes) so I can verify before shipping. Do not invent customer names, stats, or testimonials. If a social-proof variant needs evidence, write '[INSERT REAL CUSTOMER QUOTE HERE]' as a placeholder.
::what to notice · How the model handles the social-proof category. If it tries to invent testimonials, your primer needs a stronger anti-fabrication clause.
::trap · Shipping any variant with an unverified stat. The FTC does not care that AI wrote it — you ran the ad.
::play 04 · Funnel-Stage Retro Synthesis
Claude (long-context, better at structured synthesis)
Synthesize a campaign retro across funnel stages using only your own data, producing learnings ready for the next sprint
I'm running a retro on [CAMPAIGN NAME] which ran [DATE RANGE]. Below is the raw data from each funnel stage: (1) Top of funnel — impressions, CTR, CPC per channel: [PASTE]. (2) Mid-funnel — landing page conversions, asset downloads, demo books: [PASTE]. (3) Bottom of funnel — trial-to-paid, demo-to-close, deal size: [PASTE]. (4) Qualitative — sales team notes, support tickets from new users, NPS comments: [PASTE]. Produce a structured retro: (a) What worked — three claims, each grounded in a specific number from the data. (b) What did not work — three claims, same standard. (c) What surprised us — anomalies in the data, hypothesis for each. (d) What we still don't know — gaps where the data cannot tell us yes/no. (e) Three concrete bets for the next campaign, each with a hypothesis and a metric to test against. Do not invent numbers. Do not extrapolate beyond what the data shows. If a claim requires data I didn't paste, say so explicitly.
::what to notice · Whether the model respects the data boundary. If it makes claims your data does not support, the synthesis is contaminated.
::trap · Letting the retro feel like 'insight' when it's just restating the numbers. Push for the third question — what we still don't know.
::play 05 · Trend Signal Scan
Perplexity Pro (citation-grounded) or ChatGPT with web search
Identify three trend signals relevant to your category from publicly available sources, each with a primary citation
Scan publicly available sources for trend signals in [CATEGORY — e.g., B2B vertical SaaS for the construction industry] from the last [TIMEFRAME — e.g., 30 days]. Produce three signals, each with: (1) The signal — one sentence, concrete and falsifiable. (2) Evidence — at least two primary sources (news article, public company filing, industry report, regulator filing) with URLs. I will verify every URL before using any of this. (3) Why it matters for [BRAND] specifically — one sentence. (4) Confidence — high/medium/low and what would lower the confidence. Do not pull from social media trend lists. Do not invent sources. If a signal only has one source, flag it as low confidence. If you cannot find evidence for a signal, do not include it. Three real signals beat ten speculative ones.
::what to notice · Whether the URLs are real. Click every one before citing. Hallucinated URLs are the failure mode here.
::trap · Treating signals as facts. A signal is a hypothesis worth watching, not a thing to put in a deck.
::play 06 · Competitor Pricing Watch
Perplexity Pro or ChatGPT with web search
Track publicly visible competitor pricing and positioning changes without scraping or violating ToS
Track publicly visible pricing and positioning changes for these competitors: [LIST 3-5 COMPETITORS WITH URLs]. For each, produce: (1) Current published pricing — exact tiers, prices, what's included. Cite the pricing page URL with timestamp. (2) Positioning — the headline on their homepage and the first sentence of their about/manifesto page. Cite URLs. (3) Recent visible changes — anything that has changed in the last 90 days (new tier, removed tier, renamed plan, new positioning line). Only include changes you can evidence with a current page + a Wayback Machine archive showing the prior version. URL both. (4) What this might signal — one cautious sentence per competitor, framed as a question not a conclusion. Do not invent prices. Do not extrapolate from screenshots I have not seen. If you cannot verify a change with two sources, omit it.
::what to notice · Whether the citations resolve. Wayback Machine links should load and show the dated prior version.
::trap · Using this to copy competitor pricing. Pricing is yours — this scan informs, it does not decide.
::play 07 · Win/Loss Recap Synthesis
Claude (long-context, anonymized data)
Synthesize patterns from a quarter of win/loss interviews into a sales-marketing alignment brief
Below are [N] anonymized win/loss interview notes from [QUARTER]. Each interview is tagged WIN or LOSS and includes: deal stage, ICP segment, primary competitor encountered, top-3 buyer concerns, why-we-won or why-we-lost in the buyer's own words. [PASTE NOTES]. Produce a synthesis: (1) Win patterns — three patterns that appear in WIN notes but not LOSS notes, each cited with interview IDs. (2) Loss patterns — three patterns that appear in LOSS notes but not WIN notes, same standard. (3) Mixed signals — patterns that appear in both, requiring deeper investigation. (4) Quotes — pull six exact quotes (three wins, three losses) that capture the strongest patterns. Do not paraphrase quotes. Do not invent quotes. If a quote needs editing for anonymity, mark the edit with brackets. (5) Three concrete recommendations — one for sales enablement, one for marketing messaging, one for product. Each recommendation must cite the pattern it addresses.
::what to notice · Whether the model preserves the actual buyer language or sanitizes it into marketing-speak. The whole point is the buyer's words, not yours.
::trap · Acting on a 'pattern' that appears in only 2-3 interviews. Patterns need volume to be real. Flag low-N patterns as hypotheses, not findings.
::play 08 · Crisis Response Variant Lab
Claude (better at tonal nuance and restraint)
Draft three distinct response postures for a brand-sensitive situation before legal/leadership decides which posture to take
I am preparing a public response to [SITUATION — describe the facts neutrally, no spin]. Brand voice primer is attached. Produce THREE distinct response postures, each as a 2-3 sentence statement: (A) Accountability-forward — acknowledge directly, name the action, no hedging. (B) Information-forward — clarify the facts that may have been misrepresented, calm and specific. (C) Restraint-forward — minimal statement, decline to amplify, redirect to action. For each posture: the statement, what audience it serves best, the risk if we pick this one, what factual claims (if any) need legal review before shipping, what we'd need to verify before publishing. Do not pick a winner. Do not editorialize. This is a decision for me and legal — your job is to make the three options clearly distinct so the choice is real, not theatrical.
::what to notice · Whether the three postures are actually distinct or whether the model converged on one default tone with surface-level variation. If the postures sound the same, the lab failed — push back and re-prompt with sharper differentiation.
::trap · Treating any of the three drafts as ship-ready. Crisis response is human judgment with legal review. The variants exist to clarify the decision, not to remove it.