A product idea is not evidence that a customer has a consequential problem—or that a workable solution can support a business. Before committing to a build, identify who struggles, what they do today, and what evidence would change your decision. Then test whether a solution is desirable, usable, feasible, and viable; set a price against customer value, demand, and delivery costs; and explain the offer in terms the intended audience recognizes.
This chapter applies that method to FoxyInvoice as a product-building exercise, not as a report of established customer research. Its actual target segment, workflow, features, price, competitors, and traction are not established here; treat them as hypotheses until project-specific evidence supports them.
As an Amazon Associate I earn from qualifying purchases.
Start with the customer’s problem, not the product pitch
Product discovery is ongoing work to identify customer needs, choose worthwhile problems, and test and refine possible solutions before and during delivery. It is not a kickoff workshop whose job is to approve an idea the team has already chosen. Aha! describes discovery as a way for product teams to identify real customer needs and deliver suitable solutions; its guide, updated August 2026, emphasizes making the work ongoing, inclusive, real-time, centralized, and transparent (Aha!’s product discovery guide). Atlassian likewise treats discovery as part of product work rather than a one-time phase (Atlassian’s product discovery guide).
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsFor FoxyInvoice, begin by investigating people and situations rather than assuming that a particular invoicing feature is wanted. A pain point may be a real or perceived problem within a system, as Digital.gov’s human-centered design guidance explains (Digital.gov’s guide to finding opportunities). Following the customer’s experience across touchpoints can reveal root causes and consequential moments that a feature request alone might obscure.
#1 Best Overall
Map the situation and the current workaround
For each candidate problem, establish who experiences it, when and where it happens, what consequences follow, how often it occurs, and what the person does now. Look at relevant user feedback alongside support records, analytics, and other information the team already holds. Ask questions such as “Who has this problem?”, “How painful and frequent is it?”, and “What are people doing today instead?” These are questions to investigate, not answers to assume about FoxyInvoice’s customers.
Pay attention to the difference between the person who experiences a problem and the person who would choose or pay for a solution. They may be the same person, or the buying decision may involve someone else. Record the existing alternatives—including manual workarounds and doing nothing—so a proposed product is compared with what people actually use, not only with another product category.
Compare problems without pretending to have a formula
When several opportunities appear plausible, compare them across the factors that affect both customer value and the team’s ability to learn:
- How often the need arises and how severe its consequences are.
- What the current workaround costs in time, money, risk, or frustration.
- Who experiences the problem, who decides, and who pays.
- Whether the team can reach relevant people and observe the situation.
- What substitutes already exist and why customers use them.
- Whether a feasible solution could create a sustainable business.
This is a synthesis framework, not a validated scoring model. Use it to make trade-offs visible and guide research, not to manufacture certainty with a precise-looking score.
Rank #2
Run small tests that could change a decision
Research is useful when it informs a choice: whether to pursue a problem, change the audience, test a different solution, or stop. Before each interview or experiment, write down the assumption at risk, the evidence that would support or weaken it, and what you would do in either case. This prevents activity from being mistaken for learning.
- State the assumption. For example, a team might hypothesize that a particular group regularly encounters a specific invoicing difficulty. Keep this as a hypothesis until customer evidence supports it.
- Choose the smallest useful test. Talk with people who have direct experience, examine relevant existing data, or test a lightweight representation of a proposed solution. Choose a test that addresses the uncertainty—not merely one that produces a favorable reaction.
- Gather evidence about behavior and context. Ask about recent examples, consequences, current workarounds, and decisions people have actually made. Separate what participants did from what they predict they might do.
- Update the choice. Record what the evidence changes: the problem, audience, solution, price assumptions, or decision to proceed. If nothing could change the team’s plan, the test was not designed to answer an open question.
There is no universally correct number of interviews, survey responses, or threshold that proves a product idea. The useful sample and method depend on the decision, the people affected, and the evidence needed. Strategyzer describes a client that reportedly avoided $800,000 in planned software development spend after discovering no customer interest in the planned idea; this is the provider’s client anecdote, not a general savings estimate or independently verified causal result (Strategyzer’s Understanding Customers course).
For practical guidance on customer conversations, Rob Fitzpatrick’s The Mom Test focuses on learning from conversations rather than seeking compliments for an idea. A book can help structure interviews; it cannot validate a product in place of evidence from its prospective customers.
Separate desirability, usability, feasibility, and viability
A positive reaction to an idea does not establish that customers will use it, that the team can build and support it, or that it can sustain a business. Treat these as distinct risks to investigate:
Rank #3
- we like to ship out right away
- Desirability: Does a particular group have a meaningful need, and would a solution address it well enough to merit adoption?
- Usability: Can intended users understand and complete the important tasks in the proposed solution?
- Feasibility: Can the team build, operate, and support the solution with available technical and organizational capabilities?
- Viability: Can the offer work for the business, including its costs, price, demand, and route to customers?
These questions interact, but one cannot stand in for another. Evidence that a problem exists is not proof that a specific interface will work; a technically possible build is not proof of demand. Discovery should continue as delivery produces new evidence and as customer needs or market conditions change.
Set price using value, demand, and the economics of delivery
A defensible price has both a value-informed ceiling and a cost-informed floor. The ceiling depends on the benefits customers recognize and receive; the floor depends on the full cost of delivering the offer and the minimum return the business needs. Between them, demand at different prices matters: a price that appears attractive in an interview may not produce enough customers or revenue in practice.
McKinsey’s pricing guidance stresses understanding customer benefits to establish a price ceiling and cautions that cheaper is not automatically better; internal assumptions can also bias research (McKinsey’s “Pricing new products”). The article is useful for the underlying method, not as a current market benchmark for FoxyInvoice or any particular software category.
Recommended Free Tools
Estimate what the customer values
Investigate the benefits customers receive, including time saved, reduced risk, or improved outcomes where relevant. Avoid limiting questions to benefits or substitutes the team already expects. In McKinsey’s illustrative valve-supplier example, open questions about customer maintenance economics produced a substantially different willingness-to-pay result than an initial comparison with another valve. That example shows why a familiar competitor price may miss value; it does not establish a universal effect or a FoxyInvoice price.
Understand demand across price points
Explore whether demand changes at different prices and what customers compare when making a purchase decision. A single stated willingness-to-pay answer is not a complete pricing strategy: people may answer differently from how they behave, and the team’s framing can shape what they say. Combine customer evidence with evidence about real choices and relevant alternatives where available.
Calculate the floor from complete costs
Account for the costs required to deliver and support the product, along with allocated costs and the minimum acceptable return. Compare that floor with the value ceiling and likely demand. If the market will not support a price above the floor, revisit the product scope, delivery model, or business model instead of relying on an unsupported forecast to conceal the gap.
Competitor pricing and cost-plus arithmetic can inform the decision, but neither settles it alone. Price also communicates how an offer is positioned, so evaluate the value customers perceive alongside the margin and demand the business needs.
Position the offer around an evidenced difference
Positioning defines the market context and the place an offer should occupy relative to alternatives. The value proposition explains the specific benefits it offers customers; messaging adapts that explanation for a particular audience and channel. Atlassian describes product positioning as defining a product’s place in the market and shaping how customers perceive it (Atlassian’s product positioning guide).
Best Value
- If you want to build a better future, you must believe in secrets.
- The great secret of our time is that there are still uncharted frontiers to explore and new inventions to create. In Zero to One, legendary entrepreneur and investor Peter Thiel shows how we can find singular ways to create those new things.
To develop a positioning choice, establish the target audience, the problem they care about, the alternatives they consider, and the outcome that evidence supports. Translate product features into outcomes the audience can understand, but do not claim that an outcome is unique until alternatives have been checked. Customer language and evidence should support the claim.
Use a positioning statement as an internal test
A working statement can make the strategy explicit:
For [defined audience] who [specific problem or need], [product] is [category or relevant alternative] that [distinctive, evidenced outcome], unlike [alternative] because [substantiated difference].
Fill the brackets only when the audience, problem, alternatives, and difference are sufficiently understood. This is an internal tool for checking whether the choices fit together, not customer-facing copy and not permission to present an unverified FoxyInvoice claim as fact.
Connect the story to the route to market
A go-to-market story needs evidence about the buyer, their pain, the alternatives, and meaningful differences in the offer. Salesforce recommends customer and competitive research and mapping customer problems to solutions in its guide to go-to-market strategy (Salesforce’s go-to-market guide). Use those findings to decide whom to reach, what problem to lead with, and which outcome to explain—not to substitute a compelling message for evidence that the offer works.
Decision checklist for FoxyInvoice
Before committing further effort to a problem, price, or positioning claim, check whether the team can answer these questions with evidence:
- Who experiences the problem, who makes the buying decision, and who pays?
- Where does the problem occur, how often, and with what consequences?
- What do people do today, including workarounds and competing alternatives?
- Which assumption is most uncertain, and what small test could change the next decision?
- What evidence addresses desirability and usability separately from feasibility and viability?
- What customer benefit informs the price ceiling, what complete costs inform the floor, and what evidence indicates demand at different prices?
- Which audience, problem, alternative, and differentiated outcome can the team support with customer evidence?
- What new evidence during delivery would cause the team to revise the product or its positioning?
Until those questions are answered for FoxyInvoice, its segment, workflow, feature set, price, competitors, and traction remain open product hypotheses—not established claims.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
