ThisCalculator

Everyday

How to Evaluate a SaaS Idea Before Building

Updated · Standard formula, shown below

How to Evaluate a SaaS Idea Before Building

This guide walks you through a practical, step-by-step process to assess a SaaS idea before you invest time or money. You’ll learn how to test demand, understand your market, and avoid common pitfalls that lead to failed products. By the end, you’ll have a clear go/no-go decision framework.

What You’ll Need

  • A notebook or digital document for notes
  • Access to online survey tools (e.g., Google Forms, Typeform)
  • A way to record interviews (with permission) – phone, laptop, or recording app
  • Basic spreadsheet software for tracking responses and metrics
  • Optional: $50–$100 for targeted ads (if you want to run a landing page test)

Step-by-Step

  1. Articulate the problem and your solution in one sentence. Write down who has the problem, what the problem is, and how your SaaS solves it. Example: “Freelance designers struggle to track project profitability; my tool automatically calculates profit from time and expenses.� If you can’t make it clear and concise, the idea is still fuzzy.
  2. Identify your target customer segment. Define who specifically will pay for this. Be narrow – “small law firms� is better than “businesses.� List 3–5 specific characteristics (e.g., size, industry, role). If you can’t name a specific segment, you can’t validate demand.
  3. Conduct 10–15 customer discovery interviews. Reach out to people in your target segment (via LinkedIn, forums, or personal network). Ask open-ended questions about their current workflow, frustrations, and what they’ve tried before. Do not pitch your idea; listen for the problem. Look for patterns: do they mention the problem without prompting? Do they express urgency?
  4. Analyze the interviews for a “must-have� signal. After each interview, note whether the person 1) explicitly stated the problem, 2) showed emotional frustration, and 3) asked about a solution. If at least 7 out of 10 do all three, that’s a strong signal. If most are lukewarm, the problem may not be painful enough.
  5. Research existing competitors and alternatives. Search Google, Product Hunt, and app directories for similar tools. Also look for “manual� alternatives (spreadsheets, email, paper). For each, note what they do well and where they fall short. If there are zero competitors, be wary – it might mean no one cares, or that the market is underserved. If there are many, figure out your differentiation.
  6. Build a landing page with a clear value proposition and a call-to-action. Use a simple tool like Carrd or Unbounce. The page should explain the problem, your solution, and ask visitors to enter their email for early access or to join a waitlist. Do not build the product yet.
  7. Drive targeted traffic to the landing page. Share it in relevant communities (Reddit, Facebook groups, niche forums) and/or run a small ad campaign targeting your specific segment. Aim for 100–200 visitors over 2 weeks. Track how many sign up.
  8. Measure the conversion rate. A healthy early-stage conversion rate (visitor to email signup) is 10–30% when traffic is highly targeted. If you get less than 5%, your value proposition or the problem itself may be weak. Use a free tool like Google Analytics or the landing page’s built-in stats.
  9. Offer a pre-order or “letter of intent.� The strongest validation is money. Add a button on the landing page that says “Pre-order now – 20% off launch price� or “Request a demo.� If people are willing to pay or book a call, that’s a much stronger signal than an email signup. Even 5 pre-orders or 10 demo requests is meaningful.
  10. Calculate the rough market size (bottom-up). Estimate the number of potential customers in your segment (e.g., “10,000 freelance designers in the US�). Multiply by the price you plan to charge (e.g., $20/month). That gives you a rough annual revenue potential (10,000 × $20 × 12 = $2.4M). If that number is too small for your goals, reconsider.
  11. Build a minimum viable product (MVP) with just the core feature. Only after you have positive signals from steps 4, 8, and 9 should you build anything. The MVP should solve the one problem you validated, nothing more. Use no-code tools (Bubble, Glide) or a simple prototype to test with a handful of users.
  12. Get 5–10 beta users to use the MVP. Reach out to your interview participants and landing page signups. Ask them to use the product for a week. Watch them (via screen share or analytics) and ask: “Would you be upset if this disappeared?� If most say yes, you have a product worth pursuing.

Common Mistakes

  • Falling in love with your idea. You’ll be biased to see positive signals. Force yourself to look for negative evidence.
  • Asking leading questions in interviews. “Would you use this?â€� gets a polite yes. Instead ask “How do you solve this today?â€� and “What’s the most frustrating part?â€�
  • Relying on friends and family. They’ll be nice. Seek out strangers in your target segment.
  • Building before validating. Coding a full product is the most expensive way to test an idea. Use the steps above to fail cheaply.
  • Ignoring the “manualâ€� alternative. If people are already solving the problem with a spreadsheet, that’s a competitor. You need to be 10x better to make them switch.
  • Confusing interest with commitment. An email signup is cheap. A pre-order or a scheduled demo is commitment. Weight those much higher.

Tips

  • Talk to at least 10 people in your target segment before making any decision. Patterns matter more than individual responses.
  • Use the “Mom Testâ€� approach: ask about the past and present, not hypothetical futures. “What did you do last time you had this problem?â€� beats “Would you use this?â€�
  • Keep your landing page copy benefit-focused, not feature-focused. “Save 5 hours a weekâ€� is better than “Automated reporting.â€�
  • If you’re not technical, use no-code tools for the MVP. You can validate without writing a line of code.
  • Track your time. If you’ve spent more than 100 hours on validation without a clear “yes,â€� step back and rethink.

Troubleshooting

  • You can’t find people to interview. Try LinkedIn Sales Navigator (free trial), Reddit subreddits, or niche Facebook groups. Offer a $5 Amazon gift card for a 15-minute call. If you still can’t find anyone, that’s a signal that the segment is too small or hard to reach.
  • Landing page traffic is low. Your targeting is likely too broad. Narrow your ad audience or choose a more specific community. Also, test different headlines and value propositions – A/B test two versions.
  • Conversion rate is below 5%. Revisit your value proposition. Are you clearly stating the problem and the outcome? Get feedback on the page from unbiased people. It might also be that the problem isn’t painful enough.
  • Interviews are mixed – some love it, some don’t. That’s normal. Look for a common thread among those who love it. Maybe your real segment is narrower than you thought. Pivot your targeting and re-interview.
  • No one pre-orders. It could be that the price is wrong, or the trust isn’t there yet. Try offering a money-back guarantee or a “founder’s lifetime deal.â€� If still nothing, the willingness to pay is low.
  • You’re not technical and can’t build an MVP. Use no-code tools, or partner with a developer (equity or revenue share). You can also create a “concierge MVPâ€� – manually do what the software would do for a few customers (e.g., send them a report by hand) to test the value.

Frequently Asked Questions

How much time should validation take?
Ideally 2–4 weeks for interviews and landing page tests. If you can’t get a clear signal in that time, the idea is likely weak.

What if I have no technical skills?
You can still validate with interviews and a landing page. For the MVP, use no-code tools or find a technical cofounder. Many successful SaaS founders started non-technical.

How many email signups is “enough�?
It depends on your price and market. A rule of thumb: 100–200 targeted visitors with 10–20 signups is a good start, but pre-orders are worth more than signups.

Should I build a prototype before talking to customers?
No. Talk first. A prototype can bias you and the customer. Understand the problem before you sketch a solution.

What if there are already big competitors?
That’s actually good – it proves the market exists. Find their weaknesses (e.g., poor support, high price, missing features) and position your product to fill that gap.

Can I skip the landing page test?
You can, but it’s a cheap and fast way to gauge interest. Skipping it means you’re relying only on interviews, which are less reliable because people are polite.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.