To validate a startup idea, you gather evidence that real people have the problem, already spend time or money dealing with it, and will pay you to fix it. You do this before you build anything. The cheapest route is a mix of customer conversations, a small paid test, and a decision rule you write down before the results arrive.

I have started seven businesses, and the pattern repeats: the ideas that survived were never the ones friends called brilliant. They were the ones a stranger paid for while the product was still rough. Here is the process I use and teach, with Irish resources along the way.

What validating an idea actually means

Validating an idea means working out how viable it is and whether there is an audience for the product or service, which reduces the risk of a startup. Before building, that means researching the target market, the competitors and customer feedback, including willingness to pay.

It is not the same as market research for its own sake, and it is not a pitch to people who love you. The old line "if you build it, they will come" is a fallacy, and value is only proven when enthusiasm lines up with verifiable market potential.

Think of validation as a ladder. At the bottom, people say the problem is real. Higher up, they describe what they do about it now. At the top, they hand over money or time. Each rung costs you more effort, so climb in order and stop as soon as the evidence says no.

PortableText [components.type] is missing "bodyImage"

Step 1: write the idea as a testable statement

Vague ideas can't be validated. Before you talk to anyone, put the idea in four lines:

Example: "Independent shop owners in Irish towns who reorder from several wholesalers spend hours each week comparing supplier prices by hand. They use phone calls and spreadsheets. I would build a tool that does the comparison for a monthly or per-project fee."

Now list your assumptions: that the group is big enough, that the pain is frequent, that they can pay, that you can reach them. Rank them by how badly the idea fails if you are wrong. The top of that list is what you test first. The cheapest useful test is the one that credibly resolves the biggest uncertainty that could make the next investment a mistake.

Step 2: do the desk research, Irish edition

Desk research is quick and free, so do it first, but treat it as groundwork and not proof. You are looking for four things: demand, gaps, prices and competitors.

The Local Enterprise Offices recommend research to find demand, market gaps, prices and competitors, using desk and internet research, store visits, retailer or buyer research, questionnaires, focus groups and competitor research. That list is a useful checklist even if you never apply for a grant.

For competitors, go wider than the obvious names. Enterprise Ireland asks funded projects to profile direct, indirect, alternative and emerging competitors. The alternative is often the real rival: a spreadsheet, a cousin who does it for free, or doing nothing.

What to capture in one document:

If you are planning to apply for public funding later, the evidence you collect here is the same evidence applications ask for — see our guide to startup grants in Ireland for product companies.

Step 3: interview customers without leading them

Desk research ends where conversations begin. Aim for 10 to 15 conversations with people who match your "who" from step 1. Early on, validation relies mostly on qualitative customer conversations; numbers come later as your customer base grows.

Ask about the past, not the future

The worst question is "Would you buy this?" Asking people whether they would buy a finished product can produce false positives. People are polite, and a hypothetical costs them nothing.

Ask open questions about what happened instead. Ask about the last time they hit the problem, and listen for emotional reactions and specific details. Don't mention your solution early, or you will lead them into a false yes.

Know what counts as evidence

Good evidence concerns an existing cost, delay, risk, frustration or workaround, not agreement that your idea sounds useful. A host who says "I spend Sunday evenings answering the same guest questions" has given you more than ten people who say "great idea."

After each call, write down the exact words they used, what they currently do, and whether they described a cost. Then compare findings across conversations to find patterns. One angry customer is a story. Six describing the same workaround is a signal.

Step 4: run a cheap experiment

Once interviews show a real problem, test demand with something customers can respond to. Pick the test that resolves your biggest uncertainty. Here is how the options compare.

TestBest forCostWhat it proves
Manual (concierge) serviceServices, automation, anything software-likeYour timeWhether customers value the outcome and what the job really involves
Landing page with a real priceReaching a new audienceSmall ad spendWhether strangers take a step that costs them something
Fake-door page or email signupEarly interest in a new categoryLowCuriosity, which is weaker than intent
Narrow prototype or MVPProduct ideas with a clear core featureModerateWhether target users use it and what to improve

The manual-first rule

If your idea would eventually be software, do it by hand first. Deliver the result to three customers using spreadsheets, email and your own effort. You learn the real steps, the exceptions and the objections, and you find out whether anyone cares enough to pay. Building the tool comes after that, not before.

