30 Claude Prompts That Write Case Studies

You are a B2B content marketer who writes flagship SaaS case studies for sales enablement. <context> I need a complete B2B SaaS case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, following the classic Problem to Solution to Results to Quote structure. </context> <inputs> - Customer name and industry: [COMPANY, SECTOR] - Their size and role of the buyer: [HEADCOUNT, JOB TITLE] - The problem before us: [PAIN POINT, WHAT BROKE] - Our product and how they used it: [PRODUCT, KEY FEATURES ADOPTED] - Hard results with numbers: [METRIC CHANGES, TIMEFRAME] - A real customer quote: [QUOTE AND ATTRIBUTION] </inputs> <task> Build a one-page case study with: a headline stating the outcome, a customer-at-a-glance sidebar (industry, size, use case), a "Challenge" section describing the pre-product pain, a "Solution" section on how they implemented us, a "Results" block with three to four metric cards showing before and after, a pull-quote from the buyer, and a closing CTA to book a demo. Write specific, credible copy with no marketing fluff. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Every result must show a concrete number or percentage, not vague claims like "improved efficiency". - Pull-quote styled distinctly; accessible contrast and semantic headings. </constraints> <format> Return the full HTML as an artifact, then explain which metric you led with and why it is the most persuasive proof point. </format>

You are an enterprise content strategist who documents software rollouts for technical buyers. <context> I need an implementation case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, that walks a skeptical buyer through how a complex rollout actually went. </context> <inputs> - Customer and environment: [COMPANY, STACK, TEAM SIZE] - What they were replacing or integrating: [LEGACY SYSTEM OR GAP] - Implementation scope and timeline: [PHASES, DURATION] - Obstacles hit and how they were solved: [CHALLENGES, FIXES] - Measured outcomes: [ADOPTION, TIME SAVED, ERROR REDUCTION] - Stakeholder quote: [QUOTE AND ROLE] </inputs> <task> Build a case study with: an outcome headline, a project snapshot bar (scope, timeline, team), a "Challenge" section on the starting state, a "Solution" section structured as a phased rollout timeline, a "Results" section with adoption and efficiency metrics, an honest "What we learned" note, a stakeholder quote, and a CTA. Make it read credibly to a technical evaluator. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Show the rollout as a visual timeline with labeled phases. - Concrete numbers throughout; no hand-waving about "seamless" experiences. </constraints> <format> Return the full HTML as an artifact, then explain how the phased timeline reduces a buyer's fear of a hard implementation. </format>

You are a product marketer who writes case studies proving a product sells itself. <context> I need a product-led growth case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, showing how a customer expanded usage organically. </context> <inputs> - Customer and team: [COMPANY, WHO STARTED USING IT] - How they discovered and adopted the product: [ENTRY POINT, FREE TIER, ETC] - The "aha" moment that drove expansion: [WHAT CLICKED] - Expansion path: [SEATS, FEATURES, OR USAGE GROWTH OVER TIME] - Business results: [METRICS, REVENUE OR PRODUCTIVITY GAINS] - Champion quote: [QUOTE AND TITLE] </inputs> <task> Build a case study with: a headline framing organic expansion, a snapshot of starting vs current usage, a "Challenge" section on the initial need, a "Solution" section tracing the bottom-up adoption journey, a "Results" section with an expansion-over-time mini chart described in HTML and metric cards, a champion quote, and a CTA to start free. Write specific PLG-flavored copy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Visually depict usage growth (e.g. styled bar steps) using CSS only, no libraries. - Real numbers for the expansion story; accessible markup. </constraints> <format> Return the full HTML as an artifact, then explain how you showed the land-and-expand motion visually. </format>

You are a developer-marketing writer who creates case studies for technical platform buyers. <context> I need an API or integration case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, written for engineering and platform decision-makers. </context> <inputs> - Customer and what they build: [COMPANY, PRODUCT] - The integration challenge: [WHAT THEY NEEDED TO CONNECT OR AUTOMATE] - How our API solved it: [ENDPOINTS, WORKFLOW, BUILD TIME] - Performance and reliability results: [LATENCY, UPTIME, VOLUME, DEV HOURS SAVED] - Engineer or CTO quote: [QUOTE AND ROLE] </inputs> <task> Build a case study with: a technical outcome headline, an at-a-glance tech-stack panel, a "Challenge" section on the integration problem, a "Solution" section describing the architecture and build experience with one short illustrative code or request snippet styled in a code block, a "Results" section with performance metric cards, an engineer quote, and a CTA to read the docs. Keep it credible to developers. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Include one syntax-highlighted-style code block with monospace styling. - Specific, accurate-sounding technical numbers; no marketing buzzwords. </constraints> <format> Return the full HTML as an artifact, then explain how the code snippet makes the integration feel low-effort to an engineer. </format>

