case-study-and-prooflisted
Install: claude install-skill sarojkjha/aaj-marketing-skills
# Case Study & Proof
Most startups have results and no proof. The work happened, the customer is happy, the number moved -
and none of it is on the site, because nobody asked permission at the time and asking now feels
awkward.
The result is a site that claims outcomes in the abstract and demonstrates none of them, which is the
single most common reason a good consultancy or product reads as unproven.
## When to use
The user has a customer result and wants to publish it, is writing a case study, is deciding whether
they can name a client, or is looking at a page that asserts outcomes with nothing behind them.
Do not use this to invent a plausible case study from a thin engagement. If the baseline was never
measured, the honest output is a testimonial and a note to instrument the next one.
## Before you start
1. **Read the brand/product context** (`.agents/product-marketing.md`) for who the proof has to
convince and which outcome they care about.
2. **Get the before number.** Not an estimate made afterwards - what was actually true before the
work started. If it does not exist, say so early; it changes what you are building.
3. **Get what else was changing.** New hires, a pricing change, a seasonal peak. Every real
engagement has some. Hiding them is what makes a case study collapse under one good question.
4. **Find out what was agreed in writing.** Not "they were happy" - whether anything was signed, by
whom, and what it covered.
## Method
Proof has two