Tier 5: Agentic OS (emerging)
L5

Autonomous Operations: Anticipatory AI.

L5 is the system as colleague. Durable memory of the business, the people, the goals. It initiates work: sees a contract expiring and starts renewal, sees a churn signal and opens a save flow. Governed by policies, not prompts. Reports on what it did, instead of waiting to be asked. L5 is the frontier, and we say so.

Adoption
<1%
Orchestration
The agent org
Implementation
$3-8M+
Time from L4
18-24+ months
EBITDA lift (cum.)
1,450-3,350+ bps
Honest read, May 2026

L5 is emerging. We don't pretend otherwise.

Real L5 is largely aspirational in 2026. Here's what actually exists today:

What exists todayWhat it actually is
L4+ cronScheduled agents that look proactive but are trigger-reactive.
L4+ memoryDurable memory layers (Mem0, LangMem, Letta/MemGPT) bolted onto L4.
Narrow L5 · codingDevin parallel sessions, Cursor background agents, and Claude Code in CI proactively opening PRs from failing tests or lagging deps.
Narrow L5 · CXSierra and Decagon's newest tier, paid on resolution.
Bespoke internalTop engineering orgs (Anthropic, OpenAI, Stripe, Shopify), pattern proven, not productized.
“Marketing L5”L3/L4 stacks branded “Operator,” “agentic OS,” or “autonomous employee”, mostly L4 with a memory layer and a content team.

The defensible L5 question: What does it do when nobody is logged in?

Vendor matrix

The named picks at L5.

CategoryBOD PickReality check
Organization-of-agents (pattern source)PAPaperclip55K+ stars, MIT. The leading L5 reference: we borrow its primitives (org charts, budgets, heartbeats, approval gates), not a client production bet (no SOC 2, no SSO/SCIM, TypeScript runtime). Partnership is R&D-flavored.
Org-of-agents (alt)SSSim Studio · Sema4 (company-mode) · Cognition fleetCategory still forming as "company-as-code."
Memory-first frameworksMELetta (MemGPT) · Mem0 · LangMemSubstrate for L5 builds, not products.
Narrow L5: SWEDVCognition Devin (multi-session) · Cursor background agents · Claude Code in CIMost credible production L5 today.
Narrow L5: CXSDSierra · Decagon (autonomous tier)Outcome-priced. Real production volume.
Consumer-grade autonomousMNManus · ChatGPT Agent / Operator · Replit AgentEntertaining; vet carefully for enterprise.
BOD control planeBODEdge Scale"The BOD layer, orchestration-agnostic." Product-in-build; runs on top of LangGraph, CrewAI, Bedrock AgentCore, Mosaic, or Cortex.

"At L5, our value is being an early, sophisticated co-builder. The partnership is R&D-flavored, not implementation-flavored. We're not inventing the engine; we are productizing the operating environment around it so a CFO can sign a contract."

BOD L5 framework brief
Forward-deployed use cases

What L5 looks like in the rare places it exists.

Finance

Close-to-report by agents

Close, reconciliation, variance, commentary: driven by agents. Human approval only at board sign-off. The CFO reviews exceptions; the agents run the cycle.

Sales

Full-funnel agent organization

Research to negotiation support, as a fleet. The seller closes; the agents do everything else. Pricing model shifts from seat-based to outcome-based.

Support

Full resolution stack

Tier 1, tier 2, escalation triage: all agent-run. Sierra and Decagon are the production references in 2026.

HR

Sourcing to offer modeling

Talent acquisition as an agent organization. The talent leader signs offers and manages culture; the fleet does the rest.

Engineering

Devin fleet on the backlog

Parallel autonomous SWE agents shipping features overnight. Most credible L5 production reference category today.

Product-embedded

Agent-native product

The core experience is a conversation with an agent (or agents) that runs the job the user hired the product to do. Pricing shifts seat → outcome. The exit multiple reflects a category shift.

Anti-patterns

How L5 marketing differs from L5 reality.

  • Calling cron L5. A scheduled agent is L4 with a timer.
  • L5 demos that need an audience. If it only runs when leadership is watching, it isn't autonomous.
  • No kill-switch, no scope. Autonomy without enforced policy boundaries becomes incidents.
  • Memory without governance. Long-lived memory is a long-lived liability.
  • Skipping L3-L4. No leapfrog. Teams that try produce demos, not systems.
The exit angle

Why L5 moves the multiple.

"L3 is where the economics compound. L4 is where they inflect. L5 is where exit multiple moves, and where the partnership becomes R&D rather than implementation."

For software companies, an agent-native product is a category change, not a feature add. Pricing model shifts from per-seat to per-outcome, and the buyer is pricing a different business.

For non-software portcos, L5 governance is the exit asset. The buyer sees a fund that already classified durability risk before they did.

Co-build at the frontier.

BOD is mid-L4, building L5. We co-build with portfolio companies that want to be early to the operating environment shift, not late to it. Partnership is R&D-flavored. We're honest about what's solved and what's still being invented.

Talk to BOD