A founder came to me with a familiar problem. She had three business ideas. She liked all of them. She could not decide which to pursue. So she did what most people do in this situation: she researched all three simultaneously for four months, never committing to any of them.
By the time we met, she had Google Docs full of notes, bookmarks folders with hundreds of links, and zero evidence about which idea would actually work.
I told her to test all three in one weekend.
She looked at me like I had suggested something illegal. But she did it. By Sunday evening, she had real data on all three ideas. One was clearly ahead. She started building it Monday morning.
The entire four-month decision paralysis — solved in 48 hours.
The Parallel Testing Framework
The key insight is that testing an idea and building a product are different activities. Building a product takes months. Testing an idea takes hours — if you test the right thing.
What you are testing is not “will this product succeed?” You cannot know that in a weekend. What you are testing is “does this problem exist, do enough people have it, and would they pay to solve it?” That you can test in a weekend.
For each idea, you need one test that produces one measurable signal. Three ideas, three tests, three signals. Then compare.
Friday Evening: Set Up (3 Hours)
Hour 1: Write three one-sentence problem statements.
For each idea, write the problem it solves in one sentence. Not the product. The problem.
“Freelance designers spend 3+ hours per week on invoicing.” Not “An invoicing app for freelancers.”
“New parents cannot find reliable babysitters on short notice.” Not “A babysitter marketplace.”
“Small restaurant owners don’t know their actual food costs.” Not “A food cost calculator.”
The problem statement is the hypothesis you are testing. If the problem is real and painful, the product direction follows. If the problem is not real, the product does not matter.
Hour 2: For each idea, find the primary testing channel.
Where do the people who have this problem congregate online? Map the watering hole for each idea.
Freelance designers: Dribbble community, r/freelanceDesigners, Designer Facebook groups. New parents: Local parenting Facebook groups, r/NewParents, parenting Discord servers. Restaurant owners: r/restaurantowners, local gastronomy Facebook groups, hospitality forums.
You need at least two channels per idea to avoid single-source bias.
Hour 3: Create three landing pages.
One page per idea. Each takes 30-45 minutes on Carrd or a similar tool.
Each page has: one headline stating the outcome, one paragraph of detail, and one email signup form. That is all. The page does not need to be polished. It needs to be clear.
By the end of Friday evening, you have three problem statements, six channels identified, and three landing pages live.
Saturday: Drive Traffic (Full Day)
Morning: Post in channels.
For each idea, write two posts for two different communities. Six posts total. These are not advertisements. They are genuine questions or observations that include a link to your landing page.
“I’ve been talking to freelance designers about their invoicing workflow. The amount of time people spend on this is wild. I’m exploring whether there’s a better way. If this is a pain point for you, I’d love your input: [link]”
Post all six between 9 AM and 11 AM. Early Saturday posting catches people during their morning browsing.
Afternoon: Direct outreach.
For each idea, find and message five people directly. LinkedIn, DM on social platforms, email if you have it. Fifteen messages total.
“Hi, I’m researching [problem]. I’m trying to understand how people currently deal with it. Would you have 5 minutes for a quick question?”
If they reply, ask the core question: “When was the last time this was a problem for you, and what did you do about it?”
Direct outreach produces higher-quality data than community posts because the responses are more detailed and personal.
Evening: Compile first signals.
By Saturday evening — roughly 8-12 hours after posting — you will have early data. Check each landing page: how many visitors? How many signups? Check your messages: how many replies? What did people say?
Do not draw conclusions yet. Just record the numbers.
Sunday: Analyze and Decide (Half Day)
Morning: Final data collection.
Check everything one more time. Some responses will have come in overnight. Update your numbers.
For each idea, you now have:
- Landing page visitors
- Email signups
- Community post engagement (upvotes, comments, replies)
- Direct outreach response rate
- Qualitative feedback from conversations
Create a comparison table:
| Metric | Idea 1 | Idea 2 | Idea 3 |
|---|---|---|---|
| Page visitors | |||
| Email signups | |||
| Signup rate | |||
| Direct responses | |||
| Enthusiasm level | |||
| ”Tell me more” responses |
Apply the decision criteria:
The winning idea is not necessarily the one with the most signups. It is the one with the best combination of:
-
Highest signup rate (signups/visitors). This measures message-market fit. A high signup rate means the problem statement landed.
-
Most enthusiastic responses. Look at the quality of replies, not just the quantity. Did people say “this is exactly what I need” or “sounds interesting”? Enthusiasm predicts willingness to pay.
-
Strongest evidence of existing pain. Did people describe current workarounds? Frustrations? Money they have already spent trying to solve this? The more effort people are already putting into solving the problem, the more likely they are to pay for a better solution.
-
Your energy. After testing all three, which one do you want to keep working on? This matters because building a business is hard, and sustained effort requires genuine interest.
What If No Idea Wins Clearly?
Three scenarios:
One clear winner. Easy. Build that one. Start with a smoke test the following weekend.
Two ideas tied. Run a second round of testing the following weekend, but this time test demand, not just interest. Put a price on each and see who clicks “buy.” Revenue is the only real validation.
All three weak. This is information. It means none of your three problems are painful enough — or your framing of them is off. Go back to customer interviews. Spend the next week talking to people, not testing pages. The problem you need to solve might be a variation of one of your three ideas, or something completely different that emerges from conversations.
Why This Works Better Than Deliberation
Most people try to choose between ideas by thinking about them. They compare market sizes. They imagine different futures. They list pros and cons on a whiteboard.
This produces anxiety, not clarity. Because you are comparing imagined futures, not real data. Your brain is good at many things. Predicting the future of a business you have not started is not one of them.
Testing replaces imagination with evidence. You do not have to guess which idea has more demand. You measure it. You do not have to imagine which problem is more painful. You hear it directly from the people who have the problem.
The weekend test framework also breaks the emotional attachment that builds during extended deliberation. When you have spent three months thinking about one idea, abandoning it feels like loss. When you have spent one weekend testing three ideas, pivoting feels like learning.
The Speed Principle in Action
This framework is the velocity principle applied to idea selection. The fastest path to clarity is not more thinking — it is more testing.
Every week you spend deliberating between ideas is a week you could have spent testing one of them. And the data from one weekend of testing is worth more than a month of deliberation.
The founder who tested three ideas in one weekend is now running the winning idea — a food cost calculator for small restaurants — as a EUR 30K/year side business. The other two ideas sit in a “maybe later” folder. They might be great ideas. But they were not the best idea for her market, her skills, and her available time.
She found that out in 48 hours. Not four months.
Three ideas. One weekend. Real data. Then decide.
