How to Validate a Business Idea Before You Spend Any Money

The fastest way to destroy a large amount of time and money is to build a product before you know whether anyone will pay for it. This sounds obvious — and yet it's the mistake most founders make. They spend months building the product, launch it, and discover that the assumptions they built on were wrong. Validation before building isn't just good practice. It's the difference between a business and an expensive learning experience.

Start With a Problem, Not an Idea

The right starting point for a business isn't "here's a product I want to build." It's "here's an expensive problem I keep seeing." The distinction matters because solutions are easy to get attached to — and attachment makes it hard to update when the evidence says you should. Problems are stickier. If the problem is real and expensive, the right solution will reveal itself through the process of trying to understand it deeply.

The way I've found the best business opportunities is through years of direct industry experience. Zentria Flow didn't start with a product concept — it started with watching importers get blindsided by landed cost variances on every single shipment. The problem was obvious to me because I'd been inside the industry long enough to see it consistently. If you don't have that kind of direct exposure, find it before you build: spend time with the people who have the problem before you design a solution.

Talk to 20 Customers Before You Build Anything

Investor Rob Wiltbank's research suggests that 95% of new product failures can be predicted before launch. The founders who succeed talk to customers obsessively before building — and they do it in a way that generates real signal, not false confidence.

The rules for early customer conversations: never describe your product idea at the start. Ask about their current experience with the problem. Ask how they solve it today. Ask how much it costs them — in money, time, or both. Ask what's most frustrating about the way they handle it today. Listen for emotion and for specificity. The best customer conversations feel less like pitches and more like investigations.

Watch for Real Buying Signals

The signal that matters is willingness to pay, not willingness to be interested. In early conversations, people are generally polite — they'll tell you the idea sounds good. This is not validation. The signals you're looking for are more specific: a customer who asks when they can buy it. A customer who refers you to a colleague without being asked. A customer who offers to pay before you've built anything. A customer who describes the problem in the same words you used when you first identified it.

If you describe a problem to a potential customer and they immediately launch into the specific ways it affects them, with detail and emotion, that's a positive signal. If they nod politely and say it sounds interesting, it's a neutral signal at best. You need to hear from at least 10–15 people who respond with genuine urgency before you have reasonable confidence the problem is real enough to build a business on.

Use Your Existing Network First

The fastest path to validation conversations is through people you already know. LinkedIn connections, industry contacts, former colleagues, friends who work in the relevant domain — these people will give you time they wouldn't give a cold outreach. They'll also be more honest with you than strangers, because the relationship gives them a reason to tell you the truth rather than just be polite.

The mistake is treating your network as a source of encouragement rather than a source of signal. You want honest evaluation, not positive feedback. Go into these conversations asking for hard questions, not validation. If the people who know and like you are genuinely excited about the problem, that's meaningful. If they're supportive but vague, dig harder.

Price Before You Build

One of the most useful validation tests is pricing conversations. Before you've built anything, ask potential customers: "If we solved this problem completely, what would it be worth to your business?" Then ask: "What would you expect to pay for that?" The gap between what they say it's worth and what they say they'd pay is one of the most useful pieces of information you can get early.

If customers tell you a problem costs them €50,000 a year and they'd pay €2,000 for a solution, the economics are interesting. If they tell you a problem is annoying and they'd consider paying €20 a month, the economics are very different — even if both customer conversations feel positive.

The Smallest Possible Test

Once you have enough positive signal from conversations to believe the problem is real, build the smallest thing that can prove the core mechanism works — not the full product. This might be a manual process, a spreadsheet, a very basic tool, or a service delivered by hand. The goal is to test whether customers will actually use a solution and whether the core value holds up in practice. Full product development comes after you've confirmed the fundamentals.

The time you spend in this phase — talking to customers, running small tests, understanding the problem from every angle — is the least glamorous but most valuable time you can spend. Every week of genuine validation before building is worth months of development on a product that's pointed in the wrong direction.