Positioning
Is it a product problem or a positioning problem? How to know before you pivot again
TL;DR
Most growth stalls at seed to Series A are positioning failures wearing product clothing, and the misdiagnosis costs six to eighteen months of rebuild nobody needed. A product problem means the product can't deliver what the right customer needs. A positioning problem means it can, and buyers still can't tell it was built for them. Five signals separate the two, and the evidence already sits in your CRM. Run the diagnostic in a week, before you authorize the rebuild.
Growth flattens, and the first place we look is the roadmap.
It's the wrong place most of the time. The product can usually do the job. Buyers just can't tell it was built for them, which category it belongs to, or why it beats the four tabs open next to ours.
Those two failures feel identical from the inside. They cost wildly different amounts to fix.
The rebuild reflex
Call it the rebuild reflex. Growth stalls, so we reach for the roadmap, because the roadmap is the one lever we're actually holding.
Positioning sits somewhere between marketing, sales, and the buyer's head. Nobody controls it directly, nothing about it feels shippable, and there's always a feature that already feels late. So the team commits to the rebuild.
Six months go by. Sometimes eighteen. The feature ships.
Conversion doesn't move. Churn doesn't move.
The bill runs well past the engineering hours. Every customer conversation we skipped for two quarters.
The morale of a team that built something nobody asked for. A round raised to fund work that solved nothing.
Plenty of companies that shut down blaming "no market need" had a market. They never got the buyer to see the product was for them, and that failure got filed under the wrong heading on the way out.
The question worth asking before anyone authorizes a rebuild isn't what to add. It's whether the market is rejecting our product or our explanation of it.
What the label leaves out
A nutrition label is complete, accurate, and independently verified. Twelve grams of protein, four of sugar, every ingredient listed in order of weight.
It will never tell you whether the food is for you. That's a different question, and no amount of additional detail on the panel gets you closer to answering it.
Most homepages are nutrition labels. Every claim true, every capability accounted for, and nothing anywhere on the page that tells a specific person in a specific mess that this was made for them.
Ask B2B SaaS marketing leaders and almost all of them describe their own messaging as trapped in a "sea of sameness." Which is what happens when everyone publishes an ingredient panel and nobody writes the sentence about who should eat this.
A product problem means what's in the box genuinely isn't enough for the customer we want. A positioning problem means it is enough, and the label is doing all the talking.
The related patterns get fuller treatment in Your Positioning Sounds Right. That's Why Nobody Is Buying. and Why Your SaaS Revenue Is Flat Even Though You Have Product-Market Fit.
The intake form
Users never file positioning complaints. They can't. They only have product words.
Think about the clipboard at a doctor's office. You write down what hurts, when it started, and what you've taken for it.
Every box asks about symptoms, so symptoms are all you can give. Nobody expects the patient to fill in the diagnosis.
"I expected this to do X" arrives on that clipboard looking like a feature gap. Usually the homepage promised X while the product was built for Y.
"It's too complicated" arrives looking like a usability gap. Usually it was sold to a buyer it was never for.
So sort what comes in. A capability gap means the product genuinely can't do something the right customer needs. An expectation gap means the product didn't match what we promised.
Only one of those gets fixed in code.
The diagnostic
Run the last 90 days against five signals. Each one splits the same way.
Where drop-off clusters
A product problem clusters drop-off right at the core workflow. Users got there, tried it, left, and power users never appeared even inside best-fit accounts.
A positioning problem clusters earlier, with signups confused about what to do first. Or later, with users who got real value and never expanded.
What the losses say
A product problem reads as the same missing capability turning up in every segment. Real gaps ignore segment, and different buyers point at the same hole.
A positioning problem reads as "went with another solution," "decided to build internally," "no clear ROI," "couldn't get internal alignment." Those losses are about story.
The ICP sentence
Have the founder, the head of sales, and the lead marketer each write one sentence naming the best-fit customer, separately, then compare. A team that agrees on who it serves and still misses usually has a real gap.
Three different sentences means the site speaks to one customer, sales chases another, and the roadmap serves a third. The ICP Playbook walks that one all the way down.
The first-call question
"Can you do X?" is a capability question. "How is this different from [adjacent category]?" is a map question.
When the second one shows up on every first call, buyers can't place us on their map of the market. Category is a positioning choice.
Champion behavior
A product problem disengages the champion the moment they hit the wall. A positioning problem keeps them warm all the way through the trial, right up until they go quiet during procurement.
Most B2B buying teams argue their way to a decision. A champion who walks into that room carrying a feature list isn't walking out with a signature, which is the whole argument in Your Champion Loves Your Product. Here's Why the Deal Still Dies.
Three or more leaning the same way is the answer. A split almost always means positioning, because real product problems show up everywhere at once.
The cheaper move
Perplexity is the clearest public version of the choice. The product was an answer engine sitting inside a crowded "AI assistant" frame, shoulder to shoulder with ChatGPT, Claude, Gemini, and a dozen others. Buyers had no reason to pick the smaller assistant.
The team moved the category instead of the product. AI search engine. The comparison stopped being "another chatbot" and started being "the thing after Google," and the underlying technology stayed roughly where it was.
That's the billion-dollar version of a move that's available at $200K MRR for the price of a week of writing.
The week you already have
No consultant. No offsite. All five inputs already sit inside the company.
Pull the last ten lost deals and read the actual notes, not the CRM dropdown. Tag each one capability or story. Seven or more on the story side and you have your answer.
Call three paying customers. Not a survey, a call.
Ask what was happening in their world right before they went looking, who else they considered, and how they described us internally to get the money approved. If their words aren't on our homepage, the positioning is off.
Have the three leaders write the ICP sentence separately, then read all three out loud in the same room.
Find the biggest drop in the funnel. Signup-to-activation is positioning, since the homepage promised the wrong thing. Activation-to-paid against a feature wall is product.
Trial-to-close dying in committee is positioning again, one floor up. We took the after-activation version apart in Why Your SaaS Customers Are Churning (And It Is Not the Product).
Email the last five lost prospects and ask what they bought instead. Most people answer if the ask is short and honest. Their answers tell you which category they filed us under, and that filing is our real positioning regardless of what the website claims.
Five working days, and the output is a clear read on whether the next investment is engineering or language. If it's going to a board, lead with the diagnostic and put the rebuild plan behind it. A board would rather approve a $0 reposition that worked than a $2M rebuild that didn't, and How to Present Your GTM Strategy to Your Board (And Actually Get Buy-In) covers how to frame that.
The mix is real, and the mix matters. When most of it is positioning and a sliver is a genuine gap, ship the gap fast and put the strategic weight on the language. When most of it is product, the rebuild is honest work, and the team deserves a straight answer about how long it takes.
What ends companies is reaching for the expensive answer while the cheap one sits on the table.
Read your own homepage the way you'd read a label. Then ask whether anyone holding it could tell it was made for them.
What to do next
If the five signals came back leaning positioning, the fix lives in who the product is for and why that person should care.
A Bare Strategy positioning audit runs the diagnostic with you, then rebuilds the language around the customer the product already serves best.
If that's where you are, start here. The first conversation is free.
Frequently asked questions
Run the 5-signal diagnostic on the last 90 days. Look at where users drop in the funnel, what reasons cluster in win/loss notes, whether three leaders write the same ICP sentence, what prospects ask on first calls, and whether champions stay warm or go quiet. Three or more signals leaning positioning means it's positioning, and the fastest single test is a champion who loves the product while the deal dies in committee.
A product-market fit problem means the product can't deliver the value the market needs at all, so best-fit customers churn and power users never appear. A positioning problem means fit exists with the customers who buy and stay, while the funnel leaks because most buyers can't tell who the product is for, which category it sits in, or why to choose it. Fit asks whether the product delivers value, and positioning asks whether the right buyer can see it was built for them.
Reposition first, almost every time. A reposition takes one to four weeks and is reversible, while a rebuild takes six to eighteen months and binds the company's next year of strategy. If three or more signals point to product, meaning a real feature gap, churn that ignores segment, and losses decided on capability, you have the evidence to justify the rebuild and a sharper brief for what to build first.
Constantly. Users describe complaints in product language because product language is all they have, so "I expected this to do X" sounds like a feature gap when the homepage promised X and the product was built for Y. Sort what comes in, since a capability gap means the product genuinely can't do what the right customer needs, and an expectation gap means the product didn't match what the marketing promised.
Related reading
The author
Nick Pham
Founder of Bare Strategy. Twenty years in B2B marketing, the last decade in product marketing inside enterprise software.
More about the operator →If this is where you are
Bring the problem, not a brief, and you'll leave the first conversation with something useful either way.
Start a conversation