A week after 6 p.m., Farah Rahman is still at her kitchen table in Valencia, staring at a spreadsheet with 83 email replies. She has a project coordinator’s day job, a rough concept for a lightweight scheduling tool, and a very practical question: is this thing actually wanted, or is it just a nice idea she likes because it sounds smart at dinner?
That’s the real fork in the road for most aspiring founders. Not branding, not the logo, not the perfect domain name. The question is simpler and harsher: can you prove demand before you trade a salary. Benefits, and a predictable calendar for a project that may not survive month four?
Why it matters now
The cost of making a bad leap has gone up. Hiring remains uneven, interest rates have made cash feel less forgiving, and customers are more sceptical than they were a few years ago; they expect proof, not hype. Worth thinking about, no? At the same time, it’s easier than ever to build a decent-looking product in a weekend, which means a lot of polished nonsense reaches the market faster than it can be challenged.
Side note: That combination is dangerous. A founder can now spend €2,400 on a landing page, ads, and a no-code prototype, then mistake early clicks for actual demand. Validation is the filter between “this sounds promising” and “people will pay for it repeatedly.” It protects your savings, your reputation, and frankly your mood.
The core idea: prove pain, demand, and willingness to pay
No kidding, Validation is not a vibe check. You with me? It’s a set of small tests that answer three questions: does the problem hurt enough, do enough people care, and will they pay at a price that makes the business viable? If you can’t answer those clearly, quitting is not brave. It’s premature.
The trick is to test the riskiest assumptions first. Don’t build the whole product. Don’t wait for perfection. Start with conversations, then a simple offer, then a tiny transaction if the signal is strong enough. Each step should either increase confidence or kill the idea quickly and cheaply.
A useful way to think about it:
- Problem validation: are people already trying to solve this? If so, how badly?
- Audience validation: is there a group with the same pain, not just one enthusiastic outlier?
- Solution validation: does your specific approach make sense to them?
- Pricing validation: can they tolerate the cost without a long internal debate?
- Channel validation: can you actually reach them without burning cash at an absurd rate?
- Retention validation: if this is a repeat product, will they come back after the first win?
Notice what’s missing: “build a full app.” You can validate with a landing page, a service pilot, a manual workflow, a paid workshop, or a pre-order page. The format matters less than the evidence. If ten people tell you it’s interesting, that is not the same as three people paying next week.
The best early-stage signal is not praise. It’s someone pulling out a card.
Kenji Silva, a finance manager in Riga, learned this the expensive way, but not disastrously so. He spent 11 evenings testing a B2B invoice-chasing idea with 19 accounting teams across Latvia and Lithuania. The first version got smiles. The second got a polite shrug. The third, a brutally simple email template and reminder service, produced 7 paid pilots at €89 each. That was the first version worth taking seriously.
Rina Popescu, a recruiter in Seville, used a different route. She wanted to build a niche service for screening bilingual candidates in hospitality. Instead of quitting immediately, she booked 24 short calls and offered a paid trial package to 8 employers. Four said yes, and 2 renewed after the first month. That told her the pain was real, the niche was narrow, and the offer needed a tighter scope before she left her job.
The point isn’t that everyone needs the same method. It’s that the evidence should get stronger with each step. If your idea cannot survive contact with real people, real objections, and a real payment page, it probably isn’t ready for full-time attention yet.
What this looks like in practice
Farah Rahman, the project coordinator in Valencia, started with a one-page site and a waitlist. Over 14 days, she sent it to 126 people in local operations and admin groups, and 27 signed up. Then she offered a €39 “manual concierge” version to 5 of them. Three paid immediately. That was enough to justify a weekend prototype, not enough to resign.
Kenji Silva in Riga did not build software first. He created a spreadsheet-based service for overdue invoice reminders and tested it with 9 small firms. After 6 weeks, 4 were still using it, and 2 asked whether they could pay quarterly instead of monthly. You with me? That single question told him the problem was recurring, not one-off.
Rina Popescu in Seville tested a recruitment screening kit by selling access to templates, interview scorecards, and a 45-minute review call. She charged €120 and closed 6 clients from 31 outreach emails. The numbers weren’t huge, but they were honest, and honesty is what saves people from months of self-deception.
Common mistakes to avoid
-
Confusing interest with commitment. People will often say your idea is clever, especially if the conversation is short and pleasant. But compliments are cheap. A stronger signal is when they give you time on the calendar, share company details, or agree to a paid pilot with a deadline attached.
-
Testing only with friends and former colleagues. These people want you to succeed, which is lovely and also misleading. Their feedback is often filtered through kindness, shared context, or professional loyalty. If they’re not the actual buyer, treat their praise as morale support, not market data.
-
Building too much before selling anything. A polished prototype can hide a weak offer. You may spend 6 weeks on features, then discover the real issue was the pricing, the buyer, or the pain level. Start with the simplest test that forces a decision.
-
Ignoring the boring objections. Founders love strategic questions; customers ask practical ones. “How does this fit with our current process?” “Who approves this?” “What happens if we stop?” Those objections are not distractions. They are the buying process in disguise.
-
Using vanity metrics as proof. Page views, likes, and newsletter sign-ups can feel encouraging, but they rarely tell you whether someone will pay. A smaller number of direct responses, deposit payments, or booked calls is usually more valuable than a bigger audience with no buying intent.
-
Quitting before you know the channel. Even a good idea can fail if you can’t reach the right people affordably. If every lead costs too much, or your outreach only works in one tiny pocket of the market, you may have a distribution problem rather than a product problem. That distinction matters a lot.
A practical checklist
-
Write the problem in one sentence. Keep it specific. If you can’t describe the pain clearly, you’ll struggle to test it properly.
-
List 20 people who already live with that pain. Use LinkedIn, industry groups, slack communities, or your own network. If you can only name 3, your market may be too thin to support the business.
-
Run 10 short problem interviews. Ask what they do today, what it costs them, and what happens if they do nothing. Don’t pitch too early.
-
Create a simple offer page. One promise, one target user, one clear call to action. Don’t overload it with features you haven’t earned yet.
-
Ask for a real next step. A paid pilot, a deposit, a booked demo, or a formal yes. “Sounds interesting” is not a next step.
-
Set a kill criterion before you start. For example: if you can’t get 3 paid pilots from 25 targeted conversations, pause the idea. This stops you from negotiating with your own optimism.
-
Measure repeat behaviour, not just first response. If people only try it once, you may have a novelty, not a business. If they return, refer others, or ask for more, that’s a stronger signal.
-
Compare the upside against your runway. If you need 14 months of full-time work and you only have 5 months of savings, be honest about the gap. Good ideas still need arithmetic.
When NOT to do this
There are times when validation can become a stalling tactic. Some people use it to avoid the discomfort of choosing a direction. They interview, tinker, and “research” for 9 months because uncertainty feels safer than commitment. That’s not validation; that’s disguised hesitation.
Also, not every business needs the same level of pre-quit proof. Sound familiar? If you already have deep industry access, a contract lined up, or a service idea that can be sold manually before any product exists, you may move faster. But the burden of proof should still be high enough to stop fantasy from taking the wheel. Are you gathering evidence, or just postponing fear?
Where to learn more
- https://en.wikipedia.org/wiki/Lean_startup
- https://www.sba.gov/business-guide/plan-your-business/validate-your-idea
- https://www.ycombinator.com/library/5z-the-real-product-market-fit
The smartest move is not quitting boldly; it’s quitting with receipts. If you can show that real people have a real problem, that they’ll pay for your first answer, and that you can reach them without setting money on fire, then leaving your job starts to look less like a gamble and more like a decision. Want to know whether your idea deserves your resignation letter? Test it until the answer is impossible to ignore. Make sense?
