Validate an idea in two weeks without writing code

Validation isn't asking people whether they like your idea. Nearly everyone is polite, and “I'd definitely use that” predicts very little. Validation is collecting evidence about what people have already done and what they will commit to now.

Here's a two-week plan that needs no code, a small or zero budget, and about an hour a day.

Before you start: write down your riskiest assumption

Every idea rests on several assumptions: the problem is frequent, it's painful, the current workaround is bad, people will pay, you can reach them. Pick the one that, if wrong, kills the idea. That's what the next two weeks are for.

Days 1–5: problem interviews

Talk to 8 to 12 people in your target group. Not friends, ideally — strangers' behaviour is more honest. Ask only about the past:

• “Tell me about the last time this happened.”
• “What did you do about it?”
• “What do you use today? What's annoying about it?”
• “Have you ever paid for or searched for a better way?”

Avoid “Would you use…?” and “How much would you pay…?”. Hypothetical questions get hypothetical answers. Don't pitch until the very end, if at all.

Write down exact quotes. At the end of the week, count how many people described a specific, recent instance without prompting. That number matters more than how excited anyone sounded.

Days 6–10: a concierge test

Deliver the outcome by hand for three people. If your idea is an app that matches tutors with students, match three of them yourself using a spreadsheet and WhatsApp. If it's an automated report, make the report manually.

You'll learn what the job actually involves, which steps users care about, and which features nobody needs. Most importantly, you'll see whether people come back for a second round.

Days 11–14: a commitment test

Ask for something real: a scheduled onboarding call, a refundable deposit, a pre-order, a letter of intent, or an introduction to their manager. Commitments separate interest from intent.

Decision thresholds — set them before you start

• At least 8 conversations completed.
• At least 5 people described a specific, recent instance of the problem.
• At least 2 of 3 concierge users wanted to continue.
• At least 3 people made a concrete commitment.

If you hit them, build the smallest version of what the concierge test proved people want. If you miss them, change something fundamental — the target user, the problem, or the offer — rather than polishing the design.

Limits of this method

Two weeks and a dozen people show direction, not market size. A strong result means “worth building a first version”, not “guaranteed business”. Keep collecting evidence as you build.