Contracts, notice periods, and what to negotiate

I am not a lawyer and this is not legal advice. This is how an operator should read a vendor agreement before sending it to one.

Most agency contracts are not adversarial documents. They are templates, often bought once and reused, and the clauses that hurt you are usually there because nobody removed them rather than because someone aimed them at you. That is good news. It means asking usually works.

What is a fair initial term?

Long enough for the work to be possible, short enough that you are not funding indifference.

Search work does not produce visible movement in thirty days, so an agency asking for a few months of runway is being reasonable rather than predatory. What matters is what happens at the end of that period. An initial term that converts to month to month is fair. An initial term that automatically renews into another full term is where people get stuck.

Ask for two changes if the term is long. First, that it converts to monthly after the initial period. Second, that there is a defined checkpoint partway through where either side can end it if the agreed deliverables have not been produced. Tie that checkpoint to deliverables, not to results, because results at that stage are not a fair test of anybody.

What should the notice period actually say?

Thirty days from written notice is standard and workable. The details around it are where the trouble lives.

Check three things. How notice must be delivered, since some contracts require certified mail to a specific address and an email will not count. Whether the window is tied to a renewal date, which turns a thirty-day notice into a once-a-year opportunity. And whether the final month is worked or simply invoiced.

Run the date arithmetic before you sign

This is the calculation that changes people's minds, and it takes two minutes.

Version A. Twelve month initial term starting 1 March, automatic renewal into another twelve months, sixty days written notice required before the renewal date.

The renewal date is 1 March the following year. Sixty days before that is 31 December. If you send notice on 2 January, you are committed to a second full year. That is eleven extra invoices, not one, and the mistake is invisible because nothing in the document says the words "eleven months."

Version B. Same twelve month initial term, converting to month to month afterward, thirty days from written notice at any point.

You send notice on 15 April. You are out on 15 May.

Same fee, same agency, same work. The difference between those two paragraphs is eleven months of payments, and it is decided entirely by the phrase "before the renewal date."

Run it on your own document with real dates on a calendar. Then write the last possible notice date on a sticky note and put it in the file. The notice clause is the one you will read while angry. Write it while you are still friendly.

Ask for notice by email to a named address, with acknowledgment. Ask that the final period is worked normally, including the last report. And ask what happens to work in progress, because a half-finished site migration is worse than either finishing or never starting.

If you are already thinking about the exit, sequence matters more than the clause, and there is a clean order of operations for ending an agency relationship that starts before you send anything.

Which clauses are worth the negotiation?

Four are worth pushing on.

Worth it. Ownership of the site, the content, the images, the tracking configuration, and anything else produced under the agreement, assigned to you on payment. This is the single most valuable paragraph in the document, and what happens to your website when the relationship ends turns almost entirely on how it is written.

Worth it. Account access, meaning you hold owner-level access to the analytics property, the ad accounts, the business profile, and the domain registrar throughout, not just at the end. Agencies sometimes resist this out of habit. The reasonable version is that they administer, you own.

Worth it. Disclosure of subcontracting. You are not banning it, you are asking to be told which parts and by whom. That question also tells you a lot about how the shop is built, since the tradeoffs between offshore teams, local shops, and freelancers are real and worth choosing deliberately.

Worth it. A copy of work product on request, in a usable format, during the engagement rather than after it. Research is a deliverable. The competitor analysis behind your category decisions is an example, and the categories your competitors use are findable and worth keeping a copy of even if you change agencies later.

Is venue really just boilerplate?

Usually yes. There is one documented case where it was the whole ballgame, and it is worth knowing before you wave the paragraph through.

In Gaines v. LPC Survival, Ltd., decided in the Central District of California on 16 June 2026, a plaintiff sued a small business under the Telephone Consumer Protection Act for continuing to send texts after a stop request. The business tried to bring in its SMS vendor. The court granted the vendor's motion to dismiss on jurisdictional grounds, because the vendor's own customer agreement required litigation in Utah only.

The business was sued. The software that sent the messages was not, and could not be, brought into the same case. That is what a forum-selection clause does when it is pointed at you rather than at your counterparty.

So the honest revision to the usual advice is this. Fighting over governing law in your agency agreement is still mostly wasted effort. But read the terms of service of every tool the agency signs you up for, because that is where the venue clause actually bites. Ask one question in writing: which vendors will be contracted in my name, and can I see their terms before we start?

Late fee percentages, standard indemnities and confidentiality language are still not worth your afternoon. Fighting those signals that you will be expensive to work with and gains you nothing.

