How agencies should price consent work: fixed fee, retainer, or bundled
Consent work is awkward to price. It is too technical to give away, too invisible to sell easily, and too important to fold into a project for free. Most agencies handle this by doing the quiet thing: they configure the banner during the build, absorb the hours, and never put consent on the invoice as its own line. The client gets compliance work that nobody billed for, which means nobody maintains it.
There is a better way to think about it. Consent is not a feature. It is a liability surface with recurring maintenance. Price it like one.
Why free consent work costs you twice
The first cost is the obvious one: hours you never billed. Configuring a consent tool properly takes real work. You map the tags, categorize them, test the blocking, document the choices, and verify the banner in every region the client serves. That is a day or more of skilled time on a typical site, more on a messy one. Folded into a fixed-price build, those hours eat your margin.
The second cost is worse. Work the client never paid for is work the client never values. When consent is an invisible line inside a bigger project, nobody at the client owns it after handover. Six months later the marketing team adds tags outside the consent tool, the banner drifts, and the client calls you with a problem that is somehow your fault even though you were never paid to maintain it. Free work creates free responsibility.
The three pricing models that work
Most agencies land on one of three models, and each fits a different client relationship.
Fixed-fee setup, scoped by tag count
A fixed fee for the initial consent implementation, scoped by the number of tags and the number of regions served. Tag count is the honest scoping metric because every tag needs categorizing, blocking logic, and testing. A ten-tag marketing site and a sixty-tag ecommerce build are different jobs and should not share a price.
Scope the setup to include the deliverables, not just the configuration: the tag inventory, the category mapping, the test evidence, and the handover document. Deliverables make the fee tangible. Clients pay for things they can hold.
Consent as a retainer line
A monthly retainer for consent monitoring and maintenance. This is the model that matches reality, because consent decays. Tags change, plugins update, vendors add scripts. A retainer that covers a monthly scan, a drift report, and a fix allowance turns consent from a launch event into an ongoing service.
Retainers work best when the report is the product. A monthly one-page report, new tags found, drift fixed, banner behavior verified, is something the client can forward to their legal team. Legal teams renew retainers. Nobody renews a shrug.
Bundled into care plans
Consent maintenance bundled into an existing website care plan. If you already sell monthly maintenance, consent monitoring slots in as a line item with its own price. It raises the plan's value without raising the client's decision effort, because they already decided to pay for maintenance. They are just paying for the right maintenance.
What to charge, roughly
Numbers vary by market, but the shape is consistent. Setup fees scale with tag count and complexity: a small brochure site takes hours, a tag-heavy ecommerce site takes days. Retainers scale with scan frequency and fix allowance: a monthly automated scan with a quarterly human review is the entry tier, weekly scans with a fix SLA is the premium tier.
The mistake is pricing by tool cost. The consent platform's license is the cheapest part of the engagement. What the client buys is the mapping, the testing, and the ongoing proof. Price the expertise, not the subscription.
How to sell it without a scare pitch
Consent work sells badly when it is framed as fear. Clients tune out lectures about fines. It sells well when it is framed as operational hygiene. The pitch is simple: your site changes constantly, your banner should keep up, and we watch it so you do not have to.
Lead with the drift report, not the regulation. Show a prospect a one-page sample: three tags their current setup misses, one script firing before the banner choice. That is concrete, specific, and hard to argue with. Nobody buys a lecture. Everybody buys evidence that something on their site is already off.
Put it on the invoice
The agencies that do consent work well share one habit: consent appears on the invoice as its own line, every time. Setup is a line. Monitoring is a line. The handover document is a line. Line items create ownership, ownership creates maintenance, and maintenance is what keeps a banner honest after launch. The alternative is the quiet thing, and the quiet thing is how banners end up defending themselves with screenshots from launch day.