How to Validate a Business Idea in 7 Days Without Building Anything

Validation is collecting evidence that a specific group of people has a problem painful enough to pay to solve, and that your solution is something they would choose. It is not asking friends for their opinion, and it is not a survey that says "would you use this?"

The strongest evidence is behavior. A person who hands over money, a deposit, a signed letter of intent, or even a calendar slot is giving you real information. A person who says "sounds cool" is giving you politeness.

Treat validation as a way to lose cheaply. Your goal is to find out in a week, for under a hundred dollars, whether an idea deserves months of effort. A "no" on day seven is a win.

Write one sentence you can prove wrong: "[Specific customer] will pay [price] for [solution] because [problem] costs them [time or money]."

For example: "Independent massage therapists will pay $29 a month for automatic appointment reminders because no-shows cost them about two sessions a month."

Then define pass criteria in advance. Something like: "Pass if 5 of 20 people interviewed describe the problem unprompted, and 3 of 20 pre-pay or join a paid pilot." Writing the bar before you collect data stops you from bending the results to match what you hope to see.

1. Day 1: Define the customer and the problem. Pick one narrow audience. "Small business owners" is too broad; "owner-operated landscaping companies with 2 to 10 employees" is workable. List three assumptions that must be true for the business to work.
2. Day 2: Research existing alternatives. Search for competitors, spreadsheets, and workarounds. Read their reviews for complaints. Note what they charge. If nobody is spending money on this problem at all, that is a warning sign.
3. Day 3: Find 20 people to talk to. Use the places your customers already gather: Reddit threads, Facebook groups, LinkedIn, local business associations, or simply walking into shops. Send short, honest messages asking for 15 minutes about how they handle the problem. You are not selling.
4. Day 4: Run interviews. Aim for at least five conversations. Ask about the last time the problem occurred, what they did, what it cost, and what they have tried. Take notes verbatim.
5. Day 5: Build the smallest possible offer. One page with a clear headline, the outcome, the price, and a button. No product required. A free site builder or a document is enough.
6. Day 6: Drive traffic and ask for commitment. Send the page to the people you interviewed and post it where your audience lives. Ask for a deposit, a pre-order, or a paid pilot slot.
7. Day 7: Score the results. Compare outcomes against the pass criteria you wrote earlier. Decide: proceed, adjust the audience or offer, or stop.

Most interviews fail because the founder pitches. Your job is to learn, so talk about 20 percent of the time.

Ask about the past, not the future. "Tell me about the last time you had to deal with X" produces facts. "Would you use a tool that does X?" produces flattery.

Good questions include:

• What was the last time this came up, and what did you do?
• How much time or money did it cost you?
• What have you tried to fix it? What did you not like about it?
• Who else is involved in the decision?
• If this problem disappeared tomorrow, what would change for you?

End each call by asking who else you should speak to. Referrals are the fastest way to reach 20 conversations.

Listen for emotion and specifics. People who have a real problem tell stories with details and numbers. People who do not tend to speak in generalities.

Pick one or two of these, matched to your idea:

• Pre-sale. Offer the product at a discount for early buyers and collect payment before delivery. If you cannot deliver, refund. Even a handful of pre-orders is strong evidence.
• Concierge test. Deliver the service manually for a few customers. A would-be software tool can start as you doing the task by hand and emailing the result.
• Landing page with a paid waitlist. Charge a small refundable deposit to join. Free waitlists are cheap signals; deposits are real ones.
• Fake door. Add a button for the feature to an existing site and measure clicks, then tell visitors it is coming soon. Be transparent so you do not mislead anyone.
• Small paid ad test. Spend 50 to 100 dollars on a targeted ad pointing to your page. Track the share of visitors who take the main action.

Avoid treating likes, upvotes, and email signups for a free product as proof that anyone will pay.

Strong signals include: people describing the problem in their own words before you mention it, existing spending on a workaround, requests for a date or price, introductions to colleagues, and money changing hands.

Weak signals include: compliments, "let me know when it is ready," and requests for free versions.

If you get lukewarm responses, change one variable at a time: the audience, the problem framing, or the price. A narrower audience often turns a weak result into a strong one because the message becomes more specific.

If you fail the test twice with different framings, stop. Kill the idea without guilt and return to your list. The skill you are building is making cheap decisions fast.

Only talking to friends and family. They are biased toward kindness and often are not your target customer.

Leading questions. "Don't you hate wasting time on invoices?" gets a yes every time. Ask what they do about invoices instead.

Building first. A prototype feels like progress but often delays the one thing that matters: whether anyone pays.

Counting interest as demand. Interest costs nothing to give. Weight your evidence by the cost of the commitment.

Changing the bar after the results. If you passed or failed, honor the criteria you set on day one.