Overview
A customer proof library gives customer marketing one reusable place for approved quotes, metrics, use cases, source links, permission status, and proof themes. This playbook helps replace the scattered testimonial swipe file that usually lives across docs, slides, screenshots, and memory.
Juno installs a proof library table and proof catalog page. The goal is not to draft a full case study; it is to keep proof findable, source-backed, and safe enough for future case studies, landing pages, sales decks, email, and campaigns.
Run it when proof is arriving from customer interviews, reviews, sales notes, case studies, support messages, or campaign research and nobody is quite sure what is approved.
Why you should keep proof reusable and permission-aware
Customer proof loses value when the team cannot answer basic questions: Where did this quote come from? Can we name the customer? Does the metric need legal review? What claim can this evidence actually support?
That gets expensive in small ways. Writers avoid strong proof because permission is unclear. Sales uses an old quote because it is easy to find. A landing page makes a claim that sounds better than the source can safely carry.
The FTC's endorsement guidance is a useful reminder that endorsements should be honest, not misleading, and not used to support claims the marketer could not make on its own: FTC Endorsement Guides: What People Are Asking.
Juno keeps the useful texture of customer language while adding enough structure to make reuse faster. The library separates ready proof from internal-only notes, permission-needed items, legal-review candidates, and claims that should stay out of public copy.
Step-by-step
- 1Confirm the brand, priority audiences, proof sources, approval rules, and channels where proof is likely to be reused.
- 2Review available sources for quotes, measurable outcomes, use cases, switching reasons, objections resolved, before-and-after contrast, and memorable customer language.
- 3Add qualified items to the proof library with source context, source links when available, customer details, proof type, permission status, proof theme, supported claim, and claim limits.
- 4Classify each proof item as public-approved, internal-only, permission-needed, legal-review, or unusable so marketers do not confuse promising language with publishable language.
- 5Update the proof catalog so the team can scan approved proof, source gaps, permission risks, and high-priority next actions without digging through every source.
- 6Apply approval assumptions, usage boundaries, quote-editing rules, metric standards, and out-of-scope claims to the catalog and library rows.
- 7Summarize what is newly usable, what needs validation or permission, and which proof themes are strongest for upcoming marketing work.
Frequently asked questions
Is this the same as a case study builder?
No. It is a focused extension of a case study workflow. The library stores reusable proof state so future case studies, landing pages, and sales assets can start from approved evidence instead of a messy source pile.
What should I bring before running it?
Bring any testimonials, customer emails, interview notes, review links, sales notes, case-study excerpts, screenshots, approval rules, or existing proof docs. If the sources are thin, Juno will create a conservative first pass and mark the gaps.
Can Juno use proof that is not approved yet?
Yes, but it will label that proof as permission-needed, internal-only, legal-review, or unusable. Unknown permission is not treated as public approval.
When should this run monthly?
Use the monthly refresh when new customer proof arrives regularly, before a case study push, before a website refresh, or before sales enablement updates. Reusing the same library keeps approval status and source links from wandering off.