← ClaudeAtlas

case-studylisted

Builds customer success case studies across B2B SaaS, D2C ecommerce, and professional services using a 5-block Challenge-Strategy-Execution-Results-Lessons structure with STAR-to-marketing mapping. Covers title formulas, TL;DR boxes, quantitative KPIs, and quote-approval workflow. Use when user asks about case study, customer success story, success case, 고��� 사례, 성공 사례, 케이스 스터디, B2B 사례, or 고객 스토리.
Yoodaddy0311/artibot · ★ 3 · AI & Automation · score 65
Install: claude install-skill Yoodaddy0311/artibot
# Case Study ## When This Skill Applies - Drafting a customer success story for a B2B SaaS account - Building a D2C ecommerce brand's customer showcase - Turning a professional services engagement into a published narrative - Converting an internal win-report into a sales enablement asset - Any brief where the goal is to translate one customer outcome into a repeatable story ## Core Guidance ### 1. Title Formula | Pattern | Template | When to Use | |---------|----------|-------------| | Primary | `How [Company] [Result] in [Timeframe]` | Clear quantitative result, named customer | | Variation A | `[Company]: From [Before State] to [After State]` | Transformation is the main hook | | Variation B | `Why [Company] Chose [Approach] to [Solve Problem]` | Decision narrative matters more than metric | The primary formula wins most of the time. Use variations only when the quantitative result is weak or when the selection process itself is the story. ### 2. TL;DR Box Place immediately under the title, above any image or author byline. 40-60 words, three lines. | Line | Content | |------|---------| | 1 | Challenge in one sentence, name the pain | | 2 | Solution in one sentence, name the approach (not the vendor pitch) | | 3 | Key metric with before and after numbers | A reader who stops at the TL;DR should still come away with the single most important fact. ### 3. Five-Block Structure | # | Block | Purpose | Word Count | |---|-------|---------|-----------| | 1 | Challenge