Was this newsletter forwarded to you? Sign up to get it in your inbox.
The proposal nobody turned down
A proposal that goes unanswered is not a polite refusal. It is a client who cannot carry the risk of being wrong, and the reflex to double down on your argument backfires in the large majority of measured cases.
We named this problem badly, and the wrong name dictates the wrong response. We say a proposal that went unanswered was lost, as though somebody decided. Nobody decided, and that is exactly what makes it so hard to recover: there is no objection to handle, only a client who cannot carry the weight of being wrong. This edition is about what you do during that silence, because it is, I think, the only variable still yours.
Francis Beaulieu
Why this matters to you now
Matthew Dixon and Ted McKenna published, in the Harvard Business Review, a finding drawn from more than 2.5 million recorded sales conversations. Between 40% and 60% of deals are lost to customers who express their intent to purchase and then fail to act. Read that twice. Those clients said yes. They simply did nothing afterward.
The detail that changes what you should do is in the breakdown, which the authors published on their own site. Of the deals lost to no decision, 44% were lost to a preference for the status quo, and the majority, 56%, to indecision stemming from risk or fear of failure. Those are two different illnesses with one symptom. The first has had a name for a long time: William Samuelson and Richard Zeckhauser documented status quo bias back in 1988, the measurable preference for the option that changes nothing. Against that one, demonstrating the value of change works: your client does not see the point of moving, so you show them. Against the fear of being wrong, that same move works against you, because you are raising the stakes of a decision your client already finds too heavy to lift. The same authors measured that doubling down on the case against the status quo backfired 84% of the time. What they propose instead comes down to four moves, which they compress into the acronym JOLT: judge the indecision rather than assume it, offer a recommendation instead of a catalogue, limit the exploration you encourage yourself, and take risk off the table. They do not state the base of that percentage, and I will not invent one for them; take the direction, which is unambiguous.
We have touched this research from another side already, in edition #31 on the delay your client buys, where a short timeline makes the decision less irreversible at the moment it gets made. That was speed. This is structure, and it is a separate subject: a slow mandate can be easy to approve, and a fast one can be terrifying.
There is a mechanical reason for this, and it has nothing to do with you. During those weeks of silence your proposal is not sleeping in an inbox: it is circulating. It gets forwarded to someone who was not in your meeting, summarized in two sentences by an intermediary, placed on an agenda where it arrives as item nine. Every hop strips context from it and adds readers who carry none of the project's upside but would carry a share of its failure. Your argument does not travel. What travels is the amount you are asking for and the name of whoever would have signed.
It is late October. Edition #32 on the budget written without you showed that the January window closes in November. The proposals you send this week decide January, and the ones that go quiet will do it over the holidays, when no committee sits and your file has nobody in the room to defend it. Stop pleading your case. Make being wrong about it cost less.
Pricing: the price of an exit
The move: write an exit after the first phase into your price, instead of a discount on the total.
Why it works: of the four levers Dixon and McKenna draw from their data, the last is to take risk off the table. A discount and an exit do not act on the same quantity. The discount lowers the cost of BUYING. The exit lowers the cost of BEING WRONG. Those two do not weigh the same: in Thinking, Fast and Slow, Daniel Kahneman sets out how a loss counts for more than a gain of the same size. When your client hesitates, it is almost never the first number holding them back, it is the second, and the second appears nowhere in your proposal. Cut the mandate so the first slice stands on its own: a diagnostic whose report keeps its value even if nothing follows, a pilot whose results are useful internally, a scoping exercise the client could execute with their own team. That is the whole thesis of edition #28 on the diagnostic you give away, and the exit gives it its strongest reason to exist: a slice that cannot stand on its own cannot be walked away from. Then write it down in plain language: at the end of that slice, they decide, with no justification required.
The objection lands within thirty seconds: if people leave at phase 1, I convert more and collect less. That is exactly right, and it is the price. The trade turns positive as soon as the higher signature rate covers the phase 2s you lose, which, with a phase 1 at a quarter of the mandate, happens quickly. Run it on your numbers rather than mine, and run it again after six mandates.
The trap: the exit that is not one. A sixty-day termination notice on a three-month mandate is not a door, it is a polite lock. Same for the satisfaction clause that leaves the definition of satisfied to your judgment. The test is simple: if your client has to argue to get out, they have just inherited a second hard decision instead of one.
This week: take your standard offer and price the first phase as if it were the whole mandate, then ask what the client keeps if everything stops there. If the answer is nothing, that is not a phase, it is a deposit.
Sales and business development: the question that replaces the argument
The move: on the second unanswered follow-up, do not add a single argument. Ask a question about the cost of being wrong, not the cost of doing nothing.
Why now: this is the move the research condemns most clearly, and not just recently. Neil Rackham reached a neighbouring conclusion more than thirty years ago in SPIN Selling: the closing techniques that close a small sale work against you in large ones, where seller pressure raises buyer resistance. Two bodies of evidence three decades apart, the same verdict. Doubling down on the case against the status quo produced the opposite of the intended effect in the large majority of measured cases. And look at what you actually do when you follow up: a case study, a cost-of-inaction calculation, a deadline. All three tell your client the same thing, that not deciding would be a failure of nerve. To someone paralyzed by the fear of deciding badly, you have just added the fear of badly not-deciding. The first lever in the Dixon and McKenna framework is not a tactic, it is a diagnosis: judge whether you are facing a client who does not want to move or a client who is afraid. The question "what happens to you if this mandate does not deliver what we hope" separates the two in a minute. The first answers with a budget. The second answers with a name, often their own.
One caveat about the callout, and it holds for all of them: seven proposals do not make a law, and a rate moving from two in eight to five in seven is a direction, not a promise.
The trap: reading silence as an information deficit. It is the most flattering hypothesis available to us, because it makes us the solution. It is usually wrong, and it produces one attachment too many. If your client needed another argument, they would have asked for it: it is free and it commits them to nothing.
This week: pull the oldest unanswered proposal out of your files. Edition #8 on selling without selling would have had you write it as a demonstration; the follow-up has nothing left to demonstrate. Write one paragraph with no argument, no attachment and exactly one question. Send it.
Collaboration networks: the second name on the proposal
The move: name, in your proposal, the colleague you would put forward if you became unavailable, and say in the same sentence that the client would decide.
The mechanism: when a client buys a firm, they buy capacity. When they buy you, they buy a person, and that person can get sick, get absorbed by another client, or disappear. That risk is real, it is rarely spoken, and it presses on exactly the same fear as everything else in this edition: carrying responsibility for a failure. The difference is that here you can soften it in one sentence. A name, a one-line qualification, and the fact that you thought about it before anyone asked. You have just turned the structural weakness of being solo into a piece of reassurance, and you hired nobody. I have no measurement to offer on this one, unlike the rest of this edition. I give it for what it is: a line of reasoning, not a result.
The secondary benefit arrives faster than the first. To write that sentence you need a precise conversation with a colleague: what you do exactly, at what rate, for which kind of client. Most independents have never had it with anyone, and it produces referrals in both directions for years, for a simple reason: nobody refers someone whose mechanics they do not know.
The format: a reciprocal backup agreement, written in advance, fits on one page. Who steps in, on what rate terms, and the confidentiality rule that governs the handoff. What it cannot do, and this is the detail that makes it publishable: grant access to your files. Nearly all your contracts carry a confidentiality clause and often a ban on subcontracting, so the handoff stays conditional on the client's written consent, and the client is the one who would contract with your replacement. Write it that way: a backup announced as already settled between consultants worries more than it reassures. Pick someone who could genuinely take over your kind of mandate without going after your accounts.
This week: one conversation, with one person. Ask them to be that name and offer them the reverse in the same sentence, because a one-way agreement is a favour and favours expire. The one-page agreement comes later, and it deserves a lawyer's read.
Value creation: fewer options is not enough
The move: keep your options, but recommend one, in writing, over your own name.
Why it changes everything: a widespread shortcut has to go first. The idea that too much choice paralyzes is far more fragile than people think. Benjamin Scheibehenne, Rainer Greifeneder and Peter M. Todd pooled, in Can There Ever Be Too Many Options?, 63 conditions from 50 published and unpublished experiments, covering 5,036 participants: the mean effect of choice overload there is virtually zero, with considerable variance between studies, and the authors write that they could identify no sufficient conditions for producing it. In other words, cutting your three options down to one will fix nothing by itself, and anyone who advises it in the name of science is selling you a result that does not hold.
What paralyzes is not the number of options, it is the absence of a recommendation. Three options with no opinion is a transfer: you have just handed your client the work of arbitrating between scenarios you understand better than they do, and the sole responsibility for choosing wrong. The second lever in the Dixon and McKenna framework sits exactly here. Say what you would do. Not "all three are valid depending on your priorities," but "in your position I would take the second one, because your calendar constraint is tighter than your budget constraint." You are taking no choice away from your client. You are taking away the solitude. It is the same moment of authority edition #24 on the offer that bleeds you described: whoever frames the decision steers it.
Of everything in this edition, this is the cheapest move and, in my view, the most neglected. It requires no new pricing structure, no new agreement, no new conversation. Three sentences at the bottom of a page you have already written.
And treat that page as a deliverable, not a sales argument: it is the first piece of your judgment this client receives, and that is how they will read it.
The test: if your proposal can be read end to end without anyone learning what you yourself would do, it is not finished. Hand it to someone outside your practice and ask one thing: what do I recommend? If they hesitate, your client hesitated too.
This week: add a recommendation paragraph to the options page of the proposal you have in play. Name the option, give the reason, and say in which specific case another would be better. Three sentences will do.
AI: the committee that is not in the room
The move: ask a model who, around your stalled decision, carries the cost of failure. What it hands back is a list of questions, not a list of conclusions.
Why it works: your contact is almost never the one blocking. The one blocking is in the next room, has never spoken to you, carries a risk nobody asked them to accept, and has no way to ask you a question. You cannot interview them, but you can enumerate their position: what they answer for, to whom, and what stays attached to their name six months after a failed project. A model produces that list well, precisely because it has no stake in sparing your offer, where you have one, and a large one. The answer will not always be right. It will almost always be better aimed than your intuition, which drifts naturally toward the person who likes you.
Of the five exercises in the callout, the one that returns the most for the least effort is the third. Take a file that is already closed, paste the follow-ups you wrote at the time, cleaned, and ask the model to mark every sentence that argued against the client's inaction. Almost nobody thinks they are pleading until they have seen their own emails flagged that way.
The warning: a hypothesis leaves the model as a hypothesis and must enter the conversation as a question. The temptation will be to arrive at the meeting with the fear already named and the answer already prepared, to show you understood. That is still pleading, in a new suit, and your client will hear someone explaining their own fear back to them. Ask the question, let the silence do its work, and put nothing into it. The other precaution is the one in the callout, and it is not negotiable: nothing still under negotiation leaves your files.
This week: before your next follow-up call, list the roles around the decision and ask, for each, what it loses if the mandate fails. Bring the question, not the answer.
Like what you read? Get this in your inbox every Tuesday.
Free. No spam. Unsubscribe in one click.