Suppose you are considering a reporting tool for small agencies. Research can show you competing products, but it cannot tell you whether a particular agency will change its process. Before building the platform, identify what you still need to learn and choose a way to observe it.
By the end of this guide
One assumption, a small experiment and a result that would change your next step.
01 / Pick the uncertainty
What would change your mind?
For the agency tool, the uncertainty might be whether the report takes enough effort to justify paying for help. It could also be whether you can generate a useful report from the data agencies actually export. Those questions need different tests.
Choose the assumption you need to test next. Write what you expect to see and what you would do if the result is different. Keep the test small enough that you can act on the answer.
- The problem
- Does this task cause enough trouble that someone tries to fix it?
- The buyer
- Who uses the result, who decides, and who pays?
- The offer
- Would they commit to a specific outcome at a specific price?
- Delivery
- Can you produce the result with the tools, time and budget you have?
02 / Choose a test
Match the experiment to the question.
If you need to understand the reporting process, ask someone to show you their last report. If you need to learn whether your output is useful, offer to prepare one report from their export and watch how they use it. Explain whether you are doing that work manually or with software.
A landing page could help test the offer with a wider audience later. Its signups would tell you that people expressed interest; they would not tell you whether the report helped them finish their work. Match the method to the question you chose.
- Problem
- Ask someone to walk through the last time it happened. Look at the work and the workaround.
- Alternatives
- Compare what they use, pay for and complain about. Check the sources.
- Workflow
- Show a rough prototype and observe someone attempting one real task.
- Willingness to pay
- Offer a paid pilot or a clearly described service. Watch for an actual commitment.
03 / Use the result
Decide what to change.
After the test, record what happened. Did the agency give you an export, use the report with a client, ask for another one or agree to pay? Keep those responses separate from a polite comment that the idea sounds useful.
If the result contradicts your assumption, investigate why before adding features. You may have the wrong buyer, a weak offer, a difficult workflow or a problem that is not urgent. Narrow the idea, try a different test or stop.
Tools for the task
Where to do this work
Choose a tool after choosing the question. Hunting Apps helps with market evidence, The Mom Test covers customer conversations, and a coding tool becomes useful when you need someone to try a workflow.
Your next action
Plan the test before building more.
For the reporting idea, you might offer to prepare one report from a real export. Write down what you are testing, what you will deliver and which response would lead you to continue or change the offer.
0 of 3 ready
Sources and limits
These are practical recommendations drawn from the sources below. Founder accounts are retrospective, and vendor guides describe their authors' approaches. They do not establish a guaranteed result for your project.
A prototype and customer-conversation approach. Its timelines and numeric targets are author recommendations, not universal thresholds.
A distinction between testing messaging, demand and product workflow.
A different approach that begins with public evidence. It does not replace observing customer behaviour.