Key Takeaways
Sell a measurable change, not a catalog of features
Define the outcome first. A solution is not simply a product matched to a stated need. It is an answer the buyer recognizes and agrees to, with an improvement that can be measured against a starting point. That shift changes the salesperson’s job: understand the business problem, agree on what a better result means, and stay involved until the result is assessed.
Make the process teachable. Eades argues that a repeatable sales process helps ordinary performers reproduce behaviors that talented, intuitive sellers may perform without knowing how. He estimates that roughly 20 percent of salespeople are natural standouts, while the rest benefit from a clear path. Pairing that split with the book’s claim that about 80 percent of buyers are cautious and proof-seeking, he describes a 64 percent mismatch: less experienced sellers facing difficult buyers without a process.
The strongest idea here is that a sale is partly a promise about a future state, not merely a transfer of goods. That makes measurement and delivery part of selling rather than an afterthought. The process also converts tacit expertise into something colleagues can learn, coach, and improve. Still, the 20/80 categories are useful shorthand, not a complete theory of talent or buyer behavior. People vary by product, context, and experience. A process should make good judgment easier to repeat, not turn every customer conversation into a mechanical script.
Create demand among buyers who are not shopping yet
Prospect differently. Eades distinguishes prospecting from polling. Polling asks who is already looking to buy; prospecting makes a relevant problem visible to someone who has not started a search. He estimates that only 5 to 10 percent of potential buyers are actively looking, leaving most possible opportunities outside the formal buying market.
Earn a curious response. Research the organization and the likely challenges of the person being contacted. Then use a brief peer success story or a quantified, clearly tentative benefit to invite discussion, not to push a product. The book recommends protecting prospecting time, suggesting 10 percent when the pipeline is healthy and more when it is weak. It reports client interest rates of 30 to 70 percent for its targeted prompts, compared with 2 to 10 percent before their use. These are client-reported results, not a universal guarantee.
This approach treats attention as something a seller must earn by making the conversation relevant. A specific business concern gives a busy buyer a reason to listen, while a peer example can make an unfamiliar possibility feel more credible. The distinction between finding existing demand and helping someone recognize a problem is commercially important. It also carries a responsibility: a seller can manufacture anxiety as easily as insight. The test is whether the proposed issue is plausible, the evidence is honest, and the buyer can freely conclude that no change is needed.
Diagnose causes and consequences before showing your product
Investigate before recommending. The book’s 9 Block Vision Processing Model is a structured conversation for moving from an admitted problem toward a buyer-owned idea of a solution. It guides sellers to investigate three things: why the problem exists, whom it affects and how, and what capabilities might address it. Open questions invite the buyer’s account, more focused questions test possible causes and consequences, and confirming questions check that both sides understand the same situation.
Follow the evidence. In the fictitious Titan Games example, the sales leader is missing new-account revenue targets. Discussion reveals that salespeople spend time processing repeat orders and answering routine customer questions. The seller estimates the lost selling capacity with the buyer, explores effects on sales morale and company goals, and only then discusses online ordering and customer help tools.
The model resembles disciplined diagnosis in medicine and engineering: symptoms are not explanations, and interventions should follow a tested account of causes. Its practical virtue is also its ethical one. The buyer contributes the facts and confirms the interpretation instead of receiving a pitch disguised as advice. Yet guided questions can steer as well as discover. Sellers should actively test alternative explanations and ask what evidence would disprove their preferred diagnosis. Without that check, a polished conversation may create agreement around the seller’s assumptions rather than the customer’s actual problem.
Reach the buyer first, or change the scorecard you inherit
Shape the choice. Buyers often compare vendors against requirements formed before some sellers arrive. Eades calls the favored position on that comparison the Column A position. His preferred move is to engage before the buyer has fixed the criteria, understand the business problem, and help define requirements that fit the solution’s real strengths. If a competitor already shaped the choice, assess honestly whether there is a credible way to change it before committing resources.
Compete selectively. In the book’s EDS story, a manufacturer in Argentina was close to failure and evaluating outsourcing firms. EDS first responded to the technology request, then recognized that automating broken manufacturing processes would preserve the underlying problem. It returned with a broader business case, including a projected $10 million in annual manufacturing savings, and won a multiyear contract worth more than $40 million. The lesson is to compete on customer value, not automatically on the buyer’s initial checklist.
A vendor that helps define the problem can influence what counts as a good answer. This is a real strategic advantage, especially when the initial request focuses on a visible symptom rather than its cause. The EDS example shows how reframing can reveal value that a feature comparison misses. But changing the scorecard is defensible only when the new criteria correspond to a genuine business need. Otherwise, reframing becomes a way to evade fair comparison. Buyers should be able to see why a proposed requirement matters and how it connects to outcomes they care about.
Earn access to decision power by trading proof for commitment
Find the people who can act. A Sponsor supports a proposed solution and can help navigate the organization, but may not have the authority or influence to secure a decision. A Power Sponsor can make the purchase happen or bring the seller to those who can. Job titles and organization charts help, but do not reliably reveal who has practical influence.
Exchange value fairly. Once a buyer sees a plausible solution, the seller can offer a proof step in return for access to relevant decision-makers. Eades calls this quid pro quo: each side makes a commitment rather than one side providing endless unpaid work. In his example, a sales manager wanted a demonstration. The seller agreed to travel if the manager arranged access to the division president and sales vice president and covered expenses. The resulting discussion and business-focused follow-up letter helped establish credibility with the senior leaders.
The exchange protects both parties from a familiar failure: the seller invests heavily with a friendly contact who cannot move the decision, while the buyer receives demonstrations without committing to a useful evaluation. Mapping influence is also a form of organizational analysis, since authority often travels through expertise, trust, and internal relationships as well as formal hierarchy. The bargain must remain proportionate. A demand for access can feel coercive if the seller has not earned it or if the junior contact lacks the power to arrange it. Transparency keeps the exchange collaborative.
Make the buyer own a dated plan for evaluating change
Turn interest into a sequence. An Evaluation Plan lays out the events, owners, timing, and decision points needed to assess a purchase. It can include interviews, value analysis, technical and legal review, implementation planning, and measures of success. The seller proposes a draft, but the buyer should revise and accept it. Each go or no-go decision is mutual, so either side can stop when the evidence no longer supports proceeding.
Let ownership show. In one story, a prospective customer edited the seller’s proposed plan and changed the sequence. The seller asked who controlled the buying process. The buyer said the changes made it his plan, then tore up the document because it was no longer needed to decide to work together. The point is not to control the buyer’s choice. It is to help both parties organize the evaluation while giving the buyer real ownership of the process.
A shared plan brings project-management discipline to a decision that otherwise tends to dissolve into scattered meetings and vague promises. Named owners and dates make delays visible, while explicit decision points reduce the pressure to keep investing simply because work has already begun. This is useful for complex purchases with many stakeholders. The plan can still become bureaucracy if every event exists to satisfy the seller’s forecast rather than the buyer’s learning needs. Its quality is measured by whether it helps the customer make a sound decision, including a decision not to buy.
Put numbers behind value, then track whether customers realize it
Make value testable. The book defines value as total benefits minus total investment. A preliminary Value Proposition estimates what a specific customer might gain and what it would cost; as the seller learns more, the buyer verifies or revises the assumptions. In the fictitious Titan Games example in the appendix, the proposed solution carried about $1.1 million in investment. The analysis projected roughly $991,000 in first-year net benefit, a 90.2 percent return on investment, and break-even early in the fourth quarter.
Measure the change. Those figures are a business case, not a promise. The seller and buyer should establish a baseline before implementation, agree which outcomes to monitor, and compare results afterward. Eades calls the improvement between the starting point and the measured result the delta. Successful outcomes can support future customer stories, but the first purpose of measurement is to establish whether the customer actually received the expected benefit.
Quantification can turn a vague claim such as greater efficiency into assumptions that a buyer can inspect, challenge, and improve. That makes the conversation more concrete and can expose benefits that product specifications overlook. The discipline matters most when the buyer owns the inputs and understands the limits of the estimate. Projected revenue gains, in particular, can be hard to attribute to one purchase because markets, staffing, and execution also change. A credible business case separates direct savings from uncertain gains and treats post-sale measurement as a way to learn, not merely to validate the original pitch.
Keep a walk-away option before you bargain over price
Prepare before pressure arrives. The book treats closing as the result of the work already done, not a last-minute technique for rescuing a weak opportunity. Before negotiating, confirm that the buyer has authority, value is agreed, and required legal, technical, and administrative steps are understood. Then prepare a Give/Get List: what each side values, what the seller can offer, and what it should receive in return.
Trade, do not surrender. Buyers may keep several vendors in play, negotiate with their least-preferred option first, or use a deadline to encourage concessions. Sellers should know what they can give, attach value to it, and make any concession conditional on an equivalent commitment. One bank CEO in the book chose IBM despite ranking it third on price and technology, because IBM addressed the risk of a supplier failing or key staff leaving. Managing perceived risk can matter more than discounting.
The willingness to leave is not bravado; it is a negotiating resource that depends on having credible alternatives and knowing the value of the offer. A full pipeline can reduce the pressure to accept damaging terms simply to meet a quota. The bank example also widens the meaning of value: buyers may be protecting a career, an implementation, or organizational continuity, not just a budget. Still, a hard walk-away posture can become counterproductive when it ignores the buyer’s constraints. Good negotiation identifies the interests behind a request, then searches for exchanges that protect both sides.
Build a sales culture around process before automating it
Make the system usable. Eades presents a high-performance sales culture as four connected elements: a sales process, a management system for coaching and forecasting, sales automation, and marketing aligned to customer problems. He argues that automation should support a sound process rather than dictate it. Otherwise, a company may simply make disorganized selling faster and produce unreliable data.
Reinforce behavior. Implementation is organizational change, not a one-day training event. Managers need to coach against observable milestones, teams need practice, and leaders need to align measurement and rewards with the new behavior. The book’s account of training 400 software salespeople emphasizes teaching how manufacturing buyers make decisions and connecting product capabilities to those issues, rather than trying to teach every detail of a new industry and product line first. Eades reports productivity increases of 15 percent or more in some deployments, not as a guaranteed result.
A sales process is most powerful when it functions as shared learning infrastructure. It lets marketing, managers, and customer-facing staff exchange evidence in a common language, while milestones make coaching more specific than simply asking for a better quarter. The warning about automation is timely: dashboards can reward complete records instead of better customer outcomes, and people adapt to what is measured. A durable system therefore tracks meaningful buyer commitments and customer results, not just activity volume. The book’s cultural claim is persuasive, although adoption depends on leaders demonstrating the process rather than merely announcing it.
Analysis
The book’s central contribution is to treat selling as a disciplined form of joint problem-solving rather than persuasive performance. Its sequence is consequential: find a business issue, establish its causes and organizational effects, help the buyer imagine an answer, verify authority and value, and organize a decision process. This logic makes the book more than a collection of sales scripts. It links frontline conversation to forecasting, management, marketing, and implementation, arguing that predictable revenue depends on the quality of the whole system.
Its most useful tension is between customer-centered diagnosis and seller-biased vision. The seller is asked to understand the buyer before prescribing, yet also to shape requirements toward the seller’s capabilities. Those aims can coexist when the capabilities address a verified problem and the buyer can reject the proposed interpretation. They conflict when questions merely steer a prospect toward a predetermined product. The book’s insistence on buyer confirmation and measurable outcomes offers a safeguard, but only if those safeguards are practiced honestly.
The frameworks also make tacit expertise coachable. Milestones, letters, and evaluation plans turn a salesperson’s judgment into evidence that managers can inspect. This improves organizational learning, but creates a familiar measurement hazard: once a milestone becomes a target, representatives may optimize documentation instead of progress. The remedy is to validate milestones through buyer actions and outcomes, not internal confidence or CRM completion.
Finally, the book’s numerical claims and case examples should be read as persuasive evidence from the author’s practice, not as controlled proof that the method causes a given lift in every market. The underlying principles are more portable than the reported percentages. In transactional sales, a full diagnostic apparatus can be excessive; in complex purchases, it can prevent expensive assumptions. The lasting lesson is not to follow every step mechanically, but to make the buyer’s problem, decision authority, expected value, and next commitment explicit.
Review Summary
The New Solution Selling receives mostly positive reviews, with an average rating of 3.85/5. Readers praise its methodical approach to solution-based selling, focusing on understanding customer needs and pain points. Many find it valuable for complex sales processes, particularly in software and consulting. Critics note some concepts are borrowed from earlier works. The book is seen as particularly useful for those transitioning from transactional to more complex sales roles, offering practical tools and strategies for effective solution selling.
People Also Read
Glossary
Solution Selling
Buyer-aligned sales processA sales approach that organizes customer-facing work around how buyers make decisions. It combines a philosophy of solving recognized business problems, a map of selling steps, methods and job aids for carrying them out, and a management system for coaching and forecasting. Its aim is a mutually agreed solution that produces measurable improvement.
Latent Pain
Unrecognized or unacted-on problemA problem, business issue, or missed opportunity that a potential buyer has not recognized, admitted, or acted on. The buyer may be unaware of it or may believe that fixing it is too costly, risky, or difficult. The seller’s task is to establish whether the issue is real and important, not simply to push a product.
Situational Fluency
Understanding buyer contextThe ability to understand a buyer’s business situation, role, problems, and relevant ways of addressing them. In the book, it combines knowledge of the customer’s circumstances and of solution capabilities with interpersonal and selling skills. Research, experience, preparation, and structured job aids help salespeople develop it.
9 Block Vision Processing Model
Structured diagnosis and visionA conversation model for diagnosing a buyer’s problem and helping the buyer develop or revise a vision of a solution. It examines reasons for the problem, its impact across the organization, and the capabilities that could address it. The model uses open, focused, and confirming questions to keep seller and buyer aligned.
Pain Chain
Map of connected business problemsA visual map linking key people in an organization to their problems, the reasons behind those problems, and the effects on other people or functions. It helps a salesperson explore organizational interdependence, identify stakeholders, and connect a local difficulty to broader business consequences. It is refined as the customer’s situation becomes clearer.
Column A
Buyer’s favored choiceThe seller’s position as the buyer’s preferred option in a comparison of alternatives. The book argues that a seller who helps define the problem and buying requirements can improve the chance of becoming this preferred choice. When a competitor already occupies that position, the seller needs a credible strategy to alter the comparison or reconsider competing.
Power Sponsor
Buyer with decision influenceA person with enough authority or organizational influence to make a purchase happen, even if the person’s title does not suggest formal control. A Power Sponsor can negotiate the steps of a decision and bring the seller to other necessary people. The role is distinguished from a Sponsor, who supports the solution but cannot secure the decision alone.
Evaluation Plan
Shared decision scheduleA proposed sequence of activities for evaluating a purchase, with events, timing, responsibilities, and mutual go or no-go decisions. It may cover discovery, technical review, value analysis, implementation planning, and success measures. The buyer should shape and accept the plan so it serves the customer’s decision process rather than functioning only as the seller’s schedule.
Value Proposition
Quantified customer benefit claimA targeted statement estimating how a specific customer could improve a business result, what capabilities would enable that improvement, and what investment would be required. Early versions are hypotheses based on research and evidence from other customers. As the buyer tests the assumptions, the estimate can become a jointly confirmed business case.
Milestone
Verifiable sales-process checkpointA defined point in the selling process associated with specific activities and evidence of progress. Milestones help salespeople and managers assess an opportunity, agree on its status, and identify the next useful action. In the book’s system, a milestone should not be claimed until its required steps have been completed and can be verified.
Value Cycle
Value through the sales processThe book’s approach to treating value as relevant throughout the customer relationship. The seller initially uses an evidence-based estimate to stimulate interest, verifies and confirms value during diagnosis and evaluation, uses the confirmed case to support a decision, and measures results after implementation. Measurement tests whether the proposed solution produced the promised improvement.
High-Performance Sales Culture
Integrated sales operating systemAn organizational culture that coordinates a common sales process, a management system for analysis and coaching, sales automation, and marketing aligned with customer business problems. The book presents this as a sustained change effort requiring executive support, practice, aligned incentives, and ongoing measurement, rather than a one-time training program.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.