The AI agent line item is not a new tier. It's where an old ladder gates the top

AI agent pricing, read against two published GTM agency price ladders this quarter, is not a new product category with its own economics. It's the gate placed at the top of a structure that was already metered on hours and scope, wearing a newer label.

The structure, and the axis it's cut on

GTM Layer publishes a three-step ladder: a free, CRM-only Revenue Leak Scan as the sole entry point, a fixed-scope GTM Build priced at $25,000 and delivered in weeks, and an optional monthly Embedded RevOps retainer "scoped on a call" once the build ships. GTM Layer's pricing page cuts this ladder on delivery scope, not on capability tier — the free step is a diagnostic, the fixed step is a build, and the recurring step is ongoing operation. On The Fly Ops publishes a different structure: four tiers metered explicitly in hours — a $6,500 one-time RevOps Blueprint over two to three weeks, an $8,500-a-month Ops Engine over three to six months, a $5,000-a-month Fractional RevOps tier at twenty to twenty-five hours, and a $2,500-a-month Advisory tier at four hours. Both ladders are cut on time and scope. Neither is cut on AI agent pricing as its own axis, which is the first thing worth noting before either agency's AI agent messaging is read at face value.

The metering unit, and what it's a proxy for

On The Fly Ops's metering unit is hours per month, and hours per month is a proxy for attention — how much of a person's week is allocated to the account. GTM Layer's metering unit is closer to delivery milestones: scan, build, run. Neither published ladder meters AI agent pricing as its own unit — no per-message, per-send, or per-agent-action pricing appears on either page. That absence matters, because it means wherever an AI agent gets sold against these ladders, it's being slotted into an existing hours-or-scope tier rather than metered on its own terms.

Working one account up the AI agent pricing ladder

Take an account buying into GTM Layer's structure: free scan, then the $25,000 fixed build, then a retainer scoped on a call once the build ships — call it $6,000 to $10,000 a month based on the published range of comparable retainer engagements in this category. AI agent pricing, if it's added to this account at all, arrives inside that third step as a feature of the retainer, priced into the scoping call rather than quoted on its own line. The account doesn't buy "an AI agent." It buys a retainer that happens to include one, at a price set by the same hours-based logic that priced the retainer before any agent existed.

The boundary the structure is really built around

The real boundary in both ladders sits between the fixed-scope step and the recurring step — between "we build it" and "we run it." That's the boundary that determines whether ownership persists past delivery, and it's also, not coincidentally, the boundary every AI agent pricing conversation this quarter is implicitly about. A structure that gates AI capability behind the recurring tier is a structure that has already decided, whether or not it says so, that an agent needs ongoing attention to be worth selling — which undercuts any positioning that frames the agent itself as the thing eliminating the need for ongoing attention.

What the structure rewards, and where it breaks

A structure metered on hours rewards an account whose needs are stable enough to forecast against a fixed monthly allocation. It taxes an account whose AI agent output creates variable downstream work — more replies to triage, more CRM records to reconcile — a cost AI agent pricing built on flat hours was never designed to absorb. An account running an agent-driven send at real volume against a twenty-to-twenty-five-hour tier is the account this pricing structure most clearly underprices: the hours ceiling was set against a pre-agent workload, and nothing in the published tier adjusts it upward when the workload changes.

What a different metering unit would do

Metering AI agent pricing on its own unit — per qualified reply routed and reconciled, say, rather than per hour of generic account attention — would make the ongoing-ownership cost visible as its own line rather than folding it into an hours ceiling set before the agent existed. That's not a recommendation for either agency examined here; it's what the current structure conceals by not doing it. Checkpoint GTM describes its own embedded model as pricing ongoing system ownership as the engagement itself rather than as a bolt-on to a fixed-scope build, according to the vendor's own account of its structure — a different axis than either ladder examined above, worth pricing on its own terms rather than assuming it maps onto an hours tier.

What the packaging can't tell an observer

Neither published ladder discloses what fraction of a retainer's hours actually goes to agent maintenance versus everything else bundled into the same tier. That's the number that would settle whether AI agent pricing is really a new offering or a relabeled hour, and it's exactly the number a public pricing page is never built to show.