In 1981, IBM launched the Personal Computer and accidentally created Microsoft. The hardware giant that dominated computing handed the most valuable layer - the operating system - to a software vendor it barely noticed. IBM kept making computers. Microsoft owned the platform.
The mistake wasn’t technical. IBM understood computers better than anyone. The mistake was assuming value stayed in the same place when the stack changed. They thought hardware would remain the high ground. They were wrong.
Last Monday, software stocks lost $285 billion in a single trading session. The trigger was Anthropic releasing plugin updates for their Claude agent product. Not a new model. Not a major technical breakthrough. Just plugins that let AI agents interact with business systems more directly.
Wall Street looked at those plugins and realized something uncomfortable: if agents can execute workflows through APIs, maybe the UI layer that’s captured most software value for twenty years isn’t the product anymore.
But here’s what the panic missed. That $285 billion didn’t vanish into thin air. It’s repricing. And if you understand where it’s moving, you’re looking at the clearest startup opportunity landscape in a decade.
What’s Actually Happening (Without the Hype)
The simplified story circulating X: “Agents will replace SaaS. Per-seat pricing is dead. UI is obsolete.”
The reality is more interesting and more specific.
Software is unbundling. Not dying. Not being replaced wholesale. Unbundling into distinct layers, each with different economics and different winners. Some layers strengthen. Some collapse. Some didn’t exist six months ago.
Let me be precise about what’s dying and what’s not.
What’s actually dying:
Single-user data entry interfaces. The “log a call” screen in your CRM. The expense report form. The time tracking app. Anywhere one person inputs structured data that an agent could capture automatically, that interface is living on borrowed time.
Per-seat pricing without usage or outcome components. The “$99 per user per month forever” model assumes headcount drives value. When ten agents do the work of fifty people, that math breaks.
Workflow software without real moats. If your product is “nice UI over someone else’s data” with no proprietary advantage, you have maybe eighteen months to figure out what you actually own.
What’s strengthening:
Multi-user collaboration interfaces. Figma didn’t get weaker when agents learned to generate design components. It got more valuable as the place where humans review, discuss, and decide together. Google Docs isn’t threatened by agents that draft. It’s the interface where humans edit and comment.
Systems of record with canonical data. Salesforce’s moat isn’t the UI for logging calls. It’s owning the authoritative customer database that every agent needs to read from and write to. When agents amplify data quality problems, clean authoritative data becomes more valuable, not less.
Approval and governance workflows. As agents take more autonomous actions, the review gates become more important. “Check these ten contracts before the agent sends them” is a new interface category, not a dying one.
Net new categories that didn’t exist before:
Agent orchestration platforms. Something has to coordinate multiple specialized agents. That coordination layer will capture value.
Agent-specific security. Which agents exist in your organization? What are they accessing? Are they authorized? Most companies have no idea. This is now a CISO problem.
Evaluation infrastructure. How do you know if an agent’s legal contract review is actually correct? Domain-specific testing becomes its own category.
The pattern isn’t replacement. It’s restructuring.
The Stack Breakdown
Think of enterprise software as six layers. Agents don’t hit all of them equally.
The Data Layer: Incumbents Strengthen
Systems of record - your CRMs, ERPs, data warehouses - have an odd property. Agent adoption makes them more valuable.
Here’s why. Agents amplify data quality problems exponentially. If you have duplicate customer records, a human spots that and works around it. An agent might send emails to both records. Bad data in equals bad actions out, but now at scale and with no human in the loop to catch mistakes.
This creates a premium for clean, authoritative data. The companies that own canonical datasets get stronger, not weaker, because agents have to integrate with them.
Salesforce can lose the “log a call” interface and barely feel it. What Salesforce actually owns is ten years of customer interaction history, buying patterns, relationship maps, and tribal knowledge that every sales agent needs to function. That’s not getting disintermediated. That’s getting more valuable.
ServiceNow, Workday, SAP, they all follow the same pattern. Their data gravity increases. Every new agent that writes to their system makes the switching cost higher.
The startup opportunity here is narrow but real: under-digitized verticals where no incumbent owns the system of record yet. Construction project management. Healthcare operations outside the clinical setting. Legal matter management. These markets still run on spreadsheets and email because no one built the definitive operational backbone. Build that backbone with an agent-native design from day one, and you can become infrastructure.
The investment filter is simple. If Salesforce, ServiceNow, or Microsoft already serves the vertical, you’re late. If people are still using Excel, you’re early.
The Execution Layer: Winners and Losers Splitting
This is where agents live. It’s also where the most confusion exists about who wins.
The layer is splitting between three types of companies with radically different futures.
Vertical specialists win when they have workflow knowledge.
Harvey for legal works not because their underlying model is better, but because they encoded legal reasoning patterns, built legal-specific evaluation datasets, and integrated into how law firms actually work. A generic AI assistant can’t replicate that without years of domain immersion.
The pattern holds across verticals. Sales intelligence agents that know how to qualify enterprise B2B leads. Financial reconciliation agents that understand accounting rules. Medical coding agents that navigate ICD-10 complexity.
The test is simple: could two engineers replicate your product in three months using Claude’s API? If yes, you don’t have a business. You have a wrapper.
Foundation model companies capture value if they build platforms fast.
Anthropic and OpenAI don’t just sell model access. They’re racing to build ecosystems. The winner isn’t necessarily who has the best model. It’s who builds the best plugin marketplace, orchestration layer, and distribution before commoditization happens.
This follows the cloud infrastructure playbook. AWS won not because their servers were better but because they bundled services faster than the competition. Model capabilities are converging. Platform depth is diverging.
Generic horizontal agents become commodities.
The “AI assistant that does everything” is heading toward free. Not because the technology is trivial, but because distribution advantages and ecosystem effects create winner-take-most dynamics. Microsoft, Google, Anthropic, OpenAI will all bundle general-purpose agents with their platforms.
If you’re building a horizontal agent without unique distribution or proprietary data, you’re competing on price in a race to zero.
The Interface Layer: It’s Complicated
This is where everyone gets the story wrong by oversimplifying.
“UI is dead because agents use APIs” sounds clean. It’s also incomplete.
Different interfaces have radically different futures. The distinction isn’t “UI versus agents.” It’s “what job does the interface actually do?”
Interfaces for solo data entry die fast.
Expense reports. Time tracking. Call logging. Meeting notes. Anywhere one person inputs structured information, an agent can capture that directly. The form becomes unnecessary.
Expensify’s entire value proposition was making expense reports less painful. If agents eliminate expense reports entirely, Expensify doesn’t have a product.
Interfaces for multi-user collaboration thrive.
When you edit a Google Doc, you’re not just manipulating text. You’re coordinating with other humans. Commenting. Suggesting. Negotiating meaning. Agents can draft, but they can’t resolve disagreements between stakeholders or make judgment calls about ambiguous communication.
Figma, Notion, Miro, all the collaboration-first tools get stronger. The value isn’t in the canvas or the database. It’s in the coordination protocol.
Interfaces for high-stakes review become premium products.
Even when an agent completes a workflow autonomously, someone needs to review high-stakes outputs before they ship. That review interface has different requirements than the original data entry interface.
A lawyer reviewing ten agent-drafted contracts needs to see reasoning, flag anomalies, compare to templates, and track changes. That’s specialized UI. It’s also not optional. Regulatory frameworks in finance, healthcare, and legal all require human review for certain decisions.
The new interface category is “agent oversight.” Dashboards showing what agents did and why. Approval queues for batch review. Exception handling when agents fail.
The companies building that layer aren’t competing with agents. They’re building the human side of human-agent collaboration.
Context matters enormously here. Single-person workflows in small businesses get automated fast. Complex multi-stakeholder processes in regulated enterprises move slowly and maintain human interfaces throughout.
The Governance Layer: The Quiet Opportunity
This is the most interesting category because it’s genuinely new.
When ten people use software, you need some security and compliance infrastructure. When hundreds of autonomous agents use software, you need dramatically more.
Three categories are emerging:
Agent identity and access management. Most enterprises deploying agents have no idea which agents exist, what they’re accessing, or whether they’re authorized. This isn’t theoretical paranoia. It’s a CISO mandate.
The wedge product is simple: scan an organization and show them all the agents they didn’t know about. Most companies discover shadow AI everywhere. Then you sell the policy enforcement and audit layer.
Evaluation and testing platforms. How do you know an agent’s legal review is correct? Or that a sales lead qualification meets your standards? Domain-specific evaluation datasets become valuable IP.
This looks like testing infrastructure for code, but for agent outputs. The companies that build credible evaluation frameworks in specific domains can charge premium prices because getting it wrong has real consequences.
Observability and debugging. When a multi-agent system fails, diagnosis requires distributed tracing across autonomous components. This is Datadog, but for agents. The technical challenge is real, which means there’s room for venture-scale infrastructure companies.
The risk here is bundling. If Anthropic or OpenAI include governance tools for free in their platforms, standalone governance companies struggle. But the enterprise security budget is large and sacred. CISOs will pay for best-in-class tools, not just whatever comes bundled.
The other risk is timing. This infrastructure is only valuable once agents reach production scale. If adoption is slower than expected, the governance market is smaller. But the signal from February 2026 enterprise deployments suggests the need is real and urgent.
What People Are Missing
Five things that aren’t obvious from the surface narrative.
The “Thin Middle Squeeze” Needs Precision
Yes, the middle layer of software is getting squeezed. But the middle isn’t monolithic.
The layer getting squeezed is single-user data manipulation. Forms. Reports. Configuration screens. Anywhere the interface exists solely to let one human talk to a database.
The layer getting stronger is multi-user coordination. Places where the software’s value comes from helping humans collaborate, not from interfacing with data.
The distinction completely changes which companies are at risk. Expensify (single-user data entry) is in trouble. Figma (multi-user collaboration) is strengthening.
The investment filter: ask whether the software is single-player or multiplayer. Multiplayer is the safer bet.
Outcome-Based Pricing Is Harder Than It Looks
Everyone talks about moving from “$99 per seat per month” to “$5 per contract reviewed.” The vision is compelling. The execution is harder.
Three unsolved problems:
Attribution gets messy. When multiple agents touch the same outcome, who gets credit? If a lead qualification agent identifies a prospect, an enrichment agent adds context, and an outreach agent makes contact, do all three get paid? How do you split the outcome value?
Quality disputes need arbitration. Customer says the contract review was poor quality and refuses to pay. How do you resolve that? Traditional SaaS has clear deliverables: you used the software, you pay. Outcome pricing introduces risk transfer that needs contractual and technical infrastructure.
Gaming incentives break systems. If an agent is paid per action, it maximizes actions, not value. You end up with agents taking unnecessary steps to inflate billing.
The reality emerging in early 2026: outcome pricing works for high-volume, commodity tasks with clear quality metrics. Document classification. Fraud detection. Simple triage. It struggles with complex, judgment-intensive work where outcomes are ambiguous.
What actually happens is hybrid models. Base platform fee plus usage-based consumption plus outcome bonuses. The pure “pay only for outcomes” model remains niche.
If you’re underwriting a deal assuming 100% outcome-based revenue by 2028, you’re being too aggressive. Assume hybrid models generate most revenue.
Services Demand Spikes Then Craters
Early-stage agent deployment is intensely service-heavy. Data cleanup. Process redesign. Change management. Integration work. The 2025-2028 period is boom time for implementation services.
But here’s the pattern from every previous infrastructure shift: as deployment patterns mature, tooling improves, and self-service adoption increases, services demand drops.
Cloud migration was services-intensive from 2010 to 2015. Then CloudFormation, Terraform, and standardized patterns automated much of it away. The same companies that built thriving services practices in the early cloud era had to scramble to productize before self-service ate their margins.
Agent deployment will follow the same arc. The companies that build successful services businesses need explicit three-year productization roadmaps. Start with services to land customers and build workflow knowledge. Extract that knowledge into repeatable playbooks. Turn playbooks into software. Migrate customers from services to software over time.
If you’re still generating 60% of revenue from services by year three, you have a consulting firm with software on the side, not a venture-scale business.
The Real Adoption Curve Is Ten to Fifteen Years
Cloud took roughly twelve years from AWS launch in 2006 to majority enterprise adoption. SaaS took thirteen years from Salesforce’s 1999 launch to crossing 50% penetration around 2012.
Agents will probably follow a similar pattern.
This matters because seed investors writing checks in 2025 and 2026 need seven to ten year exits, not four to five years. Fund construction has to accommodate longer hold periods.
The 2026 to 2029 period will see early adopters in production, the majority in pilot phase, and laggards watching from the sidelines. True mainstream adoption, where more than half of target workflows run on agents, probably doesn’t hit until 2032 to 2035.
The signal to watch: enterprise pilot-to-production timelines. Normal enterprise software takes twenty-four to thirty-six months from pilot to scaled deployment. If agents compress that to under eighteen months, adoption is accelerating. If it stretches beyond thirty-six months, it’s slowing.
Current signal from February 2026 deployments: timelines look normal, not accelerated. That suggests gradual adoption, not revolution.
The $285 Billion Repriced Risk, It Didn’t Vanish
Software stocks didn’t lose value because business models broke overnight. They lost value because investors repriced growth assumptions and risk premiums.
Three things happened:
Multiple compression. Software trading at 30x forward earnings assumed 25% annual growth forever. Agent disruption introduces uncertainty. Multiples compress to 12 to 15x. That’s still healthy, just not bubble levels.
Growth uncertainty. If your customer might need 50% fewer seats in three years, your ARR growth projections need revision downward. Lower expected growth means lower valuation.
Margin pressure during transition. Companies have to invest in agent products while maintaining legacy products. That compresses margins temporarily.
But here’s what the market overreacted to: most software revenue doesn’t disappear. It shifts between categories and gets repriced.
Total enterprise software spend will likely grow through this transition. Agent platforms create new revenue. Governance tooling is net-new spending. Services boom. Systems of record strengthen and raise prices.
The investment opportunity in 2026 and 2027 is probably buying depressed public software stocks. Many will successfully transition and get re-rated upward. Avoid pure-play data entry software. Favor platforms, systems of record, and collaboration tools.
What This Means If You’re Building
The playbook depends on where you’re entering the stack.
Highest conviction: agent-native systems of record in under-digitized verticals.
Construction project management. Healthcare operations outside clinical settings. Legal matter management. Field services coordination. Logistics exception handling. These markets still run on spreadsheets and email threads because no one built the definitive operational backbone.
Build that backbone with an agent-native design. Start with a single workflow that delivers immediate ROI. Expand to become the system of record for all operational data. Once agents operate your system, switching costs become prohibitive.
The team you need: someone with five-plus years in the vertical who knows workflows intimately and has customer relationships. Someone who can build production systems and understands data modeling. The founding story is “I was VP Operations at this company, built this internally, now commercializing it.”
High conviction: vertical agents with measurable ROI.
Legal contract review. Sales lead enrichment. Financial reconciliation. Medical coding. Customer support triage.
Three requirements: the workflow happens more than one hundred times per month, the current process costs $50 to $500 per instance, and the outcome is measurable.
The wedge is “assist don’t replace.” Agent drafts, human reviews. That de-risks adoption and builds trust. Once you prove value, expand scope to more complex tasks.
The moat comes from proprietary training data, evaluation datasets that prove quality, and workflow integration that makes you embedded in daily operations.
Medium conviction: agent governance and security.
Agent identity and access management. Evaluation platforms. Observability and debugging tools.
This is net-new category where incumbents don’t have solutions yet. The risk is bundling (model providers might include governance for free) and market timing (if adoption is slower than expected, the market is smaller).
The wedge is free tier for discovery and scanning, paid tier for policy enforcement and compliance features. The buyer is the CISO, who has budget and regulatory mandate.
Lower conviction but viable: outcome-based pricing infrastructure.
The “Stripe for usage-based billing” play. Metering, attribution, dispute resolution for outcome-priced software.
This is high-risk, high-reward. If outcome pricing becomes standard, this infrastructure is valuable. If hybrid models dominate and pure outcome pricing stays niche, the market is smaller.
The team needs payments background (ex-Stripe, Zuora, Chargebee), technical depth, and ability to sell to both CFOs and product teams simultaneously.
What to avoid:
- Generic horizontal AI assistants. Commoditized by foundation models.
- UI-only copilots without execution capability. Agents will bypass interfaces.
- Horizontal agent marketplaces. Incumbents own distribution.
- Pure consulting without software leverage. Not venture-scale.
- Direct competition with Salesforce or ServiceNow in their core markets. You’ll lose.
Where We Are
February 2026 feels like a discontinuity, but it’s probably more like 2006 in cloud computing or 1999 in SaaS. The technology works. Early adopters are deploying. The path to mainstream is visible but will take a decade.
The companies that win won’t be the ones that “replace SaaS with agents.” They’ll be the ones that understand which layers strengthen, which collapse, and which emerge as net-new categories.
SaaS as a delivery model is fine. SaaS as a business strategy built on shallow moats and per-seat pricing for commodity workflows is over.
The easy era ended. The hard era is starting.
The best news in more than a decade for people building real things instead of wrappers.