Tier 3: Embedded · BOD entry point
L3

Workflow Agents: Done For You. This is where BOD starts.

L3 is where a single agent (coordinator with a loop, tools, memory) executes multi-step workflows autonomously. Human sets the goal and reviews. The agent picks steps, calls tools, retries, produces a deliverable. This is BOD's entry point. L3 is where workflow economics show up, not user productivity. A function gets faster and cheaper.

Adoption
~5%
Orchestration
The workflow
Implementation
$750K-$1.75M
Time from L2
9-12 months
EBITDA lift (cum.)
350-950 bps
The reverse narrative

We anchor here. Then expand outward.

The industry-standard "climb the stack" story tells portfolio companies to start at L1, build to L2, hope to reach L3, and dream of L4. That story keeps the systems integrator employed. It doesn't deliver EBITDA.

BOD inverts it. We start at L3 because L3 is where workflow economics show up: cost-per-task replaces cost-per-seat as the metric.

From that anchor we move in three directions:

The 80% chat-and-copilot adoption isn't the destination. It's the surface area that exists after the workflow is automated.

1 · enter here L3 Workflow Agents, where workflow economics compound
2 · expand down
L2Connected Intelligence: the substrate the agent needs
L1Foundational: re-incorporated at the escalation edge
3 · expand up
L4Orchestrated Systems
L5Autonomous Operations

BOD starts where workflow economics compound, then expands down, up, and re-incorporates L1 at the edges.

What L3 actually looks like in a portfolio company

FunctionIn practiceSignal
FinanceVariance, narrative and board-deck agents, chained, evaluated, observableFP&A 10d → 2d
SalesThe agent enriches, scores and routes leads; humans closeConversion uplift
SupportAgent drafts the reply; human reviews; ticket closes faster with audit trailAI-first triage
LegalAgent feeds the deal desk a risk-scored summaryNot a 60-page redline
EngineeringClaude Code / Cursor Agent in CI opens PRs from failing tests & lint debtPR throughput 2× vs L1
What an L3 agent does

The agent runs the workflow. A human reviews the edge.

This is the shift that makes a function cheaper, not just faster: the steps a person used to run are now executed by the agent, with a human reviewing the one decision that needs judgment.

L1
CopilotDone by you
Person does the work
Gather DraftAI Check Decide Send
Faster person, same process · cost-per-seat
vs
L3
Workflow AgentDone for you
Agent runs the workflow
Gather Draft Check Decidehuman Send
tools · memory · retry
Process redesigned, runs without people · cost-per-task

Same workflow as L1, but cost-per-task replaces cost-per-seat the moment the agent runs the steps.

Vendor matrix

The named picks at L3.

CategoryBOD PickWhyPricing signal
Durable workflow executionTPTemporalBOD default. Production-grade durable execution for AI workflows.OSS + Cloud tiered
Coding agent in CICCClaude Code78.4% SWE-bench Verified; 5.5× lower token cost vs Cursor Agent; MCP-native~$125/seat Premium
Coding agent (IDE)CUCursor AgentFortune 500 default; multi-provider; agent + editor~$40/seat/mo Teams
Eng-grade orchestrationLGLangChain / LangGraphBOD L3+ default for engineering teamsOSS + LangSmith
Data-centric RAG agentsLILlamaIndexBOD L3 default for data-heavy retrievalOSS + cloud
OSS visual workflowN8n8nSelf-hostable, sandboxed code, sovereignty-friendlyEUR 20-667/mo Cloud
Hyperscaler-nativeDatabricksDbrx Workflows · Snow Tasks + Cortex · Bedrock + Step FunctionsWhen the data platform is the lock-inBundled
Pre-built (rev ops)LDLindy · Relevance AIFast value for SDR / exec admin / research agents$49-200+/mo
CX outcome-pricedSISierraPaid on resolution. Outcome aligns incentives.Per-resolution
Inside SalesforceAFAgentforceLocked to SFDC; three pricing models$125/seat OR $0.10/action
EvalsBTBraintrust · LangfuseBOD primary; OSS alternativeTiered

BOD positioning

L3 is where consulting engagements compound. Edge Deploy drops a production-grade agent into your stack in 90 days: finance variance, sales SDR, support tier-1, AP, recruiting, product research.

Each is built to run on Edge Scale, our Agent Ops control plane (product-in-build): governance, audit, cost attribution, RBAC, SSO, and a managed tier targeting 99.9% SLA.

Forward-deployed use cases

Six Deploy blueprints.

Each is a repeatable 90-day engagement that drops a production-grade agent into the client's stack, wired to the Edge Scale control plane as it comes online. Same architecture, same evals discipline, same control plane.

Finance

Variance / FP&A agent

Close-to-commentary cycle compressed 10d → 2-3d. Variance agent reads the close package, drafts commentary, flags exceptions, routes to the CFO for sign-off.

Sales

SDR agent

Research → personalization → send → reply classification → meeting. Pipeline doesn't grow because reps work harder; it grows because the agent works while reps sleep.

Support

Tier-1 agent

Agent drafts the reply; human reviews. Deflection moves from 30% (L2) toward 70%+, without losing the long tail that needed a human.

Finance ops

AP agent

Invoice intake → matching → approval routing → exception escalation. Pairs with Ramp / AppZen where appropriate.

HR

Recruiting agent

Inbound screening → scheduling → first-round scorecard. The recruiter takes the shortlisted candidates into final rounds, not the inbox triage.

Product

Product Research agent

The agent watches usage signals, drafts feature briefs, summarizes user research, builds the PM the agenda for the weekly review. PM ships, doesn't curate.

Anti-patterns

How L3 stalls.

  • Agentifying an unmeasured process. No baseline cycle time or error rate; can't tell if the agent helped.
  • Cursor agent on autopilot, no observability. Token bills explode; devs disable it.
  • Write access without rollback. Agent sends 400 wrong-segment emails. Trust dies for 18 months.
  • Zapier-tax surprise. Great agent + 100K tasks/mo = $1,500+/mo with no migration plan.
  • Tool soup. Three agent platforms, no shared evals, no shared MCP server, no shared identity.
  • Picking Agentforce because the SI prefers it. Lock-in is real; agent math is opaque.
Graduation signals

What L4 looks like.

  • The workflow has natural specialization (research / draft / review / route / escalate).
  • Persistent state across runs is a hard requirement.
  • You want agents to call other agents.
  • Compliance asks for replay, audit, lineage. You need a control plane.
  • Cost-per-task replaces cost-per-seat as the metric.

L4: Orchestrated Systems →

"L3 is where the economics compound. L4 is where they inflect. L5 is where exit multiple moves."

BOD Maturity Memo, rev 3

Ship an L3 workflow in 90 days.

Edge Deploy ships production-grade agent blueprints: finance variance, sales SDR, support tier-1, AP, recruiting, product research. Drop one in. Measure it. Then we expand outward.

Talk to BOD