How does *The New Strategic Selling* define the first step in qualifying an opportunity in 2027?

A deal that looked qualified and wasn't

A RevOps team runs a mid-market platform deal. The AE has a champion — a director of sales operations who loves the product, took three demos, and volunteered to "get this through procurement." The deal sits at 60% probability, $180,000 ACV, with a close date at the end of the quarter. Discovery notes are thorough: current stack, pain points, a rough ROI story, even a mutual timeline. By every field in the CRM, it is qualified.

Then the deal stalls for eleven weeks and dies in a "budget re-prioritization."

The post-mortem finds what the Miller Heiman framework would have surfaced in week one. The champion was a User Buyer — someone whose day-to-day work the system would change — with no budget authority and no discretionary release. The Economic Buyer, a VP of Revenue two levels up, was never met and had never heard the business case in his own words. A Technical Buyer in IT security had been quietly screening the vendor against a data-residency requirement the AE never learned about, and had already recommended against proceeding. There was no Coach — nobody inside the account who was actively helping the seller understand the account's internal politics and win.

This is the scenario *The New Strategic Selling* is built around, and it explains why the book puts Buying Influence identification first rather than making it a later step. Robert Miller, Stephen Heiman, and Tad Tuleja's argument is structural: a complex sale is one in which several people must give approval before it can proceed. If that is true, then the very first question of qualification is not "does this prospect have pain?" and not "is there budget?" — it is "who has to say yes, and have I met them?" Every other qualification question is downstream of that answer, because pain, budget, timeline, and authority all live in specific human beings and differ from one buying role to the next.

The scenario above generalizes. In the deal that died, each of the four roles existed and was occupied. The seller simply had not identified them. That is the distinction the book draws: the roles are always filled — a complex sale cannot happen without someone signing, someone using, someone vetting, and someone (ideally) helping — but they are only *qualified* when the seller can attach a name, a title, and a current attitude to each one.

How the Buying Influence step actually works

The mechanic is a role-based inventory, not a checklist of deal attributes. The book asks the seller to build a list of people for a specific Single Sales Objective — one particular product or solution, sold to one particular account, in one particular timeframe — and then to sort those people into four functional roles.

Economic Buyer. There is exactly one per sales objective. This is the person with the discretionary authority to release funds and, crucially, the authority to say yes when everyone else has said no. The Economic Buyer role is defined by *final approval*, not by title. In a $15,000 departmental deal, that may be a director. In a $2 million enterprise transformation, it may be a CFO or a committee acting as a single approval function. The role tends to rise as deal size, business risk, novelty, and organizational disruption rise. The book's test for correctly identifying the Economic Buyer is simple and unforgiving: can this person release the money, and can this person override a no from anyone else on the list?

User Buyers. There can be many. These are the people who will personally use the solution or supervise its use, and who judge it on the impact it will have on their own job performance. Their question is "will this work for me?" — a personal, operational question, not a financial one. User Buyer judgment is subjective by design and cannot be delegated: a User Buyer who believes the system will make their work harder is a real problem no ROI slide will fix.

Technical Buyers. Also many, and often invisible. These are gatekeepers who screen out on specifications: IT security, legal, procurement, compliance, sometimes a technical architect. They cannot give a final yes. They can and routinely do give a final no, by declaring that a requirement was not met. Their question is "does it meet the spec?" and their judgment is meant to be objective — measurable against a written standard.

Coach. The one role the seller develops rather than finds. A Coach can be inside the account, inside your own company, or outside both. Three conditions define a real Coach in the book's terms: you have credibility with them, they have credibility within the buying organization, and they want your solution to win because your success serves their own interests. The Coach's function is specific — they help you find and understand the other Buying Influences, and they tell you what you do not know about the account's internal reality.

Once the names are on the list, the book layers two judgments onto each name, and this is where the first step becomes genuinely diagnostic rather than clerical.