You are a competitive-marketing writer who builds case studies about customers switching from a rival tool. <context> I need a switch case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, telling the story of a customer who left a competitor for us. </context> <inputs> - Customer and industry: [COMPANY, SECTOR] - The tool they left and why: [PREVIOUS TOOL, FRUSTRATIONS] - The migration process: [HOW THEY SWITCHED, EFFORT, TIMELINE] - What changed for them after: [IMPROVEMENTS WITH NUMBERS] - Quote about the switch: [QUOTE AND ROLE] </inputs> <task> Build a case study with: a headline framing the switch outcome, a before-vs-after comparison block (old tool pains vs new wins), a "Challenge" section on why they outgrew the old tool, a "Solution" section on the migration experience, a "Results" section with metric cards, a customer quote, and a CTA to start a switch. Stay factual and fair about the competitor, never disparaging. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Use a clean two-column before-and-after comparison; concrete numbers in results. - Professional tone; criticize the situation, not the competitor by name unless provided. </constraints> <format> Return the full HTML as an artifact, then explain how you kept the switch story persuasive without sounding bitter or unfair. </format>

You are an agency content lead who writes results-driven case studies that win new clients. <context> I need a marketing agency case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, proving the campaign results we delivered for a client. </context> <inputs> - Client and industry: [CLIENT, SECTOR] - Their goal and starting point: [OBJECTIVE, BASELINE METRICS] - Services we delivered: [SEO, ADS, CONTENT, ETC] - Strategy and key tactics: [WHAT WE ACTUALLY DID] - Results with numbers and timeframe: [LEADS, TRAFFIC, REVENUE, ROAS] - Client testimonial: [QUOTE AND NAME] </inputs> <task> Build a case study with: a bold results headline, a client snapshot bar, a "Challenge" section on the client's goal and obstacles, a "Solution" section on our strategy and tactics, a "Results" section with three to four big-number metric cards and a short narrative on the impact, a client quote, and a "work with us" CTA. Write confident, specific agency copy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Metric cards must headline the percentage or absolute change with a label underneath. - Tie each tactic to an outcome; no vague "we ran a campaign" filler. </constraints> <format> Return the full HTML as an artifact, then explain which result you made the hero metric and how to swap in a different client's numbers. </format>

You are a creative-agency writer who turns a rebrand project into a compelling case study. <context> I need a branding case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, that showcases a design or rebrand engagement and its business impact. </context> <inputs> - Client and what they do: [CLIENT, SECTOR] - Why they needed a rebrand: [TRIGGER, OLD PERCEPTION PROBLEM] - Our process and deliverables: [DISCOVERY, IDENTITY, ASSETS] - Visual direction we chose: [DESCRIBE THE NEW LOOK AND RATIONALE] - Business or perception results: [METRICS, AWARDS, FEEDBACK] - Client quote: [QUOTE AND ROLE] </inputs> <task> Build a case study with: a headline naming the transformation, a project-scope panel, a "Challenge" section on the brand problem, a "Solution" section walking through the design process with labeled color-block placeholders showing old vs new direction, a "Results" section combining business metrics and qualitative wins, a client quote, and a CTA. Make the visual story tangible even without real images. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Use CSS color blocks and type samples to evoke the old vs new identity, each clearly labeled. - Mix hard numbers with credible qualitative outcomes; accessible markup. </constraints> <format> Return the full HTML as an artifact, then explain how you visualized the brand transformation without uploaded images. </format>

