The One-Week Idea Test: Evaluate Any Business Idea in 7 Days

Seven days. That is all you get.

Not to build. Not to design. To find out whether your business idea is worth pursuing at all. Learning how to test a business idea before committing real resources is the single skill that separates solopreneurs who ship things that work from those who spend months building things nobody wanted.

Most founders spend weeks building before they discover what a week of structured testing would have told them upfront: the problem they assumed is real is either not painful enough, not common enough, or already solved well enough that nobody needs another option. The One-Week Idea Test surfaces that answer before you commit anything more expensive than your time.

This is not a feel-good framework. It is a structured process with specific tasks for each day, a scoring rubric at the end, and a binary output: go or kill. By day seven, you will have real signal. Not encouragement. Not opinions from people who want you to succeed. Signal.

Here is how it works.

What Is the One-Week Idea Test and Why Does It Work?

The One-Week Idea Test is a structured five-phase evaluation framework that assesses a business idea across problem reality, customer existence, competitor landscape, demand signal, and decision clarity — all within seven days and without writing a line of code. It produces a scored output with a go, wait, or kill recommendation.

The framework exists because the two most common approaches to idea evaluation are both broken.

The first: overthinking. You research for months, read competitor analysis until you have analysis paralysis, and never actually learn anything from the market. You are still at your desk. Still speculating. Still not sure.

The second: reckless action. You skip evaluation entirely and start building. Six months later, you discover that the person you built it for was a fictional customer who existed only in your assumptions.

The One-Week Idea Test is neither. It forces you to move fast enough that you cannot hide in research, but structured enough that you are collecting evidence, not just activity.

Why seven days? Long enough to get meaningful signal from real people. Short enough that you cannot rationalize extending it indefinitely. Each day has a specific task. None require a product, a prototype, or a single line of code.

How Do You Confirm the Problem Is Real Before You Talk to Anyone?

Problem reality testing means gathering documented evidence that your target problem exists outside your own experience. On days one and two, you are collecting public proof: forum posts, reviews, social media complaints, and search behavior data — all before speaking to a single person.

Days 1 and 2 are desk research. Not your opinions. Not your personal experience with the problem. External evidence that the problem is real, recurring, and frustrating enough that people talk about it publicly.

Here is where to look:

Reddit and online forums. Search subreddits related to your audience. Look for threads where people describe the problem unprompted — posts complaining, asking for solutions, or sharing workarounds. If you cannot find these threads, that is itself a signal. The absence of complaint is data.

App store reviews for competitor products. Search for products that solve adjacent or related problems. Read the one-star and two-star reviews carefully. These are real people articulating what the existing solution gets wrong. Most solopreneurs never collect this research. You now have it within two hours.

Google search behavior. Type variations of your problem into Google. Note what autocomplete suggests. Look at “People Also Ask.” These are aggregated signals of real search intent — problems people search for have a frequency that opinions do not.

Amazon reviews for educational or physical products. If your idea is in a category with existing products, Amazon reviews are a reliable secondary source. Sort by “most helpful” and read the three-star reviews especially — they are honest because the reviewer is neither angry nor a promoter.

By the end of day 2, you should have at least 10 to 15 specific documented instances of real people expressing this problem. If you cannot find them, the problem may be too niche, too latent, or insufficiently painful to drive organic discussion.

If you find them easily, you move to phase two with confidence.

How Do You Find Real People to Talk to in 72 Hours?

Customer discovery in the one-week framework means identifying and having five to eight real conversations with people who match your target customer profile. Days 3 and 4 are for finding them and talking to them — not pitching an idea, but listening for evidence of the problem.

This is the phase most solopreneurs skip because they believe finding customers to talk to takes weeks. It does not. With intentional outreach, you can have your first conversation within 24 hours.

Where to find them:

• The same Reddit threads you found in phase one. Comment, ask if you can send a DM, ask one question.
• LinkedIn, searched by job title or role that matches your target customer profile.
• Facebook groups for your niche audience. Most allow direct messages.
• Twitter/X searches for people actively discussing the problem.
• Slack communities and Discord servers for your target industry.

The goal is not to pitch. The goal is to understand.

Use the framework from The Mom Test — ask about past behavior, not hypothetical future behavior. “Tell me about the last time you dealt with this problem” reveals more than “would you use a product that solved this?” The second question invites politeness. The first invites honesty.

By the end of day 4, you should have spoken to at least five people. Take notes on the specific words they use, what they have already tried, and how much the problem costs them in time, money, or frustration.

If every conversation surfaces the same pain in similar language, you have strong evidence. If the conversations reveal that the problem you assumed is real is not a significant frustration, that is the most valuable outcome of the whole test.

You can find specific questions to ask in the customer interview script guide.

Is your idea passing the early tests or surfacing red flags you have not considered? Run it through the Idea Evaluation Scorecard — the same criteria this framework uses, scored in one sitting. Free. Takes 15 minutes. No sign-up required.

How Do You Test Whether Anyone Would Pay Attention Without a Product?

A demand signal test on days 5 and 6 measures real-world response to a solution description — without building the product. Low-cost demand tests include a one-page post in relevant communities, a waitlist landing page built in under 60 minutes, or a direct pre-sell message to the five to eight people you interviewed.

