As noted by institutional investors like Bessemer Venture Partners and tech accelerators like Y Combinator , the prevailing thesis is that the last generation of software replaced on-premise tools with the cloud, while this generation is replacing traditional SaaS with end-to-end AI execution.[](https://brocoders.com/blog/saas-ideas-startups/)
The emerging companies and categories rebuilding these workflows from scratch include:
Back-Office, Invoicing & Finance: Traditional ERP and accounting add-ons (like legacy parts of NetSuite or Coupa) are being disrupted by autonomous agents (such as platforms like Lighthouz AI and Billow AI Labs ) that handle touchless invoicing, email parsing, reconciliation, and vendor communication end-to-end without requiring a human to manually key data between systems.[](https://www.ycombinator.com/companies/industry/workflow-automation)
Would you like to explore a specific vertical (like CRM/Sales, Customer Support , or Finance/ERP ) to see detailed examples of the traditional incumbents and the exact AI-native architectures replacing them?
Yes. The interesting cohort is not “SaaS companies with an AI copilot.” It’s companies asking: if an AI agent is the primary user, why preserve the old screens, objects, workflows, and org structure at all?
A useful way to map the market in 2026:
Incumbent category
AI-native attackers
What they're rebuilding
NetSuite / Sage / QuickBooks
Rillet, DualEntry, Campfire, Light, Doss
Finance/ERP from the ground up around automated accounting
Salesforce / HubSpot
Day AI, Reevo, Clarify, Attio
CRM where the system creates/updates the record from communications rather than reps entering CRM data
ServiceNow / ticketing
Sierra, Decagon, Intercom Fin, EliseAI
Customer-service operation as an AI agent rather than queues + human agents
Traditional legal software + legal labor
Harvey, EvenUp, Clio's AI ecosystem, Legora
Legal work itself, not merely legal document management
Traditional accounting firms / ERP modules
Basis, Numeric, Vic.ai, Tabs, Finaloop
Agents executing close, AP, reconciliation, revenue, etc.
Enterprise search / intranet / knowledge SaaS
Glean
The interface to enterprise knowledge and workflows rather than another destination app
Recruiting / ATS
Mercor, Paraform, Apriora
Candidate sourcing, evaluation and matching as an agentic workflow
Travel / corporate travel SaaS
Navan, Spotnana + AI-native entrants
Travel planning/booking as an autonomous workflow rather than employee → portal → policy → agent
Procurement / spend management
Zip, Ramp, Doss and newer agentic procurement startups
Procurement execution rather than forms and approval chains
The ERP/finance group is probably the clearest example of exactly what you're describing. Rillet, DualEntry, Campfire and Light are explicitly positioning themselves as AI-native financial systems against NetSuite/Sage/legacy ERP. An independent 2026 survey of the category describes these companies as rebuilding the architecture around AI rather than simply adding an AI assistant.
The ones I'd pay particularly close attention to
1. Rillet / DualEntry / Campfire — “NetSuite, but the computer does the accounting”
This is perhaps the cleanest expression of the thesis. Instead of giving an accountant a better UI for the same ERP primitives, they're attempting to make the underlying ledger, reconciliation, close, reporting and revenue workflows AI-native.
Rillet, DualEntry and Campfire have each raised substantial capital, and their stated competitive target includes NetSuite/Sage/QuickBooks.
2. Basis — “replace the accounting department's workflow, not QuickBooks”
Basis is a slightly different attack: rather than necessarily owning the entire financial system, it uses AI agents to perform accounting work across existing systems. That's potentially a more radical wedge because the thing being replaced is labor + workflow, not just software.
3. Glean — “what if the enterprise OS were the agent?”
Glean is interesting because it attacks the horizontal layer. Rather than asking employees to know whether information lives in Salesforce, Slack, Drive, Jira, etc., it builds a context layer across those systems and increasingly lets AI take action across them. TechCrunch describes its evolution from enterprise search toward the connective layer between models and enterprise systems.
Glean reported $300M ARR in May 2026, illustrating that this isn't merely an experimental startup category anymore.
4. Day AI / Reevo — “CRM without CRM data entry”
This is one of the more conceptually interesting attacks on Salesforce.
The old model:
salesperson → Salesforce → manually create/update objects → run workflow
The AI-native model:
salesperson communicates normally → AI observes the communication → AI constructs the customer record → AI determines next actions
That distinction matters enormously. The product isn't really a prettier CRM; it's attempting to remove the human CRM operator entirely. Current AI-native CRM research identifies Day AI as particularly focused on generating the record from communications, while Reevo is pursuing a broader consolidation of the GTM stack.
5. Sierra / Decagon — “customer support as a workforce”
Here the replacement target isn't really Zendesk. It's the human support organization plus its software stack.
The really interesting legal AI companies aren't just building better document search. They're trying to execute substantive legal workflows—research, drafting, review, analysis, diligence, etc.
That's another instance of the same pattern:
application SaaS → AI worker → outcome
rather than:
application SaaS → human operator → outcome.
The bigger pattern
I think there are three increasingly aggressive levels of AI-native SaaS disruption:
Level 1 — AI-enhanced SaaS
Salesforce + AI
Workday + AI
ServiceNow + AI
The incumbent retains the database, objects, permissions and workflow model. AI is a new interface.
Level 2 — AI-native application
Rillet, DualEntry, Day AI, etc.
The underlying data model and workflows are redesigned assuming an AI can do most of the work.
Level 3 — AI replaces the application and the operator
This is the really interesting one:
Don't build better accounting software. Build an AI accountant.Don't build better CRM. Build an AI salesperson.Don't build better support software. Build an AI support organization.Don't build better legal software. Build an AI legal team.
At Level 3, the incumbent SaaS category itself can become the wrong unit of analysis.
That is also why the current debate over the “SaaSpocalypse” is somewhat misleading. Some AI companies are indeed attacking software budgets, but others are attacking the labor and business process sitting on top of the software. Recent enterprise research describes this broader shift as AI moving from task automation toward restructuring entire operational processes.
And there's an important counterpoint: incumbents aren't standing still. Salesforce, for example, is now aggressively repositioning around agents and AI-native interfaces rather than merely bolting a chatbot onto CRM.
If you're looking for the most interesting startup opportunities
I'd therefore look for incumbents where the existing SaaS product is essentially a database + workflow UI for a human employee.
Particularly juicy categories are:
ERP/accounting
customer support
recruiting
insurance operations
legal
procurement
sales operations
compliance
healthcare administration
logistics
property management
construction back office
financial operations
The strongest pattern is where the customer isn't actually buying software—they're buying the completion of a repetitive business process, and today's SaaS merely helps a human perform it.
That's the seam AI-native companies can attack from underneath.
Yes. There’s a meaningful cohort of AI-native companies whose strategy is not “add a copilot to Salesforce/NetSuite/ServiceNow,” but “replace the application layer because the workflow itself can now be executed by agents.”
This is probably the cleanest example of the thesis. Rillet isn't positioning itself as “AI for NetSuite”; it explicitly describes itself as an ERP architected around automation from day one. It has reportedly reached 600+ customers and raised more than $200M.
The important idea is that the system of record and the agent doing the accounting become the same product. That's substantially more disruptive than an AI assistant sitting on top of an incumbent ERP.
2. Campfire — rebuilding NetSuite
Campfire is unusually explicit about attacking the incumbent. Its pitch is essentially: NetSuite is the old architecture; rebuild accounting around AI.
It replaces the combination of GL + reconciliation + close management + reporting with an AI-native ERP, and explicitly markets itself as a replacement for NetSuite, SAP and similar legacy systems.
This is exactly the “redo SaaS from scratch” pattern.
3. Decagon — rebuilding customer support
Decagon is interesting because the unit of software isn't really a “support ticket” anymore.
Its agents can interact over chat, email and voice, retrieve information from CRM/helpdesk systems, take actions, and escalate when necessary. It describes the product as moving customer experience away from traditional support infrastructure toward an AI concierge.
That's potentially a much bigger change than “AI makes Zendesk agents 30% faster.”
4. Harvey — rebuilding legal work
Harvey is doing something similar in legal. Rather than simply being legal research software, it is building a connected system around the matter: research, drafting, analysis, document review, institutional knowledge and agentic workflows.
Its current scale is also notable: Harvey says it has 2,400+ customers and 75+ AmLaw 100 firms, and announced a $550M raise at a $15.5B valuation in September 2026.
5. Tennr — vertical workflow replacement
Tennr is a particularly good example of where this gets interesting outside conventional SaaS categories.
Healthcare organizations have huge amounts of messy inbound documentation. Instead of making humans navigate another workflow application, Tennr's agents gather, extract and evaluate information, determine what's missing, assess coverage and decide what should happen next.
That's effectively turning an operational workflow into an agent.
6. EvenUp — legal operations
EvenUp is rebuilding the personal-injury case workflow rather than merely adding AI search to legal software. Its system can qualify cases, identify valuable cases, analyze treatment and documentation, and coordinate handoffs through the lifecycle of a case.
The really interesting pattern
I think there are three levels of “AI SaaS disruption”, and only the third is what you're describing:
AI feature
Salesforce + AI assistant
→ Same workflow, less typing.
AI layer
Decagon connected to Zendesk/Salesforce
→ AI performs much more of the existing workflow.
AI-native application
Rillet/Campfire
→ The underlying data model, workflow and UI are redesigned around an agent doing the work.
The third category is where incumbent SaaS economics can get genuinely weird.
The old model is:
More work → more humans → more seats → more SaaS revenue.
The AI-native model can become:
More work → more AI execution → fewer humans → potentially less software spend.
That's why the most exposed categories tend to be workflow-heavy, document-heavy and seat-priced. A recent Redpoint analysis found especially high buyer openness to AI-native replacement in Salesforce automation, customer service management, ITSM, ERP and procurement.
And there's already evidence of the inverse phenomenon: companies are beginning to build internal AI systems specifically to replace expensive SaaS. Palantir, for example, said it replaced an expensive legacy CRM with an AI-first CRM built internally on AIP.
My broader watchlist
If you're looking for startups pursuing the “kill the application, own the workflow” thesis, I'd put these on a research list:
Rillet — ERP/accounting
Campfire — ERP/accounting
Decagon — customer support
Sierra — customer-service agents
Harvey — legal
Legora — legal
EvenUp — legal operations
Tennr — healthcare operations
Norm AI — compliance
EliseAI — property-management operations
Billow AI Labs — accounting/FP&A
FullSeam — corporate accounting
— AI-native accounting services
The especially interesting frontier is vertical SaaS where the customer isn't actually buying software—they're buying an outcome. Billow makes that unusually explicit: it says there is zero software for the customer to use; its agents connect to the existing systems and perform the accounting work.
That's arguably the logical endpoint of the trend: SaaS → agents → services, with the software disappearing from the customer's workflow entirely.
If you're thinking about this from a venture/investment perspective, I can also map the landscape as “$1B+ incumbent being attacked → startup → wedge → why AI changes the economics → evidence of traction” and identify the 20–30 most interesting companies.
And there's already evidence of the inverse phenomenon: companies are beginning to build internal AI systems specifically to replace expensive SaaS. Palantir, for example, said it replaced an expensive legacy CRM with an AI-first CRM built internally on AIP.
The market transition targets expensive, entrenched horizontal and vertical SaaS categories—such as finance, billing, customer support, and legal operations.
CPQ, Billing & AR (e.g., Salesforce, Zuora, NetSuite)
Manual contract data entry, invoice generation, and chasing collections
AI reads signed PDF contracts, extracts custom billing milestones, automatically issues invoices, and manages collection emails.
Fazeshift
Accounts Receivable (e.g., HighRadius)
The Core Shifts in the Competitive Landscape
Pricing Evolution: Moving away from per-seat subscriptions ($50–$150/user/month) toward usage-based or outcome-based pricing (paying per transaction, invoice parsed, or issue resolved).[](https://www.av.vc/blog/ai-is-eating-software-is-b2b-saas-dead)
System of Action vs. System of Record: Incumbents like Salesforce (Agentforce ) and ServiceNow (Now Assist ) are fighting back by embedding agents into existing databases. However, AI-native challengers win by avoiding legacy database constraints, designing interfaces completely around conversational and agentic loops rather than forms and tables.[](https://www.linkedin.com/posts/ronnizehavi_long-live-saas-and-maybe-its-time-activity-7494274864435015680-MiJg)
If you want to focus on a specific sector, let me know which industry you'd like to explore next:
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
Abridge
Medical conversations → notes, documentation, coding support
The incumbent stores data but does not own the actual business outcome.
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).
Startups and scale-ups attacking expensive incumbents are focusing on several key operational domains:
Customer Support & Service Operations: Instead of traditional ticketing systems like Zendesk or ServiceNow where human agents manually read, tag, route, and reply to tickets, AI-native alternatives (like Sierra , co-founded by Bret Taylor) are built from the ground up to autonomously converse, troubleshoot back-end database systems, and resolve entire customer workflows end-to-end.
Sales, CRM & Revenue Operations: Traditional CRMs like Salesforce or HubSpot are databases meant for humans to manually input call notes, manage pipelines, and update deal stages. AI-first challengers (like Attio or emerging autonomous outbound and pipeline agents) rebuild the CRM to auto-capture telemetry, emails, and calendar metadata, treating the CRM as a living, autonomous system rather than a digital filing cabinet.
Finance, Accounting & Billing: Incumbent ERP and billing tools (like NetSuite or legacy spend-management systems) require armies of accountants to reconcile invoices, process expenses, and run checks. AI-native financial platforms (such as Numeric for automated accounting close or various agentic AP/AR automation tools) ingest raw banking, invoice, and receipt data to execute the accounting workflow itself rather than just providing fields to type numbers into.
Legal, Compliance & Contract Review: Traditional contract lifecycle management (CLM) software just stored PDFs and tracked signatures. AI-native legal platforms (like Disclo, Harvey , or specialized compliance agents) analyze, negotiate, redline, and risk-assess documents natively through legal-domain models, bypassing the slow, human-heavy workflows of legacy tools.
Software Engineering & IT Ticketing: Traditional bug-tracking and project management tools (like Jira ) are being pressured by autonomous coding and QA agents (such as Devin by Cognition Labs or specialized engineering workflow platforms) that take a natural-language product requirement, write the code, run tests, and open the pull request directly, bypassing standard backlog-grooming workflows.
The New Playbook: Why Incumbents are Vulnerable
The Death of Per-Seat Pricing: Traditional SaaS thrives when a company buys 5,000 seats. AI-native competitors charge by the outcome, resolution, or token/compute usage , completely decoupling revenue from human headcount. If an AI agent does the work of 10 people, a per-seat model collapses the incumbent's revenue.[](https://news.crunchbase.com/saas/growing-agentic-ai-market-desilva-lateral/)
From System of Record to System of Action: Incumbents are mostly systems of record (where data sits passively). AI challengers build systems of action that actively ingest context, make API calls, trigger multi-step logic, and execute the business process without human data entry.[](https://www.youtube.com/watch?v=qzazpuD-Zpw)
Data Layer Re-Architecture: True AI-native competitors don't just "bolt on a chatbot feature" to an old database schema; they rebuild the underlying data structures specifically to feed continuous context to autonomous agents.[](https://www.saasmag.com/ai-native-vs-ai-bolted-on/)
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 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
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 pattern I'd watch
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.
And there's an even more aggressive version
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.
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. [](https://www.hubspot.com/startups/ai/aisummit-ai-agents-disrupt-saas)
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?
Here is how startups and emerging platforms are attacking expensive incumbent categories by rebuilding workflows from scratch:
Customer Support & Helpdesks
The Incumbents: Zendesk, ServiceNow, Salesforce Service Cloud.
The AI-Native Attack: Traditional helpdesks are priced "per seat," charging companies more the more human agents they hire. AI-native alternatives like Sierra (founded by Bret Taylor and Clay Bavor) and autonomous support platforms (e.g., Decagon, Kapa.ai ) don't just route tickets to humans or suggest canned macros—they resolve end-to-end multi-step issues across backend databases, handle authentication, and process refunds autonomously. The economic model shifts from charging per human seat to paying per resolution, attacking the core unit economics of legacy helpdesks. [](https://www.enjo.ai/post/best-ai-customer-service-agents)
Sales Prospecting & Outbound Development
The Incumbents: Outreach, Salesloft, ZoomInfo, HubSpot.
Traditional sales engagement platforms rely on humans building static sequences, manual list filtering, and template blasting. AI-native disruptors like (building "Alice," an autonomous digital worker for sales development) and Artisan (building "Ava") build the workflow around recursive, context-aware execution. They research prospects across the web in real-time, tailor hyper-personalized messaging based on recent company news or SEC filings, handle email replies natively, and book meetings without a human ever touching a sequence builder.
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 → 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
Parts of the analyst/IR workflow rather than another database
ERP operations / supply chain
Doss
Inventory, procurement, orders and operational workflows
The ones I'd pay particular attention to
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.
The second-order opportunity is even more interesting
I think there are three tiers of this phenomenon:
AI feature — Salesforce adds an AI agent.
AI-native application — a startup rebuilds Salesforce around agents.
AI-native service — the customer doesn't buy CRM software at all; they buy the sales outcome.
Don't sell AP software → sell invoices paid correctly
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.
Agentic workflows that autonomously score credit, converse with clients over email for collections, and reconcile ledgers.
Sierra / Decagon
Enterprise Customer Support (e.g., Zendesk, Salesforce Service Cloud)
Tier-1 human support queues and rigid macro-based ticketing
Conversational, deeply integrated reasoning agents that resolve complex backend actions (like processing refunds or changing shipping routes) rather than just deflecting calls.
Harvey / CoCounsel
Legal Practice Management & Research (e.g., Clio, Thomson Reuters)
Contract review, drafting, and legal discovery
Foundation models fine-tuned on legal workflows that replace hours of manual associative drafting and document parsing.
The Incumbents: Ironclad, Thomson Reuters, traditional legal practice management software.
The AI-Native Attack: Legacy contract lifecycle management (CLM) software treats a contract as a static PDF stored in a digital filing cabinet with metadata tags applied by a paralegal. AI-native legal platforms like Harvey or Robin AI treat legal work as a continuous reasoning engine. They draft, negotiate, and redline contracts from scratch by simulating the company's precise risk playbook, drastically reducing reliance on outside counsel and legacy document-repository workflows.
Software Engineering & Project Management
The Incumbents: Jira, Linear, GitHub (traditional issue tracking).
The AI-Native Attack: Traditional tools require humans to manually open tickets, log bugs, assign story points, and push status updates. Platforms leveraging agentic coding loops (e.g. , advanced implementations via Cursor, Devin by Cognition, and automated engineering managers) are shifting the workflow so that bugs auto-generate diagnostics, write their own pull requests, pass unit tests, and close the Jira/Linear ticket autonomously. The "project management" tool becomes secondary to the autonomous execution layer.
Finance, Accounting & Expense Operations
The Incumbents: Ramp, Brex (which evolved rapidly), NetSuite, Concur.
The AI-Native Attack: While modern fintech incumbents have done a stellar job integrating software and cards, the pure accounting, reconciliation, and audit trail workflow is being re-engineered by autonomous AI bookkeeping agents. Startups in this space use multi-modal models to read messy, non-standardized invoices, categorize complex multi-subsidiary general ledger entries, and flag anomalies without human bookkeeping intervention.