The consent pre-sales audit: what to check before you quote the project

Published 2026-10-11

Most consent projects go wrong before the contract is signed. The agency quotes based on the client's description of their tracking, which is invariably "just Google Analytics and a couple of pixels," and then discovers forty vendors, three tag managers, and a marketing team that adds tools without telling anyone. A pre-sales audit, a lightweight technical look before you price the work, is the difference between a profitable engagement and a fixed-fee trap.

Scan first, quote second

Before any numbers leave your office, run your own scan of the prospect's site. Not a sales demo, a real crawl: homepage plus key templates, with a clean browser profile and no ad blocker. Count the third parties setting cookies or firing requests before any consent interaction. Note the tag managers, the consent tool already installed (there is almost always one, usually misconfigured), and the obvious gaps like trackers firing before the banner choice.

This scan does two jobs. It sizes the work honestly, because remediation effort scales with vendor count, not page count. And it becomes your proposal's evidence section: "we found 38 third parties across 6 categories" is a far stronger basis for a quote than "consent setup project." Prospects who balk at the price after seeing their own scan were never going to be good clients; prospects who are alarmed become your best clients.

The questions that reveal the real scope

Four questions matter more than any scan. Who can add tracking to the site, and do they need approval? The answer is usually "anyone in marketing" and "no," which tells you the decay rate you are designing against. How many sites and apps share this setup? Consent scope multiplies across properties. Has the client ever received a complaint or inquiry about tracking? Past complaints predict future scrutiny and raise the documentation bar. And who owns the vendor relationships? If nobody can name who approved each tracker, your first deliverable is an inventory, not a banner.

Listen for the phrase "we just redesigned." A recent redesign or platform migration means the consent setup was probably rebuilt from scratch by people who did not know the old one existed. These projects always contain surprises, and the quote should carry a discovery buffer whether the client likes it or not.

Red flags that change the price

Certain findings should trigger an immediate requote. Server-side tracking, because it sits outside every banner and needs separate architecture. A mobile app sharing the web consent setup, because app consent is a different regime. Existing litigation or regulatory correspondence, because everything you produce may be read by a regulator. And multi-region operations with conflicting requirements, because one banner rarely serves every jurisdiction. None of these are deal-breakers, but each one moves the project into a different pricing tier, and discovering them mid-project is how margins die.

Package the audit as a product

The pre-sales audit should not be free work you eat. Productize it: a fixed-fee "consent readiness assessment" with a defined deliverable, the scan report, the gap list, and a remediation roadmap with your quote attached. Some prospects will take the report and implement it themselves, and that is fine; you got paid for the diagnosis. Most will hire you to fix what you found, because you are the one who found it. Either way, you never again quote a consent project blind.

Frequently asked questions