Crafting a Solution-Neutral Opportunity Thesis: Users, Needs, Context, and Outcomes

Hello. Last lesson separated a person’s description of heavy flow from a clinical diagnosis of heavy menstrual bleeding. That distinction matters here: you can investigate a consequential management problem without deciding who meets a clinical threshold—or what product should exist.

In this lesson, you’ll turn that framing into a solution-neutral opportunity thesis: a short, testable statement naming who experiences a difficulty, when it arises, what current options fail to address, and what better outcome the person wants. It will give your ongoing customer conversations direction without turning them into a pitch for a tech solution.

Start on the customer side of the canvas

A useful opportunity thesis describes the customer’s situation before it describes your offering. The Value Proposition Canvas makes that separation visible: its customer profile is on the right, while the proposed value map is on the left.

Strategyzer’s explanation of the canvas gives three questions to hold in mind: What is the person trying to get done? What makes that difficult? What would a better result mean to them?

In heavy-flow management, a job might be getting through a workday, sleeping without repeated checks, or deciding whether to seek care. A pain might be interrupted work, the cost of backup supplies, or uncertainty about whether an experience merits discussing with a clinician. A gain is the improvement the person seeks—perhaps fewer interruptions, more confidence making plans, or a clearer account of their experience for a care conversation.

These are possibilities to investigate, not a single universal heavy-flow journey. In particular, “I want an app” names a possible product, while “I want to make plans without constantly accounting for leaks” names a desired outcome. The second leaves room for a better physical product, different access to facilities, clearer information, a change in care, or some combination.

Make the four parts do distinct work

An opportunity thesis can fit in one or two sentences:

For [user] in [specific context], [job] is difficult because [unmet need or gap in current options]. They want [desired outcome].

Each part limits a different kind of founder guesswork.

User identifies people by the experience relevant to the problem, rather than by a diagnosis they may not have or a broad demographic category. “People who describe recurring, difficult-to-manage flow” may be a reasonable starting group. It is still broad; later evidence may show that some circumstances within it matter much more than others.

Context is the moment in which the need becomes pressing. “During shifts with restricted breaks” says more about the management challenge than “during menstruation.” The context can include a task, setting, constraint, or trigger; it need not be a location or a demographic trait.

Unmet need explains why the job remains difficult despite what people can already do. It is not just a symptom. If someone carries spare supplies but cannot reach a bathroom when needed, the gap may concern reliable access and control over timing. If someone is unsure how to describe changes in their bleeding to a clinician, the gap may be different. Do not combine those into one need merely because both involve heavy flow.

Desired outcome describes a meaningful improvement in the person’s life, not a feature or an unsupported medical promise. “Complete a shift with fewer unplanned interruptions and less worry about bleeding through” is more useful for discovery than “receive AI-powered predictions.” It also avoids promising to reduce blood loss or identify a condition.

The thesis should be specific enough to be wrong. “People with periods need better support” is hard to investigate because it leaves the user, situation, and gap undefined. Yet specificity must not masquerade as evidence: an exact age band, diagnosis, or preferred technology does not belong in the thesis simply because it sounds commercially precise.

Use existing evidence without treating it as your customer base

Published qualitative research can show what kinds of difficulties are plausible. It cannot establish that your prospective users experience the same ones. In the study below, participants described precautions, disruption, embarrassment, and sometimes a long period of treating their difficulties as normal.

The study points toward several possible opportunity theses, not one ready-made answer. Someone whose main difficulty is missing work because of flooding may seek a different outcome from someone who can manage daily activities but wants to understand a changing pattern. If an interviewee says a current approach works well, that also matters: they may not have the unmet need you hypothesized.

The lesson for a founder with customer conversations underway is to keep source, observation, and inference separate. “Participants in a published study described avoiding activities” is a source finding. “An interviewee told me about cancelling a recent event” is a direct account. “Many potential users will pay for discreet planning support” is a venture assumption. A thesis may be informed by the first two, but it should not quietly present the third as established.

Write a thesis that can survive a change of product

This short video demonstrates how to narrow a problem statement to a user, a situation, and an obstacle without putting the proposed solution in the statement.

Consider this illustrative hypothesis, not a finding from the study or from your interviews:

For people who describe recurring, difficult-to-manage flow and work shifts with limited bathroom access, getting through a high-flow workday is difficult when they cannot reliably check or change supplies during restricted breaks, even if they bring backups. They want to finish shifts with fewer unplanned interruptions and less worry about bleeding through.

You can locate all four parts: the user has a relevant experience and constraint; the context is a high-flow workday; the unmet need concerns the limits of an existing workaround; and the outcome is expressed in terms of the person’s day. Nothing in the statement requires an app. That is a strength, not a lack of ambition: a future concept can be judged against the need rather than written into it.

Contrast it with:

“We will build an AI app for women with HMB that predicts leaks.”

That sentence starts with a technology, assumes a clinical label, and makes a performance claim. It leaves the circumstances of the difficulty and the outcome people actually value largely unstated.

Solution-neutral does not mean vague or indifferent to technology. You can retain an app as a concept worth exploring privately. The opportunity thesis acts as a constraint on that idea: if interviews show that the central obstacle is lack of timely bathroom access, a prediction feature alone may not resolve it. If interviews reveal a different obstacle altogether, the thesis—and perhaps the concept—should change.

Keep the statement provisional, but useful

A sound first thesis is an explicit best current explanation of a pattern you are investigating. It should remain open to three important corrections.

First, the user may change. People who use the phrase “heavy flow” might face quite different practical difficulties, while some people who call their periods “normal” may describe substantial disruption. Your previous lesson’s distinction helps you avoid filtering either group out prematurely.

Second, the gap may change. An interviewee’s current workaround tells you more than a general expression of frustration. If they describe bringing supplies, adjusting schedules, or seeking care, you can understand what each action accomplishes and what it leaves unresolved. Conversely, lack of a workaround alone does not prove there is no need; it may mean the person sees no workable option, has normalized the difficulty, or does not regard it as a priority. Those possibilities require listening, not an automatic conclusion.

Third, the outcome may change. “Avoid leaks,” “spend less on backups,” and “feel prepared to discuss symptoms with a clinician” are distinct aspirations. A thesis becomes clearer when it names the improvement most closely tied to the particular user and context it describes. It should not promise that any startup offering can deliver that improvement yet.

A final check is whether the statement still makes sense if the proposed product disappears. If removing “app,” “AI,” or “tracker” leaves no identifiable user difficulty, you have written a concept pitch rather than an opportunity thesis. If the statement names a real situation and a consequential gap, it can guide discovery even while the solution remains undecided.

Takeaways

A solution-neutral opportunity thesis names a user, context, unmet need, and desired outcome. Start with the customer’s job, pains, and gains; describe why existing approaches fall short; and keep clinical labels and product claims separate from what people have actually reported. The strongest early thesis is neither universal nor falsely certain: it is a focused hypothesis that customer evidence can revise.

Next, you’ll make the uncertainty in that hypothesis more explicit by mapping the venture’s assumptions across desirability, viability, feasibility, trust, and regulatory risk.