How do you apply the 11 steps of SNAP Selling by Jill Konrath to a complex B2B deal in 2027?

A deal that stalls for reasons no forecast call catches

Picture a mid-market revenue team selling a $180K–$240K annual platform into a 900-person logistics company. The champion is a VP of Operations. Discovery went well. There's a signed mutual action plan. The forecast says 70% and the close date has slipped twice. Nothing is technically wrong — no competitor displaced you, no budget got cut, security review passed. The deal simply does not move.

This is the exact failure mode Konrath wrote SNAP Selling to describe, and it is worth being precise about what her book actually claims, because the framework gets misquoted constantly. SNAP Selling, published in 2010, is built on a premise about buyer psychology: the people you sell to are "frazzled." They are overwhelmed, interrupted every few minutes, managing more scope than the role was designed for, and defaulting to the safest available choice — which is almost always doing nothing. Konrath's argument is that sellers lose not to competitors but to the status quo, to indecision, and to the buyer's own cognitive load. Everything in the framework is a response to that.

The "11 steps" phrasing that circulates online is a repackaging of the book's actual architecture, which has two interlocking parts. The first part is the four SNAP Rules: keep it Simple, be iNvaluable, always Align, raise Priorities. The second is the three decisions a frazzled buyer makes sequentially — Konrath calls them the three decisions and describes them as a funnel the seller must pass through in order: Decision 1: Allow Access, Decision 2: Initiate Change, Decision 3: Select Resources. Multiply four rules across three decisions and you get the practical checklist most people mean when they say "11 steps." Rather than argue about the count, the honest way to apply Konrath's work to a complex deal is to run all four rules deliberately at each of the three decision gates, and treat the resulting matrix as your operating checklist.

Back to the logistics deal. Run that matrix and the stall becomes legible. Access was granted — Decision 1 cleared. But Decision 2, Initiate Change, was never actually won. The VP of Operations personally believes change is needed. Nobody above them has decided that the pain of the current process exceeds the pain of switching. The seller has been running Decision 3 activities — feature comparisons, reference calls, pricing negotiation — against a buying group that is still parked at Decision 2. That mismatch is invisible on a stage-based pipeline report, because CRM stages track *seller* activity, not *buyer* decisions. The forecast says late-stage. The buyer is early-stage. The deal dies at 70%.

Adjacent to this, the same diagnostic works on renewals and expansions, which is where a lot of 2027 revenue teams spend most of their motion. An expansion into a second business unit is a fresh Decision 1 and Decision 2 with a new set of humans, even though your CRM treats it as an existing-customer upsell with a warm relationship. Sellers who skip straight to Decision 3 on expansions — because the logo is already closed — see the same unexplained stalls.

How the mechanism actually works

The mechanism is friction reduction against a specific decision gate. Each SNAP rule is a lever, and each lever does different work depending on which decision the buyer is currently making.

Simple at Decision 1 means your outreach can be processed in under ten seconds. At Decision 2 it means the business case fits on one page and does not require a spreadsheet tutorial. At Decision 3 it means implementation is described in weeks and named owners, not in an architecture diagram. Konrath's point is that complexity is a cost the buyer pays, and every unit of complexity you add increases the odds they choose the simplest option available — which is nothing. In practice this means killing the 40-slide deck, cutting your proposal from 22 pages to 6, and replacing "here's our platform" with "here are the three things that change on Monday."

iNvaluable means the buyer would take your call even if you had nothing to sell. At Decision 1 that's a specific insight about their operation, not a case study. At Decision 2 it's a diagnostic frame that helps them size their own problem. At Decision 3 it's honest guidance about where you're a poor fit. The test is unforgiving: if you removed your product from the conversation, would the buyer still want the meeting? For most sellers the answer is no, and that's why access gets revoked after one call.

Align means everything you say maps to something the buyer already cares about — their stated objectives, their metrics, the language in their own board deck. Misalignment isn't just irrelevance; it's an active tax, because the buyer has to translate your framing into theirs before they can act on it. At Decision 2 this is where most complex deals break: the champion's pain is operational, the economic buyer's objective is financial, and nobody translated between them.

Priorities is the rule that actually unsticks stalled deals. Konrath's claim is that buyers don't reject you — they deprioritize you. A deal that is #7 on a VP's list will never close, regardless of how good the fit is. Raising priority means connecting your outcome to something already funded, already scheduled, or already politically hot: a compliance deadline, a board commitment, a reorganization, an integration after an acquisition.

