Case Study Builder Assistant
Generate structured case studies, engagement summaries, and project documentation using structured frameworks.
When to Use
- User wants to create a case study or success story
- User needs to document a client engagement
- User mentions: case study, client story, engagement summary, project summary, portfolio, results documentation
Output Types
- Company Summary: Quick company context
- Engagement Summary: Challenge, Solution, Results, Testimonial format
- Project Summary: Objective, Execution, Outcomes format
- Full Case Study: Comprehensive client story
Instructions
- Identify output type needed
- Collect inputs based on framework
- Generate structured output following templates
- Include quantitative results where available
Company Summary Framework
Format 1: Full Context
[Company name], [funding stage], [industry], [product category], [region], [website]
Example: Reform, Bootstrapped, MarTech, Lead Gen Form Builder SaaS, USA, www.reform.app
Format 2: Short
[Company Name] ([Business Model], [Product/Service Category])
Example: FunnelEnvy (B2B, Growth Marketing Service Provider)
Company Intro Template
[Company Name] is [Product/Service Category] for [persona + company type + industry + region] to [use case]
Engagement Summary Framework
## [Company Name] - Engagement Summary
**Challenge:**
[Brief summary of the primary problem the company faced]
**Solution:**
[Brief summary of the solutions implemented]
**Results:**
[One-liner about key improvements achieved]
**Testimonial:**
"[Customer quote]" - [Name], [Title], [Company]
Inputs Needed
- Company name and context
- Primary challenge/problem
- Solutions implemented
- Measurable results
- Client quote (or draft one)
Project Summary Framework
## [Project Title]
**Objective:**
[1-2 lines, 15-30 words: short statement of goal]
**Execution:**
- [Tool/method/framework 1]
- [Tool/method/framework 2]
- [Tool/method/framework 3]
**Outcomes:**
- [Quantitative/qualitative impact 1]
- [Quantitative/qualitative impact 2]
Guidelines
- Objective: 1-2 lines, 15-30 words
- Execution: 3-6 bullets, 15-25 words each
- Outcomes: 2-3 bullets, 15-25 words each
Full Case Study Structure
- Company Context: Name, stage, industry, product, region
- Challenge: What problem they faced, why they engaged
- Solution: What was implemented, how it worked
- Execution Details: Specific actions, tools, methods
- Results: Quantitative metrics + qualitative improvements
- Testimonial: Client quote with attribution
- Key Takeaways: Learnings or recommendations
Output Format
Generate as Markdown with:
- Clear section headers
- Bold labels (Challenge:, Solution:, etc.)
- Bullet points for execution and outcomes
- Quoted testimonials with attribution
- Specific metrics where available
Constraints
- Include specific numbers/percentages where available
- Use active voice
- Keep summaries concise
- Include testimonial or draft one labeled as [DRAFT]
- Avoid vague claims without supporting metrics
Reference
See references/case-study-examples.md for complete examples.
1---2name: case-study-builder3description: Creates professional case studies, engagement summaries, and project summaries. Use when the user wants to create a 'case study,' 'client success story,' 'engagement summary,' 'project summary,' or 'portfolio piece.'4---56# Case Study Builder Assistant78Generate structured case studies, engagement summaries, and project documentation using structured frameworks.910## When to Use1112- User wants to create a case study or success story13- User needs to document a client engagement14- User mentions: case study, client story, engagement summary, project summary, portfolio, results documentation1516## Output Types17181. **Company Summary**: Quick company context192. **Engagement Summary**: Challenge, Solution, Results, Testimonial format203. **Project Summary**: Objective, Execution, Outcomes format214. **Full Case Study**: Comprehensive client story2223## Instructions24251. **Identify output type** needed262. **Collect inputs** based on framework273. **Generate structured output** following templates284. **Include quantitative results** where available2930## Company Summary Framework3132### Format 1: Full Context33```34[Company name], [funding stage], [industry], [product category], [region], [website]35```3637Example: Reform, Bootstrapped, MarTech, Lead Gen Form Builder SaaS, USA, www.reform.app3839### Format 2: Short40```41[Company Name] ([Business Model], [Product/Service Category])42```4344Example: FunnelEnvy (B2B, Growth Marketing Service Provider)4546### Company Intro Template47```48[Company Name] is [Product/Service Category] for [persona + company type + industry + region] to [use case]49```5051## Engagement Summary Framework5253```markdown54## [Company Name] - Engagement Summary5556**Challenge:**57[Brief summary of the primary problem the company faced]5859**Solution:**60[Brief summary of the solutions implemented]6162**Results:**63[One-liner about key improvements achieved]6465**Testimonial:**66"[Customer quote]" - [Name], [Title], [Company]67```6869### Inputs Needed70- Company name and context71- Primary challenge/problem72- Solutions implemented73- Measurable results74- Client quote (or draft one)7576## Project Summary Framework7778```markdown79## [Project Title]8081**Objective:**82[1-2 lines, 15-30 words: short statement of goal]8384**Execution:**85- [Tool/method/framework 1]86- [Tool/method/framework 2]87- [Tool/method/framework 3]8889**Outcomes:**90- [Quantitative/qualitative impact 1]91- [Quantitative/qualitative impact 2]92```9394### Guidelines95- Objective: 1-2 lines, 15-30 words96- Execution: 3-6 bullets, 15-25 words each97- Outcomes: 2-3 bullets, 15-25 words each9899## Full Case Study Structure1001011. **Company Context**: Name, stage, industry, product, region1022. **Challenge**: What problem they faced, why they engaged1033. **Solution**: What was implemented, how it worked1044. **Execution Details**: Specific actions, tools, methods1055. **Results**: Quantitative metrics + qualitative improvements1066. **Testimonial**: Client quote with attribution1077. **Key Takeaways**: Learnings or recommendations108109## Output Format110111Generate as Markdown with:112- Clear section headers113- Bold labels (Challenge:, Solution:, etc.)114- Bullet points for execution and outcomes115- Quoted testimonials with attribution116- Specific metrics where available117118## Constraints119120- Include specific numbers/percentages where available121- Use active voice122- Keep summaries concise123- Include testimonial or draft one labeled as [DRAFT]124- Avoid vague claims without supporting metrics125126## Reference127128See `references/case-study-examples.md` for complete examples.
realjaymes