You are a studio writer who documents web build projects for a development agency's portfolio. <context> I need a web development case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, covering a site or app we built and the results it drove. </context> <inputs> - Client and project type: [CLIENT, WEBSITE / WEB APP / ECOMMERCE] - The brief and constraints: [GOALS, DEADLINE, TECH REQUIREMENTS] - What we built and the stack: [PAGES, FEATURES, TECH] - Performance and business outcomes: [SPEED, CONVERSION, SALES] - Client quote: [QUOTE AND ROLE] </inputs> <task> Build a case study with: an outcome headline, a project facts panel (stack, timeline, scope), a "Challenge" section on the brief, a "Solution" section describing what was built and key technical decisions, a "Results" section with performance metrics (load time, conversion, revenue) as cards, a styled screenshot placeholder of the finished site, a client quote, and a CTA. Keep it concrete and outcome-led. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Include a captioned browser-frame placeholder representing the delivered site. - Pair each technical decision with a user or business benefit; real numbers in results. </constraints> <format> Return the full HTML as an artifact, then explain which performance metric best proves the build's value to a non-technical client. </format>

You are a management-consulting writer who packages an advisory engagement into a credible case study. <context> I need a consulting case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, showing how an advisory engagement created measurable value. </context> <inputs> - Client and industry: [CLIENT, SECTOR] - The business problem they faced: [STRATEGIC OR OPERATIONAL ISSUE] - Our approach and methodology: [DIAGNOSTIC, FRAMEWORK, WORKSTREAMS] - Recommendations and what was implemented: [KEY MOVES] - Quantified impact: [COST SAVED, REVENUE, EFFICIENCY GAINS] - Executive quote: [QUOTE AND TITLE] </inputs> <task> Build a case study with: an impact headline, an engagement summary bar (industry, duration, scope), a "Challenge" section framing the business problem, an "Approach" section on the methodology and workstreams, a "Results" section with quantified impact metric cards plus a short narrative, an executive quote, and a CTA to discuss a similar engagement. Write in a sober, authoritative consulting voice. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Quantify the impact in money or percentage terms wherever possible. - Structured, scannable sections; accessible contrast and semantic headings. </constraints> <format> Return the full HTML as an artifact, then explain how you framed the methodology to signal rigor without revealing confidential client specifics. </format>

You are a copywriter helping a freelancer turn a single great project into a portfolio case study that wins more clients. <context> I need a freelancer case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, that makes one strong client project look like proof I can do it again. </context> <inputs> - My role / service: [WHAT I DO, E.G. COPYWRITER, DESIGNER, DEVELOPER] - Client and project: [CLIENT, WHAT THEY NEEDED] - The problem they came to me with: [PAIN] - What I delivered and how I worked: [DELIVERABLES, PROCESS] - The result for the client: [OUTCOME, IDEALLY WITH A NUMBER] - Client testimonial: [QUOTE AND NAME] </inputs> <task> Build a case study with: a headline pairing the deliverable with the result, a quick project snapshot, a "The problem" section, a "What I did" section showing process and craft, a "The outcome" section with the result highlighted and a styled testimonial, and a warm "hire me" CTA with a clear next step. Write in a confident but personable first-person voice. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Keep it tight and skimmable for a busy prospect; one clear result up front. - Personable first-person tone; accessible markup and a single dominant CTA. </constraints> <format> Return the full HTML as an artifact, then explain how to adapt this template for a project where the result is qualitative rather than numeric. </format>

You are a storytelling marketer who writes vivid before-and-after transformation case studies. <context> I need a transformation case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, built around a stark before-and-after contrast. </context> <inputs> - Customer and context: [WHO, INDUSTRY OR SITUATION] - The "before" state in detail: [DAILY PAIN, COSTS, FRUSTRATIONS] - What changed: [OUR PRODUCT OR SERVICE, HOW THEY USED IT] - The "after" state in detail: [NEW REALITY, METRICS] - A quote capturing the shift: [QUOTE AND ROLE] </inputs> <task> Build a case study with: a transformation headline, a side-by-side before-and-after panel contrasting the two states, a "Where they started" narrative section, a "What changed" solution section, a "Where they are now" results section with metric cards, an emotive customer quote, and a CTA. Make the contrast emotionally tangible and back it with numbers. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - The before-and-after panel must be visually distinct (e.g. muted vs vibrant styling). - Pair emotion with concrete numbers; accessible contrast and semantic structure. </constraints> <format> Return the full HTML as an artifact, then explain how the visual contrast in the panel reinforces the story. </format>

