Tier 2: Enabled
L2

Connected Intelligence: Done With You.

L2 grounds the model in your data. Still human-initiated, but the system retrieves from internal documents, databases, tickets, transcripts. Output quality jumps because the context contains permissioned company data, not the open internet. Where most "AI ROI" stories actually live in 2026.

Adoption
~10%
Orchestration
The human
Implementation
$350-750K
Time from L1
6-9 months
EBITDA lift (cum.)
150-450 bps
Definition

RAG, packaged. The first place AI knows your business.

Technically: a vector store, a retrieval pipeline, a reranker, generation, and a packaging layer (Custom GPTs, Claude Skills, Gemini Gems, or a turnkey like Glean or Hebbia). L2 is where evals start showing up, because hallucination becomes measurable when the source-of-truth is internal documents instead of the open web.

The orchestrator at L2 is still the human. Lightweight glue (Zapier AI, n8n, Dify, Flowise, Langflow, Superagent) connects retrieval to a downstream step, but the person initiates the turn.

What L2 actually looks like in a portfolio company

FunctionIn practiceSignal
SupportA grounded help-center bot answers the FAQ band; humans take the rest25–40% deflection
FinanceCopilot pulls from the close package; the CFO writes the narrative−60% CFO draft time
SalesGrounded, sourced objection answers cut by segmentCited in seconds
LegalCited answers with section references, Hebbia for diligence, Claude Skills for everydayCited Q&A
InternalGlean stitches Slack, Drive, Salesforce, Notion, permissions intactSearch that works

Evals start at L2, non-negotiable

"Good" L2 evals are a golden dataset per copilot, a scored baseline, a target, and a regression run on every prompt or tool change, with adoption measured per-cohort rather than by license count. Teams that ship L2 copilots without an eval habit cannot reach L3 without rebuilding, so we start scoring at L2, not L3.

Vendor matrix

The named picks at L2.

CategoryBOD PickBest fitPricing signal
Enterprise search / RAGGLGlean1,000+ FTE orgs with SaaS sprawl$15-25/seat/mo
Analyst-grade docsHBHebbiaPE diligence, M&A, legal reviewMid-to-high six figures
Authored capabilitiesCLClaude SkillsPortable, markdown, runs on Bedrock/VertexToken + seat
Authored capabilities (alt)GPCustom GPTs / Workspace AgentsSales enablement, internal Q&ABundled with ChatGPT Biz/Ent
BYO RAG (vector)PCPinecone (managed) / pgvectorEmbed in product / Postgres-heavy$50-700/mo+
RAG frameworkLILlamaIndexBOD L2-L5 defaultOSS + cloud
Vertical copilotsHVHarvey · Clay · Writer · Intercom FinLegal / sales / marketing / supportPer-vertical SaaS
Hyperscaler-nativeAWSAWS Q · Azure AI Search · VertexWhen the cloud is the constraintBundled
EvalsBTBraintrust primary; Langfuse OSSQuality-as-engineering vs. cost-sensitiveTiered
OSS alternativeOXOnyxSovereignty-first mid-marketFree (self-host)

BOD positioning

L2 is the substrate the agent layer above it depends on. Skipping it doesn't save time. It pushes hallucinations into production at L3. Buy Glean if you're 500+ FTE and your SaaS estate is sprawling. Build with Claude Skills + Pinecone + LlamaIndex if you're going to embed AI in your own product.

Why keep climbing

L2 makes answers trustworthy. The EBITDA is still upstream.

Grounded retrieval is a real step, but a human still drives every task, so unit cost barely moves. The value inflects one tier up, at L3, where the agent runs the workflow.

Where companies are today, share of the mid-market by tier Where the EBITDA is, cumulative lift by tier

L2 is necessary substrate, not the destination. The curves cross before L3, which is why we don't stop here.

The L2 to L3 bridge

Low-code and no-code agent platforms: a step, not a dead end.

A wave of tools market themselves as agent platforms with low-code or no-code builders. For the right workflow they're the fastest way onto the ladder: a cheap rung that proves a workflow before it earns a code-first build. We treat them as a validation substrate with a named graduation test, not a permanent architecture for anything that becomes high-stakes.

