How to validate a business idea before you build anything

By the FirstMRR team · Published October 1, 2026

A practical way to test a business idea in two weeks with conversations and a pre-sale, plus clear criteria for continuing or dropping it.

Validating a business idea means collecting evidence that specific people have the problem and will pay to solve it. Friends saying it sounds great is not evidence, and neither is a survey where people tick “very interested”, because neither of them costs the person anything. Real validation costs the customer something: time, a referral, or money.

Strong signals and weak signals

A waitlist is useful for staying in touch with people, and it can show which message gets attention. It does not show that anyone will pay, so it should not be the last step of validation.

Write down your assumptions first

Before talking to anyone, write five short answers on one page. Keep it, because it is what you will compare the conversations against.

1. Who exactly has the problem? “Small businesses” is too broad, while “independent physiotherapists who handle their own bookings” is something you can check.
2. What is the problem, in the words they would use?
3. How do they deal with it today?
4. What does it cost them now, in money or hours?
5. What would you charge, and why would they switch?

Set the bar before you start

Decide in advance what result means continue, change or stop. If you wait until after the conversations, you will find a reason to keep going whatever happens, because nobody wants to drop an idea they have been excited about for weeks.

One example of a bar, which you should adjust to your own market: out of 15 conversations with people who fit your description, at least a third describe the problem without being prompted, and at least two agree to pay or put down a deposit for a first version. Below that, change the customer, the problem or the offer, then test again.

A two-week validation plan

Days 1 and 2: list and reach out

Make a list of at least 30 people who match your description. Start with people you can reach through someone you know, then communities where they gather. Ask for a 20-minute conversation about how they handle the problem, and make clear that you are not selling anything yet.

Days 3 to 9: conversations

Aim for 10 to 15 conversations. Ask about their past behavior, not their opinion of your idea. Our list of customer interview questions includes a full script. Write your notes the same day, while you still remember the exact phrases people used.

Days 10 to 14: ask for a commitment

Go back to the people who described the problem most clearly. Show them a one-sentence offer with a price and ask whether they want to be among the first customers. A payment link or a refundable deposit is the clearest test. A yes followed by “send me the link later” that never turns into a payment counts as a no.

What to do with the result

• You cleared the bar. Build the smallest version that delivers the result to the people who paid, then follow the path to your first MRR.
• People have the problem but will not pay. The problem may not be costly enough, or you may be talking to people without a budget. Try the same problem with a customer who loses more money to it.
• People do not recognize the problem. Change the problem, not the wording of your pitch.

Common traps

• Pitching instead of listening. Once you describe your solution, most people will be polite about it.
• Only talking to people who like you. Their encouragement is sincere and almost useless as evidence.
• Treating competitors as a bad sign. Competitors usually mean people already pay for this, so the question becomes which customers they serve badly.
• Building a landing page and waiting. Without traffic, an empty signup count tells you nothing about the idea.