What Are SaaS Ideas and How Do You Find a Viable One?

A SaaS idea is a software product delivered over the web and paid for on a recurring basis. It is viable when a reachable group of customers has a recurring problem they already search for, and the price they will pay exceeds the cost of serving them. You find one by starting from existing search demand, screening for recurring pain and willingness to pay, then validating cheaply before you build. MuckBrass.com frames the core principle with an old Yorkshire saying: "where there's muck, there's brass" — unpleasant work pays, because supply and demand make pleasant work cheap.

SaaS idea vs. micro-SaaS vs. generic startup idea

The three terms overlap but differ in scope and business model. Use this table to decide which one you are actually pursuing.

The distinction matters because micro-SaaS ideas are judged on a different bar: a small niche with modest search volume can still support a one-person product, while a broad SaaS idea needs a larger addressable market to justify the build.

Why search demand beats founder intuition

MuckBrass's central argument, quoting Paul Graham, is that smart people have bad ideas because they build what they find cool rather than what the market needs. The site's counter-principle is direct: "When it hurts, they search. Build what they Google, not what you think they need."

The mechanism is simple. Search volume is a proxy for existing, expressed demand — people typing a problem into a search box are already looking for a solution. Competition is a proxy for how crowded that demand already is. Reading the two together tells you whether a gap exists.

MuckBrass publishes both signals alongside each listed idea. From its page:

Read the pattern: high volume with low competition (workout plans) is the strongest signal; high volume with high competition (no-code builder) means you need a sharp wedge; near-zero volume with zero competition (AI food critic, faceless content) may mean an untapped niche or simply no demand — you cannot tell from the numbers alone, so validate before committing.

How to screen a SaaS idea

Run every candidate through four filters before spending build time.

1. Recurring pain. Does the problem recur often enough that a subscription makes sense? A one-off need (a single tax filing) fits a one-time purchase, not SaaS.
2. Willingness to pay. Is the buyer a business or a professional whose time or money is at stake? MuckBrass's "muck" principle applies: work people dislike doing themselves is where the money is.
3. Reachable segment. Can you name the customer and find them in one or two channels — a search term, a community, a marketplace? "Everyone" is not a segment.
4. Buildable wedge. Can a small MVP deliver the core value? If the first version requires a large team or proprietary data, the idea is not yet a micro-SaaS candidate.

How to validate before you build

Validation is about confirming demand exists and people will pay, at the lowest possible cost. A practical sequence:

• Keyword check. Confirm the problem is searched for, and note both volume and competition. MuckBrass's AI analyzer is built around this step: it surfaces trending keywords, and the site's workflow is "AI analyzes trending keywords → build a product around it → see the traffic rolling in."
• Landing-page test. Describe the product and its price, then drive the target search term to the page. Measure sign-ups or clicks on a "buy" or "join waitlist" button — intent, not just interest.
• Small MVP. Build only the core loop that solves the recurring problem. MuckBrass lists "MVP-as-a-Service" as one of its offerings, reflecting the idea that the first version should be minimal.
• Pre-sell or pilot. Ask a handful of target customers to pay or commit before the full product exists. A refusal at this stage is cheaper than a refusal after launch.

A concrete example: suppose you are considering the hypertrophy workout-plan idea. The search signal is strong (92K/month, competition 19). Before building, you would check whether the searchers are individuals willing to pay a small monthly fee or coaches buying for clients, put up a landing page offering customized plans, and see whether visitors convert to a paid waitlist. If they do, build the plan generator; if not, the volume was curiosity, not demand.

Common traps

• Building what you find cool. The Paul Graham point MuckBrass leads with: founders pick ideas they enjoy, then look for demand. Reverse the order.
• Mistaking zero competition for opportunity. A 0/100 competition score with 10 searches a month may be an empty market. Treat low volume as a question to validate, not an answer.
• Ignoring the competition score. High volume with high competition means you need a specific wedge — a niche, a price point, or a workflow the incumbents ignore.
• Skipping the payment test. Interest (sign-ups, traffic) is not willingness to pay. Test the transaction, not just the attention.

Where to start

Use MuckBrass.com's idea list as a demand-screening starting point: filter for ideas with meaningful search volume and low-to-moderate competition, then run each through the four filters above and the validation sequence before writing code. The site's own framing is the shortest version of the method — find where it hurts, build what they search for, and confirm they pay before you scale.