The first is receptivity to change — the book's four modes. *Growth* means the person sees a gap between current results and desired results and wants more; they are receptive. *Trouble* means something is broken and they need it fixed; also receptive, often urgently. *Even Keel* means results match expectations and no change is wanted; the sale is stalled unless you can surface a gap. *Overconfident* means the person believes results already exceed expectations; the book's guidance is blunt — do not sell into Overconfident, because reality has to correct it first.

The second is the win — the personal result each Buying Influence gets from a favorable business result. The book's Win-Results discipline separates *Results* (objective, measurable, corporate, the same for everyone in the role) from *Wins* (subjective, personal, different for every individual). A Result might be "cut quote turnaround from four days to four hours." The Win attached to that Result might be, for one person, credibility with a skeptical board; for another, getting out of a manual workflow they hate; for a third, a defensible case for headcount. Same Result, three different Wins. The book's position is that people buy for their own reasons, and that a sale where someone gets the Result but not a Win is unstable.

The output of the first step is therefore a grid: names, roles, mode, and win — with every blank cell treated as a defect. That is the deliverable, and it is what "qualified" means at this stage of the process.

Red Flags, Strengths, and how the step is scored

The book's scoring mechanism is the Red Flag / Strength pairing, and it is what converts the Buying Influence list from a note-taking exercise into a qualification gate.

A Red Flag is any area of missing or uncertain information, or any known negative. The book names four automatic Red Flags that fall directly out of the first step:

1. Missing information. Any Buying Influence you cannot name. If you have not identified the Economic Buyer, that is a Red Flag by definition, regardless of how well the rest of the deal is going.
2. Uncertainty about information. You have a name but you are guessing at the role, the mode, or the win. A guessed Economic Buyer is not better than a blank — it is worse, because it looks like coverage.
3. Uncontacted Buying Influences. You know the person exists and have never spoken with them. The book is explicit that an unmet Economic Buyer is one of the most common and most expensive Red Flags in complex selling, because that role is the only one that can release funds.
4. New players or reorganization. Someone entered the account, changed roles, or the buying organization restructured. Any of those invalidates prior coverage and re-opens the first step.

A Strength is the inverse: an area where the position is solid and can be leveraged — a Buying Influence in Growth or Trouble mode whose Win you understand and can serve.

The discipline is that every Red Flag must be paired with either an action that removes it or an explicit Strength that offsets it. Nothing is "noted." The book's Blue Sheet — the account-planning worksheet the methodology is organized around — exists to make this pairing mechanical rather than optional.

There is a useful and often-misread nuance here. Red Flags are not failures. The book treats them as the most valuable output of the analysis, because a Red Flag is a piece of information you now possess and can act on. The failure mode is a deal with *no* Red Flags on a page where the seller has not done the work — a clean sheet on an unexamined account is the most dangerous state in the methodology, not the safest.

Realistic numbers: coverage, cycle math, and what the ratios look like

Precise industry-wide statistics on Buying Influence coverage vary by source, segment, and definition, and should be treated skeptically. What is safe to work with are the structural counts the book itself describes and the arithmetic a RevOps team can run against its own CRM.

Role counts. Economic Buyer: exactly one per Single Sales Objective — this is definitional in the book, and if you have two, you have either two sales objectives or a misidentified role. User Buyers: unbounded, and in practice scaling with how many teams touch the workflow. Technical Buyers: unbounded, and typically underestimated because several of them (security review, legal, procurement, data privacy) never appear in a discovery call and only surface at contracting. Coaches: at least one, and the book explicitly permits more than one; multiple Coaches provide cross-checkable information.

A coverage ratio worth tracking. Define coverage as *(Buying Influences named and contacted) ÷ (Buying Influences named)*. Run it per open opportunity in a given stage. Two things reliably show up in that number. First, the denominator itself is diagnostic: an enterprise deal listing two Buying Influences is almost certainly under-mapped rather than genuinely simple. Second, the Economic Buyer contact flag deserves its own binary field, because averaging it into a percentage hides the single most consequential gap.

