Customer Unmet Needs: The Growth Signal Most Brands Ignore

Customer unmet needs are the gaps between what people are trying to accomplish and what existing products, services, or experiences actually deliver. They are the single most reliable source of durable growth, and most companies are systematically blind to them.

Not because the signals aren’t there. They are, constantly, in support queues, in churn data, in the things customers say when nobody is recording. The problem is that most organisations are structured to optimise what they already sell, not to find what they should be selling instead.

Why Unmet Needs Are a Growth Problem, Not a Research Problem

I’ve sat in a lot of strategy sessions where the conversation about customer needs gets treated as a research phase. Something you commission, receive, present in a deck, and then move on from. That framing gets it almost entirely backwards.

Unmet needs are not a research deliverable. They are an ongoing commercial signal, and treating them as a project rather than a discipline is one of the main reasons growth stalls. You can spend six figures on a customer insight study and still miss the thing that’s actually driving churn, because the study was designed to confirm a hypothesis rather than challenge one.

I’ve seen this play out repeatedly across different sectors. A brand would commission research, get back a tidy report with customer segments and satisfaction scores, and then use it to justify a campaign they’d already planned. The research became a validation exercise. The actual unmet needs, the friction points that were pushing customers toward competitors, never made it into the brief.

The more useful framing is to treat unmet needs as a growth signal that lives inside your existing data. You probably already have most of what you need. The question is whether you’re reading it honestly.

If you want a broader view of how unmet needs connect to market positioning and growth planning, the Go-To-Market and Growth Strategy hub covers the commercial architecture that makes this kind of insight actionable rather than decorative.

What Unmet Needs Actually Look Like in Practice

There’s a version of this conversation that gets very abstract very quickly, with talk of latent demand and jobs-to-be-done frameworks and customer experience mapping. All of that has its place. But in practice, unmet needs tend to show up in much more mundane ways.

They show up in the support ticket that keeps getting logged with slightly different wording but the same underlying frustration. They show up in the sales call where the prospect says “we almost went with you but…” and the account manager doesn’t write it down. They show up in the product feature that’s been on the roadmap for eighteen months and keeps getting pushed because it doesn’t fit the current revenue model.

One of the most instructive moments I’ve had with this was early in a turnaround engagement. The business had decent retention numbers on paper but was bleeding customers in a specific segment. Nobody had joined the dots because the churn was spread across time and geography. When we pulled the exit survey data and actually read it, rather than averaging it into a score, the same theme came up over and over. The product worked fine. The onboarding experience made customers feel like they’d been handed a manual and left alone. That was the unmet need. Not a new feature. A different experience of the one they already had.

The distinction between functional needs and experiential needs matters here. Functional needs are about what a product does. Experiential needs are about how it feels to use it, to buy it, to get support for it. Most companies are reasonably good at identifying functional gaps. Experiential gaps are harder to see from the inside, because the people building the product have stopped noticing the friction that new customers feel immediately.

The Difference Between Stated Preferences and Actual Needs

Ask customers what they want and they will tell you. The problem is that what they tell you and what actually drives their decisions are often different things. This is not a criticism of customers. It’s just how human cognition works. People are generally better at describing their dissatisfaction than articulating the need underneath it.

A customer who says “I want a cheaper option” might actually need a clearer sense of value. A customer who says “I want more features” might actually need the existing features to work more reliably. A customer who says “I want faster delivery” might actually need better communication about where their order is. The stated preference is a symptom. The unmet need is the diagnosis.

This is where a lot of product and marketing teams go wrong. They take stated preferences at face value and build accordingly. Then they’re confused when the new cheaper tier doesn’t reduce churn, or when the new features don’t improve satisfaction scores. They solved for the symptom and left the underlying need untouched.

Getting below the stated preference requires asking different questions. Not “what do you want?” but “what were you trying to do when this went wrong?” Not “how satisfied are you?” but “what would have to be true for this to be genuinely useful to you?” The framing shifts from preference collection to need diagnosis, and the data you get back is substantially more useful.