Day 5 is competitor analysis. Day 6 is your demand signal.

Day 5: Competitor landscape. Search for direct solutions to the problem you tested in phase one. For each competitor, note three things: what they charge, what their negative reviews say they get wrong, and whether they appear to be growing or declining based on blog activity and social presence. You are looking for either a clear gap or evidence that the market does not support a new entrant. Both outcomes are useful.

Communities like Indie Hackers are a reliable source of competitor post-mortems and honest product retrospectives if your idea is in the SaaS or digital product space. Read the failure stories alongside the success stories — the failure stories reveal what the market punishes.

Day 6: Create a demand signal. This is where most frameworks stop at theory. This one does not.

Choose one of these three options based on your audience and idea type:

1. Community post. Write a 200-word post describing the problem and asking if people deal with it. Do not pitch a solution yet. Post it in the two or three most relevant communities you identified. Count the responses, upvotes, and DMs within 48 hours.

2. One-page waitlist. Build a minimal landing page using Carrd or Tally (both free, both buildable in under 60 minutes). Describe the problem, state what the solution would do, and ask for an email address. Share it in communities and with the people you interviewed. Track signups.

3. Direct pre-sell message. Message the five to eight people you interviewed in phase two. Tell them you are building a solution. State a price. Ask if they would pay. Do not discount to get a yes — a hesitant yes at the real price is worth more than an enthusiastic yes at 80 percent off.

You are not trying to generate a massive response. You are looking for any signal that people are interested enough to take a low-friction action: reply, sign up, or express willingness to pay.

How Do You Score the Results and Make the Go or Kill Decision?

On day 7, you score your evidence across five criteria using a zero-to-two scale, producing a total out of ten. Scores of 7 or above support moving to the build phase. Scores of 4 to 6 call for a defined further test. Scores below 4 indicate a kill or major pivot before committing further resources.

Day 7 is decision day. Score your evidence from the week using this rubric:

Add your scores. The total is out of 10.

7–10: Go. Your evidence supports moving to the next stage. Read the decision framework for what to build first before writing a line of code — strong demand signal tells you the idea is worth pursuing, not what to build specifically.

4–6: Wait and re-test. You have mixed evidence. Pick the lowest-scoring criterion and run one more focused week testing that specific question before deciding. This is not failure. This is the framework working as designed.

0–3: Kill or major pivot. This idea, as currently defined, does not have sufficient evidence to justify building. That is not a statement about your ability as a founder. It is a statement about this specific hypothesis. Kill it cleanly and evaluate the next one. Most solopreneurs who test ideas systematically kill two or three before finding one that scores well — that is the correct outcome, not a sign that the process is broken.

Frequently Asked Questions

How do you test a business idea in one week without a budget?

The one-week idea test requires no paid tools or advertising. Desk research uses free platforms: Reddit, Google, and app store reviews. Customer discovery uses direct outreach in communities you can join for free. Demand testing uses Carrd or Tally, both of which have free tiers. The only resource the test consumes is roughly 2 to 3 hours per day for seven days.

What is the difference between testing a business idea and validating one?

Testing collects early evidence across multiple dimensions — problem, customer, competitor, and demand signal — without committing to a product. Validation is the deeper process that follows: pre-selling, building a minimum viable version, and confirming people will pay in real conditions. The one-week test is the pre-validation filter. It tells you whether an idea deserves the longer, more expensive validation process.

What if my idea scores a 5 or 6 out of 10?

A score of 4 to 6 is a specific instruction, not a verdict. Identify your lowest-scoring criterion and run one more targeted week testing that dimension alone. The most common low scores are on demand signal (because solopreneurs skip the demand test entirely) and customer existence (because they talk to people who are too easy to reach, like friends or existing connections). Address the weakest signal before deciding.

How many customer conversations do I actually need?

Five conversations are the minimum to identify patterns. The goal is not statistical significance — it is pattern recognition. If the first three conversations surface the same core frustration in similar language, that is meaningful. If five conversations produce five entirely different problems, that is also meaningful: either the problem is not universal, or your target customer definition is too broad. Rob Fitzpatrick covers customer conversation methodology in detail in The Mom Test.

What should I do if the test kills my idea?

Kill it cleanly and move to the next one. Killing a bad idea in week one costs seven days. Building the wrong product costs six months and your savings. Most solopreneurs who use systematic idea testing kill two or three ideas before finding one with strong signal — that is the framework working correctly. Treat the kill as the output the test was designed to produce, not a failure to be avoided.

Keep Reading

• How to Evaluate a Business Idea: The Complete Framework
• Should I Build This? A Decision Framework for Solopreneurs
• The Mom Test: How to Talk to Customers Without Leading Them On

Ready to Score Your Idea?

You have the framework. Seven days, five phases, one decision.

If you want to run a deeper evaluation before starting the week test — or if you have completed the week and want a structured second opinion on the results — the Idea Evaluation Scorecard walks you through ten criteria in a single sitting.

Run Your Idea Through the Scorecard →

Free. No sign-up. Takes about 15 minutes.