← All field guides

A BlueAlly Field Guide

Six patterns.
Most of the value.

Enterprise AI looks endless. It is not. Nearly every project that earns its keep is one of a few recurring patterns — or a small stack of them. Name them, and the map gets simple. Here is the map.

Conquer Complexity

Six patterns. Most of the enterprise value. Assistant Knowledge Extraction Workflow Summarize Classify Five workhorses, plus the workflow that strings them together.

What's inside

01  The thesis

A short list runs most of the enterprise.

Walk a trade-show floor and AI looks like a thousand products. Walk a balance sheet and it looks like a handful of jobs done well. In 2025, companies spent $37 billion on generative AI — more than triple the year before.1 Almost all of that money chases the same few shapes of work.

We call those shapes patterns. A pattern is a repeatable way to point a model at a problem: what goes in, what the model does, what comes out, and what has to be true for it to be safe. Six cover most of the value. Learn them and the buying decisions get simpler — because you stop asking "which tool?" and start asking "which pattern, and is this the place for it?"

In plain English

A pattern is a recipe, not a product

Vendors sell features. Patterns describe the underlying recipe those features cook from. The same six recipes show up under a hundred brand names. Know the recipe and you can judge any product on the menu.

Model
A program that predicts text. Give it words; it returns the words that should come next. Every pattern below is a way to aim that one trick at real work.
Pattern
A repeatable shape of AI work — inputs, what the model does, outputs, and the guardrails. The unit you should actually plan around.
Grounding
Feeding the model your real documents or data at the moment it answers, so it speaks from evidence instead of memory.
Agent
A model that works in a loop — plan, act, observe, decide — calling tools until a job is done, not just answering once.6
$37B
Enterprise spend on generative AI in 2025 — a 3.2× jump in one year. The patterns below are where it went.1
72%
Of organizations now use generative AI in at least one business function. Adoption is the rule, not the experiment.2
76%
Of AI use cases are bought, not built. The recipes are the same — most teams buy the kitchen.1

So what: the field is wide, the playbook is short. The rest of this page is the playbook.

02  The six patterns

Six patterns, at a glance.

Five are workhorses you can deploy on their own. The sixth — the agentic workflow — is the conductor that strings the others into multi-step work. Each tile gives you the shape, the typical payback, the time to value, and the main risk. Numbers are typical ranges from the field, not promises.

Show patterns that fit:
Conversational assistant & copilot
Typical ROIHigh · broad
Time to valueWeeks
Main riskWrong-but-fluent
RAG knowledge assistant
Typical ROIHigh
Time to valueWeeks–1 qtr
Main riskRetrieval misses
Document extraction & processing
Typical ROIHigh · fast
Time to valueWeeks
Main riskSilent errors
Classification & routing
Typical ROIHigh · cheap
Time to valueDays–weeks
Main riskEdge cases
Summarization
Typical ROIMedium–high
Time to valueDays–weeks
Main riskDropped nuance
Agentic workflow
Typical ROIHighest · hardest
Time to value1–2 qtrs
Main riskCompounding errors

Tap a filter to dim the patterns that do not fit a given setting. ROI and timing are typical field ranges, not guarantees.

03  Pattern × function

Where each pattern pays off.

The same six patterns land differently across the business. A dark cell means a strong, common fit — a place where this pattern earns its keep again and again. A pale cell means it can work, but it is not the first place to look. Read down a column to staff a function. Read across a row to see a pattern's reach.

Fit of each pattern across eight functions Darker = stronger, more common fit. Pale = possible, but not the obvious first move. Customerservice Sales &marketing Software& IT Finance &accounting Legal &compliance HR &people Operations& supply Healthcare& clinical Assistant & copilot RAG knowledge Extraction Classification & routing Summarization Agentic workflow Fit: possible good strong & common RAG and the agentic workflow have the widest reach. Extraction and classification run deep but narrow. Illustrative fit ratings from BlueAlly delivery experience, consistent with 2025 enterprise adoption data.
Fig. 1 — The pattern × function heat grid. The signature view of this dashboard. Strong cells cluster where the work is text-heavy and repeatable — service, IT, finance, legal, healthcare. Use it to decide which pattern to reach for in any corner of the business.

