--- title: "Benedict Evans’ 2025 AI Deck — What It Actually Means for Enterprises - In Parallel" description: "Benedict Evans, former Andreessen Horowitz partner and now an independent analyst, has spent 20 years studying how tech platforms become businesses. His 2025 AI deck isn’t about model benchmarks but about workflows, margins, and where incumbents slip. The takeaway: LLMs aren’t “another app” but a way to remove steps across existing systems." url: https://www.in-parallel.com/insight/benedict-evans-2025-ai-deck-what-it-actually-means-for-enterprises --- AI in Business # Benedict Evans’ 2025 AI Deck — What It Actually Means for Enterprises AI won’t replace your company. It will remove steps between the 4–500 apps you already use. Benedict Evans’ 2025 AI Deck — What It Actually Means for Enterprises Published November 25, 2025 Kristian Luoma Co-founder, CPO kristian@in-parallel.com [LinkedIn](https://www.linkedin.com/in/kluoma/) Contents ### **Why Listen to Benedict Evans?** Evans argues that AI’s value comes from removing steps across existing enterprise workflows, not adding new apps. Companies that invest now in narrow, measurable automations will build the capabilities and data advantage others will lack later. Read the full report [here](https://www.ben-evans.com/presentations). ### **New Platforms, Fewer Steps** Mainframes → PCs → SaaS exploded the number of apps. AI flips the question from “what new app do we build?” to “what step can we remove?” For enterprises, that means: - **Treat LLMs as cross-app operators** Read → reason → validate → write → log, across tools. - **Aim at swivel-chair work** Any task that forces humans to copy/paste between CRM, ITSM, ERP, email, spreadsheets. - **Own the interface, swap the brains** Keep models interchangeable behind one orchestration layer you control. - **Make knowledge a versioned asset** Version your corpora, scope retrieval tightly, and require the system to either cite its sources or refuse. ### **Invest Now (Even If You “Pre-Build”)** Evans’ implicit warning to large companies: **waiting is also a strategy—just usually a bad one.** How to read this as a corporate policy: - **Waiting taxes you twice** You lose automation gains now _and_ arrive late to the learning curve (guardrails, metrics, playbooks). - **Early investment pre-builds capability** Even if you expect another model wave in 12–24 months, you’re banking: **Fund AI like strategy, not as a demo budget** Treat AI as a multi-year capability bet (like CRM or cloud), not a stack of pilots chasing headlines. ### **Why Usage Still Lags** Evans points out a puzzle: consumer and enterprise AI both show massive top-of-funnel curiosity, but shallow habit. Why corporate rollouts stall: - **Chat-first UX** Great for a conference demo; weak for repeatable daily work. People don’t wake up wanting “chat”—they want “this ticket closed faster.” - **Metric theater** Tokens, prompts, and “active users” don’t move the board. CFOs care about cycle time, error rates, and cost per resolved task. - **Shadow knowledge** Dumping “all our docs” into retrieval leads to leaks, hallucinations, and compliance headaches. - **Vendor glue risk** Over-coupling to a single stack makes every model upgrade a breaking change project. If you don’t design for habit and governance from day one, AI remains a sideshow. ### **From Experiments to Daily Work** **Principle:** make the safe path the fast path. **1) Ship skinny, production-grade flows** - Pick one narrow job. - Use deterministic retrieval and strict validators before write-back. - Log every query, response, decision, and override. If confidence is low or the blast radius is high, the system should refuse and escalate with evidence. **2) Instrument like a growth team** Track metrics that matter to executives: - Time-to-first-answer - % of answers grounded in approved sources - Human edit rate - Deflection rate + CSAT for support - SLA adherence - Cost per resolved task Publish weekly deltas. Kill or rework flows that don’t pay their way. **3) Assemble, don’t over-platform** Your stack should separate concerns: - **Orchestration & policy (your code):** tools, routing, approvals, rate limits. - **Pluggable cognition:** at least two external model providers + one local/edge path. - **Authoritative context:** versioned corpora, scoped retrieval, per-field provenance. - **Validation:** schema checks, reference matching, policy enforcement. You’re building a control plane for intelligence, not another monolith. **4) Aim at high-leverage loops** Start where Evans’ “platform shift” logic bites hardest: repeating, information-heavy workflows with clear truth. Examples: - **Support** Classify → retrieve → draft → validate entitlements → escalate with cited evidence. - **CRM & sales ops** Summarize calls, extract next steps, update fields, draft follow-ups for approval. - **Finance operations** Parse invoices, run 3-way match, flag variances with plain-language explanations. - **Engineering** PR summaries, test scaffolds, incident timelines, runbook suggestions. **Policy & compliance** Cited answers, exception flags, full audit trails for every AI-assisted action. ### **What to Build in 90 Days** You don’t need a “five-year AI vision deck.” You need one credible 90-day plan. **Weeks 1–2: Choose and baseline** - Pick **one revenue** surface and **one cost** surface with: - Baseline: **Weeks 3–6: Ship the skinny version** - Constrain sources aggressively; add validators before anything touches core systems. - Roll to 10–50 real users. - Capture human edits as training and evaluation signals. **Weeks 7–10: Stabilize and prove ROI** - Cut variance; tighten retrieval scopes; cap context window size. - Cache frequent queries. - Share weekly cycle-time, accuracy, and error reductions with leadership. **Weeks 11–13: Productize** - Replace chat with one-click actions inside existing tools (ticket sidebar, CRM panel, email plug-in). - Add admin controls for scopes, thresholds, approvals, and audits. - Run your first controlled model upgrade and document the impact end-to-end. ### **The Takeaway** Evans’ decks are a pattern: he shows that platforms win by **changing how work gets done**, not by adding more screens. Translate that to AI: - **LLMs are workflow compressors** , not another department. - Use them to remove steps across your SaaS estate—not to create a new island. - Measure behavior change and business outcomes, not tokens. - Quietly stack “boring” advantages: scoped knowledge, evals, guardrails, and model optionality. The companies that start now won’t just have better tooling in three years. They’ll have better workflows, cleaner data, and an organisation that already knows how to ship AI safely—while everyone else is still rewriting their first pilot. ## References [https://www.ben-evans.com/presentations](https://www.ben-evans.com/presentations) ### Get insights like this in your inbox One email per week on execution intelligence, team coordination, and enterprise AI. No fluff. By subscribing you agree to our [Privacy Policy](https://www.in-parallel.com/privacy-policy). Unsubscribe anytime. [Back to all insights](https://www.in-parallel.com/insight) [Book a demo](https://www.in-parallel.com/demo) ## Related articles The Coordination Tax — Richard H. Carson on how change actually works Leadership Insights · Oct 20, 2026 ### You Either Manage Change or It Manages You: Richard H. Carson on how change actually works Richard H. Carson, PhD — 40 years inside county governments, regional planning agencies, nonprofits, and the state of Oregon — on why every organization has a risk manager but almost none has a change manager, and what that asymmetry costs. A rope suspension bridge over a dark river towards the fells, drawn in pen and watercolour AI in Business · Oct 9, 2026 ### AI-Assisted or AI-Native: The Bridge Is Shared Context At a CIO data event in Espoo, HumanX in Amsterdam and a post-merger integration forum, large companies explained how they brought AI in by mapping processes and fitting AI into the gaps. That keeps a structure built around human limits. Getting to AI-native means rebuilding information flows into shared context first. The Coordination Tax — Adam Christing on humor as leadership Leadership Insights · Oct 7, 2026 ### You Can't Fix Culture With a Mission Statement: Adam Christing on humor as leadership Adam Christing — professional master of ceremonies, founder of Clean Comedians, and author of The Laughter Factor — on why culture is a feeling rather than a statement, and why humor is the fastest way for a leader to shift it. The Coordination Tax — Jennifer Recla on the urgency mindset breaking your team Leadership Insights · Sep 22, 2026 ### Urgency Isn't Leadership. It's Addiction: Jennifer Recla on the mindset breaking your team Jennifer Recla — leadership coach who has worked with hundreds of leaders across nonprofits, mission-driven organizations, and large financial institutions — on the urgency mindset behind most organizational chaos, and why most leaders have no idea how much of it they're creating themselves. The Coordination Tax — Barry Wolfe on value-centric leadership Leadership Insights · Sep 15, 2026 ### HR Is the Last Line of Defense Against Chaos: Barry Wolfe on value-centric leadership Barry Wolfe — HR consultant, founder of Argos HR, and author of It's All in Your Head — on why HR is the last line of defense against organizational chaos, why every role needs 3–5 clear value outcomes, and why the foundation of a well-run company is one document under 300 words. Two colleagues sharing one open binder — context handed over at the resolution the other person needs Leadership Insights · Sep 9, 2026 ### Your Job Is Already Context Management On The Coordination Tax, Stanford's Robert E. Siegel put it as an equation: truth equals facts plus context. Facts are cheap now. Context is not. Read the manager's week against that equation and the 16.5 hours a week lost to coordination stop looking like overhead — they are context management, performed manually, by the most expensive person in the room. The Coordination Tax — Alberto Torres on surviving disruption Leadership Insights · Sep 8, 2026 ### You Can't Sword-Fight a Bullet: Alberto Torres on surviving disruption Alberto Torres — former Nokia executive, ex-McKinsey partner, and author of The Z Curve — on what actually happened at Nokia, why great peace-time leaders quietly fail in war-time, and what every company facing AI right now should learn from the companies that got disruption right. The Coordination Tax — Olivia Montgomery on why decisions belong lower in the org Leadership Insights · Sep 1, 2026 ### Your Leadership Doesn't Know What's Going On: Olivia Montgomery on why decisions belong lower in the org Olivia Montgomery — principal analyst at Data Frame and former Gartner researcher — on why every layer up the org chart knows less about what's really going on, and why the fix isn't more visibility for leadership but pushing decisions down two or three levels. The Coordination Tax — Craig Denison on the founder's hardest transition Leadership Insights · Aug 25, 2026 ### You Don't Get to Be the Rock Star Anymore: Craig Denison on the founder's hardest transition Craig Denison — head of growth at The Table Group (Patrick Lencioni's firm) and founder of Green Thumb Consulting — on the transition every founder hits when execution stops running through their brain, and why 99% of the time the founder is creating the dysfunction they are trying to fix. A manager mid-explanation, watch visible — the hour spent re-explaining context AI in Business · Aug 24, 2026 ### AI Saves a Day a Week. The Coordination Tax Collects It. BCG's fourth AI at Work survey found 42% of regular frontline AI users save at least a full workday every week, and that two-thirds get little or no guidance on what to do with it. The usual reading is that leaders forgot to give direction. The better reading is that the hours were already spoken for. AI compresses the work; it doesn't touch the work about the work.