Why “Just Tell Them It’s Over” Is Not a Process
Most agencies have a defined process for onboarding a new client, a kickoff call, a shared drive, an intake questionnaire. Very few have an equivalent process for ending one. The result is that firing a client, something almost every agency eventually has to do, gets improvised in the moment, under emotional pressure, by whoever happens to be running the account at the time.
That improvisation is where most of the damage happens, not in the underlying decision to end the relationship. A notice period nobody defined in advance, a handoff nobody planned, and a referral relationship nobody protected are all avoidable, and all fixed by treating termination as its own defined process rather than a conversation to figure out on the fly.
Setting a Notice Period That Holds
A notice period is the interval between a termination notice being given and the effective end date. It can be explicit, written directly into the original contract, or implied, meaning a court would determine what counts as reasonable based on the specific facts and trade practice of the relationship if the question were ever disputed. That implied standard traces to Winter Garden Theatre, a 1948 case that remains a foundational reference for implied reasonable notice in contract law, and the framework it established applies broadly across commercial arrangements, not just employment relationships.
An agency terminating a client under a contract that never specified a notice period is not operating in a vacuum, an implied reasonable standard still applies, but relying on that implied standard is a weaker, less predictable position than simply stating the actual number of days up front. Where the original contract is silent, naming a specific, reasonable notice period directly in the termination communication, rather than leaving it ambiguous, is the safer move.
Making the End Date Concrete, Not Vague
A notice period only works if the end date it produces is clearly communicated and calculable with certainty, not a vague window like “sometime next month.” A specific calendar date, stated plainly at the moment notice is given, removes the ambiguity that otherwise turns a clean ending into a drawn out, repeatedly renegotiated one.
This matters more than it sounds like it should. A client who does not know the exact date the relationship ends has no real deadline to plan around, which tends to produce exactly the kind of extended, awkward wind down a defined process is supposed to prevent in the first place.
What the Termination Has to Address Beyond “We Are Done”
An indemnity is a contractual obligation for one party to compensate the other for losses arising from specified events, and that obligation does not automatically end just because the working relationship does. A termination that only addresses the fact of ending, without addressing what happens to liability for work already delivered, leaves a real gap open on both sides.
Standard negotiation guidance favors indemnifying only for your own negligence going forward, not accepting sweeping, open ended responsibility for anything that happens after the handoff, and it is worth noting that indemnity obligations typically fall outside standard liability insurance coverage, which can leave a party exposed to real, uninsured costs if this is left vague. Putting a clear, limited statement of ongoing liability into the termination communication itself, rather than assuming the original contract quietly covers it, closes that gap before it becomes a dispute.
Handling Work in Progress and the Handoff
Almost no client relationship ends at a perfectly clean stopping point. There is usually a campaign mid flight, a deliverable half built, or a login credential the client still needs access to. A defined process names exactly what gets finished before the end date, what gets handed off as is, and what simply stops, rather than leaving that triage to whoever is managing the account in the final week.
Writing that inventory down at the start of the notice period, not the end of it, gives both sides time to execute the handoff instead of scrambling through it on the last day.
Protecting the Referral Relationship on the Way Out
A client relationship that ends professionally is not necessarily a dead end. A former client who was treated fairly on the way out, clear notice, a clean handoff, no last minute surprises about liability, remains a plausible source of a referral down the line, even if the working relationship itself was not a long term fit.
That outcome is not automatic, it is a direct result of how the ending was handled. An agency that improvises the termination under pressure is far less likely to end up with a former client willing to speak well of it later than one that followed a defined, respectful process from notice through handoff.
What this means for you
- A notice period, the interval between termination notice and the effective end date, can be explicit in the contract or implied by courts based on reasonableness, a standard traced to Winter Garden Theatre, a 1948 foundational contract law case, and it applies broadly across commercial relationships, not just employment.
- An indemnity obligation does not end just because the client relationship does. Standard negotiation guidance favors indemnifying only for your own negligence going forward, and indemnity typically falls outside standard liability insurance, a gap worth closing explicitly in the termination itself.
- A client relationship ended professionally, with clear notice, a defined handoff, and no last minute surprises, remains a plausible source of a future referral, an outcome that depends directly on treating termination as its own defined process rather than an improvised conversation.
Sources
The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.