Section 1
The three trust levers
Trust in a buying relationship isn't a single feeling. The Trust Equation from The Trusted Advisor breaks it into credibility, reliability, and intimacy over self-orientation , and the B2B buying research adds a fourth force, personal value . Collapsed into what you can actually address with a story, there are three levers: Every story you tell pulls one of these primarily. A story can touch more than one, but it has a center of gravity, and that's how you file it. The discipline is knowing, for each story, which lever it pulls hardest, so you can grab it when that lever is the one stuck.
Section 2
Why deploying on purpose beats deploying at random
A buyer stalls for a reason, and the reason maps to a lever. If they're hesitating because they doubt you can deliver at their scale, an empathy story ("I really get your world") doesn't move them, they never doubted your empathy. You need a competence story. If they believe you're capable but sense you're just chasing the contract, no amount of proof helps, you need a personal-stake story that shows you care about the outcome. Random deployment gets the lever right by luck maybe a third of the time. Diagnosed deployment gets it right on purpose. This is also why memory matters less than filing. Paul Zak's research shows stories stick because they're character-driven and emotionally encoded , and 63% of listeners remember a story versus 5% for a statistic . But a stored story you can't retrieve at the right moment is worthless. A filing system that lets you grab the personal-stake story precisely when the buyer signals a self-orientation doubt turns a pile of memorable anecdotes into a deployable instrument.
Section 3
Build your story bank: the worksheet
Do this once. It takes an hour and it changes every call afterward. Step 1: Dump every story you have. List every real anecdote you've ever told or could tell in a sales context. Client stories, origin stories, failure stories, all of them. Aim for at least ten. Step 2: Tag each story with its primary lever. For each, ask which single question it answers best: can they do it (Competence), do they get me (Empathy), or do they care about my outcome (Personal stake)? Assign one primary tag. If it genuinely pulls two, note the secondary, but commit to a primary. Step 3: Score your coverage. Count the tags. Almost every founder finds the same imbalance: heavy on Competence (results, wins, credentials-as-stories), thin on Empathy, empty on Personal stake. That imbalance is your gap. Step 4: Fill the empty levers. For each thin lever, find or build a real story: • Empathy gap: a story about a client whose specific, unglamorous problem you understood before they explained it. • Personal-stake gap: a story where you did something that cost you but served the client, turned down scope, flagged a problem that lost you revenue, told a hard truth. Step 5: Write the trigger for each story. One line: the buyer signal that means "deploy this now." Example: "Deploy the personal-stake story when the buyer gets guarded about pricing or asks 'what's the catch.'" The finished artifact:
Section 4
The pre-call ritual: diagnose, then select
Before any call, spend two minutes on this: 1. Predict the stuck lever. From your pre-call research and what you know of the prospect's situation, guess which lever they'll most doubt. A prospect who's been burned before will doubt Personal stake. A prospect in an unusual niche will doubt Empathy. A prospect scaling fast will doubt Competence. 2. Pre-load the matching story. Pull the story tagged to that lever to the front of your mind. You're not scripting the call, you're loading the right ammunition. 3. Keep one backup per lever. Because your prediction can be wrong, and the buyer's real doubt often surfaces mid-call. When it does, you'll hear the signal (your trigger line), and you'll have the story filed under exactly that signal. This is the difference between "I told a good story" and "I told the story that cleared the specific doubt blocking this specific deal." The second one closes.
Section 5
The honest limits
A mapped story bank makes you deploy on purpose. It doesn't fix a bad offer, weak qualification, or a prospect who was never a fit, no story pulls a lever on someone who shouldn't be in your pipeline. Use this after qualification, on real opportunities, as the layer that clears trust doubts standing between a qualified buyer and a yes. And don't over-engineer the reading. Buyers don't announce their stuck lever, and you'll sometimes misdiagnose. That's fine, the backup-per-lever rule handles it, and misreading is recoverable when you're listening for the trigger signals. The system makes you faster and more accurate, not infallible. Treat a wrong read as information (their real doubt was elsewhere) and pivot to the story that matches what you just heard.
Section 6
Your story bank is mapped right when…
It's mapped right when you can name, for any story you tell, which of the three levers it pulls, and when you have at least two live stories filed under each lever, including the personal-stake lever most founders leave empty. It's mapped right when you walk into a call with a predicted stuck lever and a pre-loaded story, and when a mid-call doubt triggers a specific filed story instead of a scramble through memory. You're not ready if your "story bank" is still a shoebox of wins you deploy by recall, because a pile of competence stories can't clear an empathy doubt or a personal-stake doubt, and those are the doubts that stall qualified deals.
Section 7
Key takeaways
• Trust isn't one thing: it's credibility, reliability, and intimacy over self-orientation , plus personal value , which collapses into three deployable levers, competence, empathy, personal stake. • Stories stall when they pull the wrong lever; a competence story does nothing for a buyer whose doubt is about whether you care . • Sort every story by its primary lever, then find your gap, almost every founder is heavy on competence and empty on personal stake. • Write a trigger line for each story (the buyer signal that means "deploy now") so retrieval is diagnostic, not random; stored-but-unretrievable stories are worthless even though stories stick better than facts . • Run a two-minute pre-call ritual: predict the stuck lever, pre-load the matching story, keep one backup per lever for mid-call surprises.