The Community Proof Screenshot Kit
Type: article
Stage: Stage 9: Community Proof
Difficulty: intermediate
A random folder of screenshots is not a proof system. What belongs in a screenshot kit, how to manage it, and what makes a screenshot expire.
Overview
Screenshots are one of the strongest Stage 9 assets — but only if they are collected, labeled, and used correctly. A random folder of screenshots is not a proof system. A screenshot kit is.
What belongs in the kit
Create a folder or database with: original screenshot, blurred public version, date captured, source platform, user permission status, customer segment, problem referenced, outcome referenced, approved quote, where it can be used, and an expiration or review date. A screenshot can quickly become stale — a customer may churn, a product feature may change, a private community may not allow external reuse, or a quote may imply an outcome you cannot prove.
What to prioritize
Collect proof that shows peer trust specifically: 'Has anyone tried X?' 'Yes, we use [product]. It solved [specific issue].' 'Here's my setup.' 'This replaced our spreadsheet.' 'I made a template for this.' 'Try this instead of [incumbent].' These peer-to-peer moments are more credible than founder-solicited testimonials because no one was asked to perform.
Stage 9 rule
Raw proof is powerful, but unmanaged proof becomes trust debt.