When we build for hosts and shop owners, we start the same way: by watching the actual workflow. A property host's real problem might be guest check-in chaos, not the booking site they thought they needed. You only see that by observing.

Step 5: test whether people will pay

This is the step most founders skip, and it matters most. Encouragement, survey answers and email addresses are not customer behaviour. What counts as a meaningful commitment depends on the customer, the price, the risk and how they buy.

Paid pilots are among the strongest demand signals. A meaningful discount can test willingness to pay, and even a small payment helps separate willingness from curiosity.

  1. Scope a small version of the outcome you promise, finished in days or a few weeks.
  2. Name a real price. A free pilot teaches you little.
  3. Offer it to the people from your interviews who described the biggest cost.
  4. Track who says yes, who stalls, and the exact objection they give.

Objections are not failure. They are your roadmap: price, trust, timing, "my team won't use it." If three people raise the same one, that is the next thing to fix.

SignalStrength
"That's a great idea"Very weak
Email address or survey answerWeak
Agrees to a second meeting or shares real dataModerate
Pre-orders or depositStrong
Pays for a paid pilotStrongest

This ranking is my own working order, so adapt it to how your customers buy. A business buyer may need sign-off, so a signed letter of intent might be the realistic commitment, while a consumer can simply pay.

Step 6: decide — go, change or stop

The hardest part of validation is believing the result. Entrepreneurs can rationalise bad findings, protect their identity as founders, or move the goalposts after the test. Structured validation takes real upfront discipline to prevent this.

The fix is simple: decide in advance what evidence would make you continue, change direction or stop. Write it down before you run the test. For example:

Then check the maths. You can quickly test whether margins exist by making basic assumptions and calculating the margin to see if the business could be financially sustainable. If customers will pay €50 and delivering costs €45, you have a hobby, not a business.

Stopping is a good outcome. You spent weeks, not a year and your savings.

Irish supports that help you validate

You don't have to do this alone, and some help is free or subsidised.

Why we validate by watching the work

We have launched seven businesses, and the lesson that cost us the most is that surveys flatter you. People answer what sounds polite. What they do on a Tuesday afternoon with a pile of invoices tells the truth.

That is why everything we build is custom and starts in person. We watch how a host handles a booking, or how a shop owner compares suppliers, before writing a line of anything. The workflow shows what the idea must do, and the owner's reaction to a rough first version shows whether it is worth finishing.

The same discipline applies to your startup idea: small tests, real prices, honest decision rules. Done well, validation is not a delay to building. It is the first, cheapest version of the build.

Want the full playbook?

This process covers the validation steps. It doesn't cover the mindset, the funding strategies, or what to do when a "sure thing" falls through anyway — all of which shaped how my own ventures actually got built. That's in the book.

Get How to Start a Business with Almost No Money →

And if you're validating a business idea specifically in Ireland on a tight budget, the companion guide covers the ground before this one: How to Start a Small Business in Ireland with (Almost) No Money →

FAQ

How many people should I interview to validate a startup idea?

Start with 10 to 15 conversations with people who match your target customer. Stop when new interviews stop surprising you and the same problems and workarounds keep appearing. If you hear very different stories, your customer group is probably too broad, so narrow it and interview again.

How much does it cost to validate a business idea?

Much of it costs only time: interviews, desk research and a manual service delivered by you. Add a small budget for a landing page or ads if you test that route. The Local Enterprise Offices offer supports such as Start Your Own Business, so ask your local office about current options and fees.

Is a survey enough to validate an idea?

No. Survey answers and email addresses are not the same as customer behavior. Surveys are useful after interviews to measure how common a problem is, but they can't show whether someone will pay. Use them to size a pattern you have already seen in conversations.



What if people say the idea is good but won't pay?

Take that seriously: it usually means the problem isn't painful enough, the price is wrong, or you are talking to the user and not the person who holds the budget. Ask what they would need to see to pay, test a lower-risk scoped pilot, and compare against the decision rule you set. If nothing moves, stopping or changing direction is the right call.

Should I build a prototype before I talk to customers?

Usually not. Talk first, then offer a manual service or a narrow prototype. A prototype tested with target users can show demand and guide improvements, but it is worth building only once interviews have shown a problem worth solving.