Who is liable when the agency's script is on my site?

You, in most of the ways that matter, which is why the scope language deserves a slower read than the fee.

Three concrete examples, all of them things agencies install routinely.

Call tracking. Dynamic number insertion is a script the agency puts on your site. In California, the plaintiffs' bar has spent 2024 through 2026 repurposing the Invasion of Privacy Act against exactly that artifact, mostly under a pen register theory. The damages provision, Penal Code section 637.2, supplies the greater of $5,000 per violation or three times actual damages, and states that the plaintiff need not have suffered or be threatened with actual damages. Call recording under section 632.7 carries the same $5,000 figure and applies to parties, not just eavesdroppers, per the California Supreme Court in Smith v. LoanMe. Ask who is responsible for the disclosure script and where it fires in the call flow, because prior consent means before anything is captured.

Text messaging. TCPA statutory damages run $500 per message, trebled to $1,500 for willful violations. A single unauthorized send to a 5,000 contact list is a theoretical exposure in the millions. Carrier registration for business texting also requires a publicly visible page carrying your opt-in language and privacy policy, and carriers verify it, which makes it the agency's job whenever the agency owns the website.

Review solicitation and removal. Under the FTC rule on consumer reviews, section 465.7(a) prohibits using a groundless legal threat to prevent or remove a review. The old reputation-management move of firing a boilerplate defamation letter at a one-star reviewer is now itself the violation.

None of this means the agency is doing anything wrong. It means the exposure lands on the business name on the account. Put one sentence in the agreement: the vendor will not deploy tracking, messaging, or review solicitation without written confirmation of the consent and disclosure mechanism. That sentence costs nothing and it is the cheapest clause in the document.

What about reputation management in the scope?

Ask what the method is, in writing, and be specific about the answer you want.

Joy Hawkins of Sterling Sky has documented firsthand what part of the review-removal market actually does. Her words: companies charge businesses thousands to remove negative reviews, often through shady tactics, one common trick being abusing DMCA takedown notices with false claims, which Google often approves automatically. The example she gives is a forum thread criticising a reputation-management company that was removed from Google on a takedown notice claiming the post had stolen content from a news article about an earthquake in Haiti. Google approved it. Traffic to the page dropped to zero. Her verdict on the practice is that it is lying, and no different from buying fake reviews.

Google's own position is that you can report any review, but only those violating Google policies are eligible for removal, and that it does not get involved in conflict between businesses and customers. The legitimate grounds are narrow and real: off-topic content, and conflict of interest such as a review from a former employee or a competitor.

So the clause to ask for is a written commitment to policy-grounded flagging only, with no DMCA takedowns and no mass reporting. A vendor doing honest removal work will sign that in a second. A vendor doing the other thing will explain why it is unnecessary.

What about exclusivity in my category?

Ask for it, expect a limit, accept a defined one.

A reasonable agency will offer exclusivity by category within a defined radius or city. An unreasonable request is exclusivity across an entire industry, which no viable business can grant.

Watch also for the reverse clause: a restriction on you hiring their staff, sometimes written to survive for years and to cover anyone you ever met. A narrow version is fair. A broad one can make it awkward to hire a marketing manager later.

And check whether the contract claims ownership of content the agency writes for you. Content is the asset that keeps earning after you stop paying, since a single well-built page can answer a whole family of related questions. Licensed content that reverts on termination leaves you rebuilding pages you already paid for.

What to do this week

Take the agreement and find four paragraphs: ownership, notice, access, and subcontracting. If any of the four is missing, that is your first email.

Then work out one date, on a calendar, with the arithmetic above. If you signed today and wanted to be free by month seven, what is the last day you could send notice, and how must you send it? If you cannot answer from the document in five minutes, ask them to rewrite the clause in plainer terms. Most will.

Ask for the list of third-party tools that will be contracted in your name, and skim each one's terms for the venue clause and the liability cap.

Send all requested changes in a single message. Contracts get negotiated once, and drip-fed edits make you look uncertain. One clear list, done in a day.

Questions about a clause you are unsure of?

Email me at eric@seod.com with just the termination and ownership paragraphs pasted in, and I will send back what each one obligates and the two edits most likely to be accepted without a fight. I am not a lawyer, I will say so again in the reply, and I will not be pitching you. If the contract is already fair, that is a one-line answer and you will get it.

There is more on hiring and working with agencies if you are still at the comparison stage.