No. 44 · Drafting (English edition first) · Marketing & trust · PROVE
Proof in Public
Trust Velocity for Evidence-First Founders
Buyers don't trust claims. They trust proof you can hand them.
Early-stage founders confuse activity with evidence: more posts, louder claims, another landing page. The Proof Engine treats trust as an evidence supply chain and gives you the PROVE system to build it: pilot the smallest proof that moves a buyer, record outcomes at the moment of truth, organize a searchable asset library, validate before publication, and exhibit signals that compound. For founders who refuse to manipulate and want to outrun hype with evidence.
- pages
- 192
- chapters
- 13
- hours of reading
- ± 2
- editions
- EN · NL
- Design
- Drafting
- Manuscript
- Production
- Launched
The editions
Kindle and Paperback
Production shots of the editions. Not for sale yet — this page is the public working version.
-
Kindle
The digital edition, ready in any Kindle app.
-
Paperback
The working copy. Mark it up. Take it into the meeting.
The book
Trust Velocity for Evidence-First Founders
The buyer nods through your pitch, says it sounds great, and asks you to "send something over." Then the thread goes quiet. You did not lose to a better offer; you lost to doubt you never saw, because the prospect could not tell (fast enough) whether you were the real thing or a confident stranger. In a crowded market, the deal does not go to the best work. It goes to the work the buyer can trust before the money moves.
The usual instruction is to network harder and let your reputation precede you. But reputation is slow, and "trust me" is the one claim a skeptical buyer is trained to discount.
Proof in Public treats credibility as something you manufacture on purpose, not something you wait to accumulate. It introduces the PROVE framework (Positioning, Receipts, Origination, Verification, and Endorsement), five sources of evidence that move a buyer from "who is this?" to "this is the one" before a single sales call. It builds proof the way you build a product: deliberately, in components, and measured by what it converts.
You will learn to: - Position so the buyer knows in one line what you do and who you are not for. - Turn delivered results into receipts: specific, dated, and verifiable, not vague praise. - Originate proof of your own: the demonstration, audit, or teardown that shows competence instead of claiming it. - Make every claim independently checkable, so trust survives contact with a careful buyer. - Earn endorsement that travels: references and signals that vouch for you when you are not in the room.
The result is a shorter path to yes. Buyers arrive already convinced, price resistance softens, and the sale becomes confirmation of a decision the proof already made.
If you sell real competence and are tired of watching louder, lesser operators close the deals you earned, this was written for you.
What you learn
What this book puts in your hands
- The PROVE framework: Pilot, Record, Organize, Validate, Exhibit proof end to end
- Five proof types mapped: usage, outcome, process, third-party, comparative
- A repeatable pipeline from customer reality to forward-able trust assets
- Validation gates so claims ship only after structured verification
- Trust velocity as a measurable signal: time to credible proof
The framework
PROVE, step by step
Pilot, Record, Organize, Validate, Exhibit proof end to end
-
Pilot
-
Record
-
Organize
-
Validate
-
Exhibit proof end to end
The contents
Chapter by chapter
Every chapter of Proof in Public with its printed epigraph, what you can do afterwards, and the moment it is built for.
Introduction
Introduction: The Trust Stall
A quiet pipeline does not tell you why it went quiet. Diagnose the decision before you prescribe more proof.
What you can do afterwards
You will distinguish an evidence-related stall from product, price, priority, authority, process, and unknown causes, then decide whether PROVE is the appropriate next route.
Use this chapter when
A demo went well, the buyer promised to discuss it internally, and the opportunity stopped moving without a clear decision.
Chapter 1
The Evidence Gap
A claim becomes an operating liability when its consequence is high and its support cannot survive inspection.
What you can do afterwards
You will turn one plausible evidence constraint into a prioritized queue of exact claims, buyer questions, source status, fit, permission, consequence, and next action.
Use this chapter when
Chapter 0 found that evidence may contribute to a stalled decision, or your public surfaces contain consequential claims whose support is unclear.
Chapter 2
Proof Taxonomy
A benchmark, login count, audit, and customer result can all be evidence. They do not answer the same question.
What you can do afterwards
You will classify evidence into five practical types, identify what each can and cannot support, and select an asset by claim and buyer question rather than prestige.
Use this chapter when
Your drawer contains testimonials, screenshots, ratings, reports, and logos, yet you cannot tell which asset fits the decision in front of you.
Chapter 3
Pilot Proof
A missing claim does not become true because a deal needs it. A bounded pilot can replace the guess with an observed result and a better decision.
What you can do afterwards
You will design a proof pilot with a prespecified measure, comparison, decision threshold, rival explanations, authorization, stop conditions, and claim decision.
Use this chapter when
Chapter 2 routes a consequential outcome uncertainty to build, a willing participant exists, and a bounded test can inform the next decision without unjustified risk.
Chapter 4
Record Evidence
A result is only as durable as the record behind it. Preserve the source, method, limits, and permission while they can still be checked.
What you can do afterwards
You will install a capture practice that preserves an observed result, its method and uncertainty, and the precise permission boundary around its use.
Use this chapter when
A pilot has produced a result, a customer mentions a change worth examining, or your check-ins leave you with warm sentiment but no inspectable record.
Chapter 5
Organize Proof Assets
Recorded evidence becomes usable when another person can retrieve the right record, understand its limits, and know what they are allowed to do with it.
What you can do afterwards
You will build a controlled proof-library index that makes Chapter 4 records findable without separating a claim from its source, scope, version, or permission.
Use this chapter when
Valid records exist, but answers still depend on who remembers a customer, a deck, or a private message.
Chapter 6
Validate Claims
A claim is ready when its wording fits its evidence, its intended use, and the consequence of being wrong.
What you can do afterwards
You will install a claim-validation gate that produces an explicit release decision, a traceable rationale, and a correction path.
Use this chapter when
A public statement is being created or changed, new evidence arrives, an old asset triggers review, or someone challenges a live claim.
Chapter 7
Exhibit Trust Signals
A reviewed asset cannot inform a decision the buyer never encounters. Placement is a hypothesis you must make visible and test.
What you can do afterwards
You will map one buyer decision, place an eligible proof asset at that point, and log enough exposure detail to evaluate the change in Chapter 8.
Use this chapter when
Your library contains Reviewed assets, yet buyers ask questions those assets should answer or important proof arrives too late in the process.
Chapter 8
Trust Velocity
You cannot measure trust directly from a sales timeline. You can measure what was shown, what decision followed, and where the record goes dark.
What you can do afterwards
You will turn trust velocity from a metaphor into a disciplined operating view built on exposure events, decision intervals, outcome cohorts, delay codes, missingness, and falsifiable hypotheses.
Use this chapter when
PROVE is producing and placing assets, but you cannot tell whether an evidence-related delay changed or whether another constraint governs the decision.
Chapter 9
Proof-Led GTM Motions
PROVE becomes useful when it joins the motion you already run. The channel changes the handoff; the evidence contract does not.
What you can do afterwards
You will turn one Chapter 8 diagnosis into a 30-day, channel-specific PROVE motion with owners, handoffs, exposure logging, review criteria, and a stop rule.
Use this chapter when
The proof system works as a set of practices but still sits beside sales, product-led growth, content, or fundraising rather than inside it.
Chapter 10
Agents and Proof
AI can transform authorized evidence into candidate work. It cannot turn missing events into customer truth, and fluent output does not earn release authority.
What you can do afterwards
You will design a permission-aware AI control contract for one PROVE task, with source lineage, restricted tools, deterministic checks, human accountability, and an incident path.
Use this chapter when
Your team wants AI to retrieve, summarize, classify, draft, or monitor proof work without fabricating customer evidence or exposing restricted data.
Chapter 11
The Proof Moat
A proof system can become harder to imitate when it is rooted in real relationships, governed records, and repeated learning. It can also become expensive clutter. Build for the first and test for the second.
What you can do afterwards
You will turn PROVE into a 90-day operating roadmap with a low-volume and a mature-library path, explicit costs, maintenance controls, review criteria, and kill rules.
Use this chapter when
You have completed one PROVE loop and need to decide which practices deserve durable ownership, budget, and infrastructure.
Conclusion
Evidence-First Growth
The outcome is not a larger archive. It is a better relationship between what you claim, what you know, and what another person can inspect.
What you can do afterwards
You will leave with the book's central protocol and one scheduled action selected from your governed roadmap.
Use this chapter when
You have completed the book, reached the day-90 review, or need to re-enter PROVE after a claim, source, permission, or placement failed.
Who it is for
Who this book was written for
The reader it was written for
The proof-starved founder. Seed to Series A, 1–15 employees, selling a real product and encountering consequential evidence questions in founder-led sales or product-led growth. Technically literate, skeptical of manipulative marketing, and close enough to customers to recover or generate legitimate source records. Some stalled decisions will have non-evidence causes;
Also a fit for
The founder-led seller. Solo consultant, agency owner, or technical founder who is still the closer. Needs proof assets for decks, emails, and demos — not a marketing team.
What you will use it on
- Diagnose whether an evidence gap contributes to a difficult buying decision
- Build a proof library before the next fundraise
- Stop rewriting the pitch deck with stronger adjectives
- Use AI for authorized, traceable assistance without granting it truth or release authority
- Align marketing with evidence policy from *Evidence-Aware Life*
Probably not for you if
- Growth hackers optimizing CAC without caring about claim integrity
- Founders pre-product / pre-customer
- Enterprise marketing ops with mature proof libraries
Editions
Editions and specifications
| Edition | Formats | Chapters | Pages | Reading time | ISBN (paperback) |
|---|---|---|---|---|---|
| English Proof in Public | In production | 13 | 192 | ± 2 hours | — |
| Dutch Proof in public | In production | — | — | — | — |
Both editions are written natively. The Dutch text is not a machine translation of the English. · Trim size: 6x9″
Frequently asked
What readers usually want to know
What is Proof in Public about?
PROVE helps founders turn claims into artifacts: pilots, records, organized proof, validation, and public evidence buyers can inspect. The subtitle is: Trust Velocity for Evidence-First Founders.
What is the PROVE framework?
PROVE: Pilot, Record, Organize, Validate and Exhibit proof end to end. Pilot, Record, Organize, Validate, Exhibit proof end to end
Is there a Dutch edition?
Yes. The Dutch edition is Proof in public, written as a native edition rather than a machine translation. It moves through the same production line.
How long is Proof in Public?
This edition runs 13 chapters, 192 pages in print and roughly 2 hours of reading.
The production system
How this book was made
Every title moves through the same gated production line: sourced research, a claim-level evidence ledger, structural review, fact-checking, red-team critique, and a bilingual final edit. AI agents do specialist work inside those gates; judgment, voice, and accountability stay human.
- Claims enter an evidence ledger with a source and a confidence grade before they reach the page
- English and Dutch are two native editions, not a translation of one another
- Every chapter clears readability, rhythm, and style gates before it is typeset
