Grok

Foundation model platforms have shifted from a technical procurement question to a delivery economics question: the same client retainer now buys wildly different output depending on which model tier, context window, and retention terms an agency routes work through. Agencies that map deliverable types to model tiers and track token spend per account protect margin; those that default to one frontier model absorb cost variance they never bill for.

Model routing discipline treats model selection as a per-task decision rather than a per-agency default. Foundation model platforms price per million tokens and cap context per tier, so a retainer that runs every job through a frontier model burns margin on work a smaller tier handles at a fraction of the cost. The discipline has three moves: inventory the deliverable types an agency produces, assign each to the cheapest tier that clears the quality bar, then re-test quarterly as new releases land. OpenAI's October 2, 2026 guide splits the GPT-6 family into three variants for prototyping, feature development, and multi-step orchestration, which is exactly the tiering decision agencies now have to make explicit. Teams that route by task keep delivery costs predictable across client accounts; teams that route by habit pay frontier prices for draft work.

Context Window Economics treats a model's maximum context length as a pricing variable rather than a feature checkbox. A 200K-token window lets an agency feed an entire client brand guide, three years of support tickets, and a product catalog into one call, which removes retrieval plumbing but multiplies input-token spend on every run. The framework asks two questions before any build: how many tokens does the average client deliverable actually consume, and does that volume justify a long-context model or a cheaper short-context model plus a retrieval layer? Prime Intellect's October 2026 launch of serverless and reserved serving for frontier open models gives agencies a third lever, since reserved capacity can cap the per-token rate on high-volume retainer work. Run the math per deliverable, not per token, and long-context defaults stop quietly eroding project margin.

Retention Clause Exposure treats data-retention terms as a contract-level constraint, not a procurement footnote. Foundation model platforms differ on whether prompts and outputs are stored, for how long, and whether they train future models, so the same client deliverable can carry very different liability depending on which platform serves it. Agencies feel this first in regulated verticals: a retainer for a financial-services client can be voided by a single clause the delivery team never read. Forrester's 2026 Consumer Benchmark Survey found nearly nine in ten US and UK adults have heard of AI, yet a trust gap persists in financial services, which means clients will ask harder questions about where their data sits. The practical move is to map every active client contract against the retention terms of each platform in the delivery stack, then route sensitive work to platforms with private deployment options such as Cohere's VPC and on-premises model hosting.

Pick the model tier by mapping each recurring client deliverable to a tested tier, then verify the choice against your own eval set before it touches a retainer.

IF your agency can wrap a pre-built AI agent into a client's existing CRM, calendar, and review cycle with minimal configuration, THEN treat the agent as a component and price the wiring as a retainer. IF the agent is deployed as a standalone product without deep integration, THEN you are selling a commodity and will compete on price alone.

A fixed-scope deployment that puts a pre-built agent in front of inbound leads, support tickets, or document queues, then wires its output into the client's CRM, calendar, and review cycle. Priced as a setup fee plus a monthly retainer for monitoring and tuning.