Why the Best Framework for an 18-Month Ingredient Deal Was Written in 1985

A book with nothing to do with software describes your pipeline better than your CRM does

In 1985, Robert Miller and Stephen Heiman published Strategic Selling. There was no SaaS industry, no CRM category, no concept of a sales funnel with five stages and a 30-day cycle. What they were writing about was IBM mainframes, industrial equipment, and defense contracts: sales that touched six departments, took a year or more to close, and depended on navigating people who had never spoken to each other but all had veto power over the deal.

That description fits a bioactive collagen evaluation at a major cosmetics brand almost exactly. R&D runs the formulation trial. Procurement negotiates price and supply terms. Quality reviews the regulatory dossier. Marketing decides whether the ingredient story fits the brand. A VP signs off on the budget. None of them report to each other, and most of them will never be in the same room.

The stakeholder map: six roles, none of them on the org chart

Strategic Selling's core idea is that every complex sale involves the same six roles, regardless of industry, and that most reps lose deals by treating every contact the same way. In an ingredient evaluation, the roles map cleanly:

• Economic Buyer: usually a procurement director or VP who approves budget and supplier terms. Cares about price, reliability, and risk, and rarely has an opinion on the formulation science
• Technical Buyer: the formulation chemist or regulatory lead who evaluates spec sheets, stability data, and compliance. Can say no on technical grounds, can't say yes alone
• User Buyer: the R&D scientist or product developer who will actually work with your ingredient day to day. Cares about ease of use and real-world performance, not the spec sheet
• Champion: your internal advocate, usually the person who first got excited about your ingredient. Your most valuable asset, and the one contact most reps under-invest in
• Gatekeeper: controls access and scheduling. An assistant, a coordinator, sometimes a junior scientist triaging inbound suppliers. Ignore them and your samples never get evaluated
• Anti-Sponsor: a skeptic, often with a relationship with your incumbent competitor or a stake in the status quo. Rarely announces themselves as opposition

The framework's sharpest rule is about sequence, not roles: never let the Economic Buyer hear your pitch cold. Brief the Champion first, and let them set the internal context before procurement gets involved. Reps who skip this, usually because a warm procurement contact seems like a shortcut, routinely watch evaluations go quiet within weeks. The Champion feels bypassed, stops advocating, and the deal loses its only internal momentum.

Response Modes: the same message lands differently depending on where someone is

Strategic Selling also classifies how receptive a stakeholder currently is to change, independent of their role. A contact in Growth mode is actively looking for new suppliers and open to your pitch. One in Trouble has a burning problem, like a supply disruption, a formulation failure, or a regulatory deadline, and needs a solution now, not a relationship-building email. One who's Even Keel is satisfied with the status quo; change feels risky, and a generic pitch bounces off. One who's Overconfident believes their current setup is fine and needs evidence, not enthusiasm, to reconsider.

This matters more over an 18-month cycle than a 30-day one, because the same contact moves between modes as the deal progresses. The R&D lead who was in Trouble mode during a stability failure six months ago may be Even Keel now that the fix shipped. A follow-up email pitching a new application will read as tone-deaf if it doesn't account for that shift.

Conceptual Selling: one goal per conversation, not three

Miller and Heiman's follow-up book, Conceptual Selling, adds a constraint that's easy to state and hard to follow over a long cycle: every meaningful touchpoint should have exactly one goal. Confirm validates something you already believe about the customer's situation. Discover surfaces a new need or problem worth exploring. Commit asks for one specific next step, whether that's a sample, a call, or a signed document.

Reps running a two-year account naturally drift toward stuffing every email with all three: a status update, a new pitch, and a call to action, all in one message. It reads as noise. Over 18 months you'll have dozens of touchpoints with the same contact. Picking one goal per message is what keeps the relationship feeling like a conversation instead of a drip campaign.

The Challenger reframe: teach before you respond

Matthew Dixon and Brent Adamson's The Challenger Sale (2011) studied what separated top-performing reps from average ones in complex B2B sales, and found the biggest differentiator wasn't relationship-building or problem-solving. It was teaching: reintroducing the customer to their own situation in a way that changes how they think about it, then connecting that insight to your solution.

This matters most with the Economic Buyer, who usually has the least technical context in the room. Your Technical Buyer already understands why your ingredient's stability profile matters. Your Economic Buyer needs a different angle entirely: a reframe about supply chain risk, a regulatory shift they haven't tracked, a cost model they haven't considered. Responding to their stated question ("what's your pricing?") without first reframing the conversation leaves you competing on price against every other supplier who answered the same question the same way.

Why generic sales tech misses this entirely

Most CRMs and AI sales tools treat every contact the same way: log the interaction, set a follow-up date, move to the next task. That's a reasonable model for a single-buyer, 30-day sale. It's the wrong model for a long-cycle B2B deal, where the real work isn't logging activity. It's sequencing six relationships correctly over two years without losing the thread on any of them.

We wrote about this from the pipeline-data angle in Why Your CRM Is Killing Your Pipeline: generic stage models can't represent the complexity of a multi-department evaluation. The stakeholder problem is the same failure from a different angle. A pipeline stage tells you a deal is in "Sampling." It doesn't tell you the Champion hasn't heard from you in three weeks, that the Economic Buyer has never been briefed, or that the Technical Buyer's silence on your last email might mean they've become an Anti-Sponsor.

How we built this into Corial's relationship agent

Corial's relationship intelligence agent applies these three frameworks directly, not as inspiration but as the literal system prompt logic. When a salesperson needs to engage multiple contacts at an account, the agent classifies each contact's buying role, flags whether the Champion has been briefed before any Economic Buyer outreach, and groups contacts into coalitions when a combined email makes sense versus separate emails to avoid political friction. Before every drafted email, it also assigns a single goal (Confirm, Discover, or Commit) and, where relevant, a Challenger reframe angle.

None of this replaces judgment. It replaces the alternative, which is a rep trying to hold six relationships and their current state in their head across a deal that outlasts most software subscriptions. The frameworks are forty years old because the underlying shape of complex, multi-stakeholder sales hasn't changed. What's changed is that a system can now apply them consistently, on every touchpoint, without the rep having to remember which of six people they briefed last.