Case Study Generation
Draft pipeline for a content idea of type case_study.
When to Use
- Idea with
content_type: case_study - Buying stage must be decision or vendor only
Prerequisites
- Valid content idea (stage check)
- Firm/service/ICP/persona context
- Current agent/LLM session
- Optional: Exa reference notes via
tool-exafor quality benchmarks - A record in
workspace/firm/proof/withusable_publicly: truewhen the idea uses placeholder proof
Prompt layering
- Base writer
- Quality layer
- Case study format layer →
references/format-requirements.md
Follow the shared draft gate and writing quality rules in docs/content-generation.md.
Proof gate
If proof_source says needs real client proof before draft, or the title contains
[Client], do not ask the user to retype the facts yet — read
workspace/firm/proof/ first. See the Proof Gate in AGENTS.md.
- Look for a record matching this service and ICP.
- A case study is public material, so it requires
usable_publicly: true. A record withusable_publicly: falsemay not be drafted into a case study even though a private proposal could cite it. - Name the client only with
client_public: true; otherwise use the record's approved anonymized label. - Quote the client only with
quote_approved: true. - Use only metrics with
verified: true.
If no usable record exists, stop and ask for the client facts, then have
sales-outcome-log write them to workspace/firm/proof/ before drafting. Recording
them once is what stops this gate from blocking every future case study.
Facts needed for a record: client name or approved label, starting situation, service delivered, timeline, 2–3 real metrics, and an approved quote or a note that none is available.
Do not invent metrics, quote, client name, industry, timeline, or result.
PASTOR structure (required)
- P Problem — client challenge with context
- A Amplify — consequences (revenue, team, risk)
- S Solution — your process/approach
- T Transformation — results with metrics (%, $, time)
- O Offer — how reader gets similar results
- R Response — clear CTA
Must include
- 2–3 quantifiable metrics when real metrics are available; otherwise use verified qualitative outcomes and state proof limits plainly
- At least 1 client quote only when supplied or approved
- Before vs after comparison
- Timeline of engagement
Research
Optional Exa: 5 reference case studies/articles on topic for quality benchmark (do not copy).
Output
Brand scope. In a multi-brand workspace the draft inherits the idea file's brand: write to workspace/marketing/content/{brand}/drafts/… — same brand segment as the idea. See the Brand Scope Gate in AGENTS.md.
workspace/marketing/content/drafts/case-studies/{slug}.md — Markdown
Headline pattern: "[Client Result] in [Timeframe]" or "How [Client] Achieved [Result]"
Frontmatter: idea, content_type, buying_stage, service, icp, persona,
generated_at. Run scripts/validate-content-draft.sh {output} and update the
idea to status: generated after the draft validates.