This connects to a broader point about how go-to-market teams use customer data. Vidyard’s analysis of why GTM feels harder points to a similar tension: teams are generating more data than ever but making fewer clear decisions from it, partly because the data is collected to report on activity rather than to answer commercial questions.

Where the Best Unmet Need Signals Actually Come From

The conventional answer is customer research: surveys, focus groups, ethnographic studies, user interviews. And yes, those have value when they’re designed to challenge assumptions rather than confirm them. But in my experience, the richest signals tend to come from operational data that companies already have and aren’t reading carefully enough.

Support and service data is probably the most underused source. Every support ticket is a customer telling you something isn’t working. The question is whether anyone is aggregating those signals across time, categorising them by root cause rather than surface issue, and feeding that back into product and commercial decisions. Most companies aren’t. The support function is treated as a cost centre to be minimised, not an insight function to be mined.

Sales conversation data is the second major source that gets wasted. The things prospects say when they don’t buy, the objections that come up repeatedly, the competitor comparisons that sales teams are tired of hearing: all of that is live market intelligence about unmet needs. But it tends to stay inside individual salespeople’s heads rather than getting systematically captured and analysed.

Churn analysis is the third. Not the headline churn rate, which tells you very little, but the qualitative reasons behind it. Why did this customer leave? What were they looking for that they didn’t find? Where did they go instead? When I’ve done this properly, with actual exit conversations rather than a tick-box survey, the patterns that emerge are almost always more specific and more actionable than anything a traditional research project would surface.

There’s also value in looking at what customers are doing with your product that you didn’t design for. Workarounds, hacks, unusual use cases: these are customers solving an unmet need themselves because you haven’t solved it for them. That’s a product brief hiding in plain sight.

The Organisational Problem Nobody Talks About

Here’s the part of this conversation that usually gets skipped in favour of frameworks and methodologies. Identifying an unmet need is not actually the hard part. The hard part is what happens next.

Most organisations are structured around their existing revenue model. The incentives, the teams, the processes, the P&L lines: everything is oriented toward optimising what’s already working. An unmet need, by definition, requires doing something different. And doing something different threatens existing structures in ways that are not always comfortable for the people inside them.

I’ve watched this happen in agencies and in client organisations alike. The insight surfaces. It’s compelling. Everyone in the room can see it. And then the meeting ends and nothing changes, because acting on the insight would mean reallocating budget from a channel that has clear attribution to an experience improvement that doesn’t, or it would mean the product team taking on work that doesn’t fit this quarter’s roadmap, or it would mean a commercial conversation with a client about why the current brief is solving for the wrong problem.

The companies that consistently turn unmet needs into growth are not necessarily the ones with the best research capabilities. They’re the ones with the organisational willingness to act on uncomfortable findings. That’s a leadership and culture question as much as a strategy one.

BCG’s work on go-to-market strategy in B2B markets touches on this dynamic: the businesses that capture long-tail growth opportunities are typically the ones that have built processes for acting on granular customer signals, not just aggregated market data. The insight infrastructure matters, but so does the decision-making infrastructure around it.

How to Structure an Unmet Needs Audit Without Making It a Research Project

If you want to get a clear picture of where your unmet needs are sitting right now, without commissioning a six-month study, here’s a practical starting point.

Start with your churn data. Pull the last twelve months of customer exits and go beyond the headline number. If you have exit survey data, read it rather than averaging it. If you don’t have exit survey data, start collecting it now, and make the questions open-ended rather than scale-based. You’re looking for patterns in the language people use, not scores.

Then go to your support data. Ask your support team to categorise the last three months of tickets by root cause, not by resolution type. What keeps coming back? What takes the most time to resolve? What are customers frustrated about that isn’t actually a bug or a technical failure, but a design or experience issue?

Then talk to your sales team, specifically about the deals they didn’t win. Not the price-sensitive ones where you were always going to lose on margin, but the ones where the prospect was genuinely interested and still walked away. What were they looking for that you couldn’t give them? This is often where the most commercially significant unmet needs live.

