How to validate SaaS ideas before you write code
How to validate SaaS ideas before you write code: read complaints on the marketplace, check monthly searches and competitors, and find who pays for the job.
If you want to know how to validate SaaS ideas before you write any code, run four checks against the platform your product would live on. Read the complaints its users already post in marketplace reviews and vendor forums. Check how many people search for the task each month. Look for people who already pay a freelancer to do the job by hand. Then count the apps already selling a fix. When two or more checks find evidence, the idea is ready for a commitment test, where real buyers pre-order or pay for a pilot before you build. When none do, keep looking before you open an editor.
This guide is for developers choosing a SaaS or micro SaaS product to build, often an add-on for a platform such as Shopify, Calendly or monday.com. Those buyers complain in public and the competition sits in one app store, which makes the checks cheap. The general method for any business, including interviews and kill criteria, is in how to validate a business idea.
Key takeaways
- Check complaints, monthly searches, paid demand and competitors separately. They often disagree.
- Count distinct people behind a complaint, not posts or upvotes.
- Search volume measures interest in a task. It says nothing about willingness to pay for your app.
- A Fiverr gig with buyer reviews shows a job already has a price.
- Count the apps already selling a fix before you build. Five incumbents and zero call for different plans.
SaaS idea validation methods and what each one proves
SaaS idea validation is the work of collecting public evidence about a software idea before any code exists: who complains about the problem, who searches for a fix, who already pays for the job, and which apps already sell one. Many guides on how to validate a SaaS idea start with interviews or a landing page. Interviews go better once you know which complaint to ask about, so run these four checks first.
| Check | Where to look | What it proves | What it does not prove |
|---|---|---|---|
| Complaints | App marketplace reviews, vendor forums, Reddit | The problem exists for named users | That anyone will pay |
| Monthly searches | Google Keyword Planner, task-shaped phrases | People look for a fix | That they want your product |
| Paid demand | Fiverr gigs with buyer reviews | The job already has a price | That they will pay a subscription |
| Competitors | The platform’s app store, the web | Someone sells a fix (or nobody does) | Whether the gap is still open |
No single row proves a business. Our evidence method treats an idea as worth testing only when independent rows agree.
Start with complaints on the platform you would build for
A SaaS idea usually fixes a gap in a product people already use, so start with the places where that product’s users write: app marketplace reviews, the vendor’s community forum and the product’s subreddit. That is where we read every day. We keep the genuine complaints, drop praise, off-topic chatter and support noise, and group posts about the same frustration into one pain card with every quote linked to its source. As of November 2026 the index holds 7,775 pain cards across 78 marketplaces.
When validating SaaS ideas from complaints, count people, not posts. Our card on Calendly users who can’t create recurring appointments groups 28 posts from 26 people, has a demand score of .92 (a 0 to 1 number that weighs reach, recency, engagement and willingness to pay) and marks willingness to pay as explicit. One of them wrote on Reddit: “Please tell me there’s a way I can make 17 appointments for the next 17 saturdays for the same exact time all at once.” (source) Another wrote on the Calendly community forum: “I have been asking Calendly to offer this feature for YEARS.” (source)
A smaller card can be just as specific. Ecwid merchants who reconcile inventory by hand is 17 posts from 14 people with a score of .83. One merchant wrote: “Inventory counts across Shopify and Amazon never line up and I end up pasting numbers into a spreadsheet every morning just to see what actually sold overnight.” The same post ends with the cost of the workaround: “Now I just accept the 20 minutes of copy-paste and move on with my day” (source).
That one post names the user, the failure, the workaround and its daily cost. A first version has to beat 20 minutes of copy-paste every morning.
Monthly searches: what the number can and cannot tell you
Search volume is the second check. Put short phrases that describe the task into Google Keyword Planner, not your product name, and read two numbers: average monthly searches and advertiser competition. Competition shows that advertisers pay to reach those searchers, which adds a commercial-intent signal on top of interest.
Our public sample validation report shows how small the useful numbers can be. It checks a Shopify stock sync idea, and the one function with evidence collected 190 searches a month from three phrases: shopify inventory sync at 90, stock sync shopify at 70 and sync shopify and square inventory at 20. The report sets a bar of 50 searches a month and counts no search volume for a function unless a confirmed complaint backs it. Use both rules if you check by hand.
On the two cards above, the public page shows search demand in a range of 10 to 100 searches a month. That is low, and normal for a niche add-on. Low volume does not kill a SaaS idea that lives inside a marketplace, because buyers there can find apps in the store itself. It does mean search ads and SEO are unlikely to be your launch channel.
Paid demand: find who already pays for the job
A buyer who hires a freelancer to do the job by hand has already spent money on it, which makes a Fiverr gig with buyer reviews the strongest public evidence you can find before launch. Our paid demand catalogue groups Fiverr gigs by the concrete task and holds 78,710 clusters. Treat buyer reviews as a lower bound of paid demand, not a count of orders.
Complaints can carry payment evidence too. Our card on Linear teams that lack custom fields groups 17 posts from 16 people, and one GitHub comment reads: “Despite being eligible for Asana’s free tier, we currently pay to have custom fields.” (source) That team already pays another product for the missing function.
For a SaaS idea, paid demand also suggests a price and a pricing model. Our published idea for a Squarespace static site export found 37+ paid Fiverr orders with a median order of $92. A site export happens once, so the idea page proposes a one-time fee per export, tested at $92, instead of a monthly plan.
When nothing is sold, write that down too. Two of our published Shopify ideas show “none found” for paid orders, and the page marks them “payment not proven”. That gap is what a commitment test exists to fill.
Competitors: count the apps already selling a fix
Before you trust a gap, search the platform’s app store for the job in plain words and install the closest products. Write down what each one refuses to do. We mark a researched pain as wide open (no tool solves it today) or has gaps (someone solves it and users keep complaining anyway). The glossary defines both.
The count changes the plan. Our published Shopify bundle stock idea lists 5 apps already selling a fix, including BR Stock Take: Inventory Count, Easify Inventory Sync and Sync Power. The WhatsApp breakage alert idea for Chrome lists 0. With five incumbents you need one specific failure their users still write about. With zero, ask why nobody built it before you assume the field is free; one possible answer is a platform API that blocks the job.
What 10 published ideas show about validated SaaS ideas
A list of validated SaaS ideas is only as good as the checks behind each entry. Our published ideas show every check side by side, and the checks rarely agree. Here are six of the ten as they read today:
| Idea | Platform | People who complained | Google searches a month | Paid Fiverr orders | Apps already selling a fix |
|---|---|---|---|---|---|
| CRM and Desk contact sync | Zoho Marketplace | 14 | ~270 | 64+, median $41 | 1 |
| Missed-fraud checks | Shopify App Store | 21 | ~880 | none found | not checked |
| Bundle stock reservation | Shopify App Store | 45 | ~270 | none found | 5 |
| Plan sheet takeoffs | Procore App Marketplace | 14 | ~10,190 | 66+, median $17 | not checked |
| Campaign blueprint planner | HighLevel Marketplace | 121 | ~10 | 462+, median $12 to $173 | not checked |
| Static site export | Squarespace Extensions | 10 | ~2,220 | 37+, median $92 | not checked |
The HighLevel idea has the most complaints and the most paid orders in the table, and about 10 searches a month. The Procore idea has 14 complaints and about 10,190 searches. Across the ten ideas VettedGaps had published as of November 2026, search was not measured for the three Chrome extensions, paid orders were not found for two, and competitors were checked for only three. Each idea page shows those gaps openly, as “not measured”, “none found” or “not checked”.
How to validate SaaS ideas for a micro SaaS add-on
A micro SaaS is usually an add-on for one platform, so every check happens in one app store and one community, against one API. Definitions and examples live in what micro SaaS is; this section covers the checks that matter before code.
Before code, settle three things:
- The platform lets a third-party app do the job and will keep letting you. Some genuine complaints describe limits of the platform itself, and an outside app inherits them. The Squarespace export idea lists this risk on its own page: Squarespace could block or throttle the extension’s API access if it sees it as a churn tool. The micro SaaS build guide shows how to check the API reference.
- The price, set before you build, with the paid demand median as the floor.
- A commitment from the people who wrote the complaints, asked with a mockup, with the number that ends the idea written down first.
The micro SaaS overview linked above lays out this plan day by day over two weeks.
If your idea is a Chrome extension, the evidence comes from one-star reviews of existing extensions. Our three published Chrome ideas show complaints and paid orders but no search measurement, so plan to check search demand yourself.
FAQ
What does a SaaS idea validator check?
A good one splits your idea into functions and checks each against complaints, paid demand, search volume and competitors, then says plainly where no evidence was found. Ours grades each function from E0 (not observed) to E4 (people pay for a product). What AI validators can and cannot check is covered in our guide to AI tools for validating product ideas.
How many complaints are enough to start?
There is no fixed number. Several unrelated people in more than one source describing the same failure is a pattern; one long thread is an anecdote. The Calendly card above has 26 different people, the Ecwid card 14.
Is high search volume enough for SaaS validation?
No. Volume shows where people look. In the table above, the idea with about 10 searches a month had the most paid orders.
Other ways people search for this
Some readers search for how to validate saas idea before building, which is the question this guide answers. Others type how to validate saas idea monthly searches or saas idea validation keyword competition seo. Both point at the two Keyword Planner numbers, volume and advertiser competition, covered in the section on monthly searches.
Your next step
The short version of how to validate SaaS ideas before code: check complaints from the platform’s users, monthly searches for the task, money already spent on the job, and the competitors, each on its own. The sample validation report linked above shows the output for one real idea. To run the same checks on yours, describe it in idea validation and pick the marketplace it would sell on. It is a Pro feature at $15 a month on the pricing page, with 5 validations a day.