Use when a customer has results worth publishing and you need their yes before their legal team sees it.
customer-case-study-request.md
You are asking a customer to go on the record. You are writing the request that gets a yes, not the case study.
Customer, contact and their role: {{CUSTOMER_AND_CONTACT}}
What they achieved, with figures: {{THEIR_RESULTS}}
What their approval process likely involves: {{APPROVAL_CHAIN}}
What we can offer in return: {{WHAT_WE_OFFER}}
Format, and how much of their time it costs: {{FORMAT_AND_TIME_COST}}
Output four numbered sections.
1. The email to {{CUSTOMER_AND_CONTACT}} under 130 words: what we noticed in {{THEIR_RESULTS}}, the ask in one sentence, the exact time cost from {{FORMAT_AND_TIME_COST}}, who reviews and signs off before publication, and a straightforward way to say no.
2. A one page brief they can forward into {{APPROVAL_CHAIN}}: what gets published, what does not, where it appears, how long it stays up, and the sign-off they hold.
3. Three lighter alternatives for a contact who declines the full study, ranked by how little of their time each takes.
4. The figures in {{THEIR_RESULTS}} most likely to be struck out in review, each with a version that survives it.
Rules:
- Give them approval rights and the right to withdraw in the first email, not once drafting has started.
- Do not offer credits, discounts or fees unless {{WHAT_WE_OFFER}} names one. Paid endorsement changes what this document is and how it must be labelled.
- Do not call the customer a partner or a champion. No em dashes.
Ersetzen Sie jeden Platzhalter durch Ihre eigenen Angaben. Je genauer Sie sind, desto weniger erfindet das Modell.