Deal-size correlation. The role level of the Economic Buyer generally tracks four variables: dollar amount, business risk, degree of organizational change required, and how novel the purchase is to that company. A renewal of an established tool at $40,000 may be signed by a director. The same $40,000 spent on a first-of-its-kind system that changes how three departments work may route to a VP or an executive committee, because the risk and disruption — not the dollars — set the approval altitude. Sellers who benchmark authority purely on ACV misjudge this constantly.

Cycle-time cost of a late-discovered Technical Buyer. This is where the arithmetic bites. A security review discovered at contracting typically adds a full review cycle to the deal — questionnaire, remediation or exception request, re-review. In practice that is weeks, not days, and it lands at the exact moment the forecast assumed a signature. A Technical Buyer identified in week one runs in parallel with the rest of the evaluation and costs nothing in elapsed time. Same work, same reviewer, radically different schedule impact. This is the strongest practical argument for putting the identification step first: it is not about thoroughness, it is about serialization. Work you discover late runs in series; work you discover early runs in parallel.

Mode distribution as a forecast input. Score each named Buying Influence as Growth, Trouble, Even Keel, or Overconfident. A deal where the Economic Buyer is Even Keel and only User Buyers are in Trouble is not a near-term deal, whatever the close date says — the person who can release funds does not perceive a gap. Conversely, an Economic Buyer in Trouble mode with a specific, articulated Result compresses timelines dramatically, sometimes past the seller's own expectations. Tracking mode against actual close outcomes for a quarter or two gives a team a calibration curve that is specific to their market and worth more than any generic probability table.

A practical qualification threshold. Many teams operationalize the first step as an explicit stage gate: an opportunity cannot advance past early-stage until (a) every role has at least one named person, (b) the Economic Buyer is named *and* has been contacted, (c) at least one Coach is identified and meets all three Coach conditions, and (d) each named person has a recorded mode and a hypothesized win. Deals that cannot clear that gate are not disqualified — they are flagged with the specific missing item as the next action. That distinction matters: the first step produces work, not verdicts.

Trade-offs against other qualification frameworks

*The New Strategic Selling*'s choice to lead with Buying Influences is a deliberate trade-off, and it is worth being honest about what it costs.

Against BANT. BANT (Budget, Authority, Need, Timeline) leads with budget and treats authority as a single attribute. Strategic Selling inverts this: it treats authority as a *distributed structure* with four distinct functions and makes budget a downstream consequence of Economic Buyer engagement. BANT is faster and works acceptably for transactional, single-signature purchases. It degrades badly in complex sales because "Authority: yes" collapses four roles into one checkbox and hides exactly the gaps that kill deals. The cost of the Strategic Selling approach is time — you cannot map four roles in a fifteen-minute call.

Against MEDDIC/MEDDPICC. These are the closest relatives, and there is genuine overlap: MEDDIC's Economic Buyer and Champion map roughly onto Strategic Selling's Economic Buyer and Coach, and MEDDPICC adds an explicit Paper Process that captures much of what Technical Buyers do. The difference is ordering and emphasis. MEDDIC typically leads with Metrics — quantified pain — and treats people as elements alongside it. Strategic Selling makes the people map the entry point and derives Results and Wins from it afterward. In practice many RevOps teams run both: MEDDIC as the CRM field structure, Strategic Selling's Blue Sheet as the account-planning workshop. They are complementary rather than competing, and the Win-Results distinction is the piece MEDDIC does not natively supply.

Against Challenger. Challenger is a *how you sell* framework — teach, tailor, take control — while Strategic Selling is a *who you sell to and where you stand* framework. Challenger's Mobilizer concept overlaps with Coach and Champion but is oriented toward driving consensus rather than mapping approval structure. They compose well: use the Buying Influence map to know whose win to tailor to, and Challenger technique to deliver the teaching.

Against SPIN Selling. SPIN operates at the call level — question sequencing within a single conversation. Strategic Selling operates at the account level across a full cycle. Neither replaces the other; a seller can run SPIN questioning inside a meeting with a User Buyer that the Blue Sheet told them to book.