You are a business writer who documents turnaround stories where a struggling situation was reversed. <context> I need a turnaround case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, telling how a declining or failing situation was rescued. </context> <inputs> - Subject and what was failing: [COMPANY OR TEAM, THE CRISIS] - How bad it got: [METRICS AT THE LOW POINT] - The intervention: [WHAT WE OR THEY DID TO TURN IT AROUND] - The recovery timeline: [KEY MILESTONES] - The new state: [RECOVERED METRICS] - Leadership quote: [QUOTE AND TITLE] </inputs> <task> Build a case study with: a recovery headline, a crisis-snapshot panel showing the low point, a "The crisis" section, a "The turnaround" section structured as a milestone timeline, a "The recovery" results section with a recovery-over-time mini chart in CSS and metric cards, a leadership quote, and a CTA. Tell a tense, credible comeback story. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Visualize the decline-then-recovery as a simple CSS trend, low point clearly marked. - Honest about how bad it was before showing the recovery; real numbers throughout. </constraints> <format> Return the full HTML as an artifact, then explain how showing the low point honestly makes the recovery more believable. </format>

You are an operations marketer who writes efficiency case studies focused on time and effort saved. <context> I need an efficiency case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, centered on hours reclaimed and manual work eliminated. </context> <inputs> - Customer and team affected: [COMPANY, DEPARTMENT] - The slow manual process before: [TASK, HOW LONG IT TOOK] - What we automated or streamlined: [PRODUCT OR CHANGE] - Time and effort saved: [HOURS PER WEEK, FTE EQUIVALENT, COST] - What they do with the freed-up time: [HIGHER-VALUE WORK] - Quote: [QUOTE AND ROLE] </inputs> <task> Build a case study with: a time-saved headline, a before-vs-after time-cost panel, a "The manual grind" section describing the old workflow, a "The fix" solution section, a "Time reclaimed" results section with hours-saved and cost metric cards plus what they now do with the time, a quote, and a CTA. Make the saved time feel concrete and valuable. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Translate hours saved into a tangible equivalent (e.g. an extra FTE, or a cost figure). - Concrete time numbers; accessible markup and clear visual hierarchy. </constraints> <format> Return the full HTML as an artifact, then explain how converting saved hours into a dollar figure strengthens the business case. </format>

You are a growth writer who documents how a customer scaled rapidly with a product or service. <context> I need a scaling case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, showing how a customer grew and how we supported that growth. </context> <inputs> - Customer and what they do: [COMPANY, PRODUCT OR MARKET] - Their growth ambition and the bottleneck: [GOAL, WHAT WAS HOLDING THEM BACK] - How our solution removed the ceiling: [WHAT WE PROVIDED] - Growth metrics over the period: [USERS, REVENUE, MARKETS, TEAM] - Quote about scaling with us: [QUOTE AND ROLE] </inputs> <task> Build a case study with: a growth headline, a starting-vs-now snapshot, a "The growth ceiling" challenge section, a "How we scaled with them" solution section, a "Results" section with growth metric cards and a CSS growth-curve visual showing the trajectory, a quote, and a CTA. Convey momentum credibly with numbers. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Include a CSS-only ascending growth visual labeled with the key metric and timeframe. - Real growth numbers; avoid hype words, let the trajectory speak. </constraints> <format> Return the full HTML as an artifact, then explain how the growth visual sets the prospect's expectations about scaling with you. </format>

You are a results-focused writer who builds client transformation case studies for coaches and educators. <context> I need a personal transformation case study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, about a client who achieved a meaningful result through a coaching or training program. </context> <inputs> - Client and their starting situation: [WHO, WHERE THEY STARTED] - The struggle or goal: [WHAT THEY WANTED TO CHANGE] - The program or method they followed: [WHAT YOU OFFERED] - The journey and key turning points: [MILESTONES] - The outcome they achieved: [RESULT, IDEALLY MEASURABLE] - Their testimonial: [QUOTE AND FIRST NAME] </inputs> <task> Build a case study with: an aspirational headline naming the outcome, a quick before snapshot, a "The struggle" section, a "The work" section describing the program and journey with key milestones, a "The result" section with the outcome highlighted and a warm testimonial, and a CTA to start a similar journey. Write empathetically and specifically. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Respect privacy: use first name only and keep details general unless provided. - Emotionally resonant but honest; one clear, relatable outcome; accessible markup. </constraints> <format> Return the full HTML as an artifact, then explain how to keep the story inspiring without over-promising results to future clients. </format>