What Software AI Can't Replace: 17 Categories Still Taking Payments

The question every founder is asking in 2026 is some version of: what can I sell that a $20 AI subscription does not already solve? Almost every answer you will find is about job roles, written from personal experience, with no evidence about where money is actually still changing hands.

So we measured it. Across 30,000+ companies listed on Stripe's public directory as of September 2026, we calculated an agentic penetration rate for each of 83 active categories: the share of companies in that category that are AI-native. The result splits the software market cleanly in two, and the interesting half is the one nobody writes about.

The short answer, and why it is not about roles

The best-ranked answer to this question today is a role-by-role breakdown: outbound SDRs are 90% replaceable, inbound BDRs 95%, customer support 50%, account executives only 30%. That framing is useful if you are deciding who to hire. It is close to useless if you are deciding what to build, because it tells you nothing about which markets still have buyers.

A category-level view answers the actual question. If you want to know whether a market is safe to enter, the question is not "could AI do this job?" It is "have AI-native companies actually shown up here, and are customers still paying?" Those are both measurable.

How we measured it

Stripe publishes a public directory of companies that process payments through it. That is a useful population precisely because inclusion requires collecting money, not raising money or launching on a directory. We hold 30,000+ of those company profiles, each scored for category, business model and whether the company is AI-native.

Agentic penetration rate is then a simple ratio: AI-native companies divided by all companies taking payments in that category. A high number means the category has already reorganised around AI. A low number with a high company count means a market with proven willingness to pay that AI-native competitors have not entered.

Where AI crowded in

Ten categories carry most of the AI-native entrants. If you are building here, you are not entering a quiet market. You are entering one that already restructured, where your competitors raised money specifically to do this with AI.

Notice that this list is mostly tools for people who build software. Developer tools, APIs, workflow automation, AI infrastructure. That is the classic failure mode of building for the audience you happen to be in, and it is worth reading alongside who micro SaaS actually sells to and our analysis of the state of micro SaaS competition.

Where it never arrived

These are categories where hundreds of companies collect money every month and AI-native competition is effectively absent. Read the first row carefully: 963 companies taking payments, one AI-native competitor.

This maps closely onto the pattern in industries still running on spreadsheets and boring industries begging for micro SaaS. The categories nobody wants to build for are the categories nobody is building for, which is the entire point. If you want the broader version of this analysis, see the most underserved software markets and low competition SaaS ideas.

Why the gap holds

The market-structure data tells you where the gap is. It does not tell you why it persists. For that we went to the operators arguing about it in public. In a September 2026 thread of 126 replies on the exact question, founders converged on five conditions with almost no prompting.

1. The output has to outlive one person's laptop

"Every example you listed is single-user. The $5 box hides the catch: you debug your own dashboard at midnight, a paying customer can't. The gap holds where the output must outlive one person's machine." — r/SaaS

2. More than one person has to touch it

"the moment it needs auth refreshes, error alerts, or someone else on the team touching it without reading your prompt history, that's where paying for something beats DIY again." — r/SaaS

This is the cleanest dividing line in the whole dataset. A chat subscription is excellent at producing a personal artifact and poor at owning a shared business process, which is exactly how one commenter framed it: "A $20 AI subscription can replace features or build a personal tool; it does not automatically own a shared business process."

3. It needs domain knowledge a general model lacks

"AI can put hips or gables on any wall plan but add in a complex roof and it falls flat." — r/SaaS

That quote comes from someone selling roofing takeoff software. It is also, not coincidentally, the category with 963 paying companies and one AI-native competitor. The two independent sources agree.

4. Liability sits somewhere

"highly regulated industry where vibe coding isn't a viable option. Screw something up and it's massive civil penalties." — r/SaaS

Legal tech at 0.2% AI-native and tax and compliance near the bottom of the penetration table are the market-structure version of this sentence.

5. Most buyers will simply never build it

"Pretty much anyone can build a table. How many people do you know who have built their own table?" — r/SaaS

The most repeated argument in the thread was not technical. It was that capability and willingness are different things: "the vast majority of people will not vibecode their own solutions", and "No business is going to spend their resources building and maintaining 30+ different products". For more on how buyers actually behave, see what micro SaaS actually charges.

What buyers are actually paying for

The five conditions describe when the gap holds. They do not quite explain what the customer thinks they are purchasing, and that turns out to be the crux. The most upvoted answer in the entire thread was not about technical capability at all.

"I'm thinking they are looking for certainty rather than building it themselves. The customers don't want to do the work of building it. Just like cooking, you could cook or just order Uber Eats." — r/SaaS

Certainty is the product. Not features, and increasingly not even convenience, because a model will produce something that works on the first try often enough to feel convenient. What it will not produce is the guarantee that the thing still works in four months, that somebody else can operate it, and that when it breaks there is a person whose job it is to fix it. That guarantee is what a subscription actually buys, and it is not something a chat session can issue.

