Dear SaaStr: Have All the Good SaaS Ideas Been Built?

Dear SaaStr, I look around and it feels like every decent SaaS category already has a winner (or three). CRMs have CRMs. Project management has… seventeen thousand project management tools. Even “AI” now has an AI tool to help you pick an AI tool. So be honest: have all the good SaaS ideas been built?

Answer: Sort of… and also absolutely not. (Yes, that’s a real answer. SaaS is a business of annoying truths.)

The “sort of” part is this: the obvious, horizontal categories are crowded. If you’re planning to launch “Slack, but with more slacks,” you’re going to learn a valuable lesson about customer acquisition costs and humble pie.

The “absolutely not” part is the fun part: software keeps changing what’s possible, buyers keep changing what they expect, and entire industries are still running mission-critical processes on spreadsheets, email chains, and the sacred ritual of “Janet knows how it works.” That gap between how work actually happens and how software should support it is where new SaaS ideas are born.

Why “All the Good Ideas Are Taken” Feels True (Even When It Isn’t)

If you’re feeling idea-anxiety, you’re not alone. SaaS today is like showing up to a potluck where everyone brought mac and cheeseexcept half of them are venture-funded and the other half have “AI” sprinkled on top like parsley.

Three things create the illusion that the market is “done”:

1) The easy categories already have defaults

In big horizontal markets, customers don’t shop for “the best.” They shop for “the safest decision I can defend in a meeting.” Once a tool becomes a default, switching feels risky, even when the tool is mediocre. (Mediocrity, in enterprise software, is often a feature: it’s predictable.)

2) Distribution is harder than it used to be

It’s not 2013 anymore. Paid acquisition is expensive, inboxes are crowded, and everyone has a “community” that’s mostly one person posting and 400 people lurking. Great products still win, but they win faster when they’re built with a distribution wedgeworkflow-driven sharing, strong integrations, platform ecosystems, or clear ROI that makes a champion look smart.

3) “SaaS ideas” get confused with “SaaS features”

Adding a dashboard, a chatbot, or an “AI summary” is not a SaaS idea. It’s a feature. A SaaS idea is when you can point to a job people must get done repeatedly, with money and consequences attached, and say: “We can own that workflow end-to-end.”

The Quiet Truth: Most Big SaaS Winners Are Remakes

Here’s a comforting thought: SaaS has always been a remix culturejust with more recurring revenue. Many breakout companies weren’t “brand new categories.” They were next-generation versions of older categories, rebuilt for a new platform shift, a new buyer, a new workflow, or a new go-to-market motion.

Why do remakes keep working?

• Platforms change: on-prem → cloud → mobile → collaboration → AI-native.
• Expectations rise: users now demand fast onboarding, consumer-grade UX, and self-serve trials.
• Budgets move: departments buy tools without waiting for a six-month procurement saga (sometimes).
• Work changes: distributed teams, remote ops, compliance, privacy, and real-time analytics became non-negotiable.

So noyou don’t need to invent teleportation. You need to find a workflow where the incumbent experience feels like using a fax machine… on purpose.

Where the Next Great SaaS Ideas Actually Come From

If you want fresh ideas, stop scanning app directories like you’re speed-dating. Instead, follow the money, the pain, and the messy reality of how work gets done.

1) “Spreadsheet businesses” (a.k.a. the unclaimed kingdom)

Industries that live in spreadsheets aren’t “low tech.” They’re high stakes and high context. Spreadsheets are flexible, but they don’t enforce process, permissioning, audit trails, approvals, or data integrity. That’s why the moment a business scalesor gets regulatedspreadsheets become fragile.

Great SaaS ideas here look like: take a spreadsheet workflow, turn it into a product with guardrails, and add collaboration + reporting + integrations. The trick is not “build a database.” The trick is “capture the actual decisions people make and the sequence they follow.”

2) Vertical SaaS that becomes the “operating system” of a niche

