Scale · Sales Enablement Content
Build a Case Study Library Template
Standardize every case study into the same skimmable shape so reps can find one in 10 seconds.
When to use
Use when reps say 'we don't have a case study for that' and you actually do — it's just buried in a Drive folder, written in 4 different formats. Build the template once, retrofit your top 10 wins, and require every new study to follow it.
The prompt
You are a sales enablement editor at a digital marketing agency — every artifact you ship makes a rep faster on a real deal. You design templates that force consistency, not creativity. Agency: [AGENCY_NAME] — [SERVICES] | Top verticals: [VERTICALS] | Common buyer questions a case study must answer: [BUYER_QUESTIONS] | Where reps will use these (email, deck, sales chat): [USE_CONTEXTS] | Proof currency that matters most (revenue, pipeline, traffic, rankings): [PROOF_TYPE] Design a reusable case study library template + filing system so every past and future win is captured in the same skimmable structure reps can search and quote. - Template fits on one page per study - Fields are forced — no free-text 'overview' section - Every section must be quotable in a sales email - Include metadata fields for searchability (vertical, service, deal size, persona) - Hard cap: 250 words of narrative per study Deliver two things: 1) The case study one-pager template (with field definitions + word limits) 2) The library index schema (filename convention + filterable metadata fields)
Variables
[AGENCY_NAME]Your agency name[SERVICES]Service mix that case studies will cover[VERTICALS]Verticals you want to filter by[BUYER_QUESTIONS]Questions prospects always ask[USE_CONTEXTS]Where reps will use the case studies[PROOF_TYPE]Outcome metric that matters most to your buyers
Example input
Agency: NorthLoop | Services: SEO, paid search, CRO | Verticals: B2B SaaS, ecommerce DTC, financial services | Buyer questions: 'who like me have you helped', 'how long did it take', 'what was the actual number' | Use contexts: cold email, late-stage deck, Slack-to-prospect | Proof type: marketing-sourced pipeline and revenue
Example output
Case Study One-Pager (template) 1) Headline outcome (1 line, must include number): e.g., '$4.2M marketing-sourced pipeline in 9 months for [Client], Series B SaaS.' 2) Client snapshot (≤30 words): vertical, stage, what they sold. 3) The problem (≤40 words): what was broken before us. 4) What we did (≤80 words, bullets only): 3–5 plays we ran. 5) Results (≤40 words, numbers only): the metric, the delta, the timeframe. 6) Client quote (≤25 words): one line, attributed. 7) Best for: [vertical] / [stage] / [deal shape] — search tags. Library index schema: Filename: YYYY_Vertical_Service_Outcome_Client.pdf (e.g., 2026_SaaS_SEO_Pipeline_Acme.pdf) Metadata fields: vertical, stage, services, deal_size_band, persona, primary_metric, secondary_metric, year, quotable (Y/N). Stored in: /sales/case-studies/library, filterable by tag in your CRM or wiki.
Pro tips
- Force the headline to lead with a number — no number, no publish.
- Make 'quotable_y_or_n' a required field; reps need to know what they can paste into email.
- Audit the library every 90 days and retire studies older than 24 months unless evergreen.
Free 20 minute sales audit
A prompt is not a system.
These are free and they work. What they cannot do is make your team run the play every week. That is the part we install.
Book a Free Sales Audit