Most people stay in bad consulting relationships for the same reason they stay in bad anything: the exit feels harder than it is. The contract language is vague. The relationship is personal. Switching costs feel enormous. And somewhere in the back of your mind, the Fog Machine is still running: What if they know something I don't? What if we lose this institutional knowledge?
Let's answer those questions directly. They don't know something you can't know. There is no institutional knowledge — the consultants who understand your business are rarely the ones writing the deliverables. The things that would "break" almost certainly already broke, or they built the systems fragile on purpose to maintain dependency. The exit is easier than the Fog Machine told you.
What Do You Do Before the Conversation?
Step 1: Read the Contract. Actually Read It. Find the termination provisions both parties have forgotten. Look for: notice period (typically 30–90 days), work-for-hire clauses (who owns deliverables?), non-disparagement provisions, transition obligations (are they required to provide a handover?), data and access provisions. If the language is unclear, use Claude to parse it. AI contract review costs $0.02 instead of $650/hour.
Step 2: Run the Noon Audit. Before exit, confirm you're replacing the function, not just removing it. Apply the Noon Audit questions to the engagement. Document your replacement: which AI tools replace which functions, total replacement cost, transition timeline. This is your operational safety net.
Step 3: Build the Replacement Infrastructure First. Do not cancel the retainer and then build the replacement. Build the replacement, test it, confirm it works — then cancel. Most people do it backwards, then scramble, which creates the operational chaos consultants warned them about.
What Is the Firing Script Framework?
Communication 1 — Internal Alignment. Before talking to the consultant, align internal stakeholders affected by the transition. Keep it small. This is not a discussion about whether to terminate. The decision is made. This is a communication about the transition plan.
Communication 2 — The Termination Conversation. One professional, brief meeting or call. Not a negotiation. Not a performance review. A notification. Structure: "We've completed a review of our consulting relationships and have made the decision to end this engagement." State the effective date. Note that you'll follow with written confirmation. Do not offer extended justification. Do not apologize. Do not invite a counter-proposal. What not to say: "We've found someone cheaper" (opens price negotiation), "Your work hasn't been up to standard" (opens dispute), "We're building internally" (gives time to entrench before exit).
Communication 3 — Written Confirmation. Within 24 hours: confirms termination and effective date, specifies notice period, addresses data return and system access handover, references contract terms, notes transition obligations you expect them to fulfill.
Within 90 days of a clean exit from a major consulting relationship, most organizations report faster decision-making, clearer ownership of strategic direction, lower operational cost, and relief. The Fog Machine worked because you believed you needed it. The exit is where you find out you were wrong about that.
How Do You Handle the Counter-Moves?
"We have institutional knowledge you'll lose." Response: "We've made our decision. We're prepared to manage the transition." Do not engage with the argument.
"Can we get on a call to discuss what's driving this?" Response: "We've completed our evaluation. I'm happy to answer logistical questions about the transition, but the decision itself is final." A "discussion call" is a retention attempt dressed as dialogue.
"Could we revisit this after [project]?" Response: "Our decision applies to the full relationship. The termination date stands."
Invoice for work "in progress" you weren't tracking. Response: Request itemized documentation for claimed work-in-progress, cross-reference against the deliverable scope in the contract, dispute any amounts not supported by documented deliverables.
Three pre-conversation steps: audit the contract for exit provisions, complete the Noon Audit to document your replacement plan, build the replacement infrastructure first. Then one professional termination conversation, followed by written confirmation within 24 hours. Total timeline: 2–3 weeks from decision to clean exit.
From Obsolete By Noon: a six-question evaluation that documents whether a consulting relationship is delivering genuine value or the appearance of value. Applied before exit, it confirms you're replacing the function with a specific AI stack — not just removing the consultant and hoping for the best.
Most people cancel first, then scramble to build the replacement. This creates the operational chaos consultants warned about — and hands them evidence that they were indispensable. Build, test, and confirm the AI replacement infrastructure is operational before the retainer is cancelled. Then the exit has no operational risk.
Most organizations report: faster decision-making (no waiting for consultant deliverables), clearer ownership of strategic direction (internal judgment proves stronger than assumed), lower operational cost (AI replacement stack costs a fraction of the retainer), and relief. The Fog Machine worked because you believed you needed it. The exit reveals you didn't.
