You can validate a business idea in two weeks without writing a single line of code — using customer conversations and a free landing page. That is exactly how I validated FIKR Space: no developers, no wireframes, no software. Just conversations and common sense. Here is the week-by-week process, the free tool stack, and the signals that tell you whether to build or walk away.
Why unvalidated ideas die in notebooks
I've wasted years of my life building things nobody wanted. Not once — multiple times. Early in my career, I'd get excited about an idea, disappear into my office for months, emerge with something "brilliant," and discover the market had one response: silence.
Twenty years in product development taught me the most expensive lesson in business: the idea is never the hard part. Finding someone who'll pay for it is.
Here's a number that should keep you up at night: 42% of startups fail because nobody wanted their product. Not bad technology. Not funding. Not competition. The founder built something, shipped it, and discovered — too late — that nobody cared. And yet only 40% of founders do formal validation before building. The other 60% just start building. They trust their gut. They assume the market wants what they want.
Here's the irony. If you've spent years in business — running projects, managing clients, presenting to stakeholders — you already know you wouldn't launch a major initiative without doing your homework first. Validation is the same skill. You've just never applied it to your own ideas.
Week 1: validate the problem, not the idea
When I started building FIKR Space, I didn't touch a single technical tool for the first two weeks. In week one, I talked to people. Not about my idea — about their problems.
I used what Rob Fitzpatrick calls The Mom Test. Three rules:
- Talk about their life, not your idea. I never said "I'm building X, would you use it?" Instead: "What's the hardest part about managing your business operations right now?" If you've ever run a discovery meeting or a client needs assessment, you already know how to do this.
- Ask about the past, not the future. Not "Would you pay for this?" but "Tell me about the last time you tried to solve this. What did you do? How much did it cost?"
- Shut up and listen. Every time I caught myself talking about my solution, I stopped and redirected back to their experience — like the best stakeholder interviews you've done, the ones where you learned the most because you let the other person talk.
I had 15 conversations in 7 days. Most were 20–30 minutes over coffee or video call. I didn't pitch once. By Friday, I had a clear picture: people were stitching together 8–12 different tools, paying hundreds per month, and still dropping the ball on critical workflows.
If you want the complete interview playbook — how to find people, what to ask, when you've talked to enough of them — it's all in the full guide on how to validate a business idea.
Week 2: validate demand with a landing page
Armed with problem data, I built a simple landing page. Not the product. A page.
- Carrd (free)
- Clear value proposition
- One call-to-action: "Join the waitlist for early access"
- Shared on LinkedIn and in a few communities
I also sent the link to every person I'd interviewed. The result? Over 40% of the people I'd interviewed signed up. Several replied asking when they could pay.
That's when I knew. Not because someone said "cool idea." Because people took action.
The no-code validation stack (total cost: €0)
Here's what validation actually costs in 2026:
| Tool | Cost | Purpose |
|---|---|---|
| Your mouth | Free | Customer interviews |
| Carrd or Tally | Free | Landing page |
| Stripe Payment Link | Free | Pre-sell test |
| Google Docs | Free | Interview notes |
| LinkedIn DMs | Free | Finding interviewees |
Total cost: zero euros. Compare that to the average cost of building and launching an unvalidated product: months of your life, thousands of euros, and that familiar devastation of pouring yourself into something that goes nowhere.
Notice what's NOT on this list: coding skills. Technical knowledge. A computer science degree. Validation is a business skill, and it's one you've probably been practicing for years without calling it that.
What good validation signals look like
After hundreds of conversations and years of watching products succeed and fail, here is exactly what to look for.
Strong signals (proceed):
- People describe the exact problem you want to solve — without you prompting them
- They're already paying for a worse solution
- They ask "When can I buy this?" before you offer to sell
- They refer you to others who have the same problem
- They put money down — the strongest signal of all, which is why pre-selling is the natural next step
Weak signals (dig deeper):
- "That's a cool idea" (everyone says this)
- "I'd probably use that" (probably = no)
- "Send me the link when it's ready" (translation: I'm being polite)
- Lots of social media likes but zero signups
Kill signals (pivot or stop):
- Nobody can articulate the problem you're solving
- They have the problem but won't pay for a solution
- Your interviewees keep redirecting to different problems
- Zero email signups after 300+ landing page visitors
What validation can and can't do
Validation doesn't guarantee success. It reduces the risk of building something nobody wants — which is the #1 killer of startups — but it can't predict everything. Markets shift. Execution matters. Timing is unpredictable.
But here's what validation gives you: confidence grounded in evidence, not hope.
Joel Gascoigne validated Buffer with a two-page landing page and a tweet. Seven weeks later, he had paying customers. Drew Houston validated Dropbox with a three-minute video. Signups went from 5,000 to 75,000 overnight. Neither of them had a product when they validated. Neither of them needed technical skills to do it.
I validated FIKR Space in two weeks without writing code, without hiring a developer, without spending a cent. Only then did I start building — the €2,750 build story is its own article. The validation cost me nothing. Skipping it would have cost me everything.
Frequently asked questions
How do you validate a business idea without building anything?
Two steps: problem validation, then demand validation. First, hold 10–15 conversations about the problem — never pitch your idea. Then put up a free landing page with one call-to-action and see whether people who have the problem actually sign up. Both steps require zero code and zero euros.
How many customer interviews do you need?
I did 15 conversations in 7 days for FIKR Space, and by the end the patterns were unmistakable: the same tools, the same frustrations, the same workarounds. When you start hearing the same answers, you've found the signal.
What counts as real validation?
Action, not compliments. People describing the problem unprompted, already paying for a worse solution, signing up, asking when they can pay — and, strongest of all, putting money down. "Cool idea" and social media likes count for nothing.
Do I need to quit my job to validate an idea?
No — and you shouldn't. This week, pick one idea you've been sitting on. Talk to 5 people about the problem. Put up a free landing page on Carrd. See what happens. If nobody cares, you saved months. If people care, you've got your signal. Either way, you win — while your salary keeps funding you.