mermaid flowchart LR subgraph Inspect["Qualification layer"] M["MEDDPICC<br/>metrics, econ buyer,<br/>decision criteria, pain"] end subgraph Sequence["Sequencing layer"] S1["SNAP Decision 1<br/>Allow Access"] S2["SNAP Decision 2<br/>Initiate Change"] S3["SNAP Decision 3<br/>Select Resources"] S1 --> S2 --> S3 end subgraph Deliver["Delivery layer"] C["Challenger teach/tailor"] J["JOLT: reduce indecision<br/>de-risk the choice"] end M -->|"tells you what is missing"| Sequence C --> S1 C --> S2 J --> S2 J --> S3 Sequence -->|"tells you what to do next"| Out["Next best action<br/>per stakeholder"] </parameter>

The organizational cost. Adopting this well means changing forecast calls, CRM fields, enablement content, and manager coaching language simultaneously. Teams that adopt only the vocabulary — reps saying "we need to raise priorities" in pipeline reviews without changing a single artifact — get nothing. The minimum viable adoption is: one new CRM field for buyer decision, one new field for priority trigger and date, a rewritten one-page business case template, and a manager coaching question set that asks about buyer decisions rather than rep activities. Below that threshold, don't bother.

Where it fits poorly. Transactional, high-velocity, product-led motions with a single buyer and a credit card don't have three distinguishable decisions — they collapse into one. Applying the full apparatus there adds overhead with no return. Similarly, in a formal RFP where procurement has already committed to buying something, Decision 2 is pre-won by someone else, and your entire game is Decision 3 differentiation. Knowing which world you're in prevents a lot of misapplied effort.

Common pitfalls and how to avoid them

Treating the four rules as a script. The most common failure is reps memorizing "Simple, iNvaluable, Align, Priorities" as talk-track vocabulary and changing nothing about their artifacts. The rules are constraints on what you produce, not phrases to say. Audit the outputs: pull ten recent proposals and count pages; pull twenty outbound emails and count how many contain a fact that could only be true of that specific account. That audit tells you whether the framework is real in your org or ceremonial.

Confusing champion enthusiasm with Decision 2. A champion saying "we absolutely need this" is a Decision 2 signal from one person. The organization has not decided anything until someone with budget authority has said the current state is unacceptable. The diagnostic question — ask it directly — is: "If this project didn't happen this year, what would the consequence be, and who would feel it?" A vague answer means Decision 2 is unwon. Get comfortable with the silence after that question.

Manufacturing urgency instead of finding priority. Raising priorities does not mean discount deadlines or end-of-quarter pressure. Konrath's version is finding a priority that already exists and connecting to it. Artificial urgency is a Decision 3 tactic applied to a Decision 2 problem, and sophisticated buyers read it as weakness. If you can't name a real, dated, externally verifiable trigger, you haven't raised priority — you've raised your own anxiety.

Simplifying the wrong thing. Sellers often simplify the pitch while leaving the buying process complex — a 14-field order form, three separate contracts, a procurement portal, an unclear implementation timeline. The buyer's experienced complexity is dominated by process friction, not slide count. Map the actual steps between "yes" and "signed" and count them. If there are more than five, that's where your Simple work belongs. Removing one approval step from your own order process often does more than rewriting a deck.

Ignoring the anti-champion. Every complex deal has someone whose life gets harder if you win — the person who built the internal tool you'd replace, the manager whose headcount justification depends on the current process. Align means aligning with the buying group, including the people who oppose you. You cannot align with someone you've never spoken to. Find them early, name their objection out loud before they do, and give them something in the outcome.

Running the framework only at the top of the funnel. SNAP's rules are usually applied to prospecting and abandoned after the first meeting. But the Simple rule matters most during legal review, and Priorities matters most in the two weeks before a slipped close date. Build the four-rule check into your late-stage deal reviews, not just your outbound enablement.

Failing to re-run the sequence after a stakeholder change. Reorganizations, new executives, and acquisitions reset the decision funnel. A new CFO has not granted access, has not decided to change, and has not selected resources — regardless of the eight months of work behind your opportunity. When a key stakeholder changes, the honest move is to reset the deal to Decision 1 in your own tracking and re-earn each gate. Teams that don't do this carry phantom pipeline for a quarter and then take a surprise hit.

