How to test a startup hypothesis before writing the product
A hypothesis is not “an app for Kazakhstan”. It is an offer: who, which task, what they do today, and why they would switch. Until that exists, development tests the team, not demand. Manual checks without rent are a neighbouring page. This is the order for a product that does not exist yet.
What counts as a test
Five conversations with people who have the task now.
A note of what they use today.
One paragraph of offer and one next step that does not need the full product.
Search: do people already name the task in the words you would build a page for.
Before a first version
- Cross out features the conversation does not need.
- Find who already answers the same task.
- Get one action: a prepayment, a letter, a pilot, or a refusal with a reason.
- Do not call empty search a blue ocean until you try other words.
Before a purchase
See whether people search for the product
Before a site
See what people want to find
Before a market
Check interest and who is already there
Before ads
Make sure you promote the right thing
Search snapshot
- The hypothesis is one phrase: whether the task is searched and who is already in the results.
What you learn
What we found
A hypothesis is tested by a conversation and one phrase.
Why it matters
Otherwise you write a product for a slide.
What to do
Who, what they use, the offer, search.
Limit
Not a startup score
There is no investment probability.
Search is not payment
People can search a problem and not buy your method.
If you do not want to check this by hand, aVtonomus will show it in the analysis.
Common questions
Is this the seven cheap checks?
No. Those refuse rent and a batch. This refuses to write a product before the role and the current method are named.
Do I need an MVP?
After one manual proof. Not instead of it.
See search wording for this task
The first data are free. A full review is 4 990 ₸.