Data as of Sep 18, 2026 · Based on 52 AI responses from ChatGPT Search and Google AI Mode · See how Parse measures this
Your brand can be here too.
The companies you’re describing are usually called **AI-native vertical software**, **agentic applications**, or **SaaS challengers**: startups that do not add a chatbot/copilot to an old workflow, but instead **replace the workflow itself** (often replacing multiple seats of an incumbent SaaS product with an AI…
The companies you’re describing are usually called AI-native vertical software, agentic applications, or SaaS challengers: startups that do not add a chatbot/copilot to an old workflow, but instead replace the workflow itself (often replacing multiple seats of an incumbent SaaS product with an AI operator). The most exposed incumbents tend to be expensive, seat-based systems where humans spend time moving information around, filling forms, reviewing documents, or coordinating tasks.
A few notable examples:
| AI-native company | Workflow being rebuilt | Incumbents/categories under pressure |
|---|---|---|
| Sierra | Customer support operations run by AI agents rather than human ticket handlers | Zendesk, Salesforce Service Cloud, Intercom |
| Harvey | Legal research, drafting, contract work, and knowledge workflows | Thomson Reuters, LexisNexis, legal practice software |
| Legora | AI-assisted legal matter workflows | Legal research and document-management incumbents |
| EvenUp | Personal injury case preparation and demand-package creation | Legal operations software and outsourced legal work |
| Cognition | Software development tasks performed by autonomous agents | Atlassian Jira, developer tooling, some outsourcing workflows |
| Factory | Enterprise coding workflows with autonomous developer agents | Developer productivity tools and engineering services The Wall Street Journal |
| Abridge | Medical conversations → notes, documentation, coding support | EHR add-ons, documentation vendors |
| Hippocratic AI | Patient-facing healthcare tasks | Call centers and healthcare workflow vendors |
| Decagon | Automated support workflows | Contact-center SaaS |
| Norm AI | Compliance review and regulatory workflows | Governance/risk/compliance SaaS |
| Taktile | Risk and underwriting decisions | Legacy decision engines and workflow tools |
LeadPrysm SaaS Mag## Categories where this pattern is most active
Instead of selling 100 support seats, the new model is an agent that resolves tickets, updates systems, and escalates exceptions.
Examples:
The incumbent question changes from “how do we make agents more productive?” to “how many human-agent workflows still need to exist?”
Legal is attractive because much of the work is document-heavy and language-based.
Examples:
These companies are attacking workflows traditionally supported by expensive lawyers, paralegals, research platforms, and document tools.
This is one of the biggest targets because many processes are repetitive but expensive.
Targets:
Potential incumbents:
The thesis: replace recruiter workflows, not just add AI search.
Targets:
The new product is not “a better IDE”; it is an AI engineer that owns tickets end-to-end.
Examples:
The strongest candidates tend to have:
The big strategic question is whether AI companies become a new layer on top of SaaS or whether they become the new system of action, with old SaaS becoming a backend database. Analysts and operators disagree on how broadly this will happen; some argue incumbents will successfully embed agents, while others expect more workflow replacement.
If you’re looking from a startup/founder angle, the most interesting “white spaces” are probably the ugly $100M–$10B SaaS categories that have lots of human operators, compliance burden, and document workflows (insurance, healthcare admin, construction, logistics, procurement, tax, and regulated finance).
The enterprise software landscape is undergoing a massive structural shift . Traditional Software-as-a-Service (SaaS)—built on the premise of giving humans a digital dashboard/tool to do work and charging them per seat—is being challenged by **AI-native "systems of action" and agentic workflows** . Instead of human…
The enterprise software landscape is undergoing a massive structural shift . Traditional Software-as-a-Service (SaaS)—built on the premise of giving humans a digital dashboard/tool to do work and charging them per seat—is being challenged by AI-native "systems of action" and agentic workflows . Instead of human users clicking through menus, logging entries, and generating reports inside an expensive legacy tool, AI-native platforms treat the LLM/agent as the primary user or worker, automating the end-to-end outcome rather than just assisting with a task.
Startups and scale-ups attacking expensive incumbents are focusing on several key operational domains:
Are you looking at this shift from an investment/market perspective , or are you trying to find specific AI-native alternatives to replace a bloated tool in your own tech stack? Let me know the category and I can narrow down the exact players.
Yes. The interesting cohort is **not simply “AI SaaS startups.”** It’s companies using AI to **delete an incumbent’s workflow**, often replacing a seat-based software product *and* some of the labor around it. A useful framing is Bessemer’s “**AI systems of action**”: AI is weakening the traditional system-of-record…
Yes. The interesting cohort is not simply “AI SaaS startups.” It’s companies using AI to delete an incumbent’s workflow, often replacing a seat-based software product and some of the labor around it.
A useful framing is Bessemer’s “AI systems of action”: AI is weakening the traditional system-of-record moat around products like SAP, Salesforce, NetSuite and Workday because an agent can increasingly execute the workflow without a human operating the old UI.
Here are the companies I’d put on the shortlist:
| Company | Attacking | What gets rebuilt |
|---|---|---|
| Sierra | Zendesk, Salesforce Service Cloud, contact-center/BPO | Customer support |
| Decagon | Zendesk, Intercom, legacy contact centers | Support resolution |
| Harvey | Legal research, contract software, legal-services workflows | Legal work |
| Legora | Traditional legal research/document software | Legal knowledge work |
| Rogo | Bloomberg/FactSet-style research + banker workflows | Investment-banking research/modeling |
| Clay | ZoomInfo, Apollo and traditional sales-intelligence stacks | Prospecting + enrichment + outbound |
| Cursor | IDEs, developer tooling, parts of software-development SaaS | Software development |
| Glean | Enterprise search, knowledge-management software | Finding and acting on company knowledge |
| Hebbia | Research/document-analysis workflows | Financial/legal/enterprise research |
| LayerX | Concur, expense/AP/procurement software | Finance/back-office operations |
| Cognition | Parts of traditional engineering/project-management tooling | Engineering execution |
| Gamma | PowerPoint/Slides and presentation workflows | Creating business documents |
1. Sierra → customer support
This is probably the cleanest example of the thesis. Instead of selling another helpdesk UI, Sierra sells an agent that resolves the customer's issue. That's a fundamental change from “software that helps a support rep work” to “software that does the support work.”
Sierra reportedly reached $100M ARR in 2025 and was being used by companies including WeightWatchers, SiriusXM, Sonos and Redfin.
2. Harvey → legal
Harvey is attacking a particularly juicy combination: extremely expensive software + extremely expensive human labor. Rather than making lawyers marginally faster inside traditional legal software, it is automating research, drafting, analysis and other legal workflows.
That's why I consider Harvey more important than “AI legal research startup.” The ambition is closer to rebuilding the operating system for legal work.
3. Rogo → investment banking
Rogo is another strong example because banking has historically had enormous amounts of analyst labor wrapped around information systems. Its product handles things like presentations and financial models, and it is expanding from investment banking toward wealth management.
The interesting question isn't “Can Rogo beat Bloomberg?” It's how much of the workflow that caused a bank to buy Bloomberg, Excel, presentation software, research databases, etc. can disappear when the agent does the work?
4. Decagon → support
Decagon is slightly different from Sierra but follows the same thesis. The key metric isn't seats replaced; it's tickets/interactions resolved. One report says more than half of Decagon's customers replacing existing IVR, ticketing or CRM-based support systems moved to it.
That's the tell: the customer isn't merely adding AI to the stack. They're removing the old stack.
5. LayerX → back office
LayerX is particularly interesting because it's going after ugly, entrenched workflows—expenses, invoices, procurement, tax and HR. Its Bakuraku product competes with products including SAP Concur and other expense-management systems while using AI to automate the underlying processing.
This is exactly the kind of market where an AI-native company can ask:
Why does a human need to fill out this form at all? rather than:
How can we make the form slightly nicer?
The highest-potential targets have roughly this structure:
Expensive SaaS + lots of human labor + repetitive documents/data + terrible UX + per-seat pricing.
That's why legal, customer support, finance, recruiting, sales ops, compliance, insurance and healthcare administration are so interesting.
The startup doesn't necessarily need to replace the incumbent's database. It can initially replace the human interaction layer sitting on top of it.
That's the crucial distinction:
Old SaaS
Human → UI → workflow → database → outcome
AI-native
Human → intent → agent → outcome
The UI and much of the workflow become optional.
A 2026 BCG analysis similarly finds AI-native startups capturing disproportionate share in vertical and departmental software: startups account for 88% of the cited vertical-AI category and 60% of departmental AI spend.
The companies I would watch most closely are moving from:
“AI software replaces incumbent software”
to:
“AI service replaces the people who operate the software.”
That's the service-as-software model. Sierra is the canonical example: instead of selling customer-service software for $X per agent, the company can effectively sell resolved customer interactions. The software is becoming a delivery mechanism for labor.
That creates a much larger TAM because the startup isn't competing for the customer's $50k SaaS budget. It's competing for the $5M labor budget attached to the workflow.
So if you're looking for companies that could produce the next generation of $10B–$100B application businesses, I'd focus less on “AI features” and more on companies where the pitch sounds like:
“You don't need this software anymore. Tell us what you want done, and we'll do it.” That's the real attack on incumbent SaaS.
The software landscape is experiencing a massive shift from traditional "system of record" SaaS (where humans do the heavy lifting inside bloated, expensive dashboards) to **AI-native agentic workflows** (where autonomous digital workers execute the end-to-end task).[](https://www.11x.ai/worker/alice)…
The software landscape is experiencing a massive shift from traditional "system of record" SaaS (where humans do the heavy lifting inside bloated, expensive dashboards) to AI-native agentic workflows (where autonomous digital workers execute the end-to-end task).
Rather than just adding a generic chatbot "copilot" to an existing product, these startups are completely bypassing the legacy user-interface and pricing model. Instead of charging per seat, they charge by outcome or task completion.
Prominent companies attacking expensive incumbent SaaS by rebuilding workflows from scratch include:
Would you like to explore how these AI startups are shifting pricing models away from traditional per-seat SaaS, or look into how large legacy incumbents (like Salesforce and Workday) are trying to defend their moats?
The shift from traditional SaaS (where software is a tool humans log into to fill out forms, click buttons, and build dashboards) to **AI-native workflow systems** (where autonomous agents handle the execution and humans simply supervise) is redefining enterprise…
The shift from traditional SaaS (where software is a tool humans log into to fill out forms, click buttons, and build dashboards) to AI-native workflow systems (where autonomous agents handle the execution and humans simply supervise) is redefining enterprise tech.
Instead of legacy incumbents trying to "bolt on" a chatbot feature, a new wave of AI-native disruptors is rewriting the underlying mechanics of customer support, legal ops, sales development, coding, and finance.
Here is how startups and emerging platforms are attacking expensive incumbent categories by rebuilding workflows from scratch:
Would you like to explore how the pricing models (per-seat vs. outcome-based) are shifting between these AI disruptors and legacy vendors, or do you want to look at a specific industry workflow (like HR or marketing)?
Yes. The interesting cohort isn’t “SaaS companies adding an AI assistant.” It’s **AI-native companies trying to make the old SaaS category itself unnecessary**—often by replacing a sequence of screens, humans, and workflows with an agent that simply gets the job done. Redpoint calls the broader shift **“SaaS →…
Yes. The interesting cohort isn’t “SaaS companies adding an AI assistant.” It’s AI-native companies trying to make the old SaaS category itself unnecessary—often by replacing a sequence of screens, humans, and workflows with an agent that simply gets the job done.
Redpoint calls the broader shift “SaaS → Service-as-Software”: instead of selling software that helps a person perform work, sell software that performs the work and charge for usage/outcomes. www.slideshare.net Gartner estimates that as much as $234B of enterprise-application spending could be exposed to this “agentic arbitrage” by 2030.
Here are the companies I'd put on the watchlist:
| Incumbent / category | AI-native attacker | What is being rebuilt |
|---|---|---|
| Salesforce / CRM | Attio, DayAI | CRM that automatically captures context rather than making reps maintain records |
| Zendesk / customer support | Sierra, Decagon | The support operation itself, with agents resolving issues end-to-end |
| NetSuite / Sage / QuickBooks | Rillet, DualEntry, Campfire | AI-native accounting/ERP rather than forms + workflows + accountants |
| Legal software / legal services | Harvey, Legora, EvenUp | Legal work itself—research, drafting, review, claims/demand workflows |
| Sales engagement / lead databases | Clay, Unify, Qualified | Research, enrichment, personalization and outbound execution |
| GitHub / traditional developer tooling | Cursor, Lovable | Software creation rather than merely tooling around the coding process |
| Healthcare administration | Abridge, Assort, Valerie Health, Tandem | Documentation, referrals, front-office work, prior auths |
| Investor relations / finance workflows | Q4 and newer AI-native finance products | Parts of the analyst/IR workflow rather than another database |
| ERP operations / supply chain | Doss | Inventory, procurement, orders and operational workflows |
1. Sierra / Decagon — customer support
This may be the cleanest example of the thesis. Instead of selling a better Zendesk interface, they sell an AI agent that resolves the customer's problem. Redpoint specifically identifies Sierra and Decagon as leaders in this new support model.
The strategic difference is huge:
Old SaaS: “Give every support agent a seat.” AI-native: “Pay us for the customer issues we resolve.” That attacks both the product architecture and the pricing model.
2. Rillet / DualEntry / Campfire — ERP
This is probably the most interesting “incumbent SaaS replacement” battlefield because the incumbent products are extraordinarily expensive and painful to implement.
Rillet, DualEntry and Campfire are building AI-native accounting/ERP systems targeting NetSuite, Sage Intacct and QuickBooks. DualEntry's particularly interesting wedge is AI-assisted migration from legacy financial systems, attacking one of the biggest reasons customers don't switch.
Rillet is especially compelling because it isn't merely “AI bookkeeping”; it's trying to become the financial system of record.
3. Harvey — legal
Harvey is further along than most of these companies in turning AI from “software for lawyers” into software doing lawyer work. Redpoint highlights Harvey alongside Legora as examples of AI-native legal systems moving beyond traditional legal software toward actual work execution.
This is a particularly attractive market because the incumbent isn't just software—it's also hundreds of billions of dollars of human labor.
4. Clay — GTM
Clay is an interesting version where the target isn't one incumbent. It's attacking the stack of Salesforce + ZoomInfo + Clearbit + Apollo + Outreach + spreadsheets + human SDR research.
Its insight is essentially: why maintain six databases and make a salesperson orchestrate them when an agent can research the account, enrich it, generate personalization and execute the workflow?
Redpoint specifically calls out Clay and Unify GTM as examples of this new sales/marketing architecture.
5. Cursor — developer software
Cursor is slightly different because it attacks GitHub/Copilot-style tooling rather than classic business SaaS. But strategically it's perhaps the purest example of the phenomenon.
The old workflow was:
IDE → write code → search docs → Stack Overflow → run tests → debug → repeat
The new abstraction is increasingly:
“Build this.” → agent operates across the repository.
That's what makes AI-native applications dangerous to incumbents: they don't necessarily need to reproduce the incumbent's feature set. They can delete the workflow that made those features necessary.
I think there are three tiers of this phenomenon:
The third is where things get really disruptive.
For example:
Redpoint's research explicitly describes this movement from SaaS toward “Service-as-Software”, with companies increasingly charging by usage or outcomes rather than seats.
And that's why I wouldn't define the opportunity as simply “AI-native SaaS.” The more interesting thesis is:
Take an expensive software category where the customer is really paying for a human workflow, then use AI to collapse the software + labor stack into an outcome. The strongest current examples, in my view, are Sierra/Decagon, Harvey, Rillet/DualEntry, Clay, Cursor, and Doss.
One caveat: this is still very much an emerging market. Incumbents have enormous integration/data advantages, and Gartner currently cautions that replacing core ERP wholesale with AI remains immature. Gartner So the most vulnerable categories are generally workflow-heavy applications, not deeply entrenched systems of record.
If you're thinking about this from a startup/investment angle, I can also map out 50+ incumbent SaaS categories and the specific AI-native startups attacking each one, ranked by how vulnerable the incumbent is.
This is probably the most interesting “incumbent SaaS replacement” battlefield because the incumbent products are extraordinarily expensive and painful to implement.
Rillet, DualEntry and Campfire are building AI-native accounting/ERP systems targeting NetSuite, Sage Intacct and QuickBooks. DualEntry's particularly interesting wedge is AI-assisted migration from legacy financial systems, attacking one of the biggest reasons customers don't switch.
Rillet is especially compelling because it isn't merely “AI bookkeeping”; it's trying to become the financial system of record.
3. Harvey — legal
Harvey is further along than most of these companies in turning AI from “software for lawyers” into software doing lawyer work. Redpoint highlights Harvey alongside Legora as examples of AI-native legal systems moving beyond traditional legal software toward actual work execution.
This is a particularly attractive market because the incumbent isn't just software—it's also hundreds of billions of dollars of human labor.
4. Clay — GTM
Clay is an interesting version where the target isn't one incumbent. It's attacking the stack of Salesforce + ZoomInfo + Clearbit + Apollo + Outreach + spreadsheets + human SDR research.
Its insight is essentially: why maintain six databases and make a salesperson orchestrate them when an agent can research the account, enrich it, generate personalization and execute the workflow?
Redpoint specifically calls out Clay and Unify GTM as examples of this new sales/marketing architecture.
5. Cursor — developer software
Cursor is slightly different because it attacks GitHub/Copilot-style tooling rather than classic business SaaS. But strategically it's perhaps the purest example of the phenomenon.
The old workflow was:
IDE → write code → search docs → Stack Overflow → run tests → debug → repeat
The new abstraction is increasingly:
“Build this.” → agent operates across the repository.
That's what makes AI-native applications dangerous to incumbents: they don't necessarily need to reproduce the incumbent's feature set. They can delete the workflow that made those features necessary.
I think there are three tiers of this phenomenon:
The third is where things get really disruptive.
For example:
Redpoint's research explicitly describes this movement from SaaS toward “Service-as-Software”, with companies increasingly charging by usage or outcomes rather than seats.
And that's why I wouldn't define the opportunity as simply “AI-native SaaS.” The more interesting thesis is:
The thesis that **AI-native startups** are attacking expensive, seat-based legacy SaaS (Salesforce, Zendesk, ServiceNow) by completely rebuilding workflows around autonomous agents rather than human-driven data entry is reshaping the software landscape. Instead of charging per user seat, these companies often price…
The thesis that AI-native startups are attacking expensive, seat-based legacy SaaS (Salesforce, Zendesk, ServiceNow) by completely rebuilding workflows around autonomous agents rather than human-driven data entry is reshaping the software landscape. Instead of charging per user seat, these companies often price based on outcomes, resolution rates, or consumed compute.
Prominent AI-first challengers across key enterprise categories are redesigning traditional SaaS workflows from the ground up:
Customer Support & Success (Replacing Zendesk, Intercom, ServiceNow)
Legacy helpdesks were built as ticketing systems for humans to read, triage, and manually reply to queries. AI-native alternatives treat the support queue as an autonomous resolution problem.
Sales & Revenue Operations (Replacing Salesforce, Outreach, HubSpot)
Traditional CRM workflows require humans to log calls, update pipelines, and manually trigger sequences. AI-native tools treat the CRM as a continuous background data layer driven by ambient listening and autonomous outreach.
Legal, Compliance, and Finance Back-Office (Replacing Legacy ERP/Legal Tools)
Document-heavy, highly manual processes that previously required armies of analysts or expensive point-solution SaaS are being collapsed into single-prompt or autonomous continuous workflows.
Would you like to explore how the pricing models (seat-based vs. outcome-based) are shifting for these AI-native challengers, or look into how traditional incumbents like Salesforce and ServiceNow are fighting back?
Yes. The interesting cohort is **not “SaaS companies with AI features.”** It’s companies asking: *if an AI agent is the primary user, why reproduce the 1990s/2000s workflow at all?* That creates a fairly specific attack vector against expensive, sticky incumbents: **take the budget of an incumbent system of record,…
Yes. The interesting cohort is not “SaaS companies with AI features.” It’s companies asking: if an AI agent is the primary user, why reproduce the 1990s/2000s workflow at all?
That creates a fairly specific attack vector against expensive, sticky incumbents: take the budget of an incumbent system of record, eliminate much of the human-operated workflow, and charge for outcomes/usage instead of seats. Recent industry analysis makes the same point: document-heavy + workflow-heavy + seat-priced software is especially exposed.
Here are the companies I'd put on the watchlist.
| Challenger | Attacking | What gets rebuilt |
|---|---|---|
| Serval | ServiceNow | ITSM / enterprise automation |
| Rillet | NetSuite / Sage Intacct | ERP + accounting |
| DualEntry | NetSuite / Sage Intacct | Accounting / ERP |
| Campfire | NetSuite / QuickBooks | Finance operating system |
| qomplement | SAP / NetSuite | Supply-chain ERP |
| Sierra | Salesforce / Zendesk / contact-center stacks | Customer-service operations |
| Harvey | Thomson Reuters / LexisNexis / legal workflow | Legal work |
| Manifest | Traditional law-firm software + billable-hour model | Law-firm operating system |
| Decagon | Zendesk / Salesforce Service Cloud | Customer support |
| Basis | Traditional accounting / AP software | Accounting workflows |
| Numeric | FloQast / BlackLine / ERP close tooling | Financial close |
| Day AI / Reevo / Attio | Salesforce and legacy CRM | CRM / revenue workflow |
But there are some important distinctions.
Probably the cleanest example of the thesis.
Serval is explicitly going after ServiceNow rather than merely becoming another AI add-on.
Its Catalyst agent analyzes ticket history, determines what can be automated, and generates the underlying code/workflow/permissions for approval. The architecture is built around code-generation agents rather than a traditional workflow-builder bolted onto an old ITSM system. Serval has raised $127M and reached a reported $1B valuation.
The really interesting economic attack is:
ServiceNow: humans operate the workflow inside the system. Serval: the system operates the workflow. That's a much bigger disruption than “AI-powered ServiceNow.”
This may be the most developed “AI-native ERP” battleground.
Rillet is rebuilding the accounting system around continuous processing rather than the traditional month-end-close workflow. Its pitch is essentially: don't make accountants operate an ERP; have the ERP continuously perform the accounting.
DualEntry attacks another enormous incumbent pain point: migration itself. Its “NextDay Migration” uses AI to map and migrate historical financials from legacy systems, directly attacking one of the biggest reasons companies remain trapped in NetSuite.
Campfire is going even broader: finance/ERP as a new operating system rather than a collection of modules.
The category is unusually interesting because the incumbents have enormous implementation costs and administrative overhead. The challengers can potentially turn:
ERP → database humans maintain
into:
ERP → autonomous financial system.
qomplement is an especially aggressive example.
Its thesis is to start with a painful operational workflow—procurement, inventory, freight, ERP updates—and progressively replace the underlying ERP. YC describes it explicitly as an agentic ERP designed for AI agents rather than human users, with a goal of replacing SAP and NetSuite.
This is the “don't replace the whole ERP on day one” strategy:
That's potentially much more viable than asking a CFO to rip out SAP on day one.
Sierra is another extremely important one.
Rather than selling a better agent-assist tool, Sierra sells customer-service agents that actually execute the business process: refunds, insurance claims, refinancing, order returns, etc.
As of May 2026, Sierra said it was serving more than 40% of the Fortune 50 and that its agents were powering billions of customer interactions. It had raised $950M at a valuation above $15B.
The conceptual shift is:
Zendesk: manage tickets.
Sierra: resolve the customer's problem.
That distinction matters enormously for pricing. If AI eliminates the human ticket handler, per-agent/per-seat pricing becomes economically nonsensical.
Legal is probably the most obvious professional-services category where the workflow itself can be reconstructed.
Harvey has gone well beyond “legal research chatbot.” It is becoming an operating layer for legal work—research, drafting, review, analysis, etc. Recent reporting puts Harvey at roughly $350M ARR and a $11B valuation.
But Manifest is arguably the purer “rebuild the business” thesis.
Its AI-native law-firm model combines intake, drafting, billing, review and quality control into an operating model based on fixed fees rather than traditional billable hours.
That's fascinating because it's attacking both software and the business model underneath the software.
Instead of:
law firm + associates + legal SaaS + hourly billing the new model can become:
AI workflow + supervising lawyers + fixed-price outcome.
Decagon is another serious one.
The important distinction versus classic “AI help desk” startups is that the product is increasingly about autonomous resolution, not helping a support agent type faster.
That's the pattern I'd watch: once an agent can resolve 70–90% of interactions, the incumbent ticketing UI becomes increasingly like a legacy database sitting underneath the actual customer experience.
Sierra is going after the enterprise version of this; Decagon is another major manifestation of the same thesis. Current market comparisons explicitly place Decagon among the AI-first challengers to Zendesk.
This is a fascinating category because CRM is arguably one of the most vulnerable pieces of SaaS architecture.
The traditional CRM workflow is:
email → human enters data → human updates fields → human moves opportunity → manager reads dashboard.
AI can instead observe communications and continuously construct the commercial graph itself.
Companies worth watching include:
Attio is already being positioned as an AI-native alternative to Salesforce, although I'd classify it as modern CRM with an AI-native architecture, rather than as radical a replacement thesis as Serval or Rillet.
If you're trying to identify the next generation of companies that can kill $100M–$1B SaaS categories, I wouldn't primarily look for “AI SaaS.”
I'd screen for this combination:
1. Expensive incumbent $20K–$1M+ annual contracts.
2. Human-mediated workflow Lots of people clicking, copying, reviewing, reconciling or routing things.
3. High implementation cost The incumbent's complexity is partly its moat.
4. AI can perform the actual work Not merely summarize it.
5. Agent can become system of action The new product actually does things in other systems.
6. Data exhaust becomes the moat Every completed workflow improves the agent.
7. Pricing can move from seats → outcomes Per resolution, transaction, claim, close, case, shipment, etc.
That produces a much more interesting map:
And the broader market is starting to validate this architecture shift: BCG's 2026 analysis found AI-native startups substantially further along the AI product-maturity curve than incumbent SaaS, with startups already capturing the majority of startup spend in vertical AI and a majority in departmental AI.
If the question is “who might actually take meaningful budget away from incumbent SaaS?”, rather than simply “who has a cool AI product?”, my list would be:
The really important signal isn't that these companies use LLMs. It's that they're asking a more dangerous question of the incumbents:
“Why does this workflow need to exist in its current form at all?” That's the distinction between an AI feature and an AI-native SaaS replacement.
5. Agent can become system of action The new product actually does things in other systems.
6. Data exhaust becomes the moat Every completed workflow improves the agent.
But Manifest is arguably the purer “rebuild the business” thesis.
Its AI-native law-firm model combines intake, drafting, billing, review and quality control into an operating model based on fixed fees rather than traditional billable hours.
That's fascinating because it's attacking both software and the business model underneath the software.
Instead of:
law firm + associates + legal SaaS + hourly billing the new model can become:
AI workflow + supervising lawyers + fixed-price outcome.
Decagon is another serious one.
The important distinction versus classic “AI help desk” startups is that the product is increasingly about autonomous resolution, not helping a support agent type faster.
That's the pattern I'd watch: once an agent can resolve 70–90% of interactions, the incumbent ticketing UI becomes increasingly like a legacy database sitting underneath the actual customer experience.
Sierra is going after the enterprise version of this; Decagon is another major manifestation of the same thesis. Current market comparisons explicitly place Decagon among the AI-first challengers to Zendesk.
This is a fascinating category because CRM is arguably one of the most vulnerable pieces of SaaS architecture.
The traditional CRM workflow is:
email → human enters data → human updates fields → human moves opportunity → manager reads dashboard.
AI can instead observe communications and continuously construct the commercial graph itself.
Companies worth watching include:
The software industry is undergoing a structural shift from **selling seats and dashboards** (traditional SaaS) to **selling completed work and autonomous execution** (AI agents/services-as-software). Instead of forcing humans to click through multi-step forms, tabs, and export CSVs, AI-native challengers are…
The software industry is undergoing a structural shift from selling seats and dashboards (traditional SaaS) to selling completed work and autonomous execution (AI agents/services-as-software). Instead of forcing humans to click through multi-step forms, tabs, and export CSVs, AI-native challengers are rethinking workflows from the ground up around intent and automated outcomes.
The companies and categories aggressively attacking expensive incumbents fall into a few clear trenches:
The Two Strategic Plays: "Replace" vs. "Overlay"
When looking at how these companies attack incumbents, notice two distinct tactical approaches:
If you want to zoom in, let me know:
Sierra
The companies I’d put in this category are **AI-native workflow rebuilders**: they are not selling “AI features” inside an existing SaaS product; they are trying to replace the *process* that the SaaS product encoded. The common pattern is: > Old SaaS: “A human uses software to complete a workflow.” > AI-native: “An…
The companies I’d put in this category are AI-native workflow rebuilders: they are not selling “AI features” inside an existing SaaS product; they are trying to replace the process that the SaaS product encoded. The common pattern is:
Old SaaS: “A human uses software to complete a workflow.” AI-native: “An agent completes the workflow and humans supervise exceptions.” This is especially threatening where incumbents are expensive, seat-based, and built around repetitive knowledge work.
Thesis: The winner may not be the company with the best legal search engine; it may be the company that owns “get this contract negotiated and signed.”
Thesis: A ticketing system is less valuable if an AI agent closes the ticket without a human touching it.
Thesis: CRM historically records what salespeople do. AI-native companies aim to do the selling.
Thesis: ATS systems manage candidates; AI recruiters may find, screen, and schedule them.
Thesis: The future accounting system may not be a ledger UI; it may be an agent that reconciles, explains, and closes books.
Thesis: Jira tracks engineering work; AI agents may perform much of the work.
If the question is “who has the strongest SaaS replacement thesis?” rather than “who has the best AI feature?”, I’d watch:
The biggest targets are categories where:
A useful mental model: Salesforce, Workday, SAP, ServiceNow, etc. became systems of record. The AI-native challengers are trying to become systems of execution.