Twenty questions to answer before you write a single line of code. Work through them honestly. Every “I don't know” is a thing to go and find out this week, not a thing to build around.
A copy is on its way to your inbox too.
01
The problem
Can you describe the problem in one sentence, without naming your product?
How are people solving it today, including with spreadsheets and manual work?
What does the problem cost them per month, in money or hours?
Is it a problem they are already spending money to fix?
How often does it happen: daily, monthly, or once a year?
02
The customer
Can you name ten real people or companies who have this problem?
Have you spoken to at least ten of them without pitching anything?
Who signs off on the purchase, and is it the same person who feels the pain?
Where do these people already gather, online or offline?
Is the segment narrow enough that you can describe your first fifty customers?
03
The solution and the test
What is the one feature that, on its own, solves the problem?
Could you deliver that manually, for five customers, this month?
Can it be built with no-code tools first, and would that be good enough?
What single result would tell you the hypothesis is wrong?
What is the cheapest test that produces that result, and when does it run?
04
The money
What will you charge, and has anyone agreed to that number out loud?
Is the price at least ten times cheaper than the cost of the problem?
Which single channel will bring the first fifty customers?
What can you afford to pay for a customer, and how long until it pays back?
How many months of runway does this test consume, and what happens after?
Stuck on more than five of them?
That's normal, and it's exactly what the Fast Validation Sprint covers. Bring your answers to a free call and we'll work out what to test first.