Validate a startup idea in 30 days, before writing code

Hephaestus Technology8 min read

You can validate a startup idea in 30 days without writing code by running four short sprints: define the riskiest assumption, interview 15 to 20 target customers about their past behaviour, test demand with a landing page or manual offer, and ask for a real commitment such as a deposit, letter of intent or paid pilot. The goal is not proof that the business will succeed. It is evidence strong enough to justify building, changing direction or stopping, gathered for the cost of your time and a small ad budget.

Key takeaways

  • Validation tests whether a specific customer has a problem they already spend time or money on, not whether people like your idea.
  • No market need was the second most common reason in CB Insights' analysis of 111 startup post-mortems, cited in 35% of cases.
  • Ask about past behaviour, not hypothetical futures: 'tell me about the last time' beats 'would you use this?'.
  • Set pass and fail thresholds before each test so you cannot talk yourself into a yes.
  • The strongest signal by day 30 is a commitment that costs the customer something: money, time, data or reputation.

Why validate a startup idea before building anything?

Because building the wrong thing is the most expensive way to learn. In CB Insights' review of 111 startup post-mortems, running out of cash or failing to raise was the top reason founders gave, and tackling problems that are interesting to solve rather than ones that serve a market need was the second, noted in 35% of cases. The two are linked: money runs out faster when months go into a product nobody needs.

Validation also matters for funding in Ireland. Enterprise Ireland's Pre-Seed Start Fund FAQ says applicants may be asked for contacts such as customers during due diligence, and a Donegal County Council notice on the fund lists "a validated customer proposition with market research conducted" among the things assessors look for. Our guide to the Enterprise Ireland Pre-Seed Start Fund covers the rest of the criteria.

What exactly are you trying to prove in 30 days?

You are trying to prove three things, in order: the problem is real and frequent for a specific group, that group already tries to solve it, and they will commit something to get a better solution. Write each as a falsifiable statement before you start, for example: "Operations managers at Irish logistics firms with 20 to 200 staff lose at least two hours a week reconciling delivery exceptions by hand."

Pick the single assumption that would kill the idea if it were false. Steve Blank's drone example is a useful warning: the founders built hardware first, when the real question was whether farmers cared about the data at all, which they could have tested with a rented plane and manual processing.

How do you run the 30-day validation plan?

Run it as four weekly sprints, each with a clear output.

  1. Days 1 to 7: frame the bet. Write a one-paragraph problem statement, a narrow customer profile (role, company size, sector, country) and three to five assumptions ranked by risk. List 40 to 60 people who match the profile from LinkedIn, industry associations, your network and local enterprise events.
  2. Days 8 to 16: customer discovery interviews. Aim for 15 to 20 conversations of 30 minutes. Y Combinator's Eric Migicovsky warns against three errors: pitching your idea, asking about hypotheticals and talking too much. Use questions such as "Tell me about the last time that you encountered this problem" and "What, if anything, have you done to try to solve this problem?". Our customer discovery interview script has a full question set.
  3. Days 17 to 24: test demand. Turn what you heard into a one-page offer and test it. For broad or consumer markets, a landing page smoke test with ads measures whether strangers click and sign up. For B2B, a manual "concierge" version, where you deliver the outcome by hand to two or three prospects, is often faster and more revealing.
  4. Days 25 to 30: ask for commitment and decide. Go back to the most engaged prospects with a concrete proposal: a paid pilot, a pre-order, a deposit or a signed letter of intent. Then score the evidence against the thresholds you set on day 1.

What counts as a pass or a fail?

A pass is evidence that meets thresholds you wrote down before the test, not a feeling that the interviews went well. Kind words are cheap; behaviour is not. Useful signals, from weakest to strongest:

Signal Strength What it tells you
"Great idea, I'd use that" Very weak Politeness, not demand
Describes the problem unprompted and in detail Moderate The problem is real for this person
Joins a waitlist or books a follow-up Moderate Some interest, at low cost to them
Already pays for a workaround or spends staff time on it Strong There is a budget or a cost to displace
Introduces you to a colleague or decision-maker Strong Puts their reputation on it
Signs a letter of intent or pays a deposit or pilot fee Very strong Real commitment