So what: pick the function, follow the column, and the first one or two patterns to pilot light up on their own.

04  Value × readiness

High value. High readiness. Start there.

Score each pattern two ways: how much value it returns, and how ready you are to run it. Plot the six and a sequence appears. The top-right corner — high value, high readiness — holds your Champions: fund them first. The top-left holds Strategic bets worth a sprint to make ready. Quick Wins sit bottom-right, fast and modest. Build the ready wins, then close the readiness gaps.

Strategic readiness gap · plan a sprint Champions high value · ready · deploy now Foundation low value · low readiness · build first Quick Wins modest value · ready · ship fast Readiness (feasibility) — data, governance, integration in place → Value (business impact) ↑ low high Agenticworkflow RAGknowledge Assistant/ copilot Extrac-tion Classify Summa-rize a sensible sequence: deploy the Champions, then fund the Strategic bet Bubble size hints at breadth of fit across functions. Positions are illustrative, drawn from BlueAlly delivery experience.
Fig. 2 — Value against readiness, with a path. Classification, extraction, summarization, and the assistant are Champions — high value and ready to ship. RAG and the agentic workflow are Strategic: the value is real, but the readiness gap asks for a sprint. The dotted arc is the order most teams should follow.
Deploy the Champions first.

Classification, extraction, summarization, and the assistant are high value and ready — little new plumbing, payback in weeks. They also build the muscle, and the trust, you will need for the harder work.

Fund one Strategic bet.

RAG and the agentic workflow are where compounding value lives, but the readiness gap asks for grounding, tools, guardrails, and patience. Sponsor a 90-day sprint on one high-value process — do it properly, not ten halfway.

05  The full comparison

One table, six patterns, five questions.

For each pattern: what it does in one line, the data it needs, where it pays off, and the watch-out that bites teams who skip the homework. This is the reference you keep open during a planning session.

Pattern What it does Data it needs Where it pays Watch-out
Conversational assistant & copilot Answers and drafts in plain language, in the flow of work — chat, email, a sidebar in the app a person already uses. A clear scope and good prompts. Grounding in your content if answers must be specific. Service desks, sales, IT help, employee self-service. Coding copilots are the single largest category of AI spend.1 Fluent and wrong. Without grounding it will guess. Scope it, ground it, and keep a human on consequential replies.
RAG knowledge assistant Finds the right passages in your own documents and answers from them, with citations. An open-book exam.5 A corpus you can index — policies, contracts, tickets, wikis — kept fresh and permissioned. Anywhere truth lives in documents: support, legal, finance, clinical reference, internal search. Bad retrieval means a confident answer from the wrong page. Chunking and search quality decide everything.
Document extraction & processing Pulls structured fields from messy documents — invoices, claims, forms — into clean rows a system can use. Sample documents and a target schema. Labeled examples sharpen accuracy. Finance, operations, insurance, healthcare intake. 80–90% of enterprise data is unstructured and waiting.7 Errors are silent — a wrong number looks like a right one. Confidence thresholds and human review on low scores are not optional.
Classification & routing Sorts each item into a category and sends it the right way — tag this ticket, route this email, flag this case. A label set and examples per label. The cleaner the categories, the better. Service triage, content moderation, lead scoring, alert routing. Cheap, fast, and everywhere. Rare and ambiguous cases. Define an "unsure" bucket that escalates to a person instead of guessing.
Summarization Compresses long material into a short, faithful version — a call, a thread, a report, a day of news. The source text. Clear instructions on length, audience, and what must never be dropped. Meetings, research, support history, executive briefings, anywhere people drown in reading. It can drop the one detail that mattered or smooth over a caveat. Keep the source one click away.
Agentic workflow Works a multi-step job in a loop — plans, calls tools, reads results, decides what is next — until done.6 The other patterns as parts, plus tools (via MCP), grounding, guardrails, and a way to watch it.8 End-to-end processes: renewals, reconciliations, research-and-act. The highest ceiling of the six. Small errors compound across steps. Only ~16% of deployments are true agents today — earn the loop, don't assume it.1

Read a row to scope a pattern. Read the watch-out column first if you are deciding what to pilot.

