When AI names three tools and skips yours, it isn’t rating you badly. It’s repeating the story the market already told it.
Ask ChatGPT to recommend a tool in your category and you’ll get an answer with startling confidence. Three or four names, a sentence of reasoning each, maybe a “depends on your needs” hedge at the end. Notice what’s missing? Any hint that the model is choosing at all. It sounds like it’s reporting a fact.
It isn’t. That answer is the product of a story the model absorbed from the open web, and your competitors probably wrote more of it than you did. This piece is about how that story gets built, why it favors the brands it favors, and what you’d actually change to shift the default answer in your direction.
Why ChatGPT Picks One Brand Over Another
ChatGPT doesn’t run a scoreboard. It isn’t tallying feature counts or comparing pricing pages side by side before it answers. When it recommends a brand, it’s reconstructing what the internet seems to agree is true about your category and then naming the brands that best fit that agreement.
So the real question isn’t “how good is my product.” It’s “what does the model believe my category is for, and who does it think owns each version of that job.”
Picture two project-management tools. One gets described across blogs, forums, and comparison posts as “the simple option for small teams.” The other keeps showing up in threads about “scaling engineering orgs.” Now someone asks ChatGPT to recommend a tool for a growing startup. The model reaches for the second brand almost every time. Not because it’s better. Because the story slots it into that request cleanly.
That’s the frame doing the work. The model adopts a frame for your category. Then it picks the brand that best matches the frame it adopted. If the answer keeps naming your competitor, it usually means their framing of the problem is the one the model learned, and your product reads as an answer to a question nobody asked it.
Try this yourself. Ask ChatGPT the exact question your best customer would ask before buying. Then ask a slightly different version with different priorities. Watch how the recommended names change. You’re watching the frame shift, and you’re watching which brand each frame favors.
The Consensus Behind Every Recommendation
Here’s the part most teams miss: the model’s opinion of you is downstream of everyone else’s. AI search is a consensus machine. It reads what analysts, reviewers, Reddit threads, competitor comparison pages, and your own site all say, then it settles on the version of the story that appears most consistent across those sources. The recommendation is just that consensus, spoken back to you as advice.
This matters because it changes where the fight actually happens. You can’t argue with the model. You can’t optimize a single page and expect the answer to flip. The answer lives in the aggregate. If ten independent sources describe your competitor as “the enterprise standard” and only your homepage claims you belong in that conversation, the model sides with the ten. It has no reason not to.
Consensus also explains the frustrating gap between what you are and what AI says you are. Maybe you shipped the strongest security features in the category last quarter. If the market’s written record still frames security as your competitor’s territory, ChatGPT will keep handing them that recommendation. The model isn’t reading your changelog. It’s reading the settled story, and the settled story lags reality.
The upside is that consensus is observable and it’s shapeable. Every recommendation traces back to real sources: specific articles, specific comparison posts, specific threads the model leaned on to build its answer. Those inputs are where the recommendation is really decided. Mavel reads that upstream layer, the human-market narrative that feeds the model, so you can see whose frame is winning and which sources are carrying it.
That’s the shift in thinking this whole article rests on. Stop treating the AI answer as a verdict about your product. Treat it as a mirror of the consensus around your product. Change the consensus and the recommendation follows. Leave it alone and your competitors stay the default, no matter how good the thing you built actually is.
It’s Not About Who’s Mentioned Most
There’s a comforting idea floating around AI-visibility circles: get mentioned enough times and the recommendations follow. Rack up citations, show up in more answers, and you’ll eventually become the pick. It’s clean, it’s countable, and it’s wrong.
Mentions and recommendations run on different tracks. A model can name you in fifteen answers and still route the buyer to someone else when the question gets specific. Try this: ask ChatGPT “what are the top project management tools” and you’ll get a list where your brand might appear. Now ask “what should a 20-person design agency use to manage client work.” Watch how the list shrinks, reorders, and picks a winner. That second answer is the one that matters, and being on the first list did almost nothing to earn you the second.
The gap comes down to what the model actually learned. Presence tells you a name showed up in the training data or the retrieved sources. It says nothing about the role that name plays in the story the model tells about your category. You can be the brand everyone mentions and still be framed as the expensive option, the legacy option, the one people used to use. Meanwhile a competitor with fewer mentions gets described as the obvious choice for the exact buyer asking the question. The model isn’t counting appearances. It’s reading consensus and repeating the frame that consensus built.
This is why a vanity score misleads. Share-of-voice measures how loud you are. It doesn’t measure whether the market’s description of you lines up with the recommendation buyers want. Two brands can have identical mention counts, and one wins every specific prompt because the story attached to its name matches what people ask for.
What decides the recommendation is narrative share: whose framing of the category the model adopts when it answers. If reviewers, forums, and analysts consistently describe your competitor as “the tool built for scaling teams,” that phrase becomes the model’s default lens. You can be mentioned more and lose anyway, because you’re mentioned inside their frame instead of your own.
How Competitors Become the Default Answer
A default answer doesn’t get assigned. It accumulates. The model reads thousands of sources describing your category, and it settles on the version of the story that shows up most consistently across the ones it trusts. Whoever owns that consistent description becomes the default, and everyone else gets measured against it.
Picture two analytics tools launched the same year with similar features. One of them gets written about as “the standard for product teams” in a widely-cited comparison post. A few Reddit threads echo the phrase. A popular newsletter repeats it. G2 reviews start using the same language because the reviewers absorbed it too. Within a couple of years, that phrase is baked into how the whole internet describes the category. When someone asks ChatGPT “best analytics for a product team,” the model has already learned who the standard is. The other tool isn’t unknown. It’s just filed under “alternative to the standard,” and that filing decides how it gets recommended.
That’s the mechanism. Consensus forms upstream in human sources: comparison articles, review sites, community threads, docs, and the way sales teams and customers repeat certain phrases. AI search sits downstream of all of it. The model doesn’t invent a preference for your competitor. It inherits one that the market already wrote down, and it hands that inheritance to every buyer who asks.
The part most teams miss is that the default is a specific frame, not a general reputation. Your competitor didn’t win because they’re “better.” They won because a repeatable description of the category got attached to their name, and that description matches the questions buyers actually type. Change the description that dominates the sources, and you change the answer the model gives.
This is exactly what Mavel reads. Instead of showing you that a competitor keeps winning, it traces the sources and framing the model drew on to build that default, so you can see which pieces of consensus are working against you and which are still up for grabs. Want to see whose frame the answer in your category is actually built on? That’s the read we start with.
Reclaiming the Recommendation
If recommendations flow from consensus, then changing the recommendation means changing the consensus. That’s slower than buying keywords and harder than shipping a landing page. It’s also the only thing that actually moves the answer.
Start by figuring out what the model already believes. Ask ChatGPT to describe your category. Ask it to name the best options for a specific use case, the kind your ideal buyer would type. Then ask it why. Not “who’s the best project management tool” but “which project management tool should a 12-person design agency pick, and why.” The “why” is where the frame shows up. You’ll hear things like “known for simplicity” or “popular with enterprise teams” or “great for developers.” Those phrases are the consensus talking. They’re the compressed story the model learned from everything the market has said about that space.
Now compare that story to how you want to be seen. This is the gap that matters. Maybe the model files you under “cheap alternative” when you’ve spent two years moving upmarket. Maybe it doesn’t associate you with the use case you actually win. Maybe it invents a limitation you fixed in 2023. Each of those is a specific, fixable disagreement between the market’s story and yours.
Reclaiming the recommendation isn’t about getting mentioned more often. A brand can appear in fifty answers and still lose every one because the frame around it is wrong. What you’re after is narrative share: whose version of the category the model treats as true. When the consensus describes your category the way you describe it, the recommendation follows without you begging for it.
The catch is that you can’t argue with a model directly. There’s no support ticket. The model reflects what the sources say, so the work happens upstream, in the material the model reads. That’s why source intelligence matters more than a visibility score. A dashboard can tell you you’re losing the “best for agencies” prompt. It can’t tell you that the loss traces back to three comparison articles and a Reddit thread that all frame your competitor as the agency choice. The sources are where you gain influence over the answer.
What to Actually Ship to Change It
Once you know the frame and the sources behind it, the work gets concrete. Here’s the shape of it.
Fix the sources the model actually reads. If a G2 category page, a comparison roundup, and a couple of high-traffic blog posts are doing most of the framing, those are your priorities. Not because they get human traffic, but because the model cites them. Get your positioning right where the model is looking. That might mean updating your own docs so they describe the use case you want to own, in plain language a model can quote. It might mean earning a mention in the comparison article that currently leaves you out.
Close the perception gap in your own words. If ChatGPT thinks you’re the budget option and you’re not, the correction has to exist somewhere the model can find it. Publish the case for how you actually want to be seen. Say it clearly, say it in multiple places, and say it the way buyers ask about it. Models learn from repetition across independent sources, so one page won’t do it.
Feed the prompts, not the keywords. Buyers and models both start from questions. Map the real prompts in your category, the ones people type when they’re deciding. Then check where your story shows up and where it’s missing. If you’re absent from “best X for remote teams” and that’s a segment you win, that’s a gap with a clear fix: create and place the material that answers that prompt with your frame in it.
Prioritize ruthlessly. You can’t rewrite the whole internet’s opinion of your category. You can change the handful of inputs that shape the most answers. That’s the point of tracing sources instead of staring at a score. You act on cause, not symptom, and you skip the busywork that never touches the recommendation.
Want to see the frame the model built about your category, the sources feeding it, and the short list of moves that would shift it? That’s the whole job. Mavel measures narrative share: whose story the model tells and what to ship to change it.