CategoryRepresentative toolsThe shared ceiling
Workflow-automation incumbents (LLM steps added)Zapier · Make · n8nRule-based at heart; they hit a wall on judgment, exceptions, and multi-step reasoning. Eval and trace depth are shallow.
Horizontal no-code agent buildersRelevance AI · Lindy · Gumloop · Stack AI · Dify · Flowise/LangflowYou compose within the tool's harness with limited control of the prompt wrapper and routing; eval depth and step-level replay vary; logic lives in their canvas.
Retrieval / search layers (feed agents, don't orchestrate)Onyx (OSS) · Glean (managed)These are retrieval, not orchestration. A search layer is not an agent platform; action and orchestration live above it.
Vertical / industry-specific agentsHarvey · Hebbia · Sierra · Decagon · Writer · Clay · Intercom FinThe harness is locked: you compose within the vendor's opinions and can't control the wrapper and routing where output quality is decided.

When they're the right call at L2

When the workflow is bounded and low-stakes, a business operator should own it, the data already lives in connected SaaS, there's no hard audit or eval bar, and speed-to-validate beats control. The newer enterprise entrants (Stack AI, Sierra, Decagon) have largely closed the old governance gap, with SOC 2, RBAC, and SSO in the box, so the 2026 ceiling is harness control, eval depth, and step-level inspectability, not security.

The graduation test

Move a workflow off low-code when any one is true:

  • step-level inspection and replay are required;
  • deploys must pass trusted eval gates;
  • custom planning or decision logic (not connector breadth) is where the value sits;
  • data residency or governance needs exceed the tool's controls;
  • cost becomes unpredictable at volume; or
  • the workflow needs multi-agent coordination the tool can't express.

If the tool owns the governed foundation, wrap the locked layer rather than rebuild it.

Forward-deployed use cases

Where L2 is creating measurable value.

Support

Tier-1 deflection 25-40%

Grounded help-center bot reads the knowledge base + recent tickets. Humans inherit the long tail. Sets up the L3 graduation to ticket-resolving agents and the L4 graduation to multi-agent tier-1/2 with edge escalation.

Finance

Variance copilot

CFO draft time -60%. Copilot pulls from close package; CFO ships the narrative. Sets up the L3 graduation to AI-assisted FP&A cycle compression (10d → 2d).

Sales

Enablement Q&A

Objections, segment cuts, competitive intel: sourced, cited, fast. Sets up the L3 graduation to AI-enriched lead routing with measured conversion uplift.

Legal

Contract Q&A and review

Harvey for legal-heavy; Hebbia for diligence; Claude Skills for everyday. Sets up the L3 graduation to contract extraction at scale, feeding deal-desk risk scoring.

Internal

Enterprise search that works

Glean stitches the SaaS estate with permissions intact. The "wow" demo of L2. The graduation sign is users asking for the action, not just the answer.

Product-embedded

First in-product GenAI feature

Help-center search, in-product Q&A, summarization. Feature-flagged, per-cohort usage. The L3 graduation makes the feature the core workflow, not the side panel.

Anti-patterns

How L2 stalls.

  • "RAG-once" projects. Vector store gets built, never updated, decays in 90 days.
  • Skipping evals. No golden question set, no hallucination measurement. Confidence from demos, not data.
  • Permissioning afterthought. Index pulls in HR, salary, M&A docs. One CEO demo ends the project.
  • Buying Glean for 200 people. Wrong scale; Custom GPTs / Claude Skills would do it.
  • Treating L2 as the destination. A great Q&A bot isn't a redesigned workflow.
Graduation signals

What L3 looks like.

  • The answer isn't enough; users want the action (file the ticket, draft the email, update the CRM).
  • Repeatable multi-step work touching 3+ tools in sequence.
  • A skill heavily used enough the team wants it scheduled, not invoked.
  • Instrumented usage (completions, edits, accept rates), not just opens.
  • Willingness to give the system write access.

L3: Workflow Agents →

Edge Deploy ships L2 in 90 days.

A function-specific copilot wired to your L1 warehouse, packaged with an eval harness, governed through your hyperscaler's native AI gateway. Finance variance, sales enablement, support deflection, or marketing content: pick one, ship it, measure it.

Talk to BOD