Proof page
Story, case studies, and evidence architecture.
Your board clearly runs on a proof stack: story, platform screenshots, social validation, and downstream offer pages. This page gives you a structure for publishing that material without turning the site into a pile of unverified screenshots.
Suggested public layout
Use proof as a sequence, not a dump.
My story
Condense the origin into one page: initial position, failed attempts, breakthrough, and current operating model.
- Keep it chronological.
- Show 3 to 5 images maximum.
- Remove melodramatic claims that cannot be evidenced.
Case studies
Use only attributable examples with context, dates, and what the buyer should infer.
- What was the niche?
- What changed?
- Which screenshots support it?
Student results
Separate social proof from financial proof. Redact identifiers and get permission before publishing.
- YouTube interviews
- Telegram messages
- Payment snapshots
Verification checklist
What every proof item should pass.
Permission
Do you have explicit permission to publish the screenshot, interview, or identity-linked asset?
Attribution
Can you explain what the screenshot is, when it was taken, and what the viewer is supposed to infer from it?
Redaction
Are names, phone numbers, order IDs, addresses, or account handles hidden where required?
Substantiation
Could a reasonable person accuse this of being misleading if the surrounding context were removed?
Content sources from your board
Assets you can convert into proof modules.
YouTube interview embeds
Good for credibility. Add only after confirming titles, dates, and why the interview matters.
Dashboard or revenue screenshots
Useful only if current, legible, and paired with context. Avoid implying universal results.
Telegram or Discord testimonials
Use short excerpts with permission and aggressive redaction. Avoid publishing minors or identifying data.