Finally, look at your product usage data with fresh eyes. Where do users drop off? Which features have low adoption despite high visibility? Where are the workarounds? These are the places where your product isn’t fully meeting the need it was designed for.

This kind of audit typically takes two to three weeks with a small team and surfaces more actionable insight than most formal research projects, because it’s grounded in what’s actually happening rather than what customers say they’d prefer in a hypothetical scenario.

Tools that help you understand user behaviour on-site can complement this process. Hotjar’s feedback and growth loop tools are one way to collect qualitative signals at scale without requiring a dedicated research team. Similarly, Semrush’s analysis of market penetration strategy offers a useful lens on how unmet needs connect to addressable market size, particularly if you’re trying to make the commercial case for acting on what you find.

Unmet Needs and the Marketing Brief

One place where unmet needs thinking tends to get lost is in the translation from insight to brief. The insight team surfaces something real. The strategy team incorporates it into a positioning document. By the time it reaches the creative brief, it’s been softened into a generic customer truth that could apply to almost any brand in the category.

I’ve been on both sides of this. When I was running agency teams, we’d get briefs that described the target customer in ways that were technically accurate but commercially useless. “She’s busy and values quality.” Fine. What does she specifically need that she isn’t getting from the current category? That’s the question the brief should answer, and it usually didn’t.

The best briefs I’ve worked from were the ones where the client had done the hard work of identifying a specific, defensible unmet need and was willing to build the entire brief around it. Not a broad emotional territory, but a precise gap between what customers were trying to do and what the market was currently offering them. Those briefs produced work that actually moved commercial metrics, because the insight was sharp enough to point to a real solution rather than a generic one.

This is also where the connection between unmet needs and genuine growth becomes clearest. Marketing that addresses a real, specific unmet need doesn’t need to shout. It doesn’t need a massive media budget to get attention. It resonates because it’s saying something true that the customer hasn’t heard before. That’s a fundamentally different proposition from marketing that’s trying to make an undifferentiated product sound appealing through tone of voice and production values.

The Vidyard Future Revenue Report makes a related point about pipeline generation: the teams generating the most sustainable pipeline are the ones whose messaging is grounded in specific buyer needs rather than product features. The insight infrastructure and the commercial output are more connected than most organisations treat them as being.

The Compounding Effect of Getting This Right Over Time

There’s a version of this work that’s done once and filed. A company identifies an unmet need, addresses it, sees a lift in retention or acquisition, and then moves on. That’s better than nothing, but it misses the compounding effect that comes from building unmet needs identification into the ongoing rhythm of the business.

Markets shift. Expectations reset. The thing that differentiated you eighteen months ago is now table stakes. New competitors enter with a sharper answer to the need you were addressing. Your customers’ context changes and their needs change with it. The gap you closed last year opens somewhere else.

The companies that sustain growth over time are the ones that treat this as a continuous discipline rather than a periodic project. They have mechanisms for capturing customer signals on an ongoing basis. They review them regularly in commercial decision-making forums. They have a clear path from insight to action that doesn’t require a six-month sign-off process.

When I was growing an agency from around 20 people to over 100, the single biggest commercial advantage we had wasn’t our capabilities or our pricing. It was that we were genuinely curious about what our clients needed that they weren’t getting elsewhere, and we were willing to build for it even when it didn’t fit our existing service model. That orientation, more than any specific product decision, was what drove the growth.

Most of the strategic frameworks for sustainable growth, whether you’re looking at growth hacking approaches or more traditional market development, eventually point back to the same foundation: a genuine understanding of what customers need that they’re not currently getting, and the commercial willingness to build for it.

If you want to build a go-to-market approach that’s grounded in this kind of thinking rather than just optimising existing channels, the Go-To-Market and Growth Strategy hub is a good place to work through the broader architecture, from positioning and segmentation through to channel selection and measurement.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions