Customer evidence

Proof should be specific—or clearly labeled.

Swum separates aggregate product data, verified family reviews and consented customer outcomes so readers can see what each claim actually proves.

Evidence library

Four kinds of proof, kept distinct

Logos and account activity do not become outcome claims. Reviews do not become case studies without permission.

01

Evidence type

Operational platform data

Aggregate lesson, booking, pricing and cancellation patterns with disclosed cohorts and downloadable values.

Review the benchmark
02

Evidence type

Verified family reviews

Public instructor profiles distinguish written verified reviews from rating-only aggregates instead of blending the two.

Browse public profiles
03

Evidence type

Independent app-store feedback

Public ratings and reviews remain on the marketplace where they were submitted, alongside release history and platform details.

View the App Store listing
04

Evidence type

Named outcome stories

A customer result is published only with explicit permission, a defined baseline, a time period and a reproducible metric.

Participate in a story

Case study standard

What a named Swum story must contain

  • Explicit written permission for the customer, company name and supplied assets.
  • A dated baseline and comparison period—not an unbounded “before and after.”
  • A metric definition that another reader can understand and reproduce.
  • The implementation details and other changes that could have influenced the result.
  • A customer review of the final copy before publication and a visible last-updated date.