Opportunity Scoring: Find Underserved Customer Needs

Opportunity scoring ranks customer needs by two survey numbers — how important an outcome is and how satisfied people are with getting it today. The formula, Importance + max(Importance − Satisfaction, 0), pushes needs that are both important and poorly served to the top. Those are the underserved outcomes worth building for.

Quick Answer: Opportunity scoring surveys customers on the importance of each desired outcome and their satisfaction with current solutions, then scores each outcome as Importance + max(Importance − Satisfaction, 0). High-importance, low-satisfaction outcomes score highest — they are the underserved needs where a new product can win before competitors notice.

Most founders prioritize what to build from a list of features they already like. Opportunity scoring flips that. It starts from the outcomes customers are trying to achieve, measures which of those outcomes are still painful, and lets the math tell you where demand is being underserved. Anthony Ulwick built it as the quantitative core of Outcome-Driven Innovation, and it remains one of the few prioritization methods that produces a defensible number instead of a gut call.

This guide walks through the formula and its scale, how to gather clean importance and satisfaction ratings, how to calculate and rank scores, how to read the resulting opportunity landscape, and the mistakes that quietly break the whole exercise.

The opportunity score formula and its scale

The opportunity score for any outcome equals its importance plus the gap between importance and satisfaction, floored at zero: Opportunity = Importance + max(Importance − Satisfaction, 0). Both inputs come from customer surveys on a 1-to-10 scale, so every outcome lands on a single comparable number.

The formula does something deliberate. Importance appears twice — once on its own, and once inside the gap term. That double-counting is intentional: it means an outcome can only score high if it matters to customers and is underserved. A trivial outcome that nobody satisfies well still scores low, because the importance floor keeps it down. An important outcome that everyone already nails also scores low, because the gap collapses to near zero.

The max(...) clamp matters. When satisfaction exceeds importance — customers are more satisfied than the outcome even warrants — the gap term would go negative. The clamp sets it to zero instead of subtracting. So the worst an overserved outcome can do is score equal to its importance; the formula never punishes below that floor. This keeps the scale intuitive and prevents overserved needs from producing misleading negative numbers.

Because both inputs run 1 to 10, the theoretical opportunity range is 0 to 20. In practice, the score sorts into bands that map to a strategic read. Here is how practitioners of Outcome-Driven Innovation typically interpret the number.

Treat these bands as a lens, not a law: the exact cutoffs shift with your market and sample. The point is the ordering. An outcome scoring 14 is a more promising place to compete than one scoring 9, and the formula tells you that without you having to argue about it. For the step-by-step mechanics of running the calculation on real data, the companion piece on how to do opportunity scoring, step by step walks through a full worked example.

How to gather importance and satisfaction ratings

You gather the two inputs by surveying real customers on a list of desired outcomes, asking each respondent to rate every outcome twice — once for how important it is, once for how satisfied they are with their ability to achieve it today. The quality of your scores is capped entirely by the quality of these two questions.

Start with outcomes, not features. This is the part founders skip, and skipping it invalidates everything downstream. An outcome is a measurable statement of what the customer is trying to accomplish, phrased independently of any solution — "minimize the time it takes to confirm a report is accurate," not "add a validation button." Features are your hypotheses about how to serve an outcome; outcomes are what the customer actually cares about. Score outcomes, and the same result stays true even as the technology to deliver them changes.

Ask importance and satisfaction as two separate questions. For each outcome, one question asks how important achieving it is to the respondent, and a second asks how satisfied they are with how well they can achieve it using their current approach. Keeping them separate is what lets the gap between the two mean something. If you collapse them into one "how much do you want this" question, you lose the entire signal the framework is built on.

Sample the people who actually do the job. Opportunity scores describe a specific job-to-be-done as experienced by the people who perform it. If your respondents are a mix of job performers, buyers, and bystanders, the averages blur and the underserved outcomes hide inside noise. Segment first, then score within a segment. Grounding the outcome list itself in prior qualitative work matters here — the complete guide to customer research for founders covers how to surface the outcomes worth putting on the survey in the first place.

Use a consistent scale and enough respondents to trust the mean. Both questions use the same 1-to-10 scale so the arithmetic is valid. You need a large enough sample within each segment that the average importance and satisfaction are stable, not driven by a handful of loud voices. Small, unrepresentative samples produce confident-looking scores that mean nothing.

A quick contrast makes the difference between good and bad survey inputs concrete.

