How do I validate a new product idea?
Updated
Treat the idea as three testable assumptions: the problem is real, the buyer will pay, and you can reach them. Test them in order: interview 15–20 target buyers, put a priced offer in front of real visitors, then sign paid pilots. CorZen turns that sequence into weekly tasks with an owner on each, on the timeline you choose.
Three things must be true
What does a validation plan look like?
This is a sample 90-day roadmap for the Assess Product-Market Fit category with the Scientific Method approach. CorZen also builds 30-day, 60-day, custom, and ASAP timelines. Your own plan changes with your market, your tools, and how many hours your team has each week.
Month 1: Define and interview
Weeks 1–4
- Week 1Write the three riskiest assumptions and a pass/fail threshold for each.
- Week 2Recruit 20 interviewees from the target segment.
- Weeks 3–4Run interviews. Log how often the problem occurs and what the current workaround costs.
Month 2: Test demand
Weeks 5–8
- Week 5Publish a one-page offer with a real price.
- Weeks 6–7Drive 300–500 targeted visitors. Track the sign-up or pre-order rate.
- Week 8Compare results to the thresholds. Cut or revise the offer.
Month 3: Prove it pays
Weeks 9–13
- Weeks 9–10Sign 3–5 paid pilots.
- Weeks 11–12Deliver. Measure usage and willingness to renew.
- Week 13Go, pivot, or stop, judged against the Week 1 thresholds.
How does the plan change on a 30- or 60-day timeline?
The order of the tests stays the same on every timeline: interviews, then a priced offer, then proof that buyers pay. Shorter timelines shrink each phase, and the 30-day plan replaces the paid pilot with pre-orders or deposits. Custom and ASAP timelines keep the same order.
| Timeline | Interviews | Priced offer | Proof of payment |
|---|---|---|---|
| 90 days | 15–20, weeks 1–4 | 300–500 visitors, weeks 5–8 | 3–5 paid pilots, weeks 9–13 |
| 60 days | 15, weeks 1–3 | 200–300 visitors, weeks 4–6 | 2–3 shorter pilots, weeks 7–9 |
| 30 days | 10–12, weeks 1–2 | Priced offer to interviewees and one channel, weeks 2–4 | Pre-orders or deposits, no pilot |
What can you validate in 30 days?
In 30 days you can learn whether the problem is real and whether people will put money down. You can’t yet learn whether they keep using the product, because there is no time for a pilot.
Treat a 30-day pass as a reason to run a longer test, not as proof of fit. If you need a decision fast, run 30 days first, then a 60-day plan that adds the pilot.
30 days can show
- The problem is real
- Buyers describe it in their own words
- Some will pay before the product exists
30 days can’t show
- Whether buyers keep using it
- Whether they would renew
- Which channel scales
How do you test each assumption?
Each assumption gets its own test and its own pass threshold. Write the thresholds down before any test runs. Thresholds set after the data comes in tend to move to fit the data.
The problem is real
- Test
- 15–20 problem interviews, no pitch
- When it runs (90-day sample)
- Weeks 2–4
- Example pass threshold
- 12 of 20 describe the problem unprompted and already spend time or money on a workaround
The buyer will pay
- Test
- Landing page with a real price
- When it runs (90-day sample)
- Weeks 5–8
- Example pass threshold
- A pre-order or paid-waitlist rate you set before launch, based on your price and traffic source
You can reach them
- Test
- Recruiting interviewees from one channel
- When it runs (90-day sample)
- Weeks 2–3
- Example pass threshold
- 20 interviews booked from a single channel within two weeks
The numbers above are examples. Set your own before the first test starts.
Why do most validation attempts give false positives?
“I’d use that” costs the speaker nothing.
- 1
Founders count compliments as demand. “I’d use that” costs the speaker nothing. A pre-order, a deposit, or a signed pilot costs them something, and that is the signal worth trusting.
- 2
The second trap is asking friends and existing fans. They want you to succeed, so they answer kindly. Interview people who fit the buyer profile and have never heard of you.
- 3
The third is a free sign-up page. Sign-ups measure curiosity. A price on the page measures intent. That is why month two in this plan puts a real price in front of visitors.
How much each signal is worth
How do you decide to go, pivot, or stop at the end of the plan?
Judge the results against the thresholds you wrote in week one, not against how the plan felt.
Go
- When it applies
- All three assumptions passed and pilots are using the product
- Next plan
- Start a Go To Market plan
Pivot
- When it applies
- The problem is real, but price or reach failed
- Next plan
- Change one assumption and rerun its test
Stop
- When it applies
- Buyers did not describe the problem, or nobody paid
- Next plan
- Keep the interview notes. They often point to the next idea.
How does CorZen build this plan for you?
Tell CorZen your goal. Pick Assess Product-Market Fit, then the Scientific Method approach, then a timeline: 30, 60, or 90 days, a custom length, or ASAP. A short AI interview asks about your niche, what makes your idea different, the tools you already use, and how much time your team has each week.
CorZen then builds a roadmap for that timeline, broken into weekly tasks. Every task has an owner, and a task can have more than one. On Team and Business plans, AI agents can draft deliverables for individual tasks, such as the copy for your week-five landing page.
This is one of CorZen’s plan templates. See every template by business goal.
Frequently asked questions
How long does it take to validate a product idea?
Most founders can get a usable answer in 30 to 90 days. Thirty days shows whether the problem is real and whether people will put money down. Ninety days adds a paid pilot, which shows whether they keep using the product.
How many customer interviews do you need to validate an idea?
Plan for 15–20 interviews in one segment. Stop early if the last five interviews told you nothing new. If answers are still all over the place at 20, your segment is too broad.
Is a landing page sign-up enough proof of demand?
No. A free sign-up shows curiosity. A pre-order, a deposit, or a paid pilot shows someone will pay. Put a real price on the page.
Can you validate an idea without building anything?
Yes. The interview and priced-offer phases need no product at all. The pilot can be delivered by hand before you write any code.
What if the results are mixed?
Find the one assumption that failed and rerun only that test with a change, such as a new segment, price, or channel. Mixed results usually mean one assumption is wrong, not all three.
Which template should you look at next?
Other ways to approach Assess Product-Market Fit, and the plan that usually comes after it.