This reframes the whole AI-replacement question usefully. The right test is not "could a model build a version of my product?" It almost certainly could. The test is "is my customer buying an artifact, or an ongoing guarantee?" Artifact businesses are in genuine trouble. Guarantee businesses are roughly where they were.

Look at which categories cluster on each side and the pattern is not subtle. The contested table is full of artifact-shaped products: a generated draft, an enriched lead list, a summarised ticket, a piece of automation. The untouched table is full of guarantee-shaped ones: the job gets dispatched, the donation gets receipted, the ticket gets scanned at the door, the booking does not double-book. In the second set, a wrong answer has a physical consequence somebody owns.

One operator drew the line explicitly at the infrastructure boundary: "simple wrapper SaaS is done, but infrastructure and heavy execution layers aren't going anywhere". That is the same distinction in different language. A wrapper hands you an artifact. Infrastructure carries a guarantee, and guarantees are expensive to fake.

The practical consequence for pricing is direct. Artifact products compete against a $20 subscription, which caps what you can charge almost regardless of quality. Guarantee products compete against the cost of the failure they prevent, which is usually far larger. That is why the verified revenue distribution matters: a median of $145/month across 3,700+ startups is not a ceiling imposed by AI, it is what happens when most products are priced against a substitute rather than against a consequence.

If you are choosing between two versions of the same idea, pick the one where somebody would notice and care if it silently stopped working for a week. That is a crude test and it correlates with almost everything above. The startup idea validation process gets at the same question from the demand side.

The role answer is half right

It is worth being fair to the role-based framing, because the data partly vindicates it. The claim that customer support is roughly half replaceable lines up with what we measure: customer support and helpdesk is the fourth most AI-penetrated category at 21.4%. The instinct was correct.

What the role framing cannot do is name the other side. It has nothing to say about nonprofit fundraising, salon booking, or roofing takeoff, because those are not job titles inside a B2B software company. They are markets. And markets are where the remaining money is.

How to use this when choosing what to build

Absence of AI-native competition is a signal, not a verdict. Several of these categories are quiet because they are genuinely hard to sell into, not because nobody noticed. The useful move is to cross-check a category on three axes before committing.

First, is the gap documented? Our corpus holds 40,000+ feature gaps extracted from software reviews, 21,000+ of them flagged high-demand. A category with paying customers, no AI-native competition, and a stack of documented complaints is a far stronger signal than any one of those alone. Start with small business software pain points and the complaint analysis platform.

Second, does anyone make money there? Of 3,700+ startups with verified revenue in our data, the median is $145/month and the upper quartile $894/month. That is the realistic band for small software, and it is worth checking against revenue intelligence before assuming a category supports the business you want.

Third, is the workflow shared or single-user? This is the condition operators keep returning to, and it is the one you control. The same category can contain a doomed single-user tool and a durable multi-user one. See single feature micro SaaS ideas for how narrow a product can be while still holding shared state, and legacy system API wrapper business ideas for the integration-shaped version.

For category-specific starting points, the niche SaaS ideas and B2B SaaS ideas collections both sort by market rather than by technology, which is the right axis given everything above. If you want the AI-native side specifically, see vertical AI SaaS ideas and SaaS ideas for AI agents, but go in knowing you are entering the contested table.

A worked example: home services and trades

Take the widest gap in the dataset and run it through the three checks, because the method matters more than the table. Home services and trades shows 963 companies taking payments and one AI-native competitor. That is the strongest raw signal available. It is also not yet a reason to build anything.

Check one, is the gap documented? This is where the category stops being an abstraction. Field service software carries some of the most repetitive complaint patterns in the corpus: scheduling that cannot handle a two-technician job, quoting that breaks when a job changes on site, and photo documentation that lives in a technician's camera roll instead of the job record. These are not model problems. No amount of language model quality fixes a workflow that was never built.

Check two, does anyone make money there? The category has 963 companies collecting recurring payments. That is the answer, and it is a better answer than any market-size estimate, because payment processing is revealed preference rather than a projection. What it does not tell you is the price band, which is why the verified revenue data matters as a separate check.

Check three, is the workflow shared? Home services is almost definitionally multi-user: a dispatcher, technicians in vans, an office doing invoicing, and a customer who needs to know when someone is arriving. That is four roles touching one job record. It is the precise shape that operators said a chat subscription cannot hold, and it is why the roofing quote earlier in this piece lands where it does.

Run the same three checks against a category like AI tools and apps, which holds 955 companies and 153 AI-native competitors, and the picture inverts. The gap is contested, the workflow is frequently single-user, and the differentiation has to come from somewhere other than "we used a model". Both categories have roughly a thousand paying companies. They are not remotely the same opportunity.

