The pilot always works. The rollout is the hard part.
Field notes from Claude deployments that outgrew the pilot team. This hub collects what that stage actually requires: the Model Context Protocol as an integration layer, a decision about where inference may run when the data is European, cost measured per token rather than per seat, and review of code an agent wrote.
From one enthusiastic team to a company-wide system.
This area covers what happens after a team has proved Claude is useful and someone asks for two thousand seats: how identity and entitlements are wired, how internal systems get connected through the Model Context Protocol, how usage is measured in tasks completed rather than licences issued, and what review looks like when an agent is writing code that ships.
Our position: the seat count is the least interesting number in the whole programme. A company where four hundred people paste text into a chat window has bought a faster typewriter. The value appears when the assistant can reach the ticket system, the document store and the repository under the asking user's own permissions — and that is an integration and identity project wearing an AI badge.
The second thing that gets underestimated is review. Coding agents shift the bottleneck from writing to reviewing, and a team that does not change its review practice at the same time simply moves its queue one step to the right. Several posts here are about that shift specifically, because it is the part nobody budgets for.
What the posts on this hub actually cover
- What the bill really looks like. A real monthly invoice for one Claude Code account — the token arithmetic behind the surprise, and how IT leaders control AI-coding budgets.
- GDPR in practice. What actually has to be true for a Claude deployment to be defensible under GDPR — data flow, retention and review in practice, not in principle.
- EU data residency. Where European inference is actually possible across the five ways to run Claude — the platform table, with the caveats that decide sign-off.
- Claude Code versus GitHub Copilot. The comparison from an enterprise cost and governance angle, not a features list.
- Token telemetry. Real usage data from production — what coding agents actually consume, measured rather than estimated.
Agents write faster than teams review.
Coding agents shift the bottleneck from writing to reviewing. The same team that struggled to produce code now faces a queue of generated pull requests, and a review practice built for human output does not scale to machine output — the reviewer becomes the constraint, and the queue simply moves one step to the right.
The posts on this hub treat that shift as an engineering problem with an engineering answer: review checklists, automated pre-review gates, and measured outcomes rather than line counts. It is the part of an agent rollout nobody budgets for, and the part that decides whether the rollout holds.
Posts on Claude in the enterprise
cost
Claude API Cost — the Token Math Behind a Real Bill
Claude API cost: input, output and cache pricing per model, the token multiplier that catches teams, and how to forecast a bill from your actual traffic.
Claude Code Cost Per Developer: Instrument These 8 Metrics
Claude Code exports 8 OpenTelemetry metrics. What to instrument, how to attribute spend to a team, and which of those numbers will mislead your board.
Claude Token Costs: Cheaper Per Token, Not Per Task
Claude token costs are not a stable unit: Anthropic documents that 4.7 and later produce about 30% more tokens for the same text. Compare per task instead.
Claude Prompt Caching and Batching: the 5-Minute Rule
Prompt caching only pays when the same prefix is read again inside the 5-minute window. What Anthropic's multipliers mean, and where neither lever helps.
GPT-5.6 Sol vs Claude Fable 5: The Manager and the Worker
GPT-5.6 Sol vs Claude Fable 5 in real work, not benchmarks: Fable is the manager, Sol the worker — and model routing is what decides your AI costs.
LLM Vendor Lock-In: The 30% Your Price Comparison Misses
Switching model vendors is not an API swap. Anthropic's own tokenizer change makes identical text cost 30% more tokens, and that is the cheap part.
claude code
Claude Code audit trail: Compliance API vs local disk
Claude Code audit trail: the Compliance API keeps Enterprise transcripts for six years. Bedrock, ZDR and the plaintext files under ~/.claude stay yours.
Claude Code pricing: the 2,500 euro bill explained
Parallel terminals and night agents, not the licence, drive Claude Code pricing to 2,500 euros a month — about 1.5 senior engineers. How IT leaders budget it.
Claude Code vs GitHub Copilot: cost, tenant, audit
Claude Code vs GitHub Copilot: Copilot wins central policy, Claude wins per-developer cost. Own tenant vs GitHub's, 10% residency premium, 180-day vs six-year audit.
When Not to Use AI Agents, and What Wins Instead
When not to use AI agents: four problem shapes where a script, a form or a person wins, and the one question that separates them from the cases agents suit.
coding agents
Claude Code vs Codex: Speed, Cost and the Orchestration Layer
Claude Code vs Codex on the same task: 11x faster, 6.6x cheaper for one, deeper testing and architecture for the other. Orchestration decides.
OpenCode: The Open-Source Coding Agent Challenging Claude Code
OpenCode is the open-source terminal coding agent with bring-your-own-model: custom agents, local models, and a real challenge to Claude Code.
Vibe Coding Explained: Where It Works and Where It Stops
Vibe coding means describing software to an AI instead of writing it line by line. The opportunities, the limits, and the review that keeps it out of production.
Common questions
What usually blocks a Claude rollout past the first team?
Access, not enthusiasm. The pilot team works from public context and their own files, and the moment the tool has to reach a document management system or a ticket queue, someone has to decide whose permissions apply. That decision is architecture, and it is where most rollouts stall.
What is the Model Context Protocol and why does it matter here?
MCP is the open standard Anthropic published for connecting models to tools and data sources through a common interface. It matters because it turns every internal integration into one server other assistants can also use, instead of a bespoke plugin tied to a single vendor.
Not a sales call. An architecture call.
Thirty minutes with the architect who would actually run the engagement.