Vertical SaaS is still one of the most durable idea factories in software. Why? Because niche industries have niche workflows, niche data formats, and niche compliance headaches. When a product truly matches a vertical’s daily reality, it becomes stickyand can become the system of record.

And here’s what changed recently: AI can make small markets feel big by expanding what the software can do (not just what it can track). In other words, vertical SaaS can move from “record-keeping” to “work execution.”

Example shape of a modern vertical SaaS opportunity:

• Start with a core workflow (scheduling, quoting, claims, dispatch, billing, documentation).
• Add revenue-adjacent features (payments, financing, inventory, compliance reporting).
• Layer in AI to reduce labor (drafting, routing, customer response, QA, back-office ops).

3) AI “inside” workflows, not AI “as a product category”

“AI product” is too vague. Customers don’t buy “AI.” They buy outcomes: fewer errors, faster turnaround, lower labor cost, higher conversion, better compliance. The winning pattern is embedding AI into a workflow where:

• There’s a lot of repetitive or document-heavy work.
• There are clear quality checks (so you can measure improvement).
• There’s real cost attached to mistakes or delays.

The best AI-driven SaaS ideas often look boring on the surface (which is a compliment). They’re “do the paperwork faster,” “reduce rework,” “route requests correctly,” “answer customers accurately,” “turn raw inputs into a compliant output.” That’s where budgets live.

4) Integrations that turn chaos into a system

Every company today has a stack. And stacks drift into chaos: duplicate records, mismatched fields, broken automations, “why is the billing system yelling at the CRM again?” Integration-heavy SaaS is thriving because companies will pay to reduce operational friction.

New ideas here come from:

• Cross-tool workflows: approvals, audits, handoffs, lifecycle transitions.
• Data quality: enrichment, deduping, governance, lineage, permissions.
• Compliance automation: evidence collection, reporting, change tracking.

A Simple “Is This a Real SaaS Idea?” Filter

Before you fall in love with a clever concept, run it through this brutally simple checklist. A strong SaaS idea usually hits at least four of the five:

1) Painful

Not “annoying.” Painful. People complain about it unprompted. They’ve tried hacks. They’ve made templates. They dread it weekly.

2) Frequent

The job happens often enough that behavior change is realistic. Annual workflows are harder (unless compliance forces it).

3) Priced to value

You can charge based on ROI, risk reduction, or revenue impactnot “$9 because other tools are $9.”

4) Has a natural buyer and champion

Someone feels the pain directly and can drive adoption. If you need five departments to agree, congratulationsyou invented a committee.

5) Has a wedge

A reason you can win distribution: self-serve onboarding, virality, platform marketplaces, compliance urgency, or a narrow vertical where word-of-mouth travels fast.

The Big Opportunity: “Next-Gen” in Every Category

Even in crowded markets, there’s room when something fundamental shifts. Common “next-gen” angles include:

AI-native UX (less clicking, more doing)

Users are tired of software that behaves like a filing cabinet with opinions. AI is pushing interfaces toward “tell the system what you want” instead of “click 14 times to maybe get it.” That’s a real shiftespecially when paired with guardrails and auditability.

Outcome-based pricing (charging for results)

Traditional SaaS pricing is seats + tiers + a little confusion for flavor. In some workflows, especially where AI reduces labor, pricing can align closer to outcomes: documents processed, claims resolved, tickets deflected, dollars recovered, errors prevented.

Product-led growth as a built-in distribution engine

For tools used by individuals, teams, and departments, product-led growth (PLG) is still a powerful way to break into markets without a giant sales team. The product becomes the acquisition channel: users try it, invite others, and convert when value is obvious.

So… What Should You Build? A Practical “Idea Hunt” Plan

If you want to find a SaaS idea that isn’t just “me too,” here’s a practical process you can run in a monthwithout pretending you’re a prophet.

Week 1: Pick a pond (vertical or workflow)

Choose one industry or function where you can get close to real users. Examples: logistics ops, clinic admin, legal intake, construction project controls, insurance servicing, HR compliance, finance close, customer support QA, procurement approvals.

