Start with one story. The strongest one you have. The one where before, pressure, decision, move, and outcome are all clear. Write it down completely. Get the shape right. Show your understanding of why the outcome was possible, not just that it happened. This is archaeology, not marketing. You are digging into what actually happened, what the client was actually struggling with, what actually changed, and what was true underneath that made change possible. The difference between a story and portable proof is that the story lives in your head, but portable proof has to survive outside it. It has to work when a referrer is repeating it from imperfect memory. It has to survive compression when an AI assistant is summarising you against three competitors. It has to stay true to the original even when it is shaped into four different formats for four different moments. Build for that from the start.

The story should be specific enough that someone recognises themselves in the before state. If you work with founder-led businesses on operating rhythm, show founder dependency specifically, not vague disorganisation. Show the exact moment when the founder becomes the constraint. If you help growing teams coordinate without growing headcount, show the specific shape of chaos that makes growth hard, not generic overwhelm. Show the cost of the chaos in language a manager recognises. The specificity is not to be clever. It is to make the buyer feel seen. It is to make them read your story and think: that is exactly us, exactly our problem, this person understands what we are living through. When a buyer reads your story and thinks that, you have moved them from abstract interest to concrete belief. That is when they believe your proof.

The story should be attached to your spine. Your spine is the problem you own, the buyer you are built for, the offer they understand, and the point of view that makes the old way feel naive. Your proof shows all of those things. The problem you own. The buyer in the situation. The decision they made. The move you made that only someone with your point of view would make. The outcome that proves your spine was right. When someone reads your proof, they should think: this person owns this problem. Not they can help. They own it. They think about it differently. They have seen it more times than I have.

Once the story is clean, let the network carry it. A referrer sends the referral version. A founder writes the email version. A prospect reads it in a proposal. You open a first call with the meeting version. Each version stays true to the original. The details might change. The understanding underneath stays the same.

Do not make ten proof assets at once. One clean story is worth more than ten vague ones. Make it solid. Make it repeatable. Make it specific enough that a referrer remembers it. Then let it travel. The temptation is to create a whole library of proof stories so you can answer any situation that comes your way. What actually works is the opposite. Create one proof point so clean and so well shaped that your network knows it by heart, can repeat it from memory, can paste it into an email thread. That one story becomes your reputation. It becomes what people say about you when they describe you to someone else. It becomes the proof that moves. Then, once that story is moving and creating momentum, once you see it landing with the right buyers, you can add another.

This week's work #

Do not turn this book into admiration. Turn it into a short operating pass. The aim is not to create a full case study library. It is to shape one piece of proof that the network can carry.

• Write the story of one client situation where the before state, pressure, decision, move, and outcome are all clear.
• Check that the story shows your understanding of why the outcome happened, not just that it happened.
• Simplify it to a referral note that someone could repeat in two sentences.
• Test the language with one person in your network. Ask whether they could confidently use it if they met someone in that situation.
• Update the proof based on what you learned. Then let it travel.

Closing argument #

Proof that depends on you explaining it scales only as far as your calendar allows. Proof that travels scales through relationships you have already earned. When your network can carry your story, when a referrer can repeat it without you, when a prospect can compare you and see the difference, your practice stops depending on you being in every room. The growth compounds instead of starting over each quarter.

Portable proof is not polished language or brand design. It is evidence shaped for other people to carry. Start with one strong story. Make it specific enough to be credible. Make it simple enough to be repeatable. Make it impossible to forget or mishear or compress into something unrecognisable. Then watch the network do what networks do best: move your reputation forward without needing you to push it. That is the proof that travels. That is the proof that compounds. That is how a practice built on one person's presence becomes a practice built on one person's point of view.

Where next #

Read Actions That Create Revenue next. Proof only pays when it is attached to named action. To run the full motion with support for six weeks: nynch.com/clients-sprint.