Case study template
Turn customer notes and outcomes into a proof page Claude can write and Send can share.
A good case study is not a victory lap. It helps the next buyer see themselves in a real customer story. The useful parts are the problem, why the old way stopped working, what changed, and what results followed.
Claude can shape raw customer notes, interview excerpts, and metrics into a case study. Send turns it into a shareable page for sales conversations, follow-ups, and deal rooms.
What to include in the case study
- Customer context: company, team, use case, and starting point.
- The problem or trigger that made them look for a solution.
- Why they chose your product or service.
- What changed after implementation.
- Measurable results, before-and-after details, or qualitative wins.
- Customer quote placeholders or approved quotes.
- A takeaway for buyers in a similar situation.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/case-study" skill.
How to create it with Send
Give Claude the raw material: customer interview notes, success metrics, CRM context, implementation notes, and any approved quotes. Ask it to create a case study page using Send.
Send makes the case study easy to use in sales. You can share it as a standalone proof page or link it inside proposals, follow-ups, and deal rooms.
Case study structure
Customer context
Who the customer is and what situation they were in.
Problem and decision
What was not working and why they chose your approach.
Solution and rollout
What changed, how it was implemented, and who was involved.
Results and takeaway
The outcome, proof, quote, and lesson for similar buyers.
Why send a case study as a page
A case study works best when it is easy to share at the right moment. Send gives sales teams a clean link, and the page can be updated as quotes, metrics, or approvals change.