The honest cost. Leading with Buying Influence identification is slower up front, it requires sellers to admit what they do not know, and it produces a document that managers can inspect — which some sellers resist for exactly that reason. On genuinely simple, single-signature transactions it is overhead. The decision rule is the book's own definition: if more than one person must approve before the sale can proceed, it is a complex sale and the first step applies. If one person can sign alone, it does not.

Pitfalls that break the first step

Mistaking a champion for the Economic Buyer. The most common and most expensive error, and the one in the opening scenario. Enthusiasm reads as authority. The corrective is the two-part test applied literally: can this person release funds, and can this person say yes after others have said no? Asked plainly — "if the security team objects, who makes the final call?" — the answer usually arrives in one sentence.

Treating a friendly contact as a Coach. Liking you is not coaching you. All three conditions must hold: your credibility with them, their credibility in the account, and their win tied to your success. A well-liked contact with no internal standing gives you comfortable meetings and bad information. Test a Coach by asking a question you already know the answer to; if the answer comes back wrong or vague, you have a friend, not a Coach.

Assuming roles from titles. Roles are functions, not job descriptions. A CFO is often the Economic Buyer and is sometimes a Technical Buyer screening on a compliance spec. A CTO may be a User Buyer. One person can hold two roles simultaneously — the book allows this explicitly — and the seller must handle both roles, not average them into one. The reverse error is equally common: assuming that because someone has an impressive title, they hold the Economic Buyer role for *this* objective.

Ignoring Technical Buyers because they cannot approve. A Technical Buyer's no is final in practice even though it is not an approval. Security questionnaires, data-residency requirements, procurement's approved-vendor lists, and legal's redline standards all kill deals that were "won" everywhere else. Surface these in the first pass and ask directly what specifications the solution will be measured against.

Letting the map go stale. Buying Influences change — people are promoted, leave, reorganize, or get reassigned mid-cycle. The book treats new players as an automatic Red Flag for a reason. A map built in month one and never revisited is a map of an organization that may no longer exist. Re-run the first step at every stage transition and after any announced reorganization.

Selling into Overconfident mode. When someone believes results already exceed expectations, no amount of evidence lands, and pushing typically hardens the position. The book's guidance is to wait for reality to intervene rather than to argue. Meanwhile, work the Buying Influences who are in Growth or Trouble mode, and be honest in the forecast about the blocked path.

Confusing Results with Wins. A seller who presents only corporate Results — cost savings, cycle-time reduction, revenue lift — is presenting the same case to every person on the list. The Result is the shared, measurable outcome. The Win is what that outcome does for one specific individual, and it differs person to person even within the same role. Deals that are technically justified and personally unmotivated stall in the "we're still evaluating" state indefinitely.

Filling the grid to satisfy a manager. Because the first step produces an inspectable artifact, it invites cosmetic compliance — names entered to clear a stage gate, modes guessed, wins copy-pasted. This is worse than an empty sheet, because it converts a Red Flag into false confidence. The corrective is to make "unknown" an acceptable and expected entry in pipeline reviews, and to review the *actions* attached to Red Flags rather than the completeness of the grid.

Applying the full apparatus to simple deals. Not every opportunity is a complex sale. Forcing a Blue Sheet onto a single-signer renewal wastes selling time and breeds cynicism about the methodology. Apply the book's own gate: more than one required approval, or it does not qualify as complex.

Related questions

Who counts as the Economic Buyer if a committee approves the purchase?

The committee collectively performs the Economic Buyer function. Treat it as one role with one final-approval authority, then identify who within it drives the decision and who can veto. Do not list three separate Economic Buyers — that signals the sales objective is defined too broadly.

Can one person hold two Buying Influence roles?

Yes, and the book expects it in smaller organizations. A VP of Operations may be both Economic Buyer and User Buyer. Handle each role on its own terms — the financial-release conversation and the "will this work for me" conversation are different conversations with the same person.

What is a Single Sales Objective and why does it come before the list?