06  Composition

Most real systems are a stack.

The patterns are clean on paper. In production they combine. A contract-renewal assistant is not one pattern — it is four, working together, with the agentic loop conducting. This is why the sixth pattern matters out of proportion to its adoption: it is the glue.

One job: "Brief me on the March contract renewals at risk." Agentic workflow — plans the steps, calls each pattern, checks the result, decides what is next 1 · Classify Is this a renewal, a claim, or a complaint? → route to renewals 2 · RAG knowledge Find renewal clauses and churn signals → cited evidence 3 · Extraction Pull dates, values, parties into a table → clean rows 4 · Summarize Write the one-page brief for a human → the deliverable "Six renewals. Two at risk. The top account, $3.4M — three open escalations." Cited, drafted, and waiting for a human to approve.
Fig. 3 — Four patterns, one workflow. The agentic loop does not replace the workhorses — it orchestrates them. This is why a leader should plan in patterns, then expect to compose them. Most value comes from the stack, not any single layer.
Plan in patterns. Ship in stacks.

Two lessons fall out of this. First, the workhorses are worth deploying alone — a good classifier or a clean extractor pays for itself. Second, the big prizes come from composing them under an agentic loop, with grounding for meaning and tools for truth. The architecture behind that loop has its own field guide.8

07  Using the dashboard

How to read this, on a Monday.

A dashboard earns its place when it changes a decision. Here is how to turn these six patterns into a plan you can defend — and a few honest cautions about the numbers everyone quotes.

1
Start from the function.

Pick the part of the business with the most expensive reading and writing. Run down its column in the heat grid. The strong cells are your shortlist.

2
Sequence by value and readiness.

From the shortlist, deploy the Champions first — classify, extract, summarize. Save the Strategic bets, like the agentic workflow, for a 90-day sprint that closes the readiness gap.

3
Buy the pattern, not the logo.

76% of use cases are bought.1 Judge each vendor by which pattern it really runs and how it handles that pattern's watch-out.

An honest word on the numbers

Survey figures here come from different studies with different methods. McKinsey reports 23% of organizations scaling an agentic system and another 39% experimenting.2 Menlo finds only 16% of deployments are "true agents."1 Both are right — they count different things. Patterns also overlap: a single product can be classification and RAG and a copilot at once. And "agent" gets stretched to cover plain chatbots — what some call "agent washing." Treat the ranges as direction, not decimals. The shape of the map is solid. The exact coordinates move every quarter.

The patterns are stable. The market is loud. Plan to the patterns.

08  Sources

Where this comes from

Market figures come from the named 2025 enterprise surveys; mechanisms come from primary papers and official documentation. Fit ratings, ROI bands, and plot positions are illustrative, drawn from BlueAlly delivery experience and consistent with the cited data. Specific dollar figures in the diagrams are examples.

  1. Menlo Ventures, "2025: The State of Generative AI in the Enterprise" ($37B spend; coding 55% of departmental AI; 76% buy vs. build; ~16% true agents). menlovc.com/perspective/2025-the-state-of-generative-ai-in-the-enterprise
  2. McKinsey & Company, "The State of AI: Global Survey 2025" (72% adoption; 23% scaling agentic, 39% experimenting). mckinsey.com/quantumblack/our-insights/the-state-of-ai
  3. Andreessen Horowitz, "How 100 Enterprise CIOs Are Building and Buying Gen AI in 2025" (model choice by use case; 37% run 5+ models). a16z.com/ai-enterprise-2025
  4. Vaswani et al., "Attention Is All You Need," arXiv:1706.03762 (the transformer behind every pattern here). arxiv.org/abs/1706.03762
  5. Lewis et al., "Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks," arXiv:2005.11401. arxiv.org/abs/2005.11401
  6. Anthropic, "Building Effective Agents" (the plan–act–observe loop). anthropic.com/research/building-effective-agents
  7. Gartner / IDC, as reported — 80–90% of enterprise data is unstructured. idc.com · gartner.com glossary
  8. Anthropic, "Introducing the Model Context Protocol" (open standard, Nov 2024; how agents reach tools). anthropic.com/news/model-context-protocol