The Trust Sequence — Workbook
Walk Out
With a Yes
A methodology for sales and BD professionals. Distilled from hundreds of real conversations into principles anyone can apply.
This workbook translates The Trust Sequence into teachable frameworks, call playbooks, and reflection exercises. Use it alone to sharpen your practice, with your team to build shared language, or as an onboarding tool for anyone new to client-facing work.
Your reflection answers are saved automatically in this browser. To keep them safe across devices, download a backup from the
8
Core Frameworks
The mental models behind high-trust conversations — applicable to any industry, any deal size.
7
Call Formulas
Six formulas — one per call type — showing how the frameworks combine in practice.
6
Call Playbooks
Phase-by-phase reference guides for each call type, with real quotes as anchors.
12
Reflection Exercises
Self-assessment and team exercises to turn principles into practice.
The Trust Sequence in one paragraph
You run every conversation — internal or external — on the same underlying logic: establish safety first, then establish context, then move toward a decision. Rapport isn't small talk; it's load-bearing. Without it the conversation stays surface-level. Context-forcing ("who are they, what do they want") ensures the team is building the right thing, not just building. And explicit outcome-framing ("let me frame what we need from this call") converts drift into direction. The same pattern repeats whether you're opening an intro call with a new client or reviewing a proposal internally before it goes out.
Two modes, one voice
External — with clients & partners
Become a relationship architect. Let the other person's story lead. Before you say anything about your company or solution — make them feel genuinely understood. That's what earns you the right to be heard. Close every conversation with a concrete next step. Not "we'll follow up." A time, a name, a date.
Internal — with team
Be the person who asks the hard question before the meeting, not after. Push your team to see what the client will actually experience — not just what was built or proposed. Warmth makes honesty safe. The sharper your questions, the faster everyone's judgment grows.
Section 1
Frameworks & Mental Models
Eight reusable thinking patterns that underlie high-trust conversations. These aren't rules — they're reflexes that the best closers run without thinking.
Framework 01
The Safety → Context → Decision Arc
Every productive conversation moves through three phases — in this order. Salespeople who skip safety get defensive rooms. Those who skip context solve the wrong problem. The ones who reach real decisions are the ones who build to them. The arc holds whether the call is 15 minutes or 2 hours.
1Safety — Warmth, humor, genuine interest. The room has to lower its walls before any real business can happen.
2Context — "Who are they, what do they want, how did we get here." Shared understanding before shared solutions.
3Decision — Name the desired outcome, move toward it, close with a named action and owner — not a mood or a direction.
"I just want to frame the desired outcome of this call ahead of conversation."
— Escalation call
"As blunt and dumb as it sounds — can you please give a little refresh: who are they, what do they do, what do they want, how we got there."
— Internal proposal review
In practice — across call types
Intro calls
The arc is most visible here. The first two minutes are safety — something personal, something real about their world. Then context: ask them to describe the problem in their own words before you say anything about your solution. The decision is always the same: a specific next call, booked before this one ends.
Requirements discovery
Safety is shorter here — they've already agreed to meet. Context is the entire call. The discipline is not to jump to solutions before you fully understand the problem. The decision: what will you bring back, in what format, by when.
Proposal calls
Skip safety and you're presenting to a room that's still evaluating whether to trust you. Skip context — the recap of their objective — and the numbers float without meaning. The decision is the ask: what do they need to do next, and who owns it.
Post-proposal follow-up
Safety re-establishes the relationship after the formal proposal moment. Context is critical: name their objection before they do. The decision: move toward a signature or name what would need to change.
Existing client calls
Safety is proportional to how long the silence has been. If weeks have passed without contact, open with something personal before the agenda. Context: recap what was agreed and whether it happened. Decision: name the next commitment.
Escalation calls
Safety here is not warmth for its own sake — it's a signal that you're not defensive. 60 seconds of genuine human exchange changes the temperature of the whole call. Frame the desired outcome before anything else: not 'let's discuss the problem' but 'let's agree on what this call needs to produce.'
Research & references
Psychology — Psychology of trust reciprocity
Starting an interaction from a position of trust creates a self-reinforcing cycle. Research by Brett & Gunia on trust in negotiations found that negotiators who began with an assumption of trustworthiness — demonstrated through early personal disclosure and genuine curiosity — were significantly more likely to elicit trustworthy behavior in return. Their paper describes this as a virtuous cycle: demonstrating trustworthiness cues reciprocity, which deepens trust, which deepens cooperation. The first few minutes of a conversation set the tone for everything that follows.
Brett, J. & Gunia, B. (2013). Trust in Negotiations. Organizational Dynamics. Johns Hopkins University.
Bestselling reference — Never Split the Difference — Chris Voss
Voss describes the trust arc as moving through three stages: rapport (establishing non-threatening intent), influence (earning the right to make suggestions), and finally trust-based influence — where a recommendation is accepted without needing justification. He calls the moment rapport is confirmed the 'That's Right' moment: when the other person signals genuine emotional buy-in. His central argument: you cannot reach influence without first completing the safety and context stages.
Voss, C. & Raz, T. (2016). Never Split the Difference. Harper Business.
Bestselling reference — SPIN Selling — Neil Rackham
Rackham's landmark study of 35,000+ sales calls found that presenting capabilities before establishing situational context is one of the most common and damaging errors in major sales. High performers invested systematically in the investigation stage first — building shared understanding before positioning any solution. Rackham frames this as moving from implied to explicit needs: the context arc must be complete before a decision is offered.
Rackham, N. (1988). SPIN Selling. McGraw-Hill.
Framework 02
Story Before Structure
Numbers don't persuade. Stories create the conditions in which numbers land. The salespeople who lead with credentials, capabilities, and cost estimates are talking to people who aren't ready to hear them yet. The ones who close lead with narrative — their own background, the client's situation, an analogy — and only then introduce the structure.
1Lead with a story — yours or theirs. Not the company's features, not the portfolio.
2Use analogy to make complexity tangible before making it precise.
3Introduce estimates, proposals, and architecture only after narrative is shared.
"I came from a business and entrepreneurial background… we started small but ended up shipping to 30 countries… and then I ended up, as I sometimes laugh, on the dark side — shifting from merchant to agency."
— Intro call
"If we simply move the system, we don't remove the burdens the current system has. We have to look at what you do today and what you want to do."
— Proposal call
In practice — across call types
Intro calls
Before the deck, before the credentials — lead with a story that mirrors their situation. If you've worked with a similar business, open with that. If your background is relevant, use it. The story is the reason they trust the structure that follows.
Requirements discovery
Use analogy to make technical complexity approachable. A story about a warehouse that doesn't know what the shop floor is doing lands better than an architecture diagram. The story earns the right to go technical.
Proposal calls
Never open a proposal with a number. Open with a recap of the story: where they are, what it's costing them, what the outcome looks like. Then the structure — phases, costs, timelines — makes sense because it's in service of a narrative the client already owns.
Post-proposal follow-up
When a prospect is hesitating, structure rarely closes them. Reference a client who was in the same position — same hesitation, same question — and what happened when they moved forward. Concrete and specific beats abstract and compelling every time.
Existing client calls
When proposing additional scope, lead with the story of what you've done together. The history is the credibility. The new proposal sits inside a relationship, not outside it.
Escalation calls
In an escalation, both sides arrive with their own version of events. The one who tells the clearest story of what actually happened — without blame and without spin — controls the narrative. Use story structure: what was agreed, what happened, what it means, what comes next.
Research & references
Psychology — Bruner's Two Modes of Thought
Harvard and NYU psychologist Jerome Bruner identified two fundamentally different ways the mind processes information: the paradigmatic (logical) and the narrative mode. While the paradigmatic mode aims at truth, the narrative mode aims at meaning — and meaning is what drives decisions. His 1986 work Actual Minds, Possible Worlds argues that story is the primary cognitive tool humans use to make sense of experience. Narrative engages System 1 thinking (fast, emotional, intuitive); structure alone engages System 2 (slow, analytical, effortful) — and most decisions are driven by System 1.
Bruner, J. (1986). Actual Minds, Possible Worlds. Harvard University Press.
Psychology — Narrative Transportation Theory
Green & Brock (2000) demonstrated that when a listener becomes transported into a narrative, their resistance to the message's conclusions drops significantly. This 'transportation effect' explains why a story about a similar client's situation lands differently than a logical argument for the same conclusion: narrative bypasses the analytical gatekeeping that would otherwise contest each claim. Dahlstrom (2014) confirmed in PNAS that narrative persuasion produces effects not predicted by dual-process theories alone.
Green, M. & Brock, T. (2000). Journal of Personality and Social Psychology. / Dahlstrom, M. (2014). PNAS.
Bestselling reference — The Challenger Sale — Dixon & Adamson
Based on research across 6,000 sales representatives, Dixon and Adamson found that top-performing Challengers consistently led with a compelling story about the customer's business before presenting their solution. Their Commercial Teaching framework opens with a 'Warmer' (insight into a challenge the customer faces), moves to a 'Reframe' (a new way of seeing the problem), and only then arrives at the solution. The story is not the conclusion — it is the permission structure that makes the conclusion credible.
Dixon, M. & Adamson, B. (2011). The Challenger Sale. Portfolio / Penguin.
Framework 03
Outcome-First Thinking
The question "what are we doing?" produces a list of tasks. The question "what are we trying to achieve?" produces a decision. High-performers run every conversation — internal and external — backward from the outcome. Features are in service of goals. Proposals are in service of problems. The moment a plan loses its connection to a business objective, it becomes expensive decoration.
1Establish the business objective before any technology, methodology, or price is discussed.
2Test every proposal and plan: does this actually get them there?
3Hold teams and clients alike to the original objective — not just to current tasks.
"We project the challenges you have through the technology we have available — and figure out how we can help enable you as people, as roles, as organisational processes."
— Roadmap planning session
"If I'm shopping for a microwave and I get shoved a fridge in front of my eyes, it's not going to make me want to buy a new fridge."
— Internal strategy session
In practice — across call types
Intro calls
The best qualifying question isn't 'what do you need?' — it's 'what does success look like twelve months from now?' The answer tells you whether the project they're describing will actually get them there.
Requirements discovery
Every feature request is a symptom. Go one level up every time: 'that makes sense — what's driving that need?' Discovery calls that stay at the feature level produce proposals that solve the wrong problem.
Proposal calls
Restate their business objective at the top — before the first slide of scope or cost. This re-anchors the room and gives you a framework to explain why certain things are included and others aren't.
Post-proposal follow-up
If a prospect is stuck, bring them back: 'Let's set aside the number for a moment — is the outcome still the right one? If yes, the question is just how to get there.'
Existing client calls
Hold clients to their original goals, not just the current sprint. 'You said the goal was to unblock the content team — three months in, is that happening?' This is what separates account management from order-taking.
Escalation calls
Name what this call needs to produce before anything else. 'What do we need to be true at the end of this call?' Once that's named, everything else is either relevant or it isn't.
Research & references
Psychology — Prospect Theory and decision framing
Psychologists Kahneman and Tversky (1979) established through Prospect Theory that people evaluate decisions relative to a reference point — typically the status quo — and losses loom larger than equivalent gains. When a client evaluates a proposal without a named outcome, cost is evaluated against the status quo. When the outcome is named first, cost is evaluated against the cost of not achieving that outcome. Framing the desired outcome before the price changes the reference point of the entire decision.
Kahneman, D. & Tversky, A. (1979). Prospect Theory: An Analysis of Decision under Risk. Econometrica.
Bestselling reference — SPIN Selling — Neil Rackham
Rackham identified Need-Payoff questions as the highest-value question type in major sales — the type most strongly correlated with successful outcomes. These ask the client to articulate what the solution would be worth to them: 'If we solved X, what would that mean for your business?' The mechanism is outcome-first: the client names the value before the price is presented, anchoring to the return before evaluating the cost. Top performers ask Need-Payoff questions far more frequently than average performers.
Rackham, N. (1988). SPIN Selling. McGraw-Hill.
Bestselling reference — The Challenger Sale — Dixon & Adamson
Dixon and Adamson found that 53% of B2B customer loyalty is driven not by the product or the relationship, but by the quality of the sales experience — specifically whether the rep offered unique insights that changed how the client thought about their own objectives. Challengers don't ask clients what they want; they teach clients to think differently about what they need. The insight reframes the outcome, and the outcome frames the purchase.
Dixon, M. & Adamson, B. (2011). The Challenger Sale. Portfolio / Penguin.
Framework 04
Psychological Safety as Infrastructure
The emotional climate of a conversation isn't a soft factor — it's the infrastructure everything else runs on. Rooms where people feel safe to say "I don't know" or "I disagree" produce better information, better decisions, and faster trust. This climate doesn't emerge by accident. It has to be built — deliberately, before the hard work starts.
1Lower the stakes before raising the challenge. Humor and warmth create permission for honesty.
2Model comfortable ambiguity. Being the first to say "I'm not sure yet" makes it safe for others.
3Pair sharp feedback with genuine care. Directness without warmth is just criticism.
"The goal isn't to always have a perfect outcome — but to be nimble."
— Internal strategy session
In practice — across call types
Intro calls
The client arrives with their guard up. The fastest way to disarm it is to say something that signals you're not performing: a genuine question, a moment of self-deprecation, an admission that you don't know something yet. It costs nothing and changes everything.
Requirements discovery
Clients underreport problems in rooms that feel formal. The more comfortable they feel, the more honest they are. Create the environment deliberately: acknowledge uncertainty, invite pushback, don't write things down in silence.
Proposal calls
A proposal room where the client feels safe to object produces better outcomes than one where they smile and say nothing. Actively invite challenge: 'Where does this not feel right?' Objections surfaced in the room are better than ones discussed without you.
Post-proposal follow-up
The follow-up call is often where honest concerns surface for the first time. Make it easy: 'Is there something about this that isn't sitting right?' is a better opener than 'did you have a chance to look at the proposal?'
Existing client calls
Long-term relationships calcify into politeness. The client stops flagging problems early because it feels awkward. Deliberately create moments of honest feedback: 'If you were to change one thing about how we work together, what would it be?'
Escalation calls
The most dangerous escalation rooms are the ones where neither side says what they actually think. Be the first to say something honest — even if it's uncomfortable. The side that does that first usually controls the resolution.
Research & references
Psychology — Edmondson — Psychological Safety Research (1999)
Amy Edmondson (Harvard Business School) coined 'team psychological safety' in 1999, defining it as a shared belief that the team is safe for interpersonal risk-taking. Her hospital study produced a counterintuitive finding: the highest-performing teams appeared to make more errors than lower-performing ones — because they were willing to report and discuss errors openly, while lower-performing teams hid problems out of fear. Safety produces information; fear suppresses it. In client conversations: clients who feel safe surface real problems early; clients who feel evaluated wait until problems become crises.
Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly.
Psychology — Google Project Aristotle
Google's Project Aristotle (2012–2016) analysed 180 teams and found psychological safety was the single most important predictor of team effectiveness. Teams with high psychological safety were rated as effective twice as often. Sales teams with high psychological safety exceeded revenue targets by 17%; those with low safety missed targets by 19%. Psychological safety is not a cultural nicety — it is a performance variable.
Google Project Aristotle (2015). re:Work. / Edmondson, A. (2018). The Fearless Organization. Wiley.
Bestselling reference — The Fearless Organization — Amy Edmondson
Edmondson's 2018 book synthesises decades of research across healthcare, technology, and professional services. Her core argument: psychological safety is not about being nice — it is about creating the conditions for candour. 'It's not about being nice. It's about candor, admitting mistakes, learning from each other.' In a sales context: a client who doesn't feel safe enough to voice objections will not voice them in the room — they will voice them to your competitors.
Edmondson, A. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace. Wiley.
Framework 05
Comfortable Uncertainty as a Trust Signal
The instinct to project confidence at all times is one of the most common — and most costly — mistakes in sales. When someone says yes to everything, the experienced buyer stops believing anything. The professionals who earn the deepest trust are the ones willing to say "I don't know yet" without flinching. Stated uncertainty about one thing makes stated certainty about everything else credible.
1Say "I don't know" when you don't know — out loud, without hedging or apology.
2Stay in the conversation after admitting uncertainty. The exit is the mistake, not the admission.
3Let honesty about limits be the reason the client believes your confidence everywhere else.
"If anyone is saying yes to everything by mid-January, my honest opinion is: either they're lying or they don't know what they're talking about."
— External commercial call
In practice — across call types
Intro calls
When a prospect asks a question you can't fully answer yet, the worst response is a confident number you'll have to walk back. 'I don't know yet — I'd rather tell you that than give you a figure I can't stand behind' builds more trust than false precision.
Requirements discovery
The entire point of discovery is that you don't know the answer yet. Naming that explicitly — 'we're here to understand, not to prescribe' — resets the dynamic. The client stops performing for you and starts sharing with you.
Proposal calls
If the proposal has a range rather than a fixed price, say why. 'We can't be more precise until we know X' is a statement of professional honesty. It signals that when you are precise, you mean it.
Post-proposal follow-up
When the prospect raises an objection you haven't considered, don't counter immediately. 'That's a fair point — let me think about that' is a sign of strength, not weakness. It gives you time to give a better answer.
Existing client calls
When something has gone wrong and you don't fully know why yet, say so. 'We're still investigating — I don't want to give you an explanation before I'm confident in it' is better than a premature answer that turns out to be wrong.
Escalation calls
Resist the pressure to explain or defend when you're not sure. 'I want to understand exactly what happened before I respond to that' is not weakness — it's the posture that prevents you from saying something you'll have to retract.
Research & references
Psychology — Epistemic trust research — Kushnir, Sobel & Sabbagh
Research by Tamar Kushnir (Duke), David Sobel (Brown) and Mark Sabbagh (Queen's University) on the earliest psychology of trust found that communicating uncertainty — saying 'I think so' or 'I'm not sure' — is not perceived as incompetence. It is a cornerstone of how humans learn to trust information sources. Their research shows the human mind is built to handle communicated uncertainty; what erodes trust is not 'I don't know' but false precision that later proves wrong.
Kushnir, T., Sobel, D. & Sabbagh, M. Trust comes when you admit what you don't know. Queen's Gazette / The Conversation (2022).
Psychology — Epistemic integrity and perceived credibility
A review of research published in Rationale Magazine summarised findings across pandemic-era trust studies: 'failure in expertise can be compensated by higher integrity and benevolence.' When communicating uncertainties transparently, experts are perceived as less biased and more willing to tell the truth — a component of trust that outlasts any single accurate prediction. The Royal Society's 2019 review of uncertainty communication confirmed that stating uncertainty does not necessarily undermine trust, and in many contexts strengthens it.
Rationale Magazine (2022). / Spiegelhalter, D. et al. (2019). Communicating uncertainty about facts, numbers and science. Royal Society Open Science.
Bestselling reference — Never Split the Difference — Chris Voss
Voss argues that false confidence is a trust liability. His core observation: a reputation for always winning at the counterpart's expense means no one will deal with you again. The honest posture — naming what you can and cannot do — is what builds the trust that produces repeat engagement. He frames this through Prospect Theory: when you are transparent about what is and isn't included, you remove the loss-aversion trigger that makes clients suspect manipulation.
Voss, C. & Raz, T. (2016). Never Split the Difference. Harper Business.
Framework 06
Authority Before Architecture
The most technically elegant solution fails if it's presented to the wrong person. Before any architecture is discussed, the best salespeople map the decision: who owns the outcome, who signs, who can block, and what that person actually needs to hear. The same proposal explained to an owner lands differently than when explained to an IT manager — and it should.
1Before the solution: establish who makes the decision and what they care about most.
2Calibrate depth and language to the decision-maker — technical for technologists, commercial for owners.
3If the decision-maker isn't in the room, make getting them there the next step.
"Remember — we're talking directly to the decision maker, the project sponsor, the owner. He needs to understand every intricate detail."
— Internal proposal review
In practice — across call types
Intro calls
Before any technical discussion: find out who makes the decision and what they care about. An IT manager and a CEO need to hear completely different things. 'Who else would be involved in a decision like this?' is one of the most valuable questions in an intro call.
Requirements discovery
The people in the discovery room are rarely the people who sign. Understand who isn't in the room and what they'll need to hear. Design the outputs — the requirements doc, the proposal — for the person who will ultimately approve it.
Proposal calls
A proposal that goes to the wrong person gets forwarded without your context. If you can't present directly to the decision-maker, give the person in the room the tools to do it for you: a one-page summary, a clear recommendation, a simple 'why this and why now.'
Post-proposal follow-up
If the decision is stalling, it's often sitting with the wrong person. 'Who else needs to be comfortable with this?' surfaces the real blocker so you can address it directly rather than hoping it resolves.
Existing client calls
When proposing expansion, check whether the original sponsor is still the decision-maker. Organizational changes are common. A proposal built for the wrong stakeholder fails regardless of its quality.
Escalation calls
Escalations often get stuck because the people in the room don't have the authority to resolve them. Before the call, establish who needs to be there. If they're not present, make getting them on the next call the first output of this one.
Research & references
Psychology — Consensus buying and multi-stakeholder decisions
Research by CEB (now Gartner) found that the average B2B purchase involves 6.8 stakeholders, each with different priorities and definitions of success. Presenting a solution optimised for one stakeholder — the person in the room — without accounting for others means the proposal enters an environment it wasn't designed for. Understanding authority structures before designing the proposal architecture is not a refinement; it is a prerequisite.
CEB / Gartner (2015). The Challenger Customer. Portfolio / Penguin.
Bestselling reference — The Challenger Sale — Dixon & Adamson
A significant portion of The Challenger Sale is dedicated to tailoring for resonance — adapting the message to each specific stakeholder's priorities. Dixon and Adamson found that consensus buying — where multiple people must align before a decision is made — has become the dominant B2B pattern. The defining attribute of Challenger reps is that they treat each stakeholder as if they were the customer, because in consensus buying, that is exactly who they are.
Dixon, M. & Adamson, B. (2011). The Challenger Sale. Portfolio / Penguin.
Bestselling reference — SPIN Selling — Neil Rackham
Rackham's investigation stage explicitly includes mapping who has influence over the decision — not just who is in the room. His finding: many proposals fail not because they are wrong but because they reach the wrong person first, and get forwarded without the context that made them persuasive. The solution is to design the proposal for the person who will ultimately approve it, and equip the person in the room with the tools to present it effectively on your behalf.
Rackham, N. (1988). SPIN Selling. McGraw-Hill.
Framework 07
The Commercial Honesty Posture
Clients who have been oversold become clients who dispute invoices, delay signatures, and eventually leave. The salespeople with the highest long-term close rates are the ones who name their non-incentives out loud — who tell clients what they don't need, what isn't worth the cost, and what the risks are. Counter-intuitive transparency is one of the most durable trust-building tools available.
1Name your non-incentive before the client suspects it. Don't wait to be challenged.
2Tell them what they don't need as readily as what they do. It makes the rest credible.
3Make billing and cost logic visible — clients who understand invoices trust them; clients who don't, dispute them.
"We have no incentive to charge for something that is not being used. It's quite the opposite — we want to make sure all billable time is also effective."
— Delivery call
"Why it all comes out in one bill — I think we owe you that transparency, so we'll work on it."
— Delivery health call
In practice — across call types
Intro calls
The clients who ask 'are you the right fit?' are testing whether you'll tell them if you're not. Counterintuitively, describing the situations where you wouldn't be the right choice makes them more likely to believe you when you say you are.
Requirements discovery
When you discover that what the client wants isn't what they need, say so. 'I want to make sure we build the right thing, not just what's on the list' is the sentence that earns long-term relationships. It might delay the proposal. It will protect the relationship.
Proposal calls
Name what's not in the proposal and why. 'We left this out because it doesn't move the needle on your stated goal' is more credible than a bloated estimate that includes everything. Clients trust proposals that show editorial judgment.
Post-proposal follow-up
If budget is a genuine constraint, say so early. 'At this budget, here's what we can do well and here's what we'd be cutting corners on' respects their position and maintains yours.
Existing client calls
Make billing visible before it becomes a question. Walk through what was spent and what was produced. Clients who understand invoices pay them. Clients who don't resent them — and eventually leave.
Escalation calls
Take the part that's yours without taking the part that isn't. Both capitulation and defensiveness destroy credibility. The honest sentence: 'Here's what we got wrong, here's what we think is on your side, here's what we propose to do about our part.'
Research & references
Psychology — Prospect Theory and transparency
Kahneman and Tversky's Prospect Theory (1979) established that people are significantly more sensitive to potential losses than equivalent gains. In commercial conversations, a client who suspects they may be getting less than they paid for experiences that as a loss — not a neutral disappointment. Conversely, when billing, scope, and limitations are made transparent proactively, the loss-aversion trigger is removed: the client evaluates the relationship as it actually is, not as they fear it might be.
Kahneman, D. & Tversky, A. (1979). Prospect Theory: An Analysis of Decision under Risk. Econometrica.
Psychology — Harvard Program on Negotiation — justified offers
Research from the Harvard Program on Negotiation shows that explaining the rationale behind a commercial position is essential for maintaining trust — even when the position is firm. An offer that appears extreme without justification erodes trust; the same offer, clearly explained, tends to preserve or enhance it. When people understand why a number is what it is, they can evaluate it fairly rather than suspiciously.
Harvard Program on Negotiation (2026). Trust in Negotiations. PON / Harvard Law School.
Bestselling reference — Never Split the Difference — Chris Voss
Voss makes the point through direct observation: 'I've run into CEOs whose reputation was to always badly beat their counterpart — and pretty soon no one would deal with them.' The commercial honesty posture is not idealism; it is long-term self-interest. In professional services relationships, where clients have long memories and multiple bids to compare, a reputation for clarity and fairness compounds. A reputation for winning at the client's expense does not.
Voss, C. & Raz, T. (2016). Never Split the Difference. Harper Business.
Framework 08
Phase It or Lose It
Complexity kills momentum. The larger a scope becomes, the harder it is for a client to commit — not because they don't want the outcome, but because the decision feels irreversible. The most effective closers use phasing not as a project management technique but as a commercial one: make the first decision small enough to make, then use delivery to earn the rest.
1When a client hesitates on scope, don't defend it — break it into phases.
2Make phase one the smallest credible step that still delivers real value.
3Use phase one delivery to earn the right to propose phase two — don't pre-sell it.
"If we do it in parts there's a bit of overlap as we move along — but that's going to keep the cost down and keep the momentum up."
— Proposal call
In practice — across call types
Intro calls
When the scope of what a client wants is too large to commit to in one conversation, introduce phasing early. 'The full picture looks like X — but the place to start is Y.' You're not selling the whole project; you're selling the first step.
Requirements discovery
Discovery itself is a phase. Position it as the first decision, not a precursor to the real decision. 'Let's agree on discovery first — that gives us both the information to make a better call about what comes next' is a close in itself.
Proposal calls
When a proposal is too large for a client to commit to, don't defend it — restructure it. Phase one should be small enough that the risk feels manageable. Phases two and three are earned by delivering phase one well. Don't pre-sell what you haven't earned the right to sell yet.
Post-proposal follow-up
If a prospect is stuck on the full scope: 'What if we started with just this piece — if it goes well, the rest becomes a much easier decision.' A smaller yes now is worth more than a larger maybe indefinitely.
Existing client calls
When proposing new work, always start with the smallest viable phase. The relationship gives you credibility — use it to make a small ask that leads to a bigger one. Large proposals to existing clients carry the same risk as large proposals to new ones.
Escalation calls
The resolution is also a phase. 'Let's solve this one thing first, then we can address the wider question' prevents the conversation from becoming everything at once. Naming a single, solvable first step moves the room from blame to progress.
Research & references
Psychology — Prospect Theory & Loss Aversion
Kahneman & Tversky established that people experience losses roughly twice as intensely as equivalent gains — which explains why a large, full-scope proposal registers as a threat rather than an opportunity. A client confronting an irreversible multi-phase commitment evaluates it through the lens of what could go wrong, not what could go right. Phasing reframes the first decision as a small, bounded risk: the perceived downside shrinks to something manageable, and the evaluation shifts from dread to consideration.
Kahneman, D., & Tversky, A. (1979). Prospect theory: An analysis of decision under risk. Econometrica, 47(2), 263–291.
Psychology — Choice Overload
Iyengar & Lepper's landmark study found that shoppers shown 24 jam varieties were 10 times less likely to purchase than those shown only 6. An extensive menu doesn't inspire action — it triggers avoidance. A complex proposal is structurally identical: the more workstreams, phases, and decisions a client must evaluate simultaneously, the more likely they are to defer rather than decide. Reducing the first decision to a single, clearly scoped phase removes the paralysis and creates the conditions for a yes.
Iyengar, S. S., & Lepper, M. R. (2000). When choice is demotivating: Can one desire too much of a good thing? Journal of Personality and Social Psychology, 79(6), 995–1006.
Bestselling reference — Influence — Robert Cialdini
Cialdini's commitment and consistency principle (Chapter 3) explains why a small Phase 1 yes is commercially powerful far beyond its immediate value. Once a client has actively committed — even to a modest first engagement — their own self-image as someone who follows through creates internal pressure to stay consistent with that decision. Phase 2 no longer feels like a new decision; it feels like the natural continuation of who they already are. The first yes reshapes the entire relationship dynamic.
Cialdini, R. B. (1984). Influence: The Psychology of Persuasion. William Morrow & Company. (Chapter 3: Commitment and Consistency.)
Section 2
Call Formulas
Deep-study guides — one per call type — extracted from 491 real client conversations. Each formula names the strategic phases, the language patterns that consistently work, and the single failure point that breaks most calls. Read these when you need to understand why a call type works the way it does, not just what to do in it. The Frameworks section is the theory; these formulas are the evidence.
How to use these
Each formula is a sequence, not a script. The phases are fixed — the words aren't. Each card also includes a "Language that lands" section with phrases drawn from real recorded calls — use these as starting points, not scripts. Expand any formula to study a call type in depth, to debrief after a call that missed, or to identify exactly which phase broke down.
↓
Intro / Qualifying Call
External
Qualify the opportunity, establish rapport, and earn the right to a deeper conversation.
Open personally
Start with something real — where they're based, a shared connection, something from the context of the intro. Two to three minutes minimum. The call doesn't start until this is done.
Give your story first
Before asking about them: a short, conversational version of your background that signals relevant experience. Not a CV — a proof of alignment. 'I've sat on your side of the table' is the message.
Ask about what isn't working
Not 'what do you need?' but 'what's frustrating you most right now?' The answer to what's broken is more useful than the answer to what's wanted. Features are answers to symptoms, not causes.
Reflect before you position
Summarise what you've heard in their words before you say anything about your solution. 'So if I understand correctly, the core problem is X — is that right?' This is the moment that earns trust.
Position through a mirror
Reference a client who had the same problem — not to brag, but to show you've seen this before. One specific example beats a general claim every time.
Close on a date, not a direction
Book the next call before this one ends. Not 'we'll follow up' — a specific time in a specific calendar. The call that ends with 'let's be in touch' rarely produces a next call.
Language that lands
Open
"Before we go into that — in your own words, there are things that are working great, it would be good to hear those first"
Hypothesis
"This is our hypothesis and we might be missing something — but what we understand at the moment is..."
Credibility
"There is most likely no other organisation in the world that focuses on this particular field so deeply — I say that not to impress, but because we've seen what happens when this goes wrong with a generalist"
Close
"So let's frame the next steps very clearly if we may here — can we take a liberty and book a date before we hang up?"
""What do you know about us — how come we have this conversation at all?""
— Intro call — surfacing the real reason someone reached out
Real-world examples & how to handle them
The prospect hasn't explained why they reached out
Most reps assume they know why someone booked a call. The dangerous ones launch straight into their pitch. Instead, surface the real reason early — before you've positioned anything.
"What do you know about us — and how come we're having this conversation at all? What prompted you to reach out?"
This does two things: it tells you what actually matters to them, and it hands them control before you take it back. People trust conversations they feel they started.
You joined the call late and missed the opening context
Don't fake it. Don't piece together what you think you heard. Ask directly — and frame the ask as service, not ignorance.
"If I may ask — I joined a few minutes late. I understand you're a marketing agency with a client in B2B construction who needs a platform built. Is that right, and did I miss anything critical before that?"
Admitting you're catching up signals honesty, not incompetence. And it forces a summary that often surfaces the clearest version of the client's situation — clearer than they gave it the first time.
The client asks why they should work with you specifically
The answer is never a credential list. It's a story of seeing the same problem before and knowing where it usually goes wrong.
"The speciality — that's where the strong point sits. I could go as bold as: there is most likely no other organisation in the world that focuses on custom builds in this particular field so deeply. And I say that not to impress — I say it because we've seen what happens when this goes wrong with a generalist, and we've built everything around avoiding that."
Bold claims earn trust when they come after you've demonstrated you understand the client's world. Said too early, they sound like marketing. Said after you've reflected their situation back to them, they land as conviction.
The call is going well but there's no clear next step
A good conversation without a booked follow-up is a lost opportunity. The window to propose a date is at peak rapport — not after the call when energy has dissipated.
"This has been really useful. Can we take a liberty and put something in the calendar now? I'd rather we have a date before we hang up than go back and forth on email."
The person who proposes the date controls the pace of the relationship. 'We'll follow up' means nothing. A calendar invite means commitment.
The client seems skeptical about whether you understand their industry
Don't defend. Mirror their world back to them with enough specificity that the skepticism becomes unnecessary.
"So from what I understand — you have a B2B setup with branch-level customization, direct supply relationships with mining companies, and you need to handle hydraulic connector configurations that vary by site. That's a fairly niche catalog problem. We've seen similar setups in industrial distribution, so I have some hypotheses — but I'd rather hear from you where the biggest friction is before I say anything else."
Specificity signals preparation. But ending with a question signals that you're still listening. Both are necessary — specificity without curiosity reads as assumption.
↓
Requirements & Discovery Call
External
Understand the problem deeply enough to build a solution that actually solves it — not just the one that was asked for.
State the purpose before the agenda
Open with what this call needs to produce: 'We want to walk away with enough to give you a proposal that actually fits your situation — not a generic one.' Outcome first, then process.
Re-establish context
Brief round of introductions and role explanations, even if you've met some people before. New stakeholders need to know who you are. You need to know who they are and what they care about.
Ask why before what
'What led you to this conversation?' produces a problem. 'What do you need?' produces a feature list. Every feature request is a symptom — find the underlying condition.
Follow the number
When a client mentions a metric, go deeper. Numbers reveal priorities and constraints that words often don't. 'You mentioned X — can you give me a sense of the scale?' is one of the most useful questions in any discovery call.
Summarise back — frequently
After each major topic, reflect it back: 'So if I understand correctly, the issue is X, which is causing Y, and what you need is Z. Is that right?' Small confirmations prevent large misalignments.
Name what you'll return with
Close with a specific deliverable: what document, in what format, by what date. Not 'we'll be in touch with a proposal' — a specific thing, a specific date, and what decision they'll be making when they receive it.
Language that lands
Purpose
"I want to avoid fingerpointing — we're explaining, very rationally, that there is an organism. The system needs to work in harmony"
Dig deeper
"What is the sole goal of this? Is it purely SEO? Is there some functional goal? What is the driver behind creating these pages?"
Budget
"I want to clarify — what do we understand in scope for this particular budget? Because I want to be very frank and honest"
Close
"How soon do you need it? When is your budget meeting? The reason I'm asking — we need to involve a number of people to make sure we estimate in detail that satisfies you later"
""What is the sole goal of this? Is it purely SEO? Is there some functional goal? What is the driver behind creating these pages?""
— Discovery call — refusing to accept a feature request at face value
Real-world examples & how to handle them
The client describes what they want — not what they need
Feature requests are symptoms. The discipline in discovery is to keep asking why until you reach a business pressure, not stop at the first answer you get.
"What is the sole goal of this? Is it purely SEO improvement, or is there some functional goal underneath that? What's the driver — what happens in the business if these pages don't exist?"
Clients describe solutions when they should be describing problems. The 'why' question — asked once, twice, three times — is what gets you to the actual problem. The feature is just one possible answer to it.
You discover what the client wants may not be what they actually need
This is the moment that separates order-takers from trusted advisors. The honest call is harder in the short term and better in the long term.
"I want to make sure we build the right thing, not just the one that's on the list. Based on what you've described, I think there's a risk that what we build solves the symptom rather than the condition. Can I share what I mean by that?"
Clients can feel when you're chasing scope. When you slow down and question whether the scope is right, they feel genuinely looked after. That feeling is the foundation of every renewal and expansion.
There's a number mentioned casually — revenue, order volume, team size
Numbers always reveal more than they seem. Don't let them pass. They tell you scale, priority, and constraint simultaneously.
"You mentioned 3.5 million a month in revenue and an average cart of around £150. Just so I understand the scale — how many of those orders involve some kind of manual intervention or exception handling right now?"
Following the number is a discovery technique, not a due diligence exercise. The answer tells you not just scale but process — and process is where the real problem usually lives.
The discovery call risks becoming a premature proposal
The temptation to solve in the room is powerful — especially when you can see the answer. Resist it. The cost of being wrong is much higher than the cost of a second call.
"I have some thoughts on this, and I want to share them — but I'd rather do that once I've been able to put them in context properly. What I don't want to do is give you a half-formed idea now that I'd have to walk back later. Can I come back to you by Thursday with something more considered?"
Restraint in discovery is a trust signal. It tells the client you're not selling — you're solving. Those are different things, and the client can feel the difference.
The MVP question — client says there is no minimum
Every project has a minimum viable version. The client's resistance to naming it usually means they're afraid of committing to something that feels incomplete. Reframe what minimum means.
"We need to figure out the MVP — not the version you'd be embarrassed by, but the version that goes to market and proves the model. What's the minimum you'd be comfortable showing to your first hundred customers?"
Changing the frame from 'what can we cut?' to 'what do your first customers actually need?' turns a constraint conversation into a product conversation. It also surfaces the real priorities faster than any requirements document.
Multiple stakeholders with different priorities in the room
Discovery rooms with mixed stakeholders produce noise unless you actively manage it. Name the competing views and make them productive.
"I'm hearing two different priorities here — and I don't think either of you is wrong. It sounds like on the business side the urgency is speed to market, and on the technical side the priority is not creating debt. Can we spend ten minutes on what the minimum clean version looks like that satisfies both? Because I think that version probably exists."
Naming the tension takes ownership of it. If you leave it unnamed, both stakeholders will assume the other is blocking them. If you name it and propose a resolution frame, you become the person who found a path forward.
↓
Proposal Presentation
External
Present a solution that the client experiences as theirs — not something done to them, but something built for them.
Restate their problem first
Before the first slide: recap what you heard in discovery — in their words. This proves you listened and re-anchors the room to the outcome before cost or scope is discussed.
Walk, don't present
Go through the proposal together, not at them. Stop at each section. Ask questions. Invite challenges. 'Does this match how you see it?' turns a presentation into a conversation and a conversation into a collaboration.
Name what's in and what's out — and why
For every major element: explain why it's included. For anything left out: explain why. Editorial judgment builds trust. A proposal that includes everything signals that nothing was prioritised.
Give them control over scope
Clearly separate mandatory from optional. Let the client make choices rather than having choices made for them. This reduces sticker shock and increases ownership of the final decision.
Anchor the number
Before the cost lands, give it context: a comparable project, a benchmark, a calculation of what the problem is currently costing them. A number without context feels arbitrary; a number in context feels reasoned.
Close with a named decision
The meeting ends with one explicit question: what needs to happen for this to move forward? Name the decision, the person who makes it, and the next date.
Language that lands
Open
"We'll explain two approaches with three options — we will let you make the decision. Obviously we have our thoughts, but I really want to make sure you understand all the options"
Candid anchor
"I mean, we are not going to get much richer if you take this proposal" — said when the budget is tight and you want to signal you're not padding
Cost reframe
"From one perspective it can be seen as additional expense. However, for the size of this business, the investment is relatively tiny against what it solves"
Close
"Shall we chase you up on Thursday? I can put together a one-pager so you have what you need to walk your team through it"
""The difference is literally one or two line items where we marked it optional instead of having two tiers.""
— Proposal call — giving the client control over scope
Real-world examples & how to handle them
The proposal is complex and the client looks overwhelmed
Stop presenting. Start walking. The shift from monologue to dialogue is a physical one — it requires you to pause and ask a real question.
"Before we go further — does this match how you see it so far? I'd rather we slow down here than have you nodding along and then going back to your team with questions I could have answered now."
A client who nods through a presentation hasn't bought anything. A client who has been invited to push back — and does — is already collaborating. Collaboration is much closer to a signature than agreement.
The scope is large and the cost is going to be a shock
Cost without context always feels arbitrary. Give the number something to stand next to before it lands.
"Before I show you the number — let's just anchor it. We calculated that at your current conversion rate and traffic, a 0.5% improvement would generate roughly £180,000 in annual additional revenue. The investment we're proposing is around £60,000. So the question isn't whether the number is big — it's whether the return justifies it. And I think it does, but let's see what you think."
This is not spin. It's context. The client was always going to evaluate cost against value — you're just making that calculation explicit and doing it before they have to do it alone.
There are items in the proposal that are optional — but this isn't clear
Ambiguity about what's mandatory vs optional creates sticker shock and slows decisions. Separate them explicitly and give the client control.
"The difference between the two tiers is literally one or two line items — we've marked them optional rather than creating two separate proposals. So the base is what we consider necessary; anything optional is there if you want it and can be removed without affecting the core."
Giving clients control over scope reduces the size of the decision they're making. Instead of 'do I approve this whole thing?', the question becomes 'do I want this specific piece?' Small decisions are easier to make than large ones.
You're proposing a platform or technical approach they're unfamiliar with
Technical confidence without accessibility creates distance, not trust. Use analogy to close the gap before going deep.
"Think of it like a car going into a new service station. The car is the same — the engine works the same way, the parts are standard. The only difference is who knows where everything is. Give it a service or two and it becomes entirely familiar. We're not changing the machine; we're getting to know it."
The client isn't evaluating the technology — they're evaluating their risk. The right analogy doesn't simplify the technical reality; it translates it into a risk framework they already understand.
The client says they need to share the proposal internally
This is the moment most proposals die — they get forwarded without the context that made them make sense. Give the person in the room the tools to present it for you.
"Completely makes sense. Let me make sure you have what you need to walk your team through it. The one-line version is: we're recommending this approach because it solves X without creating Y risk, and the investment is Z against a return of W. Would it help if I put that on one page so you have it as a leave-behind?"
The proposal that gets forwarded as a PDF rarely gets approved. The proposal that gets explained by someone who understood it has a much higher chance. You're creating an internal advocate, not a forwarded attachment.
↓
Post-Proposal Follow-Up
External
Move from 'interesting' to 'yes' — by understanding what's actually in the way.
Open with curiosity, not pressure
The worst opener is 'did you have a chance to look at the proposal?' The best is something warm and personal — then 'where did you land on it?' Let them tell you what's in the way before you assume you know.
Surface the real objection
The stated objection is rarely the real one. Budget concerns often mask alignment issues. Timeline concerns often mask risk aversion. Keep asking: 'Is it the number, or is there something else giving you pause?'
Return to the outcome
If cost is the objection, stop defending cost. 'Let's set the number aside for a moment — is the outcome still the right one?' If yes, the conversation is about how to get there, not whether to go.
Offer a smaller first step
When a client is stuck on the full scope, phase it. 'What if we started with just this piece — if it goes well, the rest becomes an easier decision.' A smaller yes now is worth more than a larger maybe indefinitely.
Name the blocker explicitly
Ask who else needs to be comfortable with this. The person you're talking to is rarely the only decision-maker. Getting other stakeholders named means you can address their concerns before they become blockers.
Give urgency a reason
Urgency without a reason is pressure. Urgency with a reason is information. 'If we're going to hit your Q3 target, we'd need to start by X' is useful. 'We need an answer by Friday' is not.
Language that lands
Open
"Perhaps we're completely off the expectations. Maybe you don't want to engage — or maybe we're slightly off and we can adjust. We'd like to get that feedback"
Objection
"I understand that the budget is the budget... but what I want to see still is whether the outcome is still the right one for you"
Blocker
"Who else needs to be comfortable with this before a decision can be made? Is there something specific they'd want to see that we haven't addressed yet?"
Close
"And if I may — I want to be very time conscious — I would encourage us to focus on finalising the next concrete step before we end this call"
""Perhaps we're completely off the expectations. Maybe you don't want to engage — or maybe we're slightly off and we can adjust. We'd like to get that feedback.""
— Post-proposal call — creating space for the honest objection
Real-world examples & how to handle them
Radio silence after the proposal was sent
The default follow-up — 'did you get a chance to look at it?' — is the question with the least information value. Try something that creates space for honesty instead.
"I wanted to reach out — not to chase a decision, but because I'd genuinely like to understand where you've landed. Maybe it's a timing issue, maybe something in the proposal didn't land right, maybe it's exactly what you wanted. Any of those is useful for me to know."
Permission to give negative feedback is a trust move. Most clients go silent because they don't know how to say 'not quite' without feeling like they're starting a difficult conversation. You're telling them that conversation is welcome.
The client says the price is too high
Budget is rarely the real objection. It's often a proxy for 'I'm not convinced the value is there yet' or 'I'm not sure I can get internal buy-in.' Dig before you discount.
"Let's set the number aside for a moment — is the outcome we described still the right one for you? If yes, then the question is really just how to get there. If no, then maybe we've proposed the wrong thing and we should back up."
Discounting immediately signals that you didn't believe the price was right in the first place. Returning to the outcome resets the conversation to value. If the value is clear, the price becomes a solvable problem. If the value isn't clear, no discount will fix it.
The decision is stalling without an obvious reason
Invisible blockers are always people. Someone who isn't in this conversation has a concern. Find out who and what before the deal goes cold.
"I want to make sure we're not losing time on something fixable. Who else needs to be comfortable with this before a decision can be made? And is there something specific they'd want to see or hear that we haven't addressed yet?"
Stalled deals rarely restart on their own. The person you're talking to usually knows what's blocking it but may feel awkward naming it. Asking directly and non-judgmentally gives them an easy way to surface it.
Prospect raises an objection you hadn't considered
The instinct is to respond immediately. The better move is to pause — genuinely — before answering. It signals that you heard the point, not just the words.
"That's a fair point and not one I'd thought about in that way. I don't want to answer it off the top of my head and give you something half-considered. Can I come back to you on that specifically — tomorrow at the latest?"
Answering every objection instantly signals you were waiting for it. Pausing on a genuine point signals you're actually thinking about their situation. The latter builds more trust, even if it feels slower.
The scope feels too large for the client to commit to
Large decisions are hard. Small decisions are easy. Phase the ask before you lose the deal.
"What if we started with just phase one — the diagnostic and the architecture. That's a much smaller commitment, it gives us both more information, and if it goes well, the decision about what comes next becomes much easier. A smaller yes now is more useful than a bigger maybe for another three months."
Phase one is not a consolation prize — it's a commercial technique. It gets the client into the relationship, demonstrates delivery, and earns the right to propose phase two. The full project is still the destination; phase one is just the entrance.
↓
Decision & Commercial Alignment
External
Move a stakeholder-aligned, commercially interested conversation toward a decision — by managing competing priorities, surfacing unspoken hesitations, and naming exactly what "yes" looks like.
Re-anchor to their world
Before any commercial discussion, prove you've been listening. Restate what you understood from discovery — in their language. The commercial room is not where you discover their situation; it's where you demonstrate you already know it.
State your hypothesis
Share your reading of what they need before asking for confirmation. 'Our hypothesis is X — we might be missing something, but that's what we understand.' This signals collaboration, not presumption — and invites the kind of correction that actually improves your proposal.
Split the decision into parts
Complex engagements rarely get one signature. Separate the conversation into discrete workstreams — 'keeping the existing situation stable' vs. 'building the next stage.' Clarity on structure removes ambiguity from the decision and makes each part a smaller, more achievable yes.
Surface the unstated hesitation
There is always something no one has said. 'Am I speaking nonsense, or does this feel reasonable?' is a disarming way to invite pushback. The unstated hesitation will surface at exactly the wrong moment if you don't bring it into the room first.
Name who decides — and what they need
Get to the decision-maker's actual question before the proposal is shared internally without you. 'What does the internal conversation look like on your side — and is there anything specific they'll want to see?' You can't influence a conversation you're not in. But you can shape it before it happens.
Close on a date, not a direction
'We'll follow up' is not a close. 'We're going to take your inputs, run them through our teams, and come back with a strategic plan by [date]' is. Commit to the specific output and the specific date before you end the call.
Language that lands
Re-anchor
"My role here is to figure out how to make your lives easier. So hopefully we're all on the same team"
Hypothesis
"I would like to reconfirm — if I understand correctly — sorry for everyone who doesn't know the background: what you're saying is..."
Structure
"I believe we need to treat this engagement in two parts: one part is keeping the existing beast alive, and then there's this other part which is building the next stage"
Fishing analogy
"We know we're going fishing — we don't know what we're going to catch yet. We have a good idea of where we're going and what fish lives there"
Close
"Just the status and next steps — how we win it, as always"
""Frankly, we don't know yet how big the fish is that we're going to fry. We know that we're going fishing, but we don't know what we're going to catch yet.""
— Commercial alignment call — anchoring shared uncertainty before price is discussed
Real-world examples & how to handle them
There are multiple stakeholders with different levels of context in the room
Commercial calls frequently have people in the room who weren't in discovery. Before you advance, reset the context — not for your benefit, but for theirs.
"Sorry for everybody who doesn't know — my role here is to figure out how to make your lives easier. So hopefully we're all on the same team. Let me just take two minutes to summarise where we are, so everyone is working from the same picture before we go any further."
A stakeholder who doesn't understand the context will object to the conclusion. A stakeholder who's been brought up to speed will evaluate it on its merits. Two minutes of alignment saves thirty minutes of confusion.
You need to present two very different technical approaches
Complex technical alternatives overwhelm non-technical stakeholders. Use the car analogy to translate risk, not capability.
"Let's get back to the car. Nothing wrong with driving a McLaren if you can afford the service every other week — but you could drive a Porsche, which does about the same thing, and if you look at the maintenance cost, it's a perfect daily driver. You can do it in winter, it hardly ever breaks down. That's essentially the choice we're presenting — same destination, very different total cost of ownership."
The client isn't evaluating the technology — they're evaluating their risk. The right analogy doesn't simplify the technical reality; it translates it into a risk framework they already understand. Once the risk frame is clear, the decision becomes much easier to make.
The conversation stalls when cost comes up
A number without context always feels arbitrary. The job of the commercial alignment call is to give that number the right frame before it lands — not after.
"Before I show you the investment — let's think about this differently. You have digital markets where you can grow quickly right now. This is one of the ways you can generate revenue relatively fast. The question isn't whether the number is large — it's whether the return justifies it. And I think it does. But let's see what you think."
Clients who see cost in isolation will always feel it's too high. Clients who see cost in the context of return will evaluate it rationally. Your job in the commercial call is to make sure the context is built before the number arrives.
You're asked to present multiple regional or product variants
Complexity multiplies when you're dealing with multiple markets or product lines. Anchor to one reusable foundation before expanding into variants.
"What we technically end up doing is building a reusable foundation — the theme, the logic, the architecture — and then deploying it across regions. It's not one code base repeated blindly, but it's not N separate projects either. The reuse is where the efficiency lives. Let me show you where the savings come from and where the customisation cost sits."
Multi-variant proposals confuse clients because the numbers grow fast. Showing the shared foundation first makes the structure legible — and makes the per-variant cost feel like a fraction of the whole rather than a whole new project.
The client wants to compare you against another vendor
Vendor comparison is legitimate — and trying to talk someone out of it usually backfires. The better move is to shape what they're comparing.
"Of course I understand you want to evaluate options — that's a sane thing to do. Usually it's a positive signal. There is genuine interest, we're having a conversation about specifics. What I'd ask is: when you brief the other options, use the same brief. What you'll see is that the differences become very apparent — and they tend to be in delivery risk, not just price."
Telling a client not to compare you signals insecurity. Telling them how to compare fairly signals confidence. It also shapes the evaluation criteria in your favour — which is exactly where you want to be before they talk to anyone else.
↓
Existing Client / Delivery Health Call
External
Maintain the trust that was earned to win the relationship — and turn delivery into the foundation for the next conversation.
Start with a real question
Not the agenda — a genuine check-in: 'How is it actually going?' A client who feels asked rather than processed is a client who tells you things before they become problems.
Recap original goals — then check them
Start from objectives, not tasks. 'You said the goal was to unblock the content team — how is that going?' Holding clients to their own goals is what separates account management from order-taking.
Make billing visible before it's a question
Walk through what was spent and what was produced. Clients who understand invoices trust them. Clients who don't understand them build resentment quietly — and voice it loudly later.
Surface problems before they escalate
Ask directly: 'Is there anything not working the way you expected?' The clients who don't flag problems early are the ones who terminate relationships without warning. The question has to be asked out loud.
Propose the next thing from delivery
The best time to expand a relationship is when delivery is going well. Not 'we have other services' — 'based on what we've been doing together, here's the next thing that would move the needle for you.'
Close with explicit actions
Don't let the call end with 'we'll look into that.' Every open item gets a name, a date, and a format for the response. The client leaves knowing exactly what happens next and when.
Language that lands
Feedback
"On that note, I really appreciate you sharing that — it gives me the opportunity to go back to the process setup and figure out where things did go wrong"
Diagnostic
"What do we miss to get an A?" — one short, disarming question that often produces the most honest feedback you'll hear
Agenda
"What do we want to get through? So technically this call says a feedback call — probably we want to focus on that, and also go through the budgets update"
Close
"I will send a quick recap — next steps are very clear: [name], you're looking at X. [name], we're waiting for your feedback on Y by [date]"
""You specifically said one of the goals was to unblock content teams. How is this process improving?""
— Delivery call — holding a client to their original objective
Real-world examples & how to handle them
The client mentions something is frustrating — not on the agenda
When something emerges off-agenda, stop the agenda. The thing they mentioned is always more important than the status update you were about to give.
"Hold on — before we go through the rest of the update, I want to make sure I understood what you just said. It sounds like X is causing a problem for your team. Can you tell me more about that? I'd rather we spend time on something live than tick through items that aren't the priority."
Clients who feel heard at the moment they raise something difficult will raise things early in future. Clients who get redirected to the agenda stop raising things early — and surface them as escalations instead.
The invoice is larger than the client expected
Surprise invoices are trust killers. The antidote is transparency about what drove the cost — before the invoice is questioned, not after.
"Before we wrap up, I want to walk through the billing this month — not because there's a problem, but because I think it's important you understand where the hours went. There were a couple of things that took longer than estimated, and I'd rather explain that now than have you see a number that looks different from last month without context."
Clients who understand invoices pay them without friction. Clients who don't understand them wait, push back, or go quiet. Proactive billing transparency is one of the fastest ways to build account stability.
Progress is happening but the client's original goal is being forgotten
Delivery conversations drift toward tasks. The discipline is to anchor them back to outcomes — even when the client doesn't bring it up.
"We said at the start that the goal was to unblock your content team so they could publish without going through development. We're three months in — how is that actually going? Not the technical delivery, but that specific thing. Is it better?"
This question is harder to ask than it sounds. If the answer is 'not yet', you've surfaced something important that might otherwise sit unaddressed for months. If the answer is 'yes', you've just given the client a reason to feel good about the relationship.
You want to propose new work but the timing feels uncertain
The best time to expand a relationship is when recent delivery has been solid. Use that specifically as the frame — not 'we have other services' but 'based on what we've done together.'
"The last three months have gone well — I think we've found a good rhythm. Based on what I've seen of how your team works and where the pressure is, there's one thing I think would move the needle significantly for you that we haven't looked at yet. Would it be useful if I put together a short note on it?"
Expansion proposals that come from observation of the client's actual situation feel very different from upsell attempts that come from a product catalogue. The former strengthens the relationship. The latter erodes it.
The call has been going well but nothing concrete has been agreed
Delivery calls that end warmly but vaguely are almost as bad as ones that go poorly. Both leave the client without a clear picture of what happens next.
"Before we wrap up — let me just make sure we're clear on what happens after this call. From my side: I'm going to look into X and get back to you by Wednesday. From your side: you were going to check on Y and let me know. Does that sound right? And shall we put the next check-in in the calendar now?"
The explicit close on a delivery call is not administrative — it's relational. It signals that you take the commitments from this call seriously, which makes the client take them seriously too.
↓
Escalation & Resolution Call
External
Resolve a specific problem without destroying the relationship — and leave with more trust than you arrived with.
Open with humanity
Even in the most difficult call: one genuine personal exchange before anything else. This is not deflection — it's a deliberate signal that you're not defensive. A defensive opener makes the whole call harder.
Frame the desired outcome first
Before any detail: 'I want us to walk away with a clear picture of what happened, and a single agreed next step.' Without this, escalation calls drift into blame rather than resolution.
Reduce to one answerable question
Escalations accumulate layers of complexity. Cut through it. 'The question right now is X — let's answer that first, then we can address everything else.' One clear question is better than three competing debates.
Take your share — not theirs
Honest attribution is the credibility move. Take the part that's yours clearly and directly. Don't take the part that isn't. Credibility comes from fairness, not from capitulation.
Name the next step, not the full plan
The resolution doesn't have to happen in this call. What has to happen is a specific action, a named owner, and a date. 'We'll look into it' is not a next step. 'I'll send you the analysis by Thursday' is.
Close the call explicitly
Explicitly summarise before hanging up: 'We've agreed that X, you're going to do Y, we're going to do Z. We'll reconnect on [date].' Escalation calls that drift to an end feel worse than the problem that caused them.
Language that lands
Honest regret
"I'm disappointed. I wish you would have reached out to me when you had that pain — at that point I would have loved helping. Now we need to figure out where we go from here"
Reduce
"The question is very simple: are the cookies firing or not, as of this time? That's it. Then we decide what to do with it"
System view
"We have all of these components — who can explain to me how does it all work? Who is the project owner who can tell me how does this connect?"
Close
"Can we get to some net zero final line — next steps? What are we doing?" — forces action when the call has gone in circles
""The question is very simple. Are the cookies firing or are they not firing, as of this time? That's it. And then we decide what to do with it.""
— Escalation call — reducing a complex situation to one answerable question
Real-world examples & how to handle them
The client arrives to the call clearly angry
The instinct is to go straight to the explanation. Do the opposite. One minute of genuine human acknowledgment changes the entire texture of what follows.
"Before we get into any of this — I just want to say that I understand this has been a frustrating situation, and I appreciate you taking the time to be on this call. That's not a small thing when things haven't gone the way they should."
Acknowledgment is not admission of guilt. It's recognition that the client has had a difficult experience. These are different things, and the client can tell the difference. Acknowledgment first creates space for a genuine conversation. Skipping it makes everything that follows feel defensive.
The escalation call is going in circles — multiple issues, no resolution
Escalations that try to resolve everything at once resolve nothing. Identify the single thing that, if answered, would unblock the rest.
"We've covered a lot of ground — and I think the most important question right now is actually one specific thing: are the cookies firing outside of consent as of today? That's the question we need to answer before anything else, because everything else depends on it. Can we just nail that one down before we go any further?"
Complexity in an escalation is often a defence mechanism — both sides keep adding context to avoid committing to an answer. Naming one answerable question cuts through it and forces progress.
The client is trying to put all responsibility on you
Honest attribution — taking your share without taking theirs — is the credibility move in an escalation. Neither capitulation nor defensiveness works.
"I want to be straightforward about this. Here's what we got wrong on our side — and I'm not going to minimise that. At the same time, there are things that were on your side that contributed to this situation. I think we both know that. I'd rather we name both clearly and figure out how to move forward, than spend the next hour assigning percentages of blame."
Clients respect honesty about accountability more than they respect protection of position. Taking your share disarms the aggression. Naming theirs — calmly and fairly — prevents the kind of one-sided resolution that festers into resentment.
The resolution requires action from both sides but there's no clarity on who does what
Escalations that end with 'we'll figure it out' don't end — they continue. The close has to be specific enough to be tracked.
"Let me just make sure we leave this call with something concrete. From our side: I'll send you the full incident analysis by Thursday and flag the specific points where we fell short. From your side: you were going to check with your IT team about the GTM configuration. Shall we put a follow-up in the calendar for Friday so we can confirm both have happened?"
Naming actions, owners, and dates in the room prevents the post-call ambiguity that lets escalations reignite. It also signals professionalism — which matters a lot when trust has been damaged.
The client wants to reduce the engagement — not end it, but scale back
This is not a commercial conversation — it's a trust conversation. Treat it that way. Find out what's underneath the request before you respond to it.
"I want to make sure I understand what you're actually asking for. Are you looking to reduce the engagement because the budget has changed, or is there something about how we're working together that's made you feel like it's not delivering enough value? Because those are really different conversations and I want to make sure I'm answering the right one."
Clients who are reducing engagement are either managing costs or managing disappointment. Cost is fixable with a scope conversation. Disappointment is fixable with a trust conversation. Treating cost management as disappointment — or vice versa — makes the situation worse.
You're the one who has to acknowledge a genuine mistake
The worst version of this is a qualified apology that sounds like a defence. The best version is direct, complete, and followed immediately by what you're going to do.
"I'm glad you raised this, because I know otherwise it probably goes nowhere and then we're all upset. Here's what happened and why it shouldn't have: [specific explanation]. Here's what we're doing to make it right: [specific action]. And here's what we're changing so it doesn't happen again: [specific change]. I appreciate you being willing to have this conversation directly."
A complete apology has three parts: what happened, what you're doing about it, and what changes. Most apologies only have the first part — which leaves the client wondering whether anything will actually improve. All three parts together close the loop.
↓
Internal Escalation & Team Recovery
Internal
Align the team on a client problem without blame spirals — so you walk into the client conversation with one clear, credible voice.
Establish facts first
Get the situation on the table before anyone assigns blame. "What happened, when did we find out, and what do we know for certain right now?" Facts first creates a working surface. Speculation and defence in the same breath create chaos.
Draw the responsibility line
Name clearly what is yours and what isn't — before the client does it for you. "We are responsible for this part. This part belongs to a third party. This part is a grey area we need to investigate." A team that hasn't agreed on this will contradict itself in front of the client.
Find the analogy
Before the client call, agree on how you'll explain the technical reality in plain language. If a system failure was caused by bad data from a third-party ERP, the client needs to understand that without feeling redirected. The analogy has to be agreed internally before it's used externally — and it has to be fair, not self-serving.
Separate the apology from the defence
If something is your fault, say so cleanly — without immediately following it with a "but." "We didn't catch this before go-live. That's on us. As soon as we caught it, we fixed it the same day." The apology and the mitigation are two separate sentences. Combined, they read as defensiveness. Separated, they read as accountability.
Agree the narrative
Before anyone talks to the client, the team agrees on one version of what happened and what comes next. Not who said what internally — the client-facing version: what the situation is, what caused it, what you're doing about it, and what stability means going forward. One voice is a non-negotiable output of an internal escalation call.
Name next steps precisely
Leave the internal call with a specific action list — not a feeling of alignment. Who sends the update to the client? What does it say? When? Who joins the client call and who doesn't? What is the one thing the client needs to hear, and who says it? Vague internal alignment produces vague client communication.
Language that lands
Facts first
"What exactly is our part? Let's be precise. And what's the narrative we use to explain the rest without making it adversarial?"
Attribution
"We didn't catch it before go-live — that's on us. As soon as we caught it, we fixed it the same day. The rest of the issues are coming from outside"
Stop the spiral
"Let's park who did what for now. The only question that matters is: what does the client need to see from us in the next 24 hours? We do the retro after the fire is out"
Align
"Before we do anything else — we need to agree on what we're going to say to the client. Once we agree, nobody speaks to this client until we've aligned. Then we go together"
"We didn't catch it before go-live — that's on us. As soon as we caught it, we fixed it the same day. The rest of the issues are coming from third parties. But we can't just say that. We need to explain it in a way that doesn't look like we're pointing fingers."
— Internal SWOT call, platform stability incident
Real-world examples & how to handle them
Each scenario shows a specific internal situation and how to navigate it before it reaches the client.
The delivery team says the client is wrong — but the client is already upset
Being technically correct and being helpful are different things. When the client is blaming your system for problems caused by a third-party integration, the instinct is to defend. The better move is to separate the facts from the framing.
"We didn't do anything wrong here — maybe a little bit, but not most things. Most things are coming from outside. That's a lot of finger-pointing, and we want to make sure we communicate it without looking like we're deflecting. So: what exactly is our part? Let's be precise. And what's the narrative we use to explain the rest without making it adversarial?"
The team needs permission to be honest internally before they can be clear externally. Force that conversation first — then build the client narrative from what you found.
A team member knew about the problem but didn't escalate it
This comes up repeatedly. The PM knew. The developer knew. Nobody told the client. The internal conversation has to establish what happened — without becoming a tribunal that stalls the fix.
"Before your vacation we went through this list. This was on it. After your vacation, we went through it again. This was still on it. I'm not trying to make you feel bad — I'm trying to understand how this slipped. Because now we're two months into a client issue we haven't addressed. Let's figure out what we do now, and separately figure out how this doesn't happen again."
Separate the immediate fix from the process conversation. Conflating them means neither gets resolved. The client situation is urgent; the process discussion can wait 48 hours.
The team wants to patch the problem rather than fix the root cause
When a client is upset and the pressure is on, the team's instinct is to do something fast. Challenge that instinct internally before it produces a fix that breaks trust further.
"Are we actually tackling the issue? Or are we slapping a fix on top of something? Because if we send a patch now and it fails again next week, we're in a much worse position than we are today. What does the client actually need — what is the real thing that needs to be solved?"
Speed feels like progress. But a visible fix that fails again damages trust more than a slightly slower correct fix. Make this argument internally before the team commits to a shortcut.
Different team members have different versions of what happened
The most dangerous situation: the client calls, and depending on who picks up, they get a different story. The internal call must produce one agreed version before anyone speaks to the client again.
"Before we do anything else — we need to agree on what we're going to say to the client. What's accurate, what's fair, what explains the situation without placing blame in a way that sounds defensive? Once we agree, nobody speaks to this client until we've aligned. Then we go together."
A client who gets three different answers from three people stops trusting the organisation — not just the individuals. One voice is a non-negotiable output of this call.
The problem was partly caused by the client's own team
Attribution matters internally — but tone matters more externally. The internal call should establish what's on their side clearly enough that the team doesn't carry responsibility for it. But the client call needs to handle this without triggering defensiveness.
"We're not going to say 'you caused this.' We're going to say 'the stability of any system depends on everything that connects to it — including the data that arrives from outside.' Then we show them specifically what that means. The goal is to give them enough clarity to fix it on their end. If we do it well, they'll draw the conclusion themselves."
Clients who reach their own conclusion are far more receptive than clients who are told. Structure the explanation so the conclusion is obvious without needing to be stated.
The team has started blaming each other internally
Internal blame spirals feel like honesty. They're not — they're consuming time that should go toward the client situation. Someone has to stop it.
"Let's park who did what for now. That conversation is worth having — but not in this call and not under this pressure. The only question that matters right now is: what does the client need to see from us in the next 24 hours, and what do we need to do to make that happen? We do the retro after the fire is out."
The retro is legitimate and necessary. But it belongs after the client is stabilised — not during the crisis. Naming this distinction gives people permission to stop defending themselves and start solving.
Section 3
Call Playbooks
Quick-reference cards — one per call type. Where the Formulas give you depth and background, the Playbooks give you speed. Five phases, a few sharp moves, and a real quote. Use these the morning of a call, to brief a colleague in ten minutes, or to check your plan against what actually works. Fast to scan, immediately actionable.
External calls
Intro / Diagnostic Call
External
Open
Genuine warmth before business. Comment on something real — where they're based, something from the intro email, a shared conference. Spend 2–3 minutes here. This is not optional.
Orient
Your backstory as credibility signal. Where you came from, how long you've been doing this, what you've seen. Told conversationally, not as a pitch. The goal is alignment, not a CV.
Listen
Ask what isn't working before asking what they need. "There are things that are working great — let's start there. And then the shortcomings?" Let them lead. Take notes on what they don't say as much as what they do.
Position
Your company through their problem, not your portfolio. Reference clients or situations that mirror theirs. Specificity over breadth — one relevant example beats ten logos.
Close
Name the next step and book it on the call. "Can we take a liberty and book a date on our calendars for it?" Don't leave with "we'll follow up" — leave with a time.
"The speciality — that's where the strong point sits. I could go as bold as: there is most likely no other organisation in the world that focuses on this particular field so deeply."
— Intro call
Problem & Requirements Discovery
External
Anchor
State the purpose before the agenda. "Today we want to make sure the vision we bring back is well aligned." Outcome first, then process.
Context
Re-introduce yourself even if you've met. Especially with new stakeholders on the client side. Names, roles, how long, what you care about. Signals respect and resets the room.
Dig
Clarify the "why" before the "what." "What led them to this conversation?" Ask this out loud or to yourself. Features are symptoms; business pressure is the disease. Understand the disease.
Confirm
Summarise back before moving on. "So you're not really running Google Ads — it's all on the Google Ads platform, right?" Small confirmations stop big misalignments from forming.
Close
Name what you'll bring back and when. "We don't want to go too detailed but want to make sure we give you something tangible." Commit to a format and a date, not a vague "we'll be in touch."
Ballpark / Proposal Presentation
External
Reframe
Business objective before the numbers. "What I said about keeping the business objective first — simply moving the system doesn't remove the burdens." Remind them why they came before showing them what it costs.
Walk
Walk through it together — don't present at them. "Probably look at that presentation together." Stop at decision points. Invite challenges. Make it a conversation, not a slide show.
Handle
Distinguish mandatory from optional clearly. "The difference is literally one or two line items where we marked it optional." Give them control over scope. Reduces sticker shock and builds trust in the estimate.
Anchor
Name a concrete reference point for the price. Use a comparable client or project. Don't leave a number floating without context — it will feel arbitrary.
Close
Name the decision and the person who makes it. "From there it's going to be a bit of a ping pong on both teams just to make sure we're nailing the value." Be explicit about what happens next.
Escalation & Recovery Session
External
Warm
Humanity before the problem. Even in a difficult call. Especially in a difficult call. A 60-second genuine exchange lowers cortisol. It also signals you're not defensive.
Frame
Name the desired outcome before discussion. "I just want to frame what we need from this call ahead of the conversation." Without this, escalation calls drift into blame rather than resolution.
Simplify
Reduce the problem to one clear question. "The question is very simple: are the cookies firing or are they not firing, as of this time. That's it." Stop arguing about everything when there's one thing to verify.
Own
Take the part that's yours without taking the part that isn't. "There damn should be someone in your organisation who understood this." Honest about both sides. Credibility comes from fairness, not capitulation.
Exit
Leave with an action, a name, and a date. Not a mood. Not a direction. A specific commitment. "Let me know when you want to talk to someone on our side about it — not Muhammad."
Delivery Health & Feedback Loop
External
Check in
Real question first, agenda second. "How is it? Is this process improving?" Don't just run through the status list. A client who feels unheard won't surface real problems until they're escalating.
Transparency
Explain the why behind the bill. "I think we owe you that transparency — we'll work on it." Clients who understand invoices trust them. Clients who don't, dispute them.
Validate
Ask about original goals, not just current tasks. "You specifically said one of the goals was to unblock content teams. How is this process improving?" Hold them to what success was supposed to look like.
Wrap
Explicit closure on open items. "If no questions on that, I think we've wrapped up all the topics I wanted to discuss." Don't let a delivery call end with lingering ambiguity.
Internal calls
Proposal / Strategy Review (Internal)
Internal
Orient
Force the narrative first — every time. "Who are they, what do they do, what do they want, how did we get here." Even if you know the account. This ensures the team owns the story before they walk into the meeting.
Challenge
Push on what the client will experience. "What's the typical engagement that they have?" "Why are we proposing this?" If the team can't articulate the client's experience, the proposal isn't ready.
Sharpen
Find the most important part. "I think the most important part of this proposal is…" Name it. If it's buried on slide 9, move it. Clients read with partial attention.
Decide
Leave the review with a clear next action. "Let's put that in black and white — let's look at the flow." Meetings that end with a list of outstanding questions don't advance deals.
Coach
Note what to develop, not just what to fix. "I know I'll ask very specific questions on the call — that's why I want you on it alone sometimes." Development is intentional, not accidental.
"Now that you're live, always happy — not only at the time of the launch. You guys specifically said one of the goals was to unblock content teams. How is this process improving?"
— Internal strategy call
Internal Escalation & Team Recovery
Internal
Contain
Stop the spiral before it starts. When a client problem surfaces internally, the first instinct is to explain, defend, or assign fault. Shut all three down. "Before we talk about whose it is — what actually happened? What do we know for certain right now?" Facts before positions. Clarity before emotion. The team that can't state the facts plainly in the internal room will not be able to state them plainly to the client.
Draw the line
Name precisely what is yours and what isn't — before the client names it for you. "We are responsible for this part. This part is a third-party issue. This part we need to investigate." This is not about avoiding accountability — it is about accurate accountability. A team without this clarity will either over-own or under-own. The internal room is where you agree on the line. The client call is not.
Translate
Technical truth is not client communication. If the system failed because a third-party ERP pushed malformed data, the team knows that — but the client sees a broken platform. The internal work is building the bridge: how do you explain what happened in a way that is accurate, fair, and doesn't read as fingerpointing? Find the analogy before the call. "The system is like a diesel engine — it runs fine. The problem is someone put petrol in it." Agree on that language in the room. Don't improvise it in front of the client.
Own cleanly
If there's a genuine mistake on your side, name it without qualification. "We didn't catch this before go-live — that's on us. As soon as we caught it, we fixed it the same day." The apology and the mitigation are two separate sentences. Combined — "we made a mistake but..." — they read as defensiveness. Separated, they read as accountability. Take the part that is yours. Don't take the part that isn't.
Agree the narrative
Before anyone speaks to the client, the team agrees on one version. Not the internal version — the client-facing version. What the situation is. What caused it. What is being done. What comes next. One voice is a non-negotiable output of this call. "Before we close — can we each say the one-line version of what we're going to tell the client? Let's make sure it's the same sentence."
Name next steps
The call ends with specific actions, not a feeling of alignment. Who sends the client update? What does it say, exactly? When? Who joins the client call and in what role? What is the one thing the client needs to hear first, and who says it? The team that leaves with "we'll figure it out" will not figure it out. Names, dates, and formats.
"We didn't catch it before go-live — that's on us. As soon as we caught it, we fixed it the same day. The rest is coming from third parties. But we can't just say that. We need to explain it in a way that doesn't look like we're pointing fingers."
— Internal SWOT call, platform stability escalation
Section 4
Reflection Exercises
Exercises for yourself, for 1:1s with your team, or as onboarding material for anyone new to client-facing work. Your answers are saved locally in your browser — use Export / Import on the Home tab to back up or share them.
For yourself — after a call
Did the call follow the Safety → Context → Decision arc?
Post-call
Rate each phase: did it happen, and how well?
Safety (rapport, warmth)
SkippedStrong
Context (shared understanding of the situation)
SkippedStrong
Decision (named outcome, action taken)
SkippedStrong
What did you learn about their business that you didn't know before?
Post-call
Did the call end with a specific named action and owner?
Post-call
A specific next step was named out loud (not just implied)
An owner was named (a person, not "we")
A date or timeframe was agreed
It was booked on the calendar before the call ended
Research & references
Psychology — Commitment and consistency — Cialdini
Robert Cialdini's research (1984) identifies commitment and consistency as one of the most powerful drivers of human decision-making. Once a person has made a small commitment, they are psychologically motivated to remain consistent with that commitment in subsequent decisions. In sales terms: a signed phase one is not just revenue — it is a psychological commitment that makes phases two and three dramatically more likely. The client who has said yes to something small is far more likely to say yes to something larger, because doing so is consistent with who they have declared themselves to be.
Cialdini, R. (1984). Influence: The Psychology of Persuasion. Harper Business.
Technical playbook — Phase-Gate Process — Robert Cooper / PMI
The phase-gate methodology — formalised by Robert Cooper and adopted across engineering, product development, and professional services — divides complex initiatives into discrete stages separated by decision points (gates). The PMI's (Project Management Institute) PMBOK research found that phase-gate processes reduce project uncertainty and cycle time, enhance cross-functional commitment, and make large engagements manageable by breaking commitment into sequential, reviewable decisions. Cooper's research showed that killing weak projects early at gates reduces development costs by 25–30%.
Cooper, R. (Stage-Gate International). / Project Management Institute — PMBOK. / Wikipedia: Phase-gate process.
Technical playbook — Agile methodology and sprint-based delivery
The Agile methodology — now dominant in software delivery — is built on the same logic: deliver in increments, review at each increment, adjust before committing to the next. The Scaled Agile Framework (SAFe) formalises this through Program Increment milestones creating structured decision points between delivery phases. The commercial implication is identical to phase-gating in sales: smaller commitments at each stage reduce perceived risk, which reduces resistance to starting, which makes the full project more likely to happen than a single large commitment would have been.
Agile Alliance (2001). Agile Manifesto. / Scaled Agile Framework (SAFe). / Planisware: What Is Stage-Gate Project Management?
For your team — in 1:1s or group reviews
The narrative test: explain this account in 3 sentences
Team exercise
Before any proposal review, have the team member complete this without notes. Then check: do the sentences describe the client's business problem — or your company's solution?
The client experience test: walk me through what the client sees
Team exercise
Ask this before any external call or proposal. If they describe what the team built — prompt them again. The answer should describe what the client will see, feel, and decide.
What's the most important part — and is it visible?
Proposal review
Name the single most important thing in this proposal or presentation. Then check: is it in the first third? Is it named explicitly? Or is it buried?
For new team members — building the mental model
What's the difference between rapport and small talk?
Onboarding
The best salespeople open every external call with genuine warmth — but it serves a structural purpose, not a social one. Reflect on the difference, then write your answer.
Rapport reduces the stakes before you raise the challenge. Without it, the person across the table is still in evaluation mode — they're deciding whether to trust you, not listening to what you're saying. Two minutes of genuine warmth buys you the next hour of honest conversation.
— The Trust Sequence
Why should you always ask yourself "who are they, what do they want" — even when you already know?
Onboarding
Before any internal review or client call, this question resets your thinking. Who actually benefits from asking it out loud, and why?
It's not for you — you already know the facts. It's to test whether you've synthesised them into a story. If you can't explain it in three sentences without notes, you're not ready to walk into that room. Knowing the account and owning the narrative are different things.
— The Trust Sequence
Pre-call checklist — external calls
Preparation
I know who is on the call and what their role is
I can explain in one sentence what this client needs from us
I know what a successful outcome for this call looks like
I know what next step I want to propose at the end
I have a relevant client story or analogy ready if needed
I have a genuine opening line that isn't about business
0 of 6 complete
Your answers are private
Everything you write here is saved automatically in this browser — nobody else can see it. If you clear your browser data, switch devices, or use a different browser, your answers will be lost unless you download a backup first. Keep a copy somewhere safe and restore it any time.