Scenario Surfacing
Scenario Surfacing is a Discovery Optimization research methodology that asks whether you are recommended when a real problem shows up in natural language. Most buyers do not start by naming a category (that question is Category Visibility). They start by describing a situation: something broke, something is slow, the team outgrew a tool. They tell the assistant what is wrong and ask what to do. This methodology measures whether you surface at that moment, before the buyer has framed their problem as a category at all.
When to use it#
Run Scenario Surfacing when:
- You want to test the earliest, messiest part of the journey, where buyers describe pain rather than shop for a category.
- Your product solves a recognizable problem people can articulate in their own words.
- You suspect you are invisible until someone already knows they want your category.
How the method works#
The session generates five problem-framed questions, each opening with a first-person situation: "My team just hit X," "I need to solve Y," "We are evaluating a change because Z." These are not category queries. They are the way a founder or engineer actually talks to an assistant when something is wrong.
The scenarios stay grounded in your category without naming it, and never name your brand. The point is to see whether the assistant connects a described problem to you as a solution, which is a harder and more valuable test than category recall.
Each prompt runs in search-enabled mode. The session records whether you surface, and just as importantly, what the assistant recommends instead when it does not reach you.
A worked example#
Same category as the other chapters, project management for engineering teams. Category Visibility asked "what do teams use." Scenario Surfacing starts from the pain, before the buyer has even decided they are shopping for a project management tool:
The pain comes first: "Our eng team has grown to 30 people and our GitHub issues are total chaos. Planning happens in three different spreadsheets and nobody trusts any of them. How do other teams actually keep this organized?"
A situation, not a category: "We keep missing deadlines because no one has a clear view of what everyone is working on. We live in GitHub and Slack. What should we change?"
Notice the buyer never says "project management software." They describe a mess. The test is whether the assistant hears "30-person eng team, GitHub chaos, missing deadlines" and routes them to your category, and to you specifically. If you sell a dev project management tool and the assistant suggests "better issue hygiene and a tool like Linear or Jira" without you, you are invisible at the exact moment the buyer is most ready to act.
How to read the results#
- You surface from the pain itself. Excellent. You are connected to the problem, not just the category label. This is the hardest visibility to earn.
- You surface only once the category is named, not from the scenario. You have category presence but no problem association. The opportunity is content that speaks to the symptom, not the product.
- You do not surface at all. The assistant does not associate your category, or you, with the problems your buyers describe. Start with the problem language your customers actually use.
What to do about gaps#
- Publish content framed around the problem and symptoms, in the buyer's words, not around your feature list.
- Make sure your problem framing is extractable and concrete enough for an answer engine to match a described situation to it (see AI Visibility).
- Re-run with the same scenarios to track whether you start getting reached from the pain.
Run it in Rampify#
Scenario Surfacing runs as a Discovery session. Make sure your business profile describes your category clearly, then use the Connect Rampify button at the top of this page to start it. The agent writes the scenario prompts, probes the answer engines, and turns each gap into a spec you can act on.
See if you surface from the pain
Run a Scenario Surfacing session and find out whether the answer engines reach you when buyers describe a problem instead of a category.
Start free