Anthropic

Claude's consumption-based token pricing means an agency that quotes a fixed retainer without usage caps can lose money on every heavy client, while an agency that meters usage and resells Claude Code and Cowork access at the $20 Pro or $200 Max tier builds a defensible margin layer. The real strategic stake is not model quality but who owns the client's prompt library and workflow configuration, because that asset is what makes the retainer sticky.

Claude bills by consumption, not seats: Free at $0, Pro at $20 monthly ($17 annual), and the Max plan at $200/mo for 200+ requests per minute. That structure means an agency's gross margin on any Claude-powered retainer is set by token burn, not by headcount. Picture a content agency selling the Claude Starter Content Kit at $1,800 for 16 hours of setup: the build fee is fixed, but every client chat widget reply and every regenerated social post draws on the same API meter. Before quoting a monthly retainer, log a week of real client usage, multiply by the model tier in play, and set the retainer floor above that number. Agencies that skip this step discover the leak in month three, when a chatty client's FAQ widget has quietly eaten the setup fee. Cap usage per client in the contract, then reprice annually against measured burn.

Inference Cost Pass-Through Ceiling is the point at which an agency can no longer absorb a model provider's price or latency change inside a fixed retainer, so the cost has to move to the client or the work has to shrink. The framework asks three questions per client engagement: what share of delivery cost is metered inference, how fast can that share be re-routed to a cheaper model, and what contract language lets you reprice. Forrester's 2027 predictions flag AI growth colliding with energy and infrastructure limits, which converts compute scarcity into API price movement on agency tools. A concrete case: an agency running document analysis on a frontier API can shift bulk classification to a smaller open-weight model served through Ollama or a gateway like Helicone, keeping the frontier model only for reasoning steps. That split is the ceiling defense.

Provider Substitution Window is the interval during which an agency can move a client workload from one model provider to another without rewriting prompts, evals, or integration code. The window is widest at the orchestration layer and narrowest at the fine-tuned weights layer: a gateway swap takes hours, a retrained model takes a quarter. Agencies that measure this window per client account know exactly when they hold pricing leverage and when a vendor holds it. Forrester's 2027 predictions flag compute and energy constraints pushing API pricing upward, which turns a wide substitution window into a margin defense rather than an engineering nicety. A concrete case: an agency routing Claude and GPT traffic through a gateway such as Helicone or Portkey can shift a client's summarization workload in an afternoon when one provider raises rates, while a competitor with hardcoded SDK calls absorbs the increase on a fixed retainer.

Price Claude work on metered token consumption or a hard usage cap, never on an uncapped flat retainer.

Map every AI dependency in the delivery stack to a named provider, a fallback route, and a pass-through cost clause before quoting fixed-fee client work.

IF your delivery model bills clients for AI-assisted content, code, or document analysis and you can meter token consumption per engagement, THEN start on the Free tier to prototype, move to Pro at $20/month for Claude Code and Research access, and only commit to the Max plan at $200/mo for 200+ requests per minute once concurrent client workflows demand it. IF you sell flat-rate retainers with no usage cap or pass-through clause, THEN defer Anthropic until you can price the consumption risk, because input and output token costs vary by model and cannot be white-labeled.

A five to seven day sprint that takes a client from raw Anthropic account to a live Claude-powered workflow, using the API, Slack and Microsoft 365 connectors, and a documented handoff so the agency can move straight into a retainer.