Example thresholds for a B2B idea: at least 10 of 20 interviewees describe the problem as a top-three priority, at least five already spend money or staff time on it, and at least two agree to a paid or formally committed pilot. These numbers are illustrative; choose your own before you start. If you miss, change one variable (customer segment, problem framing or offer) and rerun the relevant sprint rather than starting over.

Passing these tests gives you early problem-solution evidence, not proof of a business.

What does a 30-day validation cost?

Mostly founder time. Interviews, a simple landing page and manual delivery cost little in cash. The main spend is optional advertising, which you control: Google says a campaign can spend up to twice its average daily budget on a given day, but no more than 30.4 times the daily budget in a month, and LinkedIn sets a minimum daily budget of $10 for any ad format.

Irish founders can sometimes get help with early research costs. For example, the Local Enterprise Office feasibility grant in Limerick can cover up to 50% of eligible research and prototype costs, to a maximum of €15,000 excluding VAT, for businesses with fewer than 10 employees, but approval is needed before costs are incurred. Check your own county's LEO for current terms.

What are the common validation mistakes?

The most common mistake is collecting compliments instead of evidence. Others to avoid:

  • Interviewing friends and family. They want to be kind. Talk to strangers who match your profile.
  • Changing the customer every week. Keep one segment fixed long enough to learn something.
  • Ignoring GDPR when you collect emails. If you capture sign-ups or run ads with tracking pixels in Ireland, the Data Protection Commission's cookie guidance says trackers such as pixels generally need prior consent given by a clear affirmative action, and pre-checked boxes are not allowed.
  • Building "just a quick prototype" in week one. Code anchors you to a solution before you understand the problem.

Your 30-day validation checklist

Copy this list and tick it off:

  • [ ] One-paragraph problem statement and narrow customer profile written
  • [ ] Riskiest assumption identified and written as a falsifiable statement
  • [ ] Pass and fail thresholds set for each test
  • [ ] 40 to 60 target contacts listed
  • [ ] 15 to 20 discovery interviews completed and notes logged the same day
  • [ ] Problem patterns summarised in a simple table (frequency, current workaround, cost)
  • [ ] One-page offer or landing page live, with GDPR-compliant consent for emails and trackers
  • [ ] Demand test run with a fixed budget and end date
  • [ ] Commitment asked for from the five most engaged prospects
  • [ ] Decision recorded: build, change one variable, or stop

If the evidence says build, the next step is to define the smallest product that tests your remaining assumptions.

Frequently asked questions

Can I validate a startup idea without a product?

Yes. Most early validation needs no product at all: interviews, a landing page, a mock-up or a service you deliver by hand are enough to test whether the problem is real and whether people will commit. Build software only once the evidence justifies it.

How many customer interviews do I need?

There is no official number, but 15 to 20 interviews within one narrow segment is a practical target for spotting repeated patterns. If answers are still very different after 10 to 12 conversations, your segment is probably too broad.

Is a waitlist sign-up enough validation?

Usually not on its own. A sign-up costs the visitor almost nothing, so treat it as a moderate signal and follow up with a stronger ask such as a deposit, pilot fee or letter of intent.

What if my idea fails validation?

A failed test is useful if it tells you which assumption was wrong. Change one variable, such as the customer segment or the problem framing, and rerun the relevant step, or stop and keep the money you would have spent building.

Do I need consent to collect emails on a validation landing page?

If you plan to send marketing emails, the Data Protection Commission's guidance under the ePrivacy Regulations generally requires clear opt-in consent, and pre-ticked boxes do not count. Non-essential cookies and ad pixels also need prior consent.

If you want a second opinion on your validation plan, book a free 30-minute call with us.

Cover photo by Sora Shimazaki on Pexels.

Hephaestus Technology

We help founders and businesses validate, build and launch products across software, AI and hardware, from offices in Ho Chi Minh City, Dublin and Delaware. See how we work.

Tell us what
you're building.

A free 30-minute call. You'll get an honest view of the idea, the risks we see and what we'd do first, whether or not we end up working together.