Most business ideas do not fail because the person behind them lacked effort. They fail because the effort went into the wrong thing first. Months go into a website, a logo, a course outline or a content plan, and only afterward does anyone find out whether the problem underneath was one people would act on.
Validation is how you find that out earlier, while being wrong is still cheap. It is not a formality or a box to tick before the real work starts. It is the real work at this stage, because what you learn decides what, if anything, is worth building.
The method in this article applies to almost any offer built on experience: consulting, a service, a workshop, training, a small digital product. The question is the same in each case. Before you spend significant time or money, is there evidence that a specific person has a problem serious enough to do something about, and that your help is something they would act on?
What Validation Actually Means
Validation is not proof that a business will succeed. Nothing gives you that in advance. It is the gradual replacement of assumptions with evidence, in the order that matters.
It helps to separate four kinds of signal, because they are easy to confuse:
- Interest is attention. Clicks, likes, traffic, downloads, survey responses and kind comments all belong here. Interest tells you a subject is not invisible. It says very little about whether anyone will act.
- Problem evidence is when real people can describe the problem in their own words: when it last happened, what it cost them, what they have already tried and why that did not work well enough.
- Offer evidence is when a specific person understands a specific outcome you are proposing and recognizes it as relevant to their situation.
- Buyer evidence is when someone commits something real to trying your solution: money, meaningful time, access to their team or their data, or another cost they would not give away casually.
Each level is stronger than the one before it. For a commercial idea, buyer evidence matters most, because it is the only kind that reflects a decision rather than an opinion.
Why Interest Is Not the Same as Demand
The most common validation mistake is treating attention as if it were demand.
A post that gets shared widely, a free guide that gets hundreds of downloads, a survey where most people say the idea sounds useful: all of these feel like evidence. They are real signals, but they measure how easy something is to notice or agree with. Agreeing costs nothing. Downloading something free costs almost nothing. Saying an idea sounds useful costs nothing at all.
None of that is a criticism of content, audiences or email lists. They can be valuable later, once you know what you are building them around. The problem is sequence. If you build them first and then read their numbers as validation, you can spend a year growing attention around a problem nobody was prepared to pay to solve.
A useful habit is to ask of every signal: what did this cost the person who gave it? The higher the cost, the more the signal is worth.
Start With a Problem, Not an Idea
Many ideas begin as a solution. A course on a subject you know well. A service you would enjoy delivering. A template you wish had existed. There is nothing wrong with starting there, but validation works better if you turn the idea around and look at the problem it assumes.
Write the problem down in one or two sentences, from the point of view of the person who has it. Not "I want to teach project management," but something closer to "Small service businesses keep losing work in the handoff between sales and delivery, and they don't know how to fix it without hiring someone."
Then check whether you can answer three questions without guessing:
- Who specifically has this problem?
- What usually happens right before they go looking for help?
- What does it cost them when it goes unsolved?
If any of those answers is vague, that is not failure. It is the first thing to find out.
Talk to People About What They Did, Not What They Would Do
The most useful early evidence comes from conversations with people who plausibly have the problem. Former colleagues, past clients and people in your professional network are the obvious place to start. You are not pitching. You are trying to understand what actually happens in their world.
The quality of those conversations depends almost entirely on the questions. Questions about the future invite polite optimism. Questions about the past produce facts.
Weak questions:
- Would you buy this?
- Do you like this idea?
- Does this sound useful?
Stronger questions:
- When did this last happen?
- What did you do about it?
- What made it difficult?
- What have you already tried?
- What did that cost you, in time, money, risk or frustration?
- What happens if you do nothing?
The weak questions ask people to predict their own behavior, which most of us do badly, and they make it awkward to disappoint you. The stronger questions ask for things that already happened. If someone cannot remember the last time the problem occurred, or has never tried to solve it, that tells you something no amount of enthusiasm can.
Listen for the words people use to describe the problem. They are often different from yours, and the difference matters. If you find yourself explaining the problem to them rather than hearing it from them, the problem may matter more to you than to them.
Make the Outcome Specific
Once you have heard the problem described several times, define what would be different for the person afterward. Be concrete. "Better processes" is not an outcome. "A documented handoff your team uses, so jobs stop stalling after the sale" is.
A specific outcome does three things. It lets the right person recognize themselves quickly. It keeps your first offer from swelling into everything you know. And it gives you something you can actually test, because either the outcome matters enough for someone to act on it or it doesn't.
If the outcome keeps getting broader as you describe it, narrow the person or the problem until it stops.
Offer the Smallest Credible Version
The first test should be the smallest piece of work that still produces a result the buyer can recognize. Small does not mean trivial. It means bounded.
Depending on the problem, that might be:
- a paid consultation or short advisory session
- a narrowly scoped assessment that ends in a clear list of priorities
- a half-day workshop for one team
- a manual version of a service you might later systematize
- a short pilot with one client
- a single, simple paid deliverable
A good first test solves one narrow problem, for one identifiable type of person, with one understandable outcome. It needs very little infrastructure. It is cheap to be wrong about. And it generates feedback you can use.
What it does not need is a website, a logo, a sales funnel, a course platform, an automated email sequence, a community or an advertising budget. Those may all have a place later. At this stage, a clear description, a price and a way to deliver the work are usually enough. Most first tests can be offered in a conversation or a short email.
Ask for a Real Commitment
At some point, the test has to involve a real decision. For a commercial idea, that usually means asking someone to pay for the small version.
The reason is not to charge as much as possible, and it is not to prove the business will work. A real exchange simply produces information nothing else can. When someone pays, even modestly, you learn that the problem is worth money to at least one person. When people hesitate, you learn what stands in the way: the price, the timing, the scope, trust, or the problem itself.
Not every conversation needs to end with an offer, and not every offer will be accepted. That is expected. What matters is that some of your evidence comes from decisions rather than opinions. A handful of paid engagements, or a clear pattern of people declining for the same reason, will teach you more than months of encouraging feedback.
Where money is not the right first step, look for another commitment that carries a genuine cost: a scheduled working session, access to real material, or an introduction to the person who would approve the purchase.
Learn From What Actually Happens
Validation is rarely a clean pass or fail. It is a set of observations you can act on.
After each round of conversations and offers, look at:
- who responded, and who didn't
- which description of the problem people recognized immediately
- which outcome they cared about, and which they ignored
- what objections came up more than once
- what they already use instead
- whether the scope was too broad
- whether the problem was urgent enough to act on now
- whether your solution seemed credible coming from you
Then decide. The evidence might tell you to continue as you are. It might tell you to narrow the offer, change the audience, reframe the problem, adjust the outcome, or pause until the timing is better.
It might also tell you to stop. That is a legitimate result, not a failure. If careful testing shows that a problem is not serious enough, or that your offer is not the right answer to it, you have saved yourself the months or years you would have spent building around it. That is exactly what validation is for.
Build Only After the Evidence Supports It
When people have described the problem in their own words, recognized the outcome and committed something real to getting it, you have earned the right to build more.
Now infrastructure starts to make sense, because you know what it is for. A website can describe an offer people have already bought. Content can answer the questions you actually heard. An email list can serve people who have shown a real need. A product can package what you have already delivered by hand. Each of those decisions is easier and cheaper when it rests on evidence rather than hope.
Validation does not end there. Every new client, every declined offer and every repeated question keeps adding to what you know. But the order matters most at the start. Evidence first, then the machinery. It is far easier to change a sentence, a scope or a price than to rebuild something you built for a buyer who never appeared.