The same exercise works for any row in either table. Nonprofit and fundraising, at 647 paying companies and zero AI-native competitors, has an obvious multi-user workflow and a well-documented tolerance for unglamorous software. Newsletters and publishing, also at zero, is far more single-user and therefore far more exposed despite the identical headline number. The ratio starts the analysis. It does not finish it. Our writeup on how to find problems worth solving covers the sequencing in more depth.

There is a failure mode worth naming here, because it is the most common way this analysis gets misused. Seeing a category with hundreds of paying companies and no AI-native competition, the instinct is to conclude the market is asleep. Usually it is not. Usually the category is quiet for a reason that has nothing to do with technology: fragmented buyers who are hard to reach, a sales cycle that runs through trade associations, seasonal revenue, or an incumbent that has been good enough for fifteen years and owns the integrations. None of those are visible in a penetration ratio.

What the ratio does reliably tell you is what kind of risk you are taking. In the contested table, your risk is competitive: somebody funded is building the same thing and their pitch already sounds more modern than yours. In the untouched table, your risk is distribution: the product may be straightforward and reaching the buyer may be the entire job. Those need completely different plans, different amounts of capital, and arguably different founders. Choosing without knowing which one you are in is the actual mistake.

What actually changed in 2026

It is worth separating what genuinely shifted this year from what simply got louder, because the two are easy to confuse and only one of them should change your plans.

The AI-native land grab concentrated rather than spread. Of 83 active categories, ten carry the overwhelming share of AI-native companies. If the story were "AI eats software", penetration would be rising broadly across categories. Instead it is clustered in markets that are adjacent to the technology itself: infrastructure, automation, developer tooling, and the customer-facing functions that are mostly text. That is a narrower event than the discourse suggests.

Agent-payable commerce is a frontier, not a trend. Of 30,000+ companies in the directory, ten support machine-payable transactions. Ten. That is a real and genuinely interesting frontier, and it is not a market you can sell into this year. Treat any advice built on agentic commerce volume with suspicion, including ours, because the population is currently too small to generalise from.

Attention moved faster than structure. Search interest in AI agents peaked mid-2026 and has since fallen to roughly a third of that peak. Meanwhile the underlying category structure barely moved. This is the normal gap between narrative and market: the conversation reorganises in months, the payment flows take years. Building against the conversation is how founders end up in the contested table by accident. Our micro SaaS trends analysis tracks the same divergence, and AI SaaS ideas covers the contested side directly.

The bar for single-user tools genuinely rose. This is the part of the AI-replacement thesis that survived contact with the data. If your product is one person solving one workflow for themselves, a chat subscription plus an afternoon is now a credible substitute, and the operators making that argument are right. The mistake is generalising from that to all software, when the categories where money actually changes hands are dominated by shared, multi-party, accountability-bearing workflows that look nothing like the personal dashboard example.

What did not change: buyers still prefer paying over building. That was true before language models and it is the oldest force in this analysis. See the micro SaaS ideas guide for how that preference translates into pricing.

Where this could be wrong

This is a snapshot of one payment processor's public directory, and it carries real limits worth stating plainly.

• Stripe is not the market. Companies on other processors, or selling through marketplaces and resellers, do not appear. Categories with heavy offline or enterprise sales are undercounted.
• AI-native is a positioning label, not usage. It is assigned from public descriptions. A roofing company quietly running a model reads as non-AI here. The ratio measures who is competing as an AI company, which is the thing that reshapes a market, but it is not the same as AI adoption.
• A snapshot, not a trend. These numbers say who is in a category in September 2026. A category at 0.5% today can be contested next year, and the ones adjacent to the contested list are the likeliest to move.
• Low competition is not automatically opportunity. Some of these categories are quiet because distribution is brutal. Market saturation analysis is the counterweight here, covered in SaaS market saturation and oversaturated side hustles.

One more honest limit: this measures entry, not outcome. A category with 43% AI-native companies is not a category where AI-native companies are winning. It is one where they showed up. Some of those markets will look very different in two years once the ones that cannot retain customers wash out, and a few of the quiet categories will have been entered and taken by then. The ratio is a map of where attention and capital went, which is useful precisely because it is leading rather than lagging, but it should not be read as a scoreboard.

Those caveats do not move the headline. A market with 963 paying companies and one AI-native competitor is a structurally different proposition from one where four in ten companies are AI-native, and no reasonable adjustment to the method collapses that difference. For methodology on how the underlying corpus is built, see how to find SaaS ideas and micro SaaS examples.

Frequently asked questions

BigIdeasDB Research. (2026). What Software AI Can't Replace: 17 Categories Still Taking Payments. BigIdeasDB. Retrieved from https://bigideasdb.com/what-software-ai-cant-replace-2026