Over-instrumenting. The counter-pitfall: adding fifteen fields, three scorecards, and a weekly SNAP audit. Two fields and one coaching question outperform an elaborate system nobody fills in accurately. Instrument the minimum and let the behavior change do the work.

Related questions

Are there literally 11 steps in SNAP Selling?

Not as Konrath numbered them. The book presents four SNAP rules and three buyer decisions. The "11 steps" framing is a secondary repackaging that circulates online. Applying four rules across three decisions gives you the same practical checklist without misattributing a step count to the book.

Does SNAP Selling still work with AI-assisted buying research in 2027?

Yes, and arguably more so. Buyers arrive with more self-serve research, which shifts the seller's value away from information delivery and toward decision facilitation — exactly what Decision 2 addresses. What breaks is generic personalization, because AI-generated outreach has made buyers far more sensitive to it.

How do you combine SNAP with MEDDPICC?

Use MEDDPICC as the data model — what you must know and record — and SNAP's three decisions as the sequencing layer that dictates the next action. MEDDPICC tells you the economic buyer is unidentified; SNAP tells you that means Decision 2 is unwinnable until you find them.

What's the fastest signal that a deal is stuck at Decision 2?

The buyer engages willingly but nothing external ever changes — no calendar holds with new people, no budget line, no internal document you're shown. Activity without organizational commitment is the signature. Pleasant meetings that generate no artifacts are the tell.

Does this apply to renewals and expansions?

Yes. An expansion into a new business unit is a fresh Decision 1 and Decision 2 with new humans, even though the CRM calls it an upsell on an existing account. Skipping to Decision 3 because the logo is closed is a common source of surprise churn.

FAQ

What are the four SNAP rules, exactly?

Keep it Simple, be iNvaluable, always Align, raise Priorities. Simple means reducing the effort a buyer spends understanding and acting. iNvaluable means being worth the meeting independent of your product. Align means mapping to objectives the buyer already holds. Priorities means connecting to something already funded, scheduled, or politically urgent. Konrath frames all four as responses to buyer overwhelm rather than as persuasion techniques.

What are the three decisions and why does the order matter?

Allow Access, Initiate Change, Select Resources. The order matters because they're strictly sequential — a buyer who hasn't decided to change cannot meaningfully evaluate vendors. Most stalled complex deals are running Decision 3 activity against a buying group parked at Decision 2, which is why feature comparisons and discounts fail to move them.

Is SNAP Selling outdated given it was published in 2010?

The tactical surface has aged — channels, cadences, and research tooling all changed. The underlying premise has aged well: buyer attention is scarcer than ever, buying groups have grown, and no-decision remains a dominant loss category. Treat the four rules and three decisions as durable and rebuild the tactics for current channels.

How do you apply the Priorities rule when the buyer has no deadline?

Stop looking inside your deal and look at the company's public commitments — earnings calls, annual reports, press releases, regulatory filings, announced acquisitions, new executive mandates. A priority you connect to must already exist and be owned by someone. If you genuinely can't find one, the honest classification is that the deal is unprioritized, and it should not carry a near-term close date.

Can a small team apply this without a formal enablement function?

Yes, and the minimum version is small: add two CRM fields (current buyer decision, priority trigger with date), cut your executive-facing proposal to a single page, and change one question in your deal reviews from "what's the next step?" to "what is the buyer currently deciding?" Those three changes capture most of the value.

How does this interact with a formal RFP process?

An RFP means someone already won Decision 2 for you — usually a competitor who shaped the requirements, or an internal mandate. Your work is almost entirely Decision 3: differentiation, risk removal, and simplicity of implementation. If you're responding to an RFP you didn't influence, apply the framework backward and ask whether you should participate at all.

Sources

• https://www.jillkonrath.com/
• https://en.wikipedia.org/wiki/Jill_Konrath
• https://hbr.org/2017/03/the-new-sales-imperative
• https://hbr.org/2015/03/making-the-consensus-sale
• https://www.gartner.com/en/sales/insights/b2b-buying-journey
• https://www.mheducation.com/
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://www.forrester.com/blogs/category/b2b-sales/
• https://hbr.org/2012/07/the-end-of-solution-sales

Related on PULSE

• How do you run MEDDPICC on a deal that's already late-stage?
• What actually causes no-decision losses in complex B2B deals?
• How do you multi-thread into a buying group without going around your champion?
• How do you build a one-page business case an executive will actually read?
• What's the difference between manufactured urgency and a real priority trigger?
• How do you reset a deal when the economic buyer changes mid-cycle?