Consent scope creep: the five phrases that turn a banner setup into an unpaid project
Consent projects rarely blow up all at once. They expand one reasonable-sounding sentence at a time, usually in a client call, until the fixed-fee banner setup you quoted has become a multi-week compliance engagement with no extra line item. The expansion almost always starts with one of five phrases. Learn to hear them, and you can price or deflect each one on the spot.
1. While you are in there, can you also check the app?
This is the scope double. A website consent setup and a mobile app consent setup are different projects with different vendors, different platforms, and different rules. The app has its own SDKs, its own consent framework, and usually a different team on the client side. Treat this as a second engagement, not an extension of the first. The answer that keeps the relationship warm: confirm the website work is covered, then quote the app as its own fixed-fee piece with its own timeline.
2. Legal wants to review everything before it goes live
This one sounds like a small step, but it puts your delivery date in someone else's calendar. Legal reviews of consent copy routinely take one to three weeks, and the comments come back as a markup of your implementation, not a sign-off. Build this into the quote: a review round is included, the round has a defined turnaround, and the launch date moves if the review does. Agencies that do not price the review round end up holding a finished project they cannot ship while the client considers it your delay.
3. Can we just do one banner for all our regions?
A single global banner is a real configuration with real tradeoffs. Different regions require different default states, different category structures, and different handling of legitimate interest. One banner that behaves correctly in the EU, the UK, California, and Brazil is four consent experiences behind one interface. That is genuinely more work than four separate simple banners, because every rule has to account for every other rule. Quote the matrix, not the banner. If the client wants to simplify, offer a phased approach: launch with the strictest configuration everywhere, then relax regions in a second phase with its own budget.
4. The marketing team added a few new tools since the audit
This is the moving target. Between your audit and your implementation, the client onboarded a new analytics tool, a review platform, and an A/B testing tool, none of which were in the tracker inventory you priced. Consent implementations decay toward inaccuracy whenever the tag inventory changes, so a stale inventory is not a small detail. Your statement of work should name the inventory date and say plainly that new tools discovered after it are a change order. Better yet, sell the recurring piece here: a monthly tracker re-scan is cheap to run and gives the client a standing answer to what is actually firing.
5. Could you write up what we did for our records?
This sounds like fifteen minutes and is actually half a day. What the client is asking for is a record of processing, a consent configuration document, and evidence the setup matches it. That documentation is valuable, and auditors ask for it, so do not give it away. Package it as a named deliverable in the original quote: the consent handover document, fixed fee, shipped with the implementation. When the client asks for it mid-project, you get to say it is already included and look organized instead of doing free work.
The line that stops all five
None of these phrases is unreasonable. Clients ask them because consent feels like one small thing when it is actually an ongoing practice. The fix is not to argue; it is to have the price ready. Keep a one-page rate card for consent add-ons: app consent, review rounds, multi-region matrices, re-scans, documentation. When the phrase lands, you name the line item, quote the fee, and keep the original project exactly the size you sold. The agencies that make money on consent work are not the ones that avoid scope creep. They are the ones that had a price for it before the call.