Asking “would you pay for this?” can produce an agreeable answer without revealing whether the problem has ever justified spending. Past behaviour offers a different kind of evidence, provided the question does not become an intrusive sales qualification script.
For founders researching a workflow, ask about resources already committed to solving it. Money is one resource; staff time, workarounds and abandoned attempts can also explain the decision context.
What does past spending tell a founder?
It can show that a person or organisation took a concrete action under specific circumstances. It does not prove that they will buy your proposed product at a particular price.
The respondent may use the system without approving its purchase. Record that role distinction instead of assuming every detailed user account includes budget authority.
Ask about a recent decision without promising a solution
Use the following proposed prompts for a fictional enquiry-management study. Give respondents room to decline details they do not want to share.
| Research area | Open question |
|---|---|
| Existing solution | What do you currently use for this task? |
| Purchase context | How did the team choose that approach? |
| Resource commitment | What time or budget does maintaining it involve? |
| Previous attempt | What else did you try, and what happened? |
| Approval process | Who was involved in deciding to adopt it? |
Avoid inserting a sales promise between answers. Saying your product will eliminate the cost can change the conversation from discovery into evaluation of your pitch.
Preserve the limits of each account
An old purchase may reflect a different team size, requirement or purchasing environment. Ask enough context to interpret it, while collecting only information relevant to the research question.
If the person cannot provide a precise amount, retain the uncertainty. Do not replace it with an estimated budget and then cite that estimate as respondent evidence.
The feature-request evidence guide separates interest, behaviour and commitment. The neutral question guide helps avoid prompting the answer you want.
Use the evidence to scope the next experiment
A costly workaround can justify investigating a smaller replacement task, but the proposed alternative still needs testing. A cheap effective process may suggest a narrower audience or a weak opportunity.
My StackFlight case study describes a research collection product. It does not claim that any response about spending validates a new product's revenue potential.
Summarise what was reported, the relevant context and the remaining uncertainty. Keep commercial assumptions separate when the findings become an engineering brief or investor discussion.
Does existing spending prove willingness to buy our product?
No. It establishes a past commitment in a particular context, which may differ from the proposed purchase.
Should we require exact budget figures?
Ask only for useful appropriate detail and preserve uncertainty when the respondent cannot or prefers not to share it.
What should we record first?
Capture the current approach, decision context and source account before a founder discovery review.