1. What problem do you solve?
Name the specific business problem your offering addresses for this buyer, not a generic category of problem your product solves for everyone.
Resources → Value Selling
Move From Features to Financial Impact.
Value selling means leading with the customer’s problem and its quantified cost, not your product’s feature list, and using that number to justify price instead of defending it.
These seven resources apply whether you sell enterprise software, technology hardware, capital equipment, intermediate goods, or MRO consumables. Only the value drivers change, not the discipline.
Article
Sell the Problem, Not the Product
Most sales conversations start with a product pitch, but value-based sellers start with the buyer’s problem instead. The first move is to stop describing what your product does and start asking what’s broken in the buyer’s business and what that’s costing them.
Once the problem is named, the next step is sizing it: what is the current approach costing the buyer in wasted time, lost revenue, or unnecessary risk, right now, before your solution ever enters the conversation? Only after the cost of the status quo is on the table does it make sense to introduce your offering as the fix, because now the buyer is evaluating your solution against a number they helped build, not a generic pitch.
This sequence works the same way whether the “problem” is a broken CRM workflow costing a sales team hours per week or a piece of aging capital equipment causing unplanned downtime on a production line. The problem changes; the discipline of quantifying it before pitching a fix does not.
Article
How to Build a Value Proposition Buyers Actually Believe
A credible value proposition answers three questions in order: what business problem do you solve, what impact does solving it have on the buyer’s business, and how can that impact be quantified in real currency. Most value propositions fail at the third question, staying vague (“improves efficiency”) instead of specific (“cuts changeover time by 40 minutes per shift, worth roughly $340 per shift in an average plant”).
A useful second path to the same answer is working forward from features: a feature should create a benefit, and that benefit needs a dollar figure attached before it counts as value to the buyer. Generic value propositions that never get quantified are really just feature lists wearing better adjectives.
Because value propositions need to flex by segment, tailor the quantification to the buyer in front of you. A SaaS platform’s efficiency gain looks like hours saved per user per week; a capital equipment upgrade’s gain looks like additional units produced per shift or scrap reduced per run. The three-question structure stays fixed. The units of measurement change by industry.
Article
Moving the Conversation From Price to Value
When a buyer opens with “what does it cost,” answering directly locks the conversation into a price comparison you’re likely to lose. The better move is redirecting toward the buyer’s problem: what are they trying to accomplish, what’s getting in the way, and what would solving it be worth. This isn’t stalling, it’s sequencing, because price only makes sense once there’s a value number to compare it against.
If a buyer pushes back and insists on a number up front, stay persistent that price is irrelevant until you both understand what your solution is worth to their business specifically. This is also the point where a value calculator or ROI tool earns its place in the conversation, turning a subjective debate about whether the price is fair into a specific calculation both sides can inspect and challenge.
This approach holds in a plant manager’s office as well as it does in a CFO’s, because in both cases, the buyer wants proof the number reflects their situation, not a marketing average.
Article
Value Selling for Multi-Stakeholder Buying Committees
Complex deals rarely have one buyer; they have a committee, and each member cares about a different slice of value. An economic buyer wants revenue growth or cost savings. A technical evaluator wants proof the solution works in their actual environment. Finance and procurement want transparent, defensible assumptions they can vet without taking your word for it.
Trying to sell every stakeholder the same pitch is a losing strategy, because a plant operations lead does not care about the same numbers a CapEx committee cares about, and neither cares about the numbers a sales VP would want. What value selling contributes here is not a single pitch but a single set of underlying assumptions that each stakeholder can view through their own lens: throughput and uptime for operations, IRR and payback for finance, total cost of ownership for procurement.
The buyers who most need this are often internal champions who have to carry your case into rooms you’re not in. Give them a business case built from assumptions transparent enough that they can defend it on their own, and the deal keeps moving without you.
Article
Why Value-Based Selling Outperforms Feature Selling
Value-based selling works because it changes what the buyer is actually deciding. A feature-led pitch asks the buyer to decide whether your product is good. A value-led pitch asks the buyer to decide whether solving their quantified problem is worth the quantified cost, a much easier yes when the math is favorable and transparent.
The mechanism is straightforward: understand the problem first, quantify what the status quo is costing, then show that your solution delivers the greatest financial benefit relative to that cost. Buyers who reach this point aren’t comparing your product to a competitor’s feature list anymore. They’re comparing a documented cost of inaction to a documented cost of action, and the second number usually wins when it’s real.
This holds across industries because the underlying buyer psychology doesn’t change. An IT buyer wants to avoid the cost of downtime as much as a plant manager wants to avoid the cost of a failed production run. Value selling just gives both of them a number to point to when they justify the decision internally.
Framework
The 3-Question Value Discovery Framework
Use these three questions, in this order, at the start of any value-selling conversation, whether you’re qualifying a self-service SaaS trial or scoping a capital equipment upgrade.
2. What’s the business impact?
Identify where that problem shows up financially: lost revenue, wasted labor, scrap, downtime, risk exposure, or missed capacity.
3. How much, in real numbers?
Quantify the impact in the buyer’s own currency and units, using their data and credible benchmarks, not a generic industry average.
Answering all three before introducing your solution is what separates a value-selling conversation from a feature pitch that happens to mention ROI at the end.
Template
Value Discovery Conversation Template
Use this sequence of prompts on a discovery call to move a buyer from problem to quantified value without ever pitching a feature.
Open
“What are you trying to accomplish this year, and what’s currently getting in the way?”
Size the problem
“How often does that happen, and what does it cost you when it does, in hours, dollars, or units?”
Explore alternatives
“Have you looked at other ways to solve this? What’s kept you from fixing it already?”
Confirm ownership
“Who else feels this problem, and who would need to sign off on fixing it?”
Quantify together
“If we could remove this cost, roughly what would that be worth to your business per month or per year?”
Bridge to solution
“Here’s how our approach is built to address exactly that, based on what you just told me.”
FAQ
Common questions
What is value selling?
Value selling is a sales approach that leads with the customer’s business problem and its quantified financial impact, rather than leading with product features, and uses that quantified impact to justify price.
How is value selling different from value pricing?
Value selling focuses on justifying your price to a specific buyer using their own numbers. Value pricing focuses on setting your price in the market based on the value your offering creates relative to alternatives.
Does value selling work for industrial and manufacturing sales, not just software?
Yes. The same discovery-first, quantify-the-problem approach applies whether the buyer is evaluating enterprise software, capital equipment, intermediate goods, or MRO consumables. Only the value drivers and benchmarks change.
Put value selling into a live deal today.
Try ValueNavigator free, no registration or credit card required, or talk with us about your specific rollout.