How to Validate a SaaS Idea in 7 Days

Most validation advice is either too abstract or too slow. This is a seven-day plan you can run while keeping your day job. The goal is not to prove your idea is good. The goal is to find out, cheaply and quickly, whether enough people will pay to solve the problem.

Day 1 — Write the problem sentence, not the product name

Fill in this sentence with real evidence:

"[Who] needs [outcome] because [current workaround] fails when [trigger]."

Example: “Freelance designers need to send polished proposals quickly because copying Google Docs fails when a client asks for revisions and pricing in one place.”

If you cannot fill in all five parts, that is your Day 1 task. Do not start with a product name or a feature list. A product is a bet about a problem; make the bet explicit.

Day 2 — Collect 20 real signals

Search Reddit, Hacker News, Product Hunt, and GitHub for people describing the problem in their own words. Use the search operators from the Reddit research guide.

For each signal, record:

• the exact quote and link
• the date
• the current workaround
• whether the person is already paying for something
• where the person hangs out

Cluster the signals by job to be done. Twenty signals should collapse into two or three clusters, not twenty different ideas. DemandRadar can automate this step; start with Reddit-sourced opportunities.

Day 3 — Talk to five people

Go back to the communities where the signals came from. Ask for a short conversation, not feedback on your idea.

A script that works:

• “I'm researching how [job] gets done. How do you handle [problem] today?”
• “What breaks or slows down?”
• “What tools or workarounds do you use?”
• “What did you try before that?”
• “What does it cost you in time or money?”

Ask about past behavior, not hypotheticals. “Would you use this?” is nearly worthless. “What did you do the last time this happened?” is evidence.

Day 4 — Map alternatives and prices

List every alternative your interviewees mentioned: spreadsheets, virtual assistants, internal tools, freelancers, and existing products. For each one, note the price, the target user, and where it fails.

If nobody pays for anything, you may be looking at a vitamin rather than a painkiller. That does not make the idea impossible, but it changes the sales motion and the price point.

Day 5 — Build a one-page offer

Create a single page with:

• a headline that names the outcome
• a subhead that names the user and the trigger
• three bullets about what changes for them
• one piece of evidence (a quote, a data point, or a before/after)
• one call to action: join the waitlist or pre-order

Do not build the product yet. The page is the test. If you cannot explain the offer in one page, the product will be hard to sell.

Day 6 — Distribute and measure

Post in two communities where these users actually gather. Send ten personal messages. Share it in one relevant Slack or Discord. Do not spray it across ten generic groups.

Track four numbers:

• targeted visits
• waitlist signups or replies
• conversations booked
• pre-payments

A useful early benchmark: 100 targeted visits, 10 waitlist signups, 3 calls, and 1 pre-payment is a strong signal. Zero replies from 100 targeted visits is also a signal, just not the one you wanted.

Day 7 — Decide: build, iterate, or kill

• Build: five real conversations plus three pre-payments, or ten qualified waitlist signups from one channel.
• Iterate: interest but no money. Change the audience, the offer, or the price, then run another week.
• Kill: no replies, no signups, and no one paying for any alternative.

Write down the result and the evidence. “Let's give it another month” without new evidence is how side projects become expensive hobbies.

The traps to avoid

• Asking friends whether they like the idea.
• Asking “would you use this?” instead of asking about past behavior.
• Building an MVP before testing the offer.
• Confusing traffic with demand.
• Targeting only other indie hackers.
• Treating one passionate rant as a market.

If you want a shortlist to start from, browse validated opportunities or pressure-test your own idea with the AI analyzer.