Week 2: Map one ugly workflow

Don’t map the “happy path.” Map the messy reality: exceptions, handoffs, approvals, rework, missing data, “we email a PDF because the system can’t handle it.” These ugly parts are where customers pay.

Week 3: Prototype the wedge

Build the smallest thing that delivers a real outcome. Not a platform. Not a dashboard museum. A wedge that solves one painful job end-to-end: “turn intake into a ready-to-process case,” “route requests with the right metadata,” “generate the compliant output with review steps,” “close the loop with customer messaging.”

Week 4: Validate willingness to pay

Ask for commitment, not compliments. A pilot fee. A letter of intent. A prepay discount. Access to production data. Integration help. Anything that signals: “This matters enough to allocate budget and attention.”

The Answer, in One Sentence

No, all the good SaaS ideas haven’t been built. The obvious ideas have been built. The real opportunities are in the evolving edges: vertical workflows, AI-driven execution, messy integrations, compliance-heavy processes, and next-gen remakes where the incumbent experience is stale.

In SaaS, the idea isn’t “new.” The idea is right: right customer, right pain, right timing, right distribution, right execution. If you can nail those, the market doesn’t care whether your category existed before. It only cares that you make the work easier, cheaper, faster, or safer.

Experience Add-On: What Founders (and Teams) Learn While Chasing “Good SaaS Ideas” (Approx. )

When people talk about SaaS ideas, they usually imagine a lightning bolt: someone has a brilliant thought, builds a product, and rides into the sunset on a surfboard made of ARR. The more common reality is less cinematic and more… spreadsheet-shaped.

Experience #1: The “crowded market” panic fades when you sit with real users. Teams often start by obsessing over competitors. Then they interview ten potential customers and realize something calming: buyers don’t experience “the market,” they experience their Tuesday. A category might be crowded, but a workflow can still be underserved. The competitor list stops mattering the moment a user says, “I hate this step so much we made a 27-tab spreadsheet and it still breaks.” That’s not a feature requestthat’s a business.

Experience #2: The best ideas start as annoyingly specific. Many successful products begin as something that sounds too narrow to matter: “intake for this one type of service,” “compliance evidence for this one regulation,” “dispatch + billing for this one trade,” “QA for this one type of support team.” The founders who win don’t broaden too early. They go deep until knowing the customer feels like muscle memory. Then, once they’ve become the default in that niche, they expand to adjacent workflows that share data and users.

Experience #3: Distribution is usually the real product. Founders love features because features are tangible. Distribution is weird and social and uncomfortable. But when teams look back, the growth inflection often came from a distribution wedge, not a new UI. A self-serve trial that actually gets users to value quickly. An integration that makes the product show up where work already happens. A report that gets forwarded to leadership. A compliance deadline that forces adoption. The “product” becomes the easiest path to a result people already need.

Experience #4: AI doesn’t remove the need for workflow designit makes it more important. When teams add AI, they often discover that the hard part isn’t generating text or extracting fields. The hard part is building the review loop: who approves, what’s logged, what happens when confidence is low, how exceptions get routed, how the system learns. The winners treat AI like a powerful intern: helpful, fast, occasionally wrong, and always in need of guardrails. Customers trust you when you’re honest about limits and obsessive about reliability.

Experience #5: “Good idea” is a lagging indicator. In the early days, most ideas feel medium. What makes them “good” is the compounding: better onboarding, tighter positioning, improved retention, smarter pricing, and a clearer promise. The teams that keep shipping toward one measurable outcomefaster close, fewer errors, more conversions, less laboroften turn a “fine” idea into a great business. And the teams that chase every shiny feature often end up with a beautiful product that nobody adopts.

So if you’re hunting for the next great SaaS idea, don’t look for something nobody has done. Look for something people are doing badlyrepeatedlybecause they don’t have a better option. Then build the tool that makes them wonder how they ever lived without it.