Scoring Framework

SaaS Opportunity Score: Rate Any Idea 1-10 (Build or Not)

Six dimensions, calibrated thresholds from 3,100+ real scored opportunities, and a decision rule that tells you when to stop.

12 min readShare →
5.2 / 10
Average score, 3,100+ ideas
~3%
Score 8 or higher
~56%
Score under 5
6
Dimensions scored

A SaaS opportunity score rates an idea from 1 to 10 across six dimensions: pain severity, willingness to pay, competition level, MVP simplicity, marketing difficulty and acquisition potential. The point is not the number. The point is that scoring each dimension separately stops one exciting attribute from hiding five fatal ones.

The short answer

Score 8 or above and build. Score 5 to 8 and validate first. Score under 5 and drop it. Those thresholds are calibrated against 3,100+ real scored software opportunities, where the average overall score is 5.2 out of 10, only about 3% clear 8, and roughly 56% fall under 5. If your own idea keeps scoring 9, your scoring is broken, not your idea. Snapshot as of August 2026.

Key takeaways
  • Most ideas are mediocre and that is normal. The average documented opportunity scores 5.2 out of 10.
  • A score of 8+ is rare, roughly 3%. Treat 8 as exceptional, not as a passing grade.
  • Competitive gap scores highest (5.7 average) and pain intensity lowest (4.2). Room in the market is common. Severe pain is not.
  • Willingness to pay is the dimension with no workaround. Severe pain with no budget is a hobby.
  • Score against evidence, not vibes. Check the pain in 1M+ real complaints before you assign a number.

The rubric in one table

Score each dimension 1 to 10, then take the average. Four of these six map directly onto dimensions we score across our own opportunity database, so the benchmark column is measured rather than asserted.

DimensionQuestion it answersReal averageScore 8+ when
Pain severityHow badly does this hurt?4.2People pay for ugly workarounds today
Willingness to payIs there budget attached?4.9 (demand proxy)The sufferer controls a budget line
Competition levelIs the gap real?5.7Incumbents exist but all miss the same thing
MVP simplicityCan you ship v1 alone?4.8Useful in under 6 weeks, no exotic integrations
Marketing difficultyCan you reach them?Not directly scoredThe audience gathers somewhere you can post
Acquisition potentialIs there an exit?Not directly scoredAdjacent players buy in this category already
OverallBuild or not5.2Roughly 3% of ideas
Source: BigIdeasDB opportunity scoring across 3,100+ documented software opportunities (August 2026). Benchmarks shown where we score the dimension directly.

What a good score actually is

Scoring frameworks fail when nobody calibrates them. Everyone rates their own idea 8 or 9 because they have no reference distribution. Here is ours, from real documented opportunities rather than pitches.

Score bandShare of ideasWhat to do
8 to 10~3%Build. This is genuinely rare.
7 to 8~9%Run a two week validation sprint, then decide.
5 to 7~32%The crowded middle. Attack the weakest dimension.
Under 5~56%Drop it. Your time is the scarce asset.
Source: BigIdeasDB, distribution of overall opportunity scores across 3,100+ opportunities (August 2026).

Over half of all documented software gaps score under 5. That is the single most useful fact on this page, because it means a mediocre score is the expected outcome, not a sign you researched badly. See the most underserved software markets for where the higher scores actually cluster, and niche opportunities by industry for the category breakdown.

1. Pain severity

Score 8+ when people already pay for an ugly workaround. That is the cleanest test. A spreadsheet maintained by a human, a contractor doing manual data entry, or a hated tool nobody cancels all indicate real severity.

Pain intensity is the lowest scoring dimension in our data at about 4.2 out of 10. Most complaints are irritation rather than agony, and irritation does not open wallets. Look for this shape:

"I need to convert about 6 months of PDF invoices to LEDES files. Does anyone know of a tool that can automate this? I've done some regex-based approaches but always end up with multiple problems." via r/LegalTech

Named format, named volume, a failed do-it-yourself attempt. That is an 8. Compare to "wish this app was faster", which is a 3. Search your own idea in the complaints browser before assigning a number, or read business pain points in 2026 and finding SaaS ideas from real pain points.

2. Willingness to pay

Score 8+ only when the person feeling the pain controls a budget. This is the dimension with no workaround, and the one founders inflate most.

The trap is the split between sufferer and buyer. An overworked junior employee feels the pain intensely and cannot approve $50 a month. Their manager can, and does not feel the pain. B2B ideas die here constantly.

"Monitoring performance metrics, comparing channel effectiveness, and generating client reports was an absolute nightmare of scattered data." via r/automation

Client reporting is billable work, so the pain and the budget sit with the same person. That scores high. Check whether anyone monetises the fix using revenue intelligence, and read revenue benchmarks by category for what categories actually earn. Median MRR across startups with verified revenue sits under $150 while the mean is near $4,300, so assume the median unless you have evidence otherwise.

3. Competition level

Score 8+ when incumbents exist but all miss the same specific thing. An empty market is usually a dead market, not an open one.

