Up North AIUp North
Back to insights
5 min read

The Extinction Evidence: Why Traditional SaaS Is Hemorrhaging Value

The Extinction Evidence: Why Traditional SaaS Is Hemorrhaging Value. The New Breed: Y Combinator's Agent-Native Pivot.

orchestrationLLMagents
Share

The Extinction Evidence: Why Traditional SaaS Is Hemorrhaging Value

Goldman Sachs' latest research cuts straight to the heart of the disruption [3]. Traditional software companies face a double threat: AI-native challengers building from the ground up, and customers increasingly building their own agent-powered solutions instead of buying off-the-shelf SaaS products.

The math is brutal. Software valuation multiples have compressed from 11.5x in 2025 to 8x currently, reflecting investor skepticism about subscription models in an agent-driven world [2]. When an AI agent can analyze financial data, generate reports, and execute trades, why pay for separate analytics, reporting, and trading platforms?

Take the London Stock Exchange Group (LSEG), highlighted in Goldman's analysis. Their market data and analytics business faces direct competition from AI systems that can process raw financial information and generate insights in real-time, potentially eliminating the need for their value-added data products [3].

The seat-based pricing model is fundamentally broken when one AI agent can replace the work of dozens of human users. Enterprise customers are waking up to this reality, demanding outcome-based pricing or building internal agent capabilities instead of renewing expensive SaaS contracts.

The New Breed: Y Combinator's Agent-Native Pivot

Y Combinator's Winter 2026 batch tells the story of where smart money is flowing. Of 199 companies, the overwhelming focus has shifted to what YC calls "AI-native agencies"—not companies that use AI tools, but organizations architected as AI entities from day one [4].

This isn't about adding ChatGPT to your existing workflow. Agent-native companies operate as networks of specialized AI agents, each handling specific functions while communicating through standardized protocols. They don't have traditional org charts; they have agent topologies.

The progression is clear: from AI-enhanced incumbents trying to bolt intelligence onto legacy systems, to AI-native challengers building entirely new paradigms. The latter group is winning because they're not constrained by existing software architectures designed for human operators.

Nordic companies are particularly well-positioned for this transition. Our cultural emphasis on efficiency, automation, and pragmatic problem-solving aligns perfectly with agent-native thinking. We've seen this firsthand in our work with Nordic enterprises—they're more willing to abandon legacy processes if AI can deliver better outcomes.

Agent-Native Architecture: The Technical Foundation

Building agent-native software requires fundamentally different architectural principles. Traditional software follows the request-response pattern optimized for human interaction. Agent-native systems operate as autonomous networks exposing actions rather than interfaces [5].

The emerging standard is captured in frameworks like AGENTS.md, which defines how AI agents should behave consistently within codebases. Instead of documenting APIs for human developers, we're documenting behavioral protocols for AI agents [5].

Key architectural shifts include:

  • Action-oriented design: Agents expose capabilities as discrete actions that other agents can invoke
  • Outcome-based monetization: Revenue tied to results achieved, not seats occupied
  • Continuous adaptation: Systems that modify their own behavior based on performance data
  • Judgment injection points: Critical decision nodes where human oversight remains essential

Google's Agent Development Kit (ADK) exemplifies this approach with multi-agent frameworks that can spawn, coordinate, and terminate agent instances based on workload demands [6]. This isn't microservices—it's micro-intelligences.

The Quality Code Problem: Benchmarking AI-Generated Software

As AI generates more code, defining "good" software becomes critical. The open-source community is developing benchmarks where maintainers define quality criteria around architecture, efficiency, and maintainability [7].

The challenge is that AI agents often ignore traditional code quality metrics if they can achieve the desired outcome through other means. We need new evaluation frameworks that balance functional success with long-term maintainability.

Emerging benchmarks like CodeJudge-Eval use LLMs as code reviewers, but the real innovation is in community-driven quality definitions. Nordic developers, with our emphasis on clean, efficient code, are well-suited to lead these standardization efforts [7].

At Up North AI, we've found that the best AI-generated code exhibits three characteristics:

  • Modularity for agents: Easy for AI systems to understand and modify
  • Context awareness: Adapts behavior based on operational environment
  • Audit trails: Clear logging of decision points for human review

Builder's Playbook: Navigating the Post-SaaS Transition

For CTOs and technical leaders, the transition to agent-native architecture requires strategic thinking, not just tactical tool adoption. The companies winning this transition are those that embrace hybrid judgment infusion—combining AI capability with human oversight at critical decision points.

What works:

  • Start with outcome-based pilot projects rather than trying to replace entire systems
  • Invest in agent orchestration platforms that can coordinate multiple AI capabilities
  • Build judgment injection points into workflows where human expertise remains valuable
  • Focus on data quality and standardization—agents are only as good as their inputs

Common pitfalls:

  • Trying to retrofit agent capabilities onto legacy SaaS architectures
  • Underestimating the complexity of agent coordination and error handling
  • Ignoring security and compliance requirements in agent-to-agent communication
  • Assuming AI agents can operate without human oversight indefinitely

Nordic companies have a particular advantage in this transition due to our cultural comfort with automation and systematic approaches to problem-solving. We've observed that Nordic enterprises are more willing to experiment with agent-native approaches, leading to faster learning cycles and better outcomes.

The Economics of Infinite Software

Andreessen Horowitz makes a crucial point: there will be more software than ever before, not less [1]. AI doesn't eliminate software—it makes software creation essentially free. The scarce resource becomes judgment: knowing what software to build, how to architect it, and when human oversight is essential.

This creates entirely new economic models. Instead of selling software licenses, successful companies will sell curated judgment and orchestrated outcomes. The value shifts from the code itself to the intelligence that guides its creation and deployment.

The implications are profound:

  • Software development cycles compress from months to hours
  • The barrier to entry for new applications approaches zero
  • Competitive advantage comes from data, judgment, and orchestration capabilities
  • Traditional software companies must evolve or face extinction

We're entering an era where the question isn't whether you can build software—AI ensures you can. The question is whether you can build the right software and deploy it effectively. That's where human judgment becomes the ultimate differentiator.

The Nordic Advantage in the Post-Code Era

As we navigate this transition at Up North AI, one thing becomes clear: code is becoming free, but judgment isn't. The companies that thrive in the agent-native era will be those that can effectively combine AI capability with human insight, creating systems that are both autonomous and accountable.

Scandinavian builders planning on a fjord overlook, symbolizing Nordic edge in post-code innovation

The SaaSpocalypse isn't the end of software—it's the beginning of software that thinks. Nordic builders, with our emphasis on pragmatic problem-solving and systematic approaches, are uniquely positioned to lead this transformation. The question isn't whether AI will eat application software. It's whether we'll be the ones teaching it what to bite.

The future belongs to those who can architect intelligence, not just code. Welcome to the post-code era.

Sources

  1. https://a16z.com/good-news-ai-will-eat-application-software
  2. https://markets.financialcontent.com/wral/article/marketminute-2026-3-26-the-great-saas-reset-b2b-software-equities-plunge-25-as-ai-disruption-rewrites-the-playbook
  3. https://www.goldmansachs.com/pdfs/insights/goldman-sachs-research/will-ai-eat-software/report.pdf
  4. https://www.extruct.ai/research/ycw26
  5. https://every.to/guides/agent-native
  6. https://a16z.com/there-are-only-two-paths-left-for-software
  7. https://www.forbes.com/sites/petercohan/2026/02/06/saaspocalypse-now-ai-is-disrupting-saas---but-not-all-software-is-doomed

Want to go deeper?

We explore the frontier of AI-built software by actually building it. See what we're working on.