A promising business idea is still a collection of assumptions. Before you spend weeks building a website or product, identify the assumption most likely to make the idea fail. Then design a small, honest experiment to learn about it. Early validation reduces uncertainty; it does not guarantee commercial success.
Write down what must be true
Describe the customer, the problem, their current workaround, and how you might help. Separate what you know from what you hope. If the entire idea depends on people experiencing a costly problem, that is usually more important to investigate than your future logo.
Choose a narrow starting audience you can actually reach. You can broaden later after learning whether the problem is real and whether your approach is useful.
Assumption: independent tutors lose time arranging lesson bookings and are actively looking for a simpler process.
Ask about the last time it happened
Speak with a few people who fit the audience. Ask them to describe a recent instance of the problem: what happened, what they tried, and what it cost them in time or money. Avoid opening with your solution or asking whether they think your idea sounds good.
Compliments and hypothetical willingness to pay are weak evidence. Actual behavior, existing spending, and specific follow-up requests are more informative, though each still needs interpretation.
- When did this last happen?
- What did you do to handle it?
- What made that approach difficult?
- Who else is involved in choosing a solution?
Test the riskiest assumption honestly
You might offer a manual version of a service, demonstrate a prototype, or ask people to try a small workflow. Be clear about what exists and what does not. Do not pretend that an unbuilt product is available or collect commitments you cannot responsibly honor.
Set a time and spending limit. Record the question, the action you are observing, and what you will do with each likely result. A small unsuccessful test can save a much larger investment.
Help three tutors organize their booking process manually. Observe where the process breaks before writing software to automate it.
Decide what the evidence supports
Compare what happened with your original assumption. Did people use the help, return for more, or change their behavior? Did they describe a different problem as more urgent? Avoid redefining success after every result simply to protect the idea.
Continue, narrow the audience, change the approach, or stop. All four can be sensible outcomes. Keep your notes so future experiments build on learning instead of repeating the same conversations.
- List your three largest assumptions.
- Pick the one with the greatest consequence if it is wrong.
- Arrange one conversation or experiment this week.
A little idea to take with you
Invest in evidence before investing in a full build. A useful experiment tests behavior and gives you a clear next decision.
An original Grow Me guide. Educational information, not a promise of results. Platform features and tool policies can change.
Back to the library
