"Sure, we can customize that" is the most expensive sentence in the deal
Over-customizing · complexity · solution fatigue · when to go back to simple and direct·4 moves · 4 diagrams
Push the consultative playbook far enough and it turns into its own opposite: the harder you work at "giving them a solution," the harder it gets for them to decide — and most deals really need you to remove two options and quote a price.
Diagnosis, customization, the integrated solution — earlier pieces covered how to use them well. This one is about how they go wrong: when the word "solution" starts killing deals. Four traps bite in order. One, over-customizing: every "we can change that" is free on signing day and the invoice arrives two years later. Two, complexity: one more option, one more bullet, and the close rate goes down, not up. Three, solution fatigue: "end-to-end integrated platform that empowers growth" is a phrase buyers auto-filter into noise. Four, mismatch: run a forty-minute discovery on someone who just asked for a price and you aren't being professional, you're being an obstacle.
MOVE 01
Customization is free the day you sign. The invoice arrives two years later.
Every customization you agree to costs you nothing, and costs nothing this month — it lands on delivery, on support, on the upgrade team, on whoever inherits the account two years out. So reps systematically over-customize. It isn't a character flaw, it's a structural one: the upside is immediate and yours, the cost is delayed and someone else's. Knowing that is the only way you get to install a brake.
The rep sees box one. The cost happens in the other three.
In the room
Situation: the buyer says "your approval flow doesn't match how we work — could you build us a version that does?"
✗ The reflex nod
"Sure, I'll get product to schedule it." — You think you're demonstrating flexibility. What you actually just did was sign an IOU on behalf of the delivery team with no price, no timeline, and nothing in the contract. And the customer will treat it as promised.
✓ Get the outcome first, state the cost second
"We can. But let me be straight about the cost first: a custom build doesn't ride the main upgrade path, so every release needs a separate re-fit and support responses run a notch slower. What you actually want is for managers to stop approving line by line, right? There's a batch-rule workaround in the standard product that gets about eighty percent of that — and it improves on its own next year. Want to try that first? If it really doesn't work, I'll quote and schedule the custom build separately."
Script · four questions before you say yes
1. Outcome, not spec: "What result is this change actually for?" — people describe the implementation they imagined, not the outcome they need.
2. Try the standard road: "Would this workaround with existing features get you eighty percent of it?"
3. Filter with price: "I'll quote and schedule this separately — are you willing to pay extra and wait extra for it?" Requests people will fund are usually real.
4. Count heads: "Has one customer asked for this, or ten?" One means customization. Ten means your roadmap has a hole.
Why it works · mechanism and evidence
Why it works
People don't measure "benefit now" and "cost later" with the same ruler: the further out it sits, the more the weight collapses. Layer an organizational mismatch on top — the cost doesn't even hit your team — and "sure, we can customize that" becomes a sentence with almost no friction behind it.
Hard evidence · discounting is hyperbolic, and the near term is systematically inflated: Ainslie (1975, Psychological Bulletin) and Kirby & Herrnstein (1995, Psychological Science) show that people discount delayed gains and costs on a hyperbolic rather than exponential curve — weights near the present are inflated absurdly, which is why preferences reverse over time (the commitment that looked cheap today is regretted when it comes due). Peer-reviewed, replicated across species and populations. Hard.
Hard evidence, with a caveat · immediate rewards are louder in the brain: McClure, Laibson, Loewenstein & Cohen (2004, Science) found stronger activation in the ventral striatum, medial prefrontal cortex (vmPFC) and posterior cingulate when an immediately available reward is on the table, while intertemporal comparison leans more on lateral prefrontal and posterior parietal regions. Flagged honestly: their "two systems" interpretation was challenged by Kable & Glimcher (2007, Nature Neuroscience), who showed a single valuation system with subjective discounting explains the same data. The phenomenon is rock solid; that particular mechanism story is contested. Cross-ref psychology / neuroscience.
Weaker · complexity costs rise faster than revenue: Gottfredson & Aspinall (2005, HBR) argue that product and process complexity carries non-linearly rising cost, with an "innovation limit" past which it destroys value. Management analysis plus consulting cases, not peer-reviewed — treat as directional, not law. But everyone who has worked in delivery recognizes the curve.
Edges: this is not "never customize." Some custom work is a genuine moat, and some customers are big enough to be worth changing for. The rule is that customization has to be run as a piece of business — priced separately, scheduled separately, written into the contract separately — rather than tossed in as a sweetener to get a signature. Custom work given away free is you spending other people's time to buy your own quota.
MOVE 02
Every extra selling point dilutes the strongest one you have
Adding feels risk-free: one more option, one more bullet, one more slide — worst case it just goes unused. Wrong. Extra information is not neutral. Impressions behave more like an average than a sum, so a hard piece of evidence sitting next to three mediocre ones doesn't read as four points, it reads as one diluted point. And the more options there are, the more likely the winner is "not yet."
Impressions get averaged, not added
Script · four cuts to a proposal
1. Down to one option: one recommendation (two at most, and they must differ obviously on a single axis — "expensive but fast" versus "cheap but slow," not three near-identical tiers).
2. Run the deletion test: for each claim ask "if I remove this, does the decision change?" No → cut it.
3. Sink the weak proof: strong evidence stands alone; everything soft moves to an appendix. Never side by side.
4. Dare to recommend: "We can do all of these, but given what you just told me I'd only recommend this one, because…" — range shown, decision converged, one sentence.
Why it works · mechanism and evidence
Why it works
Two independent mechanisms are billing you at once. First, mediocre or irrelevant information dilutes the force of diagnostic information. Second, the harder the conflict between options, the more people defer — and deferral doesn't go to a competitor, it goes to doing nothing.
Hard evidence · the dilution effect: Nisbett, Zukier & Lemley (1981, Cognitive Psychology) — adding neutral, non-diagnostic information alongside genuinely diagnostic information pulls judgments significantly back toward the middle; the strong signal gets watered down. Same direction: Anderson (1965, JPSP) found that adding "moderately positive" traits to a description lowers the overall evaluation. The brain averages; it doesn't add. Peer-reviewed, well replicated. Hard.
Hard evidence · conflict produces deferral and inaction: Tversky & Shafir (1992, Psychological Science) showed that when two options each have a clear advantage and the trade-off is hard, people are markedly more likely to defer the decision or choose neither — even when both beat the status quo. That is exactly what three parallel proposals produce. Classic, repeatedly replicated. Hard.
A famous study to discount · the jam experiment: Iyengar & Lepper (2000, JPSP) ran the supermarket tasting study (24 jams drew more passers-by, but the 6-jam table converted far better) and it has been cited for two decades — but it must be flagged. The meta-analysis by Scheibehenne, Greifeneder & Todd (2010, JCR) found the average choice-overload effect is close to zero; Chernev, Böckenholt & Goodman (2015, JCP) narrowed it further: the effect is reliable only under specific conditions — complex options, unclear preferences, time pressure. A B2B proposal happens to hit all three, so the direction holds here; just don't recite "24 versus 6" as a universal law.
Edges: subtraction is not hiding information. The detail still has to exist — it belongs in the appendix and in the answer when they ask, not stacked across the decision page. One counter-case: when the buyer's core worry is literally "can you cover all our scenarios," breadth is the hard evidence. Then list it — on a capabilities annex, not mixed into the recommendation page.
MOVE 03
"End-to-end integrated solution" now carries exactly zero information
solution fatiguesignal costconcreteness
The principle in one line
A sentence carries information in proportion to how many people couldn't say it. When every vendor's homepage promises an end-to-end platform that empowers growth, the phrase's signal strength is zero — buyers filed it under noise years ago. Only two kinds of sentence get through the filter: results concrete enough to be falsified, and a plain statement of what you don't do.
The filter inside the buyer's ear
In the room
Situation: thirty seconds of introduction, across from the finance lead at a retail company.
✗ A stack of generic words
"We're an industry-leading provider of end-to-end integrated solutions, helping enterprises achieve digital transformation while reducing cost and increasing efficiency." — They've heard every word of that eight times this month. The only thing the sentence accomplishes is confirming "here's another one," after which they start thinking about their next meeting.
✓ Concrete, plus a deliberate exclusion
"We do one thing: automate the dirtiest part of your reconciliation — multi-channel transactions that don't match what's in the ERP. Last month a retailer with about your store count went from a five-day close to a day and a half. We don't do cross-border settlement or tax planning; you'd need someone else for that."
Script · three steps to wash out the slogans
1. The competitor test: line by line, ask "could my biggest competitor lift this verbatim?" If yes, strike it.
2. Trade adjectives for hard currency: every adjective becomes a number, a customer's name, or a specific scene. "Efficient" → "a five-day close down to a day and a half."
3. Add an exclusion: "We don't do ___." It's the cheapest credibility signal available, because people who are bluffing can't bring themselves to say it.
Why it works · mechanism and evidence
Why it works
A signal is only credible when it is more expensive for an impostor. Zero-cost adjectives are available to everyone, so they transmit nothing. And when the listener is motivated to process carefully — which spending money and carrying accountability guarantees — empty rhetoric isn't merely useless, it files you under "marketing copy."
Hard evidence · a signal needs differential cost: Spence (1973, Quarterly Journal of Economics) — a signal separates high from low quality only if it costs the low-quality party more. That work won a Nobel in economics, and it is the formal version of "anything anyone can say for free carries no information." It also explains why self-limiting statements like "we don't do X" raise credibility: a bluffer won't pay that cost.
Hard evidence · peripheral cues stop working under motivation: Petty & Cacioppo (1986), the Elaboration Likelihood Model — when an audience is both motivated and able to process carefully they take the "central route," where only concrete, checkable arguments shift attitudes, and those shifts last longer; polished slogans are peripheral cues that only work on people who aren't paying attention. B2B purchasing is almost always high-motivation. Peer-reviewed. Hard. Cross-ref psychology.
Hard evidence · concrete material is processed faster and remembered better: the dual-coding work beginning with Paivio, Yuille & Madigan (1968, JEP Monograph) repeatedly shows concrete words are processed faster and recalled more reliably than abstract ones. The sentence your champion has to repeat in a meeting must be concrete — an abstract slogan evaporates in their mouth (how to arm a champion is covered in the value selling piece).
Industry data, discount it · buyers already did the research: Adamson, Dixon & Toman (2012, HBR), citing CEB survey work, report that B2B buyers are on average about 57% through their purchase process before contacting a vendor. Consulting-firm survey, definitions shift by year, not peer-reviewed — order-of-magnitude reference only. But the direction is solid: the generic part of your introduction, they read before you opened your mouth.
Edges: concrete doesn't mean burying someone in technical specs. "99.99% SLA, active-active distributed architecture" is hard currency to a CTO and still noise to a finance lead — concreteness is relative to the listener, so get concrete about their ledger, their process, their day. And an exclusion only works if you genuinely made that trade-off; faking "we don't do that" to sound credible falls apart on the first follow-up question.
MOVE 04
Most deals don't need a solution. They need you to shut up and quote.
match the situationtransactional vs consultativefriction cost
The principle in one line
Diagnosis has a price: it spends the buyer's time, stretches the cycle, and transmits a piece of meta-information — "buying from these people is a project." When the buyer already knows what they want, the requirement is standard, and the amount is small enough for one person to sign, every extra round of questions costs you points. Consultative isn't a posture, it's an investment; size it to the complexity of the decision, not to your professional pride.
Pick the play by "how clear are they" and "how heavy is the decision"
In the room
Situation: a buyer messages you directly — "how much is the basic plan, and can you invoice us?"
✗ Reaching for the discovery process
"Before I quote, I'd like to understand your current workflow and main pain points — could we set up a 45-minute call?" — They wanted a number and a yes/no. You just converted a two-minute close into a piece of homework they can abandon at any moment. Most people abandon it.
✓ Answer first, leave one small hook
"Basic is $980 a year, we can invoice, and you can be live tomorrow. The only thing that might change the recommendation: do you need multiple locations connected? If so, that part is worth ten minutes. If not, take Basic — I'll send the link."
Script · three signals to shut up and quote
1. They open with price, lead time or contract terms — they're at the last step and you're trying to drag them back to the first.
2. They can state the exact spec, model or seat count — the requirement is standardized; discovery has no new information to find.
3. The amount is small enough for one person to sign — nobody else has to be convinced, so there's no internal selling to arm.
Two or more → quote, and compress the whole discovery into one question (the "multiple locations?" line above).
Why it works · mechanism and evidence
Why it works
Sales technique isn't good or bad in the absolute; it's matched to the situation. The same moves raise win rates on complex deals and lower them on simple ones, because the return on diagnosis comes from finding what the buyer doesn't know — and when they know it all, the return is zero while the cost still bills.
Large-sample industry research · technique effectiveness flips with deal size: Rackham's SPIN Selling (1988), built on field observation of roughly 35,000 sales calls, found that closed questions and classic closing techniques help in small transactions and actively reduce success in large complex ones. Discount it — not peer-reviewed, underlying method not fully published — but the sample is enormous and the direction has been confirmed repeatedly in practice. (How to use the question funnel itself is in the piece on asking better questions.)
Hard evidence · working memory has a hard ceiling: Sweller (1988, Cognitive Science), cognitive load theory — working memory is capacity-limited, and load unrelated to the goal (extraneous load) crowds out the resources available for the actual decision. Forty minutes of discovery bolted onto a simple purchase is exactly that kind of extraneous load. Peer-reviewed, widely replicated. Hard.
Hard evidence · less information sometimes judges better: Gigerenzer & Goldstein (1996, Psychological Review), the "less-is-more" effect — in particular environments, people with fewer cues judge more accurately, because irrelevant cues dilute the valid ones (same substrate as the previous section). Peer-reviewed, hard, but bounded: it is not a licence for "less information is always better."
Mechanism · the discovery itself is meta-information: ask ten questions of someone who just wants to buy a screwdriver and what they learn isn't "these people are thorough," it's "these people are a hassle" — your process complexity gets read as the complexity of working with you.
Edges: don't treat this as permission to coast. The genuinely dangerous box is "very clear, and clearly wrong" — they open by asking for A, and A won't solve their problem. The test: can they state what they want and also why they want it? If they can answer "why," quote. If they can only answer "what," it's worth one probing question — this is where the Challenger material earns its keep, but as a question, not a meeting.
Your Day 39 Action
Forty minutes. Install three brakes on a live deal.
1 (15 min) · Customization subtraction: take the deal you're working and list every "sure, we can change/add that" you've said out loud. Run each through the four questions (what outcome? does a standard workaround get eighty percent? willing to pay and wait separately? one asker or ten?). Prepare the wording to walk at least one of them back to standard.
2 (15 min) · Proposal subtraction: open the last proposal you sent. Count the options and the claims. Cut to one option (two at most, and obviously different on one axis), run the deletion test and keep the three strongest claims, move the rest to an appendix. Then say the recommendation sentence out loud.
3 (10 min) · Wash out the slogans: write your thirty-second introduction, strike every line a competitor could lift verbatim, swap each adjective for a number or a customer name, and end with "we don't do ___."
Boundary: this isn't an argument against consultative selling. It's an argument against running it on reflex. Diagnosis, customization and integrated solutions are good tools, and a tool's value depends on the occasion — skipping one when it's needed is laziness; forcing one when it isn't is performance. One test settles it: does this step make it easier for them to decide, or make me look more professional? When those conflict, pick the first.
Think It Through
1. The customer explicitly wants a custom feature and says no deal without it. Now what?
First separate the feature from the result it would produce — when people describe a requirement, what comes out of their mouth is usually the implementation they imagined. One question — "what is this change ultimately meant to solve?" — often turns "must be custom" into "a workaround with standard features is fine."
If it really is a hard requirement, then run it as a piece of business rather than tossing it in as a gift: priced separately, scheduled separately, written into the contract separately. Price is the cleanest filter there is — a request someone will fund and wait two extra months for is usually real; the one that evaporates the moment money is attached was a nice-to-have all along.
The worst outcome isn't losing the deal. It's agreeing for free, jumping the internal queue, slipping delivery, and still shipping something mediocre — at which point you've spent the money, spent the delivery team's trust, and lost the customer anyway. Better to say honestly today "we don't do that" than to trade a promise you can't keep for a signature. Daring not to sell is covered in the consultative selling piece.
2. If I only present one option, won't we look thin and inflexible?
That question fuses two different jobs. Keep them apart: capability is shown by what you've done (cases, customer names, numbers), and options are shown by what you recommend. A single sentence does both: "We can do all of these, but given what you just told me I'd only recommend this one, because…"
And from their side of the table, daring to recommend reads as more expert than laying out choices: a recommendation carries accountability, while three parallel proposals hand the risk back to them and quietly announce that you didn't understand their situation. Buyers can tell the difference.
When options genuinely are warranted, make them obviously different on one axis — "expensive but live in two weeks" against "cheaper but three months." That choice is easy to make. Three tiers that differ by a line or two of feature list are the kind that produce delay.
3. Our product actually is complex — a multi-module B2B platform. How can I possibly keep it simple?
The product is complex; the first conversation isn't. Separate the complexity of the product from the complexity of this decision. You don't need them to understand the whole platform at once — you need them to make the next decision, and the next decision is usually much smaller (run a pilot, bring finance to one call).
The move is a wedge: one scenario that hurts most, one module, one verifiable result. The rest of the capability surfaces naturally once they're aboard — and expansion is far easier to sell than the first purchase.
Also, "complex products require complex explanations" is mostly an illusion. Compressing it into one sentence is the mark of actually understanding it; being unable to keep it simple usually means you haven't worked out which part they need. A self-check: if you could leave your champion exactly one sentence to repeat in the meeting, which one? When you can't produce it, the problem isn't the product's complexity — it's that you haven't finished choosing.