From grimoire
Writes B2B case studies using situation-solution-results framework to demonstrate customer success and build social proof for sales enablement.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:write-case-studyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structure a customer success story using situation, solution, and results to convert skeptical buyers into confident ones.
Structure a customer success story using situation, solution, and results to convert skeptical buyers into confident ones.
Adopted by: HubSpot, Salesforce, Deloitte, McKinsey, and virtually every B2B company with a sales cycle over 30 days. Impact: Demand Gen Report (2023) found that 79% of B2B buyers rely on case studies during vendor evaluation; CMI (2024) reports case studies as the top content type for late-stage pipeline acceleration. Why best: The situation-solution-results (SSR) framework mirrors the buyer's own mental model — they are experiencing a situation, seeking a solution, and want proof of results. This alignment reduces cognitive load and builds trust faster than any other format.
Sources: Hennig-Thurau et al. "Electronic Word-of-Mouth Via Consumer-Opinion Platforms" (2004); Demand Gen Report "B2B Buyer Behavior Study" (2023); Content Marketing Institute "B2B Content Marketing Benchmarks, Budgets, and Trends" (2024); HubSpot "How to Write a Case Study" (2023).
Select the right customer — Choose a customer whose before-state matches your ideal buyer's pain. A fintech startup and an enterprise bank have different persuasive value for different prospects. Prioritize customers with measurable, defensible results and willingness to be named publicly.
Conduct a structured interview — Ask six core questions: (a) What was the problem before? (b) What alternatives did you consider? (c) Why did you choose us? (d) How did implementation go? (e) What specific results have you seen? (f) What would you say to a peer considering this solution? Record and transcribe verbatim for authentic quotes.
Open with a hook headline — Lead with the result, not the company name. Format: "[Customer] [achieved X result] in [timeframe] with [your product]." Example: "Acme Corp Reduced Churn by 34% in 90 Days." Quantified headlines increase click-through rates by 36% (Conductor, 2022).
Write the Situation section — Describe the customer's world before your solution in 100–150 words. Use the customer's own language from the interview. Make the pain visceral and specific — budget constraints, manual hours wasted, lost deals. This is where the target reader recognizes themselves.
Write the Solution section — Describe how your product was implemented in 150–200 words. Focus on the customer's experience, not your feature list. Include implementation timeline, who was involved, and any obstacles overcome. Avoid jargon; write what actually happened.
Write the Results section — This is the most-read section. Lead with the three strongest metrics in bold callout boxes. Follow with supporting narrative. Use before/after comparisons: "Previously took 8 hours; now takes 45 minutes." Include both hard metrics (revenue, cost, time) and soft outcomes (team morale, customer satisfaction).
Insert direct quotes at key transitions — Place one pull-quote after the Situation section, one after Results. Quotes must be specific, not generic. "It saved us time" is useless; "We recovered 12 hours per week per account manager" is compelling. Edit for clarity with customer approval.
Add a visual summary sidebar — Include a 3-cell summary box: Industry, Company Size, Result. Buyers who skim (most of them) must grasp the story in under 10 seconds. This sidebar does that work.
End with a soft CTA — Close with a forward-looking quote from the customer about continued use, then a single call to action: "See how [your product] can do the same for your team." Link to a relevant demo or contact page. Avoid hard-sell language at this stage — the case study has already done the persuasion.
Distribute strategically — Publish as a web page (SEO), a downloadable PDF (gated for lead gen), and a 3-slide summary (sales deck insert). Tag by industry, company size, and use case so sales reps can retrieve the right case study during calls.
SaaS case study: Zendesk publishes one-page case studies with a metric-first headline, a 3-line situation summary, a 4-line solution description, and three bold outcome stats — a model of brevity and impact.
Professional services: McKinsey case studies use anonymous client references ("a global logistics company") when clients won't allow naming, focusing entirely on methodology and results, which still builds credibility through specificity.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireGenerates customer case studies and success stories using interview guides, StoryBrand structure, metrics validation, and publish-ready format. Activates for 'write a case study' or customer success requests.
Generates a structured case study creation plan with interview framework, data visualization approach, format variations, and distribution strategy for client success stories.
Generates a professional B2B case study PDF from customer details with 7 layouts, 9 style presets, and 1-4 page output.