It is one specific solution, sold to one specific account, within one specific timeframe. The Buying Influence list only makes sense against a defined objective, because the Economic Buyer for a $30,000 pilot is often not the Economic Buyer for a $500,000 rollout in the same account.

How is a Coach different from a champion?

A champion advocates for you. A Coach guides you — telling you who the other Buying Influences are, what they care about, and where you actually stand. A Coach must have credibility inside the account and a personal win tied to your success; a champion may have neither.

Does the first step change for renewals and expansions?

The step is the same, but the answers shift. Renewals often have a lower-altitude Economic Buyer and established User Buyers. Expansions frequently introduce new Technical Buyers and a new Economic Buyer, which is precisely the new-player Red Flag the framework flags automatically.

FAQ

Is the first step "identify Buying Influences" or "define the Single Sales Objective"?

Both, in sequence, and they are not in conflict. The Single Sales Objective scopes the analysis — one solution, one account, one timeframe — and the Buying Influence identification is the first *qualifying* step performed against that scope. Practitioners usually describe the first step as identifying the Buying Influences, because that is where the qualifying work begins; the objective is the frame that makes the list meaningful.

Why does the book insist there is only one Economic Buyer?

Because the role is defined by final approval and discretionary release of funds, and if two people genuinely hold that authority independently, you are looking at two separate sales objectives. When sellers list multiple Economic Buyers, it is almost always a symptom of a sales objective that has not been narrowed enough, or of confusing influence with authority.

How do I find the Economic Buyer when nobody will tell me?

Develop a Coach first. That is the role's explicit function in the framework — a Coach helps you identify and understand the other Buying Influences. Failing that, ask User Buyers directly who signs off when a purchase of this size and disruption is involved. Reluctance to answer is itself information: it usually means the internal process is unclear to them too, which is a Red Flag worth recording.

Does this framework still apply with modern buying committees and product-led motions?

The role model holds because it describes functions, not org charts. Product-led motions often produce many User Buyers in Growth mode with genuine enthusiasm and no Economic Buyer engagement — which is exactly the pattern the framework predicts will stall at the commercial conversation. Larger buying committees increase the number of Technical Buyers, which raises the cost of discovering them late rather than changing the method.

What is the relationship between Red Flags and forecast accuracy?

Red Flags are unresolved information gaps, and unresolved gaps are where slippage originates. A team that requires every Red Flag to be paired with a dated action or an offsetting Strength converts vague optimism into a specific list of unknowns. That does not guarantee accuracy, but it makes the reasons for a bad forecast inspectable after the fact, which is how calibration improves.

Should Buying Influence data live in the CRM or on the Blue Sheet?

Both, with different purposes. The CRM holds structured fields — role, contacted yes/no, mode — so they can be reported on across the pipeline. The Blue Sheet holds the narrative analysis, the Red Flag/Strength pairing, and the action plan, which resists field-ification. Teams that try to force the entire analysis into CRM picklists usually end up with cosmetic compliance and lose the reasoning that made the exercise valuable.

Sources

• https://millerheimangroup.com/
• https://www.kornferry.com/capabilities/sales-strategy
• https://hbr.org/2015/03/making-the-consensus-sale
• https://hbr.org/2017/03/the-new-sales-imperative
• https://www.gartner.com/en/sales/insights/b2b-buying-journey
• https://www.mheducation.com/
• https://www.forrester.com/blogs/category/sales/
• https://www.salesforce.com/blog/sales-qualification/
• https://openlibrary.org/search?q=the+new+strategic+selling

Related on PULSE

• How MEDDIC and MEDDPICC map onto Buying Influence roles in a modern CRM
• What separates a Coach from a champion in enterprise deal reviews
• Why unmet Economic Buyers are the leading cause of end-of-quarter slippage
• Building a stage gate that requires named stakeholders before a deal advances
• Red Flag discipline: turning unknowns into dated pipeline actions
• Choosing between BANT, MEDDIC, and Strategic Selling by deal shape