Competitive gap is our highest scoring dimension at about 5.7. Room in the market is the common case. The mistake is treating "no competitors" as a 10 when it usually means nobody pays. Competitors validate the market. See low competition SaaS ideas and turning G2 reviews into SaaS ideas for finding the shared blind spot.

4. MVP simplicity

Score 8+ when a solo developer ships something useful in under six weeks. Feasibility averages about 4.8 in our data, and the recurring killer is integration surface, not algorithmic difficulty.

Every third party API you require multiplies auth work, rate limits, breaking changes and support load. Ideas that need five integrations to be useful at all score 2, however simple the core logic looks. See single feature micro SaaS ideas and micro SaaS examples for the shape that ships, plus simple SaaS ideas for solo developers.

5. Marketing difficulty

Score 8+ when your audience already gathers somewhere you can reach without paying. A named subreddit, a forum, a conference, a directory.

We do not score this dimension directly in the database, so treat it as judgement. The practical test: name the exact place you will post on launch day. If you cannot name it, score 3. We mine 170+ subreddits precisely because reachable audiences leave visible trails. See finding business ideas on Reddit and the Reddit sourcing guide.

6. Acquisition potential

Score 8+ when adjacent players already buy companies in this category. Acquisition is the most speculative dimension, so weight it least early on.

Signals that raise it: the category has strategic buyers, your data or integrations would be expensive to rebuild, and comparable deals exist. Signals that lower it: you compete directly with a giant, or your only asset is code anyone could rewrite. See how to find SaaS acquisition targets and SaaS valuation multiples.

Do not score from memory. Check the pain against 1M+ real complaints first.

The build or do not build rule

Average the six dimensions, then apply two overrides. The overrides matter more than the average.

  1. Any dimension at 2 or below is a veto. A 2 on willingness to pay cannot be averaged away by a 9 on MVP simplicity. Low scores multiply, they do not offset.
  2. Willingness to pay under 5 is a veto. Everything else is solvable with effort. Absent budget is not.
  3. 8+ overall and no veto: build. You are in the top few percent.
  4. 5 to 8: validate. Take your lowest dimension and design a test that attacks it specifically. Follow the 8 stage validation framework.
  5. Under 5: drop it and score the next one. Most ideas land here and that is the system working.

The reason to write scores down is that it makes you argue with yourself in writing, which is harder to fake than a gut feeling. For the full workflow see how to validate a startup idea, multi-signal validation, and the idea evaluator guide.

Methodology and limitations

The benchmark numbers come from a live query against our opportunity database on the verification date. Four of the six rubric dimensions map onto dimensions we score directly. Two do not, and we have labelled them as judgement rather than inventing a benchmark.

InputScaleEvidence typeLimitation
Opportunity scores3,100+ scoredStructured gap analysis from B2B reviewsModel generated. Consistent, but not ground truth.
Complaint corpus1M+ complaintsReddit, G2, Capterra, app storesSkews technical and Western. Complainers are not always buyers.
Verified revenue3,700+ startupsSelf-reported and verified MRRSurvivorship bias. Failures stop reporting.
Marketing and acquisitionNot scoredAnalyst judgementNo benchmark exists. Treat these two as opinion.
Source: BigIdeasDB scoring methodology and data inventory (August 2026). Counts rounded.

The honest limitation of any rubric: it measures what it can see. A score is a prioritisation aid for deciding what to investigate next, not a prediction of outcome. Scoring cannot substitute for talking to five people who have the problem, and a high score on a badly framed idea is still a badly framed idea.

Frequently asked questions

What is a SaaS opportunity score?

A rating from 1 to 10 across six dimensions: pain severity, willingness to pay, competition level, MVP simplicity, marketing difficulty and acquisition potential. Scoring each separately stops one strong attribute from masking several fatal ones.

What is a good SaaS opportunity score?

Calibrated against 3,100+ real opportunities: 8+ is genuinely strong and describes about 3% of documented gaps. 7 to 8 warrants a validation sprint, roughly 9%. 5 to 7 is the crowded middle. Under 5 should be dropped, and about 56% land there.

Which dimension matters most when scoring a SaaS idea?

Willingness to pay, because it has no workaround. Severe pain with no budget is a hobby. In our data pain intensity averages about 4.2 while competitive gap averages 5.7, so most markets have room but the pain is mild, and mild pain rarely converts to spend.

Should I build if my idea scores 6 out of 10?

Not yet. A 6 is plausible but unproven, which is where most ideas sit. Find your lowest scoring dimension and design a cheap test that attacks it directly, because that dimension is what will kill the product if you skip it.

Can AI score a SaaS idea accurately?

Consistently, yes. Accurately on its own, no, because a language model infers plausibility rather than measuring demand. Scoring gets reliable when the model is handed evidence: real complaints proving the pain, competitor data proving the gap, and revenue data proving comparable companies earn. Score against the complaint database, not from the prompt alone.

Cite this page
Last verified: August 18, 2026
BigIdeasDB Research. (2026). SaaS Opportunity Score: Rate Any Idea 1-10 (Build or Not). BigIdeasDB. Retrieved from https://bigideasdb.com/saas-opportunity-score
Founder, BigIdeasDB
Share →
Keep reading