The strong column is more work up front and produces numbers you can actually stake a roadmap on. The weak column produces a spreadsheet that looks rigorous and encodes your existing biases right back at you.

Calculating and ranking opportunity scores

Once every outcome has an average importance and average satisfaction from your sample, you apply the formula to each row and sort the results descending. The outcome at the top is your single best-supported opportunity; the ranking below it is your prioritized landscape.

Compute per outcome, using segment averages. For each outcome, take the mean importance and mean satisfaction across respondents in the segment, then plug them into Opportunity = Importance + max(Importance − Satisfaction, 0). Do this within a segment, never across a blended crowd — a mixed average can show moderate satisfaction that hides one group in real pain and another perfectly content.

Walk through the logic on a few illustrative shapes so the formula stops being abstract:

• High importance, low satisfaction. Say importance is high and satisfaction is low. The gap is large, and it adds to an already-high importance. This is the classic underserved outcome — the highest scores in almost any study look like this.
• High importance, high satisfaction. Importance is high but satisfaction is nearly as high, so the gap term shrinks toward zero. The score settles close to importance alone. This is an appropriately served outcome: it matters, but the market already handles it well. It is table stakes, not a wedge.
• Low importance, low satisfaction. The gap might be sizable, but it adds to a low importance base, so the total stays modest. Customers are dissatisfied with something they do not care much about — rarely worth chasing.
• Low importance, high satisfaction. Both the base and the gap are small. This is an overserved outcome, where the market may even be over-investing. The formula floors it near the bottom.

Rank descending and read the top of the list. Sorting puts the underserved, high-importance outcomes at the top by construction. That ordered list is the deliverable. It converts a room full of opinions about what to build into a defensible sequence you can point to when someone asks why one outcome beat another.

Hold the numbers as directional, not precise. An opportunity score is a prioritization signal, not a physical measurement. A 14.2 versus a 13.8 is a tie; a 15 versus a 10 is a real difference. Use the score to separate strong opportunities from weak ones and to order the strong ones roughly — do not over-interpret decimal places or treat one survey as the final word.

Reading the opportunity landscape: overserved, served, underserved

Every scored outcome falls into one of three strategic states — overserved, appropriately served, or underserved — and the whole point of scoring is to sort your outcomes into these buckets so you know where to compete. The state is determined by the relationship between importance and satisfaction, which the score already encodes.

Underserved outcomes are where new products win. These are high-importance, low-satisfaction needs — the top of your ranked list, typically scoring above the market's midpoint. Customers care deeply and current solutions leave them frustrated. This is the sweet spot for innovation, because a better solution has room to create obvious, felt value. A startup entering an established market almost always needs to find its wedge among underserved outcomes; competing on outcomes the incumbents already satisfy is a losing fight.

Appropriately served outcomes are table stakes. Here importance is high and satisfaction is close behind. The market already does a good job. You still have to meet these outcomes — a product that fails table stakes is disqualified — but you cannot differentiate on them. Leading your positioning with an appropriately served outcome tells customers you solve a problem they already consider solved.

Overserved outcomes are where you can subtract. These are low-importance, high-satisfaction outcomes — often the place incumbents have piled on features that customers do not value. Overserved outcomes are the opening for disruptive, lower-cost, simpler offerings: you can strip out the over-engineering, serve the outcome "well enough," and redirect that investment toward the underserved needs that actually move customers. Recognizing overservice is how you decide what not to build.

To make the states concrete, here is how a typical outcome set distributes across them. The takeaway is that most outcomes are not opportunities — the framework's value is isolating the few that are.

Reading the landscape this way turns a list of scores into a strategy. It tells you where to invest (underserved), where to keep pace (served), and where you can safely do less than incumbents (overserved). Pairing the scores with a visual read helps — the importance vs. satisfaction matrix plots the same two axes so the three states become regions on a chart your whole team can align around.

Common opportunity scoring mistakes

Most failed opportunity scoring efforts fail at the input stage, not the arithmetic. The formula is simple and hard to get wrong; the survey design and interpretation around it are where founders lose the signal. These are the errors that most often turn a rigorous-looking exercise into false confidence.

Scoring features instead of outcomes. This is the most common and most damaging mistake. If your survey rates "add a mobile app" or "faster export," you are scoring your own solution ideas, not customer needs. The results will confirm whatever you already wanted to build, and the moment technology shifts, your scores expire. Always phrase items as solution-neutral, measurable outcomes.

