Skip to main content
Most customers cannot carry a case study. This skill finds the ones whose evidence is deep enough for a story, and tells you what is still missing before you commit an interview slot to it.

​
Usage

Name a topic, product area, value outcome, launch, or segment. Defaults to the last 90 days.

​
What You Get

  • Story candidates in order, each with the person, their role, and their customer account
  • A narrative angle: the story this customer can actually tell
  • Evidence depth: how much you already have
  • Missing proof: what you still need before the story holds up
  • Interview questions written for this candidate
  • Verbatim evidence with dates
  • A follow-up action into the permission workflow

​
Design Principles

Every candidate is a lead, not an approval. Evidence depth says a story is possible. It never says you may publish one. Validate before publishing. Metrics, attribution, and exact wording get checked with the customer first. Ask for participation first. Final story approval comes later, and separately. Never sends customer email. To log a permission request, use Proof Permissions.