Most people spend months validating business ideas. They read books, create surveys, build prototypes, and attend networking events. After all that work, they still don’t know if anyone will pay for their idea.
I’m going to give you a process that produces a clear answer in 72 hours. Not a definitive, stake-your-life-savings answer. But a real signal — based on real customer behavior — that tells you whether to invest more time or move on.
I’ve used this process myself and taught it to dozens of startups through the Startup Burgenland accelerator. It’s fast, it’s uncomfortable, and it works.
Before You Start: The Mindset Shift
The goal of 72-hour validation isn’t to prove your idea works. It’s to find out if it doesn’t.
This distinction matters. If you’re looking for proof that your idea is brilliant, you’ll interpret every piece of ambiguous data as confirmation. If you’re looking for evidence that it doesn’t work, you’ll be honest about what you find.
The best 72-hour sprints are run by people who genuinely want to know the truth, even if the truth is “this isn’t it.” That emotional honesty makes the data useful.
One more thing: this process requires talking to real people and asking them to take real actions. If that makes you uncomfortable, good. It should. Discomfort is the price of honest validation. Staying comfortable is the price of self-delusion.
Hour 0-8: Define, Research, and List (Day 1 Morning)
Define Your Hypothesis
Write one sentence: “I believe [specific group of people] will pay [specific amount] for [specific solution] because [specific reason].”
Example: “I believe freelance designers in Europe will pay EUR 29/month for a client follow-up automation tool because they currently spend 3+ hours per week chasing late invoices.”
Every word in this sentence matters. “Specific group” means you can find these people. “Specific amount” means you’ve thought about pricing. “Specific solution” means you can describe what you’re offering. “Specific reason” means you have a hypothesis about why they’d buy.
If you can’t write this sentence, you’re not ready for validation. You’re still in the problem-finding phase.
Research Existing Solutions
Spend one hour researching what your target customers currently use to handle this problem. Check app stores, Google, Reddit, product review sites, and industry forums. You’re looking for:
- What solutions exist
- Where they fall short (read the 1-star reviews)
- What people wish existed that doesn’t
If you find a solution that does exactly what you’re proposing and does it well, that’s not necessarily a kill signal. It’s a “you need a differentiated angle” signal.
Build Your Contact List
List 20 specific people who fit your target customer description and whom you can reach within 24 hours. These can be:
- People in your professional network
- Members of online communities you belong to
- People whose contact information is publicly available
- Connections through mutual contacts (ask for an intro today)
Twenty is the target because you’ll realistically get responses from 8-12. You need at least that many to see patterns.
Hour 8-24: Customer Conversations (Day 1 Evening + Day 2)
Reach Out
Send a direct, honest message to all 20 people. Something like:
“Hey [name], I’m researching a problem that I think affects [their context]. I’m not selling anything — I just want to learn about your experience with [problem]. Would you have 10 minutes for a quick call or chat?”
Don’t mention your solution. Don’t pitch. You’re having discovery conversations, not sales conversations.
Conduct the Conversations
For each person who responds, run through these questions:
- “How do you currently handle [problem]?”
- “What’s the most frustrating part of your current approach?”
- “How much time/money do you spend on this per week/month?”
- “If a solution existed that [brief description of outcome — not features], how valuable would that be to you?”
- “What would you need to see before you’d switch from your current approach?”
Take notes. Look for patterns. Don’t defend your idea. Don’t fill silence with explanations. Listen.
After 8-10 conversations, you should be able to answer:
- Do people actually have this problem? (Frequency and intensity check)
- Are they spending money or significant time on it already? (Willingness to pay check)
- Is there a gap between what they want and what they currently have? (Opportunity check)
If the answer to all three is yes, proceed to Day 3. If any answer is clearly no, you’ve saved yourself months. That’s a successful validation — even though the answer was negative.
Hour 24-48: Build and Position (Day 2 Evening + Day 3 Morning)
Create a Landing Page
You don’t need a product. You need a page that describes your solution clearly enough that someone can decide whether they want it.
The page needs exactly five elements:
- Headline: The outcome you deliver, in the customer’s language (use the exact words from your conversations)
- Problem statement: 2-3 sentences about the problem, framed in a way that makes your target customer nod
- Solution description: What your product does, focused on benefits not features
- Price: A specific number. Not “starting at” or “contact for pricing.” A number.
- Call to action: “Pre-order now,” “Join the waitlist,” or “Sign up for early access” — with an email capture or payment link
Use whatever tool gets this done fastest. Carrd, a simple WordPress page, even a Google Doc with a payment link. The tool doesn’t matter. The clarity of the offer does.
This connects to shipping ugly: the page doesn’t need to be beautiful. It needs to be clear.
Create the Offer
Decide what you’re asking for. The hierarchy of commitment, from weakest to strongest:
- Email address: “Join the waitlist.” Weakest signal but still useful.
- Email + specific interest: “Which feature matters most to you?” Slightly stronger.
- Pre-order with payment: “Pay now, receive when we launch.” Strongest possible signal.
I recommend aiming for the strongest commitment you’re comfortable with. Pre-sales produce the clearest data, but even email sign-ups tell you something.
Hour 48-72: Drive Traffic and Measure (Day 3)
Share the Page
Go back to the people you interviewed. Send them the landing page with a message like:
“Based on our conversation, I built this. Take a look and let me know what you think. If it solves the problem we discussed, I’d love you to [sign up / pre-order / join the waitlist].”
Also share the page in:
- Relevant online communities (Reddit, Facebook groups, Slack channels, Discord servers)
- Your social media, with a clear description of who this is for
- Direct messages to additional people who fit the target profile
Track everything. How many people visited the page. How many took the action. What questions or objections came up.
Measure the Results
After 24 hours of traffic, evaluate:
Strong positive signal (proceed):
- 10%+ of visitors signed up or pre-ordered
- Multiple people from your interviews expressed strong interest
- People you didn’t contact found the page and signed up organically
Moderate signal (iterate and retest):
- 3-10% of visitors took action
- Interest was mixed — some enthusiastic, some indifferent
- The value proposition landed but the specifics needed adjustment
Weak signal (reconsider):
- Less than 3% of visitors took any action
- Interview subjects were polite but didn’t sign up
- No organic interest
A weak signal doesn’t always mean the idea is dead. It might mean the positioning is wrong, the price is off, or the audience wasn’t right. But it does mean something needs to change before you invest more.
What Happens After 72 Hours
You now have something most founders don’t after months of work: real data from real people about a real offer.
If the signal is strong, your next step is to deliver the value to your first customers and learn from the experience.
If the signal is moderate, refine your hypothesis based on what you learned and run another 72-hour sprint. The second sprint is almost always better because you’re working with better information.
If the signal is weak, honestly assess whether this idea is worth more testing or whether your time is better spent on a different problem.
Why 72 Hours Works
The time constraint is the feature, not the bug. Three days prevents you from:
- Over-researching instead of talking to customers
- Over-building instead of testing with the minimum
- Over-thinking instead of putting something in front of real people
- Getting emotionally attached to the idea before the evidence is in
Speed is strategy. The faster you validate, the faster you either build on something real or move on to something better.
Takeaways
- Write your hypothesis in one sentence. Specific customer, specific price, specific solution, specific reason. If you can’t, you’re not ready to validate.
- Talk to 8-10 real people before building anything. Listen for patterns about the problem, current solutions, and willingness to pay.
- Build a landing page with a clear offer and price. Five elements: headline, problem, solution, price, call to action. Ship it ugly.
- Measure behavior, not opinions. Sign-ups and pre-orders are data. “Cool idea” from friends is noise.
- Decide based on the signal. Strong signal: proceed. Moderate: iterate and retest. Weak: reconsider or move on.
