Most lists of SaaS business ideas are written for clicks, not for founders. They throw fifty disconnected suggestions at you, mix dropshipping with newsletters with AI agents, and assume the bottleneck is not enough ideas. It almost never is. What's actually scarce is a way to tell which ideas are worth a year of your life and which are decorations on a slide.
This is a different list. Before the twelve, there's a single question that filters them. After the twelve, there's a short test for the one you're considering. (Not set on software? The same filter applied to offline models is in 12 unique business ideas.)
If you skip the question and jump to the ideas, you'll do what most founders do: pick the one that sounds coolest and discover six months later that nobody actually needed it.
The Question That Filters Everything
The most useful question you can ask of any product idea is the simplest one:
If this disappeared tomorrow, who would miss it? And would they miss it enough to come looking for it?
Most "business ideas" don't survive that question. A clone of an existing tool, a slightly cheaper version of something popular, a "ChatGPT for X" wrapper — if any of these vanished overnight, nobody would notice. Their users would shrug and move on. They exist by extraction rather than contribution.
The ideas worth building work the other way. Someone, somewhere, would actively miss them. They'd email you to ask what happened. They'd go back to whatever painful workaround they were using before, and they'd resent it. That gap between having the product and not having it is where willingness to pay lives. It's also where retention lives, which is the only thing that matters in SaaS once you get past launch.
This is the difference between extraction (you're trying to capture a slice of a market that already exists) and contribution (you're making something that didn't exist and that someone would feel a real loss without). Extraction businesses can work, but they're brutal — you're competing on price, channel, or distribution from day one. Contribution businesses are easier to defend, easier to charge for, and easier to feel proud of when you're working at midnight.
The twelve patterns below are filtered for contribution. Each one names a specific person who would miss the product, what they'd be doing instead, and how to tell quickly whether your version of it has a real audience.
The 12 SaaS Business Idea Archetypes
These aren't twelve specific ideas; specific ideas date in months. They're patterns — shapes of opportunity that have produced profitable SaaS companies repeatedly, that filter well through the contribution test, and that you can plug your own context into.
| # | Archetype | Who would miss it |
|---|---|---|
| 01 | The Painful Spreadsheet Replacement | A specific operator at a specific kind of company who currently spends two hours a week wrestling with a sheet that's broken in a known way |
| 02 | The Agency-in-a-Box | A founder or operator who needs the output but can't justify agency pricing and doesn't want to hire |
| 03 | The Internal Tool Gone External | A team currently building or maintaining a worse version of the same thing in-house, badly |
| 04 | The Compliance / Regulation Translator | A founder, IT lead, or legal contact who has to sign something attesting to compliance and currently does it in a Google Doc with manual evidence collection |
| 05 | The First SaaS in a Boring Industry | Someone running a small business in an industry you've probably never thought about, who is currently spending a meaningful percentage of their week on logistics or paperwork that should be automated |
| 06 | The Unbundled Feature | A team using the big platform that has to bolt on Zapier, three integrations, and a custom script to make the underbuilt feature work |
| 07 | The "I Wish This Existed" Tool for Your Own Niche | You. Plus the other ten thousand people doing the same job who've had the same thought |
| 08 | The Expensive Tool, Democratized | A startup or mid-market team that needs the capability but has been told "we'll quote you" every time they've tried to buy |
| 09 | The Community-to-Product | The thousand or so most active members of a specific community whose recurring frustration you've been quietly cataloguing for months |
| 10 | The Data Nobody Else Has | Anyone who's been making a decision in the dark and now can't |
| 11 | The Vertical CRM (or ERP, or PM Tool) | A team in a specific industry that currently uses Salesforce / Asana / Monday and spends hours per week translating their actual work into the tool's generic objects |
| 12 | The "Do This Hard Thing for Me" Service-as-Software | Someone who's stopped doing the task themselves because your product does it well enough, and would now have to learn to do it again |
Twelve archetypes, each with who would miss it and the check that tells you whether it is real.
The Painful Spreadsheet Replacement
Find a spreadsheet that someone uses every week, hates using, and would never abandon because it runs their work. Build the smallest possible app around the same data model with one or two killer affordances the spreadsheet can't have — automatic notifications, a cleaner mobile view, audit history, multi-user editing without the formula breaking.
Who would miss it
A specific operator at a specific kind of company who currently spends two hours a week wrestling with a sheet that's broken in a known way.
How to validate
Ask three people in that role to send you the spreadsheet they use most. If two of the three send you the same shape of sheet, you have a market.
Examples in the wild
Airtable was a spreadsheet replacement before it was anything else. So was Notion. So was every vertical CRM that took share from "we use Excel for that."
The Agency-in-a-Box
Look at what a small services agency charges $3k/month for and ask whether 60% of the work is repeatable. If it is, productize the repeatable 60% as software and charge $99/month. You won't replace the agency for big clients. You'll replace it for the 80% of clients the agency couldn't profitably serve anyway.
Who would miss it
A founder or operator who needs the output but can't justify agency pricing and doesn't want to hire.
How to validate
Find an agency in the space and look at their service tiers. The tier they don't enjoy delivering is your product.
The Internal Tool Gone External
Every successful operating company has internal tools that solve real problems beautifully. Most of those tools never leave the company. The pattern: take an internal tool you (or a friend) built that saved your team hours per week, and ask whether the same problem exists at companies in the same shape as yours. If it does, the tool is a product.
Who would miss it
A team currently building or maintaining a worse version of the same thing in-house, badly.
How to validate
Talk to engineers or operators at three companies similar to yours. If they describe the same problem and you can show them a working tool, you have your first paying users.
The Compliance / Regulation Translator
Every regulation creates a market. GDPR, SOC 2, HIPAA, the EU AI Act, state-level privacy laws — each one converts a generic compliance concern into a specific operational headache that companies will pay to make go away. The pattern: pick a regulation that's recent, technical, and feared. Build the tool that turns "we need to comply with X" into "we comply with X."
Who would miss it
A founder, IT lead, or legal contact who has to sign something attesting to compliance and currently does it in a Google Doc with manual evidence collection.
How to validate
Find ten companies in your target segment that visibly need to comply (their site mentions it, their customers ask for it). Ask how they currently track it. If the answer is "spreadsheets and Notion," you have a wedge.
The First SaaS in a Boring Industry
The internet's loudest SaaS markets are saturated. The quiet ones aren't. Plumbing software, funeral home management, livestock auction platforms, dental lab logistics, septic tank routing — these all have real businesses inside them, and most of them are still being run on FileMaker Pro, paper, or one specific desktop app from 2003 that's locked to a single Windows machine in the back office.
Who would miss it
Someone running a small business in an industry you've probably never thought about, who is currently spending a meaningful percentage of their week on logistics or paperwork that should be automated.
How to validate
Pick an industry you have a personal connection to — a family member, a friend, your old summer job. Spend a day shadowing them. The first thing you watch them do that makes you cringe is your product.
The Unbundled Feature
Big horizontal SaaS platforms (HubSpot, Salesforce, Notion, Asana) have features that are tenth-priority for them and dealbreaker for someone. The feature ships at 30% of what it should be. Customers complain. Roadmap doesn't move because the platform has bigger fights.
Who would miss it
A team using the big platform that has to bolt on Zapier, three integrations, and a custom script to make the underbuilt feature work.
How to validate
Search Reddit, G2, and HubSpot/Salesforce community forums for "I wish [Platform] had better [feature]." If the same complaint shows up across years, the gap is real and persistent.
The pattern: find that feature, build the standalone version of it that goes ten times deeper, and sell to the segment for whom it's the whole job.
The "I Wish This Existed" Tool for Your Own Niche
If you spend forty hours a week inside a specific kind of work — backend engineering, technical SEO, video editing, freelance design, B2B sales — you have a list in your head of things you keep wishing existed. Most founders ignore this list because it feels too small, too specific, or too obvious. That's exactly why it's a real list.
Who would miss it
You. Plus the other ten thousand people doing the same job who've had the same thought.
How to validate
Post about the missing tool in the community where your peers hang out (Twitter, an industry Slack, a subreddit). If twenty people reply "I would pay for that," go build the smallest version that would solve their version of the problem.
The Expensive Tool, Democratized
Some categories of software are dominated by enterprise vendors charging $50k–$500k a year. The reason isn't always that the technology is hard. Sometimes it's that the vendor is charging for proximity to a budget — they sell to procurement, they have sales engineers, they negotiate. The work itself can be done with modern infrastructure for a fraction of the cost.
Who would miss it
A startup or mid-market team that needs the capability but has been told "we'll quote you" every time they've tried to buy.
How to validate
Get pricing from the enterprise vendor in the space. If the answer is "we don't list pricing publicly," that's your opening.
The pattern: take a category where the cheapest serious option is $30k+/year and the smallest customer is a 200-person company, and build a self-serve version for the 50,000 companies the enterprise vendor will never call.
The Community-to-Product
The pattern works in reverse from how most founders think about it. Don't build a product and then build a community around it. Find a community that already exists — a subreddit, a Slack, a Discord, a forum — where the same problem keeps coming up, and build a product for that exact group.
Who would miss it
The thousand or so most active members of a specific community whose recurring frustration you've been quietly cataloguing for months.
How to validate
You shouldn't have to validate it if you're already in the community. The validation happened in every "anyone know how to..." thread you read. The risk is moving too slowly because you assume someone else will build it. They probably won't.
The Data Nobody Else Has
The most defensible SaaS businesses sit on top of data that's hard to get. Sometimes that's data the founder collected themselves over years of operating. Sometimes it's data you can scrape, license, or aggregate from public sources that nobody's bothered to assemble. Sometimes it's data your users generate by using your product, that becomes valuable in aggregate.
Who would miss it
Anyone who's been making a decision in the dark and now can't.
How to validate
Show a sample of the data to ten potential customers. If three of them say "wait, where did you get this?" you have a product. If they say "interesting" politely, you don't.
The pattern: identify a question your target customer can't currently answer, find or build the dataset that answers it, and ship the answer as a product.
The Vertical CRM (or ERP, or PM Tool)
Horizontal CRMs and project management tools are powerful and generic. Generic tools force every customer to do the work of customizing them. For some industries, that customization work is the same problem solved a thousand times. The pattern: take a horizontal tool and rebuild it specifically for one industry, with that industry's vocabulary, workflows, and integrations baked in.
Who would miss it
A team in a specific industry that currently uses Salesforce / Asana / Monday and spends hours per week translating their actual work into the tool's generic objects.
How to validate
Talk to five teams in the industry. If they all describe the same custom fields, the same bolt-on integrations, the same workarounds for a missing feature, the vertical product is the consolidation of all of that.
The "Do This Hard Thing for Me" Service-as-Software
The newest pattern, enabled by LLMs and automation infrastructure: take a discrete task that knowledge workers do reluctantly — write the meeting summary, draft the contract redline, reconcile the receipts, generate the report — and ship a product that does the task end-to-end with the user reviewing the result.
Who would miss it
Someone who's stopped doing the task themselves because your product does it well enough, and would now have to learn to do it again.
How to validate
Get five people to use the product for a week. If three of them stop doing the task the old way without you having to remind them, the product has earned its place in their workflow.
This is narrower than "AI for productivity": one specific output, done well, that the user used to pay a person or spend an hour producing.
How to Tell If Your Idea Passes the Test
Pick the archetype that fits your situation and run your specific version through this short check before you write any code.
Three signals of extraction (red flags)
- You can't name a specific person who would miss the product. The "target user" is a category like "small businesses" or "developers."
- The differentiator is price or speed against an existing tool, not a different shape of solution.
- When you describe the idea, people nod politely but don't immediately ask when they can use it.
Three signals of contribution (green flags)
- You can name three real people who'd be the first users, and you can describe the painful workaround they're currently using.
- When you describe the idea to someone in the target audience, they interrupt you to ask a specific question about how it would handle their version of the problem.
- The first version of the product is small enough to build in a few weeks but specific enough that it solves a complete unit of work rather than a fragment.
If your idea has the green flags, the next step is the Mom Test — five conversations with people in the target audience about what they're already doing, not about whether your idea is good.
If it has the red flags, the next step is to keep looking. Starting on the wrong idea has a real cost, measured in months.
From Pattern to Decision
The twelve archetypes above are starting points. They tell you where good SaaS ideas have historically lived. They don't tell you whether your version of the pattern has a real market, real demand signals, and real willingness to pay. Confirming that means you validate the business idea itself — the pattern only tells you where to look.
That's what discovery is for. A structured discovery process — understanding the job your user is hiring the product for, looking at demand signals from existing workarounds, and pressure-testing whether the gap between useful and pay-for is wide enough — is the difference between a pattern that fits and a product that works.
Most founders skip that step because the idea sounds good and they're impatient. The cost of skipping is six months of building before you find out the pattern was right but the specific instantiation was wrong.
If you have a candidate idea from the list above and want to know whether someone would actually miss your version of it, Scoutr runs that analysis in minutes — surfacing the workarounds, the existing alternatives, the demand signals, and a clear verdict on whether the idea is worth the months it would take to build. The output gives you a sharper map before you start walking.
If the twelve archetypes feel too big to start alone, the narrower end of the same market is covered in 25 micro SaaS ideas with real search demand, where every idea comes with the monthly searches, keyword difficulty and cost per click behind it.