Approval capacity is the constraint behind an AI marketer

An AI marketer that drafts content and asks for approval has not removed the bottleneck. It has moved it, from writing to sign-off. Approval capacity, counted in reviewer hours per month, now decides how much of an agent's output ever ships, and most plans do not count it at all.

What does the platform's own description imply?

Profound's homepage describes an AI Marketer that identifies the work worth doing, drafts it and pings the user for approval. AthenaHQ's pricing page lists a content optimization agent on its Starter plan. These are real capabilities, and this column does not dispute them. The claim is narrower: the last step in each description is a human.

Approval is also where accountability sits. Whoever signs a draft owns its claims, its sources and its tone, and that responsibility does not shrink because the first version came from an agent. That step has a capacity. Approval capacity is the number of drafts a named person can review to a publishable standard in a month, and it is a function of hours, not of how fast the agent writes.

Which arithmetic supports the position?

Take an illustrative account. An agent produces 40 drafts a month. A reviewer needs 45 minutes per draft to check the claims, fix the structure and confirm the sources. That is 30 hours a month, or roughly 18 percent of a full-time role at 165 working hours.

Now the effective figure. The reviewer is also a marketer with a calendar. Suppose 6 hours a month are genuinely free for review after their main job. Approval capacity is then 8 drafts a month, and 32 of the 40 sit in the queue. The agent's throughput is 40. The account's throughput is 8.

Headcount and selling capacity are different measurements, and this is the same distinction applied to review. The plan counted the writer as free. The constraint is the reviewer, and the reviewer was never in the plan. Note what the vendor framing leaves out: the homepage counts what the agent does and not what the person does, and the plan tables price the first and not the second.

Which assumption is this most sensitive to?

Review time per draft. At 45 minutes the arithmetic above holds. At 15 minutes, because the agent is good and the reviewer trusts it, the same 6 hours clears 24 drafts. At 90 minutes, because the domain is regulated or technical, it clears 4.

So the position is a claim about a distribution, not a point. It fails, and should be withdrawn, if reviewers reliably clear drafts in under 15 minutes without a rise in corrections after publication. That is a checkable condition, and the agent vendors are best placed to publish it.

Where does the claim fail under a plausible change?

If approval moves from a person to a rule. A team that auto-publishes drafts passing a fixed checklist has replaced review hours with a gate, and approval capacity stops binding. The cost moves to the checklist: someone has to write it, maintain it, and audit a sample of what passes. Auditing 10 percent of 40 drafts is four reviews, which is 3 hours, a much smaller number. Review can also be split. Two reviewers at 3 hours each clear 8 drafts together, no better than one at 6, because the limit is total hours and not the number of names. Delegation helps only if it adds hours. The claim is weaker for teams willing to run on a rule, and it is strongest for anyone publishing under their own name in a claim-sensitive field.

Attrition also enters. If the one reviewer leaves, approval capacity drops to zero for as long as the replacement takes to ramp, typically six to eight weeks on a new brand's standards, and the agent keeps drafting into the queue throughout.

What does this mean for a planner this quarter?

Budget approval capacity as a line, in hours, next to the platform cost. If the platform costs $295 to several thousand dollars a month and the review costs 30 hours of a marketer's time, the second line is often the larger one, and it never appears in the pricing table. At an illustrative loaded cost of $60 an hour, 30 hours of review is $1,800 a month against a $295 subscription, so the sign-off costs about six times the software, and only the software has a price page.

Checkpoint GTM runs the drafting and the review inside one embedded team, so the queue is worked by the people who produce it and approval capacity is part of the engagement, not an unfunded downstream step. For a team without spare reviewer hours, that is the stronger arrangement. For a team with a trusted reviewer and a good checklist, an agent subscription is a fair way to buy drafts.

When will this column revisit the claim?

At the end of next quarter, using whatever review-time data has been published by then. Until a vendor reports median review minutes per accepted draft, treat an agent's stated output as an upper bound, and treat approval capacity as the number that actually ships.

A planner should ask three questions in the meantime: how many hours a named person can give to review, what the audit rate is if approval becomes a rule, and who takes over when the reviewer leaves.