Skip to content
The Proof Operating System
02

Proof Vault

Every demo, sample, document and result in one place — each clearly labeled.

A buyer should never have to guess whether they're looking at a live customer result or a slick demo. The Proof Vault holds everything you can prove and forces one honest label onto each asset — so a buyer instantly knows what's live, what's a demo, and what's a scoped result.

The problem

Unlabeled proof is the easiest place to blur the truth.

Scattered across decks, drives, and DMs, your evidence loses its shape. A demo gets described as a "result." A benchmark on sample data starts to sound like a customer outcome. None of it is checkable, and a careful buyer can feel the gaps.

The fix isn't more polish — it's a label on every asset. The Proof Vault makes that label mandatory, so the strongest thing you can do for a skeptical buyer is also the most honest.

The five honest labels

One label per asset — what it is, and what it isn’t.

The taxonomy is the core defense of the whole system, not a footnote. Each label sets a clear expectation, and each gives a buyer a specific kind of trust.

  • Live

    Running in a real customer's production system, right now.

    What the buyer gets

    It already works in the real world — the lowest-risk proof there is.

  • Demo

    A guided walkthrough on sample data — not a live customer.

    What the buyer gets

    See the product actually do the thing, with no claim that it's in production.

  • Sample

    A real example output or a past deliverable you can open and inspect.

    What the buyer gets

    Judge the quality of the work first-hand, instead of taking a promise.

  • Pilot outcome

    A measured result from a consented design-partner pilot.

    What the buyer gets

    Evidence it delivers in a context like yours — with the receipts attached.

  • Founder statement

    A first-hand claim the founder personally stands behind.

    What the buyer gets

    On-the-record context, clearly marked as a claim — never disguised as data.

Honest labeling keeps you safe under the FTC's 2024 rule on fake reviews (US) and is the affirmative-disclosure posture German UWG §5a expects (EU) — and it's what a skeptical buyer actually trusts.

The lifecycle

Five steps from a raw asset to a verifiable reference.

Capture
Label
Verify
Share
Maintain
acme-prod-dashboard.url
Unlabeled
exactly one — never zero, never two
LiveDemoSamplePilot outcomeFounder statement

Capture — pull in anything real: a recording, a sample, a benchmark, a result.

  1. Capture

    Add a demo recording, a sample output, a benchmark, a document, or a pilot result. Anything real that helps a buyer judge you.

  2. Label

    Tag the asset with exactly one honest label — Live, Demo, Sample, Pilot outcome, or Founder statement. The label declares what it is and what it isn’t.

  3. Verify

    Attach the substance that makes the label checkable — the method behind a benchmark, the scope behind a pilot outcome, the source behind a sample.

  4. Share

    Pull the right assets into a Buyer Room, scoped to one prospect. Only what’s relevant, shown read-only, with its label intact.

  5. Maintain

    Keep the vault current as proof strengthens — a demo becomes a pilot outcome, a pilot outcome becomes a Live reference. Revoke or retire anything that no longer holds.

Why the lifecycle matters

Proof isn't static. The same vault that starts with a demo and a benchmark is where your first Pilot outcome lands — and, once a customer goes to production, your first Live reference. The vault is the ledger of that progress, kept honest at every step.

Next: put the right assets in front of one buyer

Get started

Make every piece of proof checkable.