Write Case Study Ads for Social Platforms
You'll end up with: A case-study ad pack: hero narrative, two platform-native variants, a hook bank, and one publish-ready doc with compliance and UTM notes.
Leading with your credentials or process instead of the client's outcome—or using unverifiable claims ("10x growth") without a measurable anchor. Fix: first line = outcome for them; every stat ties to a footnote you could show a reviewer.
- One concrete client story (can anonymize)
- Before/after metric or proxy
- Whether you have quote approval
- Claude open
- One doc (Google Docs or Notion) for the final pack
Lock the case facts and proof
Turn a fuzzy win into a single factual spine: situation → what changed → measurable result → optional quote (with permission rules).
1. Go to claude.ai and start a **new chat**. Keep this thread open through step 5. 2. Paste this prompt and fill the bracketed section with your honest notes: "I'm writing case-study ads from one customer win. Build a **Case Fact Sheet** from my notes below. Include bullets for: - Client context (industry / role) — anonymize if needed - Problem / situation (specific) - Intervention (what we actually did — high level) - Metric(s): before → after, %, $, or hours — include timeframe - Timeline (how long until results showed) - Quote I may use (or write **none**) + whether I have permission - Anonymization rules (what must stay private) Then: A) Flag **missing proof** (no numbers → suggest one **proxy metric**, or confirm an honest **qualitative-only** path) B) Flag claims that sound **unverifiable** My rough notes: [paste notes here]" 3. If Claude flags gaps, reply with missing facts or ask it to **narrow claims** to what you can defend. 4. Copy the **Case Fact Sheet** — you'll reuse it in steps 2–5.
Choose platform, objective, and angle
Pick primary and secondary platforms and **one** ad angle aligned to your funnel objective—before you draft long copy.
1. In the **same chat**, paste your **Case Fact Sheet** from step 1. 2. Paste this prompt: "Given my Case Fact Sheet, recommend **one primary platform** and **one secondary platform** for case-study ads. Explain **why** each fits my buyer + proof type. Then lock decisions: - **Funnel objective** — pick exactly one: awareness | consideration | lead gen - **Ad angle** — pick exactly one: results-led | story-led | objection-breaking - **CTA type** that fits the **primary** platform (examples: comment prompt, DM script, link in bio, lead form, book a call) Apply branching: - If objective is **lead gen**, CTA must be conversion-oriented. - If objective is **awareness**, CTA must be engagement-first (follow/save/comment) — no hard pitch in line 1. Case Fact Sheet: [paste here]" 3. If Claude hedges, reply: "Pick one primary platform and one objective — no tie votes." 4. Save the **Platform decision block** (platforms + objective + angle + CTA) — you'll paste it into steps 3–5.
Draft the hero case-study ad (long form)
One full narrative ad for your **primary** platform: hook → tension → intervention → proof → CTA — voice matches native norms.
1. In the **same chat**, paste your **Case Fact Sheet** + **Platform decision block** from step 2. 2. Paste this prompt: "Draft **one hero case-study ad** for my **primary platform** using my chosen angle. Structure: - Hook (lines 1–2 land **their** outcome or cost of staying stuck) - Tension / context (short) - What changed — what we did differently (concrete) - Proof (hero metric or approved quote) - CTA (match my chosen CTA type) Constraints: - Use **line breaks** for mobile reading - Prefer commas or periods instead of em dashes - Do **not** open with my credentials — open with **their** outcome - Voice fits **primary platform** norms (LinkedIn: crisp lines; IG/Meta: tighter sentences + shorter paragraphs) Also write a **3-line above-the-fold preview** that still communicates the outcome in lines 1–2. Inputs: [paste Case Fact Sheet + Platform decisions here]" 3. Read it aloud. If line 1 is about you, reply: "Rewrite so line 1 is **their** outcome or specific pain — not my bio or awards."
Headlines, hooks, and first-frame lines
Most tests are won or lost in the first line — generate distinct hooks without rewriting the whole body each time.
1. In the **same chat**, paste your **hero ad** + **Case Fact Sheet**. 2. Paste this prompt: "Generate **10 hooks** for split tests. Mix: - Pattern interrupts (specific moment) - Metric-first hooks (only if the number is in the Case Fact Sheet) - Question hooks - Contrarian hooks (**only** if supported by the Case Fact Sheet) For each hook output: - **Hook** (≤15 words) - **Risk level**: safe | spicy (spicy = bolder tension, still truthful) - **Source fact**: which bullet from the Case Fact Sheet it depends on Hero ad + Case Fact Sheet: [paste here]" 3. Delete hooks that sound generic ("Transform your business…"). Ask Claude to replace only the weak lines. 4. Star **6 hooks** you'll actually test first.
Platform-native cuts (primary + secondary)
Adapt length, CTA placement, and formatting for **two** surfaces — plus tight on-image text so creative isn't guesswork.
1. In the **same chat**, paste **Case Fact Sheet**, **Platform decision block**, **hero ad**, and your **6 starred hooks**. 2. Paste this prompt: "Produce **platform-native primary text** for **Platform A** (primary) and **Platform B** (secondary). For each platform output: - **Full primary text** (hook + body + CTA) — native rhythm; **not** the same copy with different line breaks only - **Character discipline**: treat limits as soft targets; prioritize clarity - **Hashtag rule**: **0–3** hashtags only where native — no spam stacks - **On-image / supers**: up to **8 words** per headline; if carousel, **slide titles only** (one idea per slide) - If short video: add **first-frame line** + **on-screen text** beats (≤8 words per beat) Label clearly: **Platform A** and **Platform B**. Inputs: [paste everything here]" 3. If both versions feel like duplicates — reply: "Rewrite Platform B opener + paragraph rhythm so it feels native to that platform — not a resize of Platform A."
Pack for publishing (doc + compliance pass)
One handoff doc: final copy, UTMs, proof checklist, and permissions — so scheduling doesn't require reopening the chat.
1. Open **Google Docs** (https://docs.google.com) **or** **Notion** (https://notion.so) — pick **one** and use it for this pack. 2. Create a doc titled **Case study ad pack — [client/project nickname]**. 3. Paste sections in this order: - **Case Fact Sheet** (step 1) - **Platform decisions** (step 2) - **Hero ad + 3-line preview** (step 3) - **Hook bank** (step 4) - **Platform A + Platform B copy** + on-image lines (step 5) 4. Add **Compliance**: - Each metric/claim → what backs it (export, invoice, client email, analytics screenshot) - Quote → permission status 5. Add **CTA + UTM pattern**: suggest placeholders like `utm_source`, `utm_medium`, `utm_campaign`, `utm_content` per variant (e.g. `linkedin | paid-social | case-q2 | hook-A`). 6. Share with anyone who uploads creatives or manages ads.
All done!
You now have: A case-study ad pack: hero narrative, two platform-native variants, a hook bank, and one publish-ready doc with compliance and UTM notes.
Explore more guidesWant this workflow built for your business?
Book a free audit