Blending segments into one average. A single opportunity score across a mixed audience hides the exact insight you are hunting for. One segment can be in acute pain on an outcome while another is content; the blended average shows mild dissatisfaction and buries the opportunity. Score within a segment, then compare segments deliberately.

Combining importance and satisfaction into one rating. If you ask a single "how badly do you want this" question, you cannot compute a gap, and without the gap there is no way to distinguish an underserved outcome from one that is important but already well served. Keep the two questions separate — the entire method depends on it.

Treating the score as precise truth. Opportunity scores are directional. Founders who agonize over a 13.6 versus a 13.9, or who build an entire roadmap off one survey of thirty people, are over-trusting the number. Use it to separate tiers and order priorities, then validate the top candidates with real experiments rather than treating the survey as the verdict.

Stopping at the score instead of validating. A high opportunity score is a strong hypothesis about where demand is underserved — it is not proof that customers will pay for your specific solution. The score tells you where to look; it does not tell you whether your product actually delivers the outcome or whether people will switch. That still requires validation. This is exactly where a platform like Edmired helps: it turns the underserved outcomes your scoring surfaces into structured experiments and evidence, so a promising number becomes a tested one before you commit a roadmap to it.

Key Takeaways

• Opportunity scoring ranks customer needs by two survey inputs — importance and satisfaction — using the formula Opportunity = Importance + max(Importance − Satisfaction, 0). The math surfaces needs that are both important and poorly served.
• The highest scores come from high-importance, low-satisfaction outcomes. These underserved needs are where a new product has room to create obvious value and win before competitors react.
• Score solution-neutral outcomes, not features. Rating features encodes your existing biases and produces scores that expire the moment technology shifts.
• Ask importance and satisfaction as two separate questions on the same 1-to-10 scale. The gap between them is the entire signal; collapsing them into one question destroys it.
• Score within a single customer segment, never a blended crowd. Mixed averages hide the acute pain of one group inside the contentment of another.
• Read outcomes as overserved, appropriately served, or underserved. Build for underserved outcomes, meet the served ones as table stakes, and simplify or cut the overserved ones.
• Treat scores as directional prioritization, not precision, and validate the top candidates. A high score is a strong hypothesis about demand, not proof that customers will switch to your solution.

Frequently Asked Questions

What is the opportunity score formula?

The opportunity score for an outcome is Importance + max(Importance − Satisfaction, 0), where both importance and satisfaction come from customer surveys on a 1-to-10 scale. Importance is counted once on its own and again inside the gap term, so an outcome only scores high when it is both important to customers and poorly served by current solutions. The max(...) clamp floors the gap at zero so overserved outcomes never produce negative scores.

What counts as an underserved outcome in opportunity scoring?

An underserved outcome has high importance and low satisfaction — customers care about achieving it but current solutions leave them frustrated. These outcomes produce the highest opportunity scores and represent the best places to build, because a better solution can create value customers immediately feel. They are the wedge a new entrant needs, since competing on outcomes incumbents already satisfy well is far harder.

How is opportunity scoring different from other prioritization methods?

Opportunity scoring is grounded in Anthony Ulwick's Outcome-Driven Innovation, so it prioritizes customer outcomes measured through surveys rather than internal guesses about feature value. Unlike scoring models that rate features on effort and reach from a team's own judgment, it derives priority from two customer-supplied numbers — importance and satisfaction — making the result harder to bias toward what you already wanted to build.

How many customers do I need to survey for reliable scores?

Enough that the average importance and satisfaction within each segment are stable rather than driven by a few respondents. The exact number depends on your market, but the key discipline is scoring within a single, well-defined segment of the people who actually perform the job — a large blended sample across mixed segments is worse than a smaller focused one, because blending hides the very opportunities you are trying to find.

Can opportunity scores be negative?

No. The max(Importance − Satisfaction, 0) clamp prevents the gap term from going negative when satisfaction exceeds importance. The lowest an outcome can score is its importance value alone, which happens when customers are as satisfied as the outcome warrants. This floor keeps overserved outcomes near the bottom of the ranking without producing confusing negative numbers.

Does a high opportunity score mean I should build immediately?

No. A high score is a strong, quantified hypothesis about where demand is underserved — it identifies where to look, not whether your specific solution will deliver the outcome or convince customers to switch. Treat the top-scoring outcomes as candidates for validation through real experiments, and confirm that your product actually satisfies the outcome before committing a roadmap to it.