Skip to content
Fritz Gerald ZephirinMenu

The Client Reset Conversation

4 min read

Every service relationship drifts. The contract said weekly reports; somewhere around month four it became daily dashboards. The scope said two brands; a third arrived attached to an email that began “quick favor.” The team sized for the engagement is now doing the engagement plus a shadow engagement that nobody priced, nobody approved, and — this is the dangerous part — nobody decided. Drift is never a decision. It’s a hundred small yeses, each individually cheap, compounding in one direction only. Clients don’t drift toward asking for less.

The standard response is the one that feels professional and is actually corrosive: absorb it. Preserve the relationship. Over-deliver — it’s marketing, we’ll fix it at renewal. I ran this play for years, and here is the honest accounting of where it goes. The margin erodes first, which your cash cycle feels before your P&L admits it. Then the resentment arrives — your team knows they’re working for free, and they know you know. Then, at renewal, you finally raise the issue, at the exact moment you have the least leverage and the conversation is adversarial by construction. The relationship you were protecting by silence now experiences your honesty as an ambush, attached to an invoice. Absorption doesn’t preserve relationships. It defers a worse version of the conversation to the worst possible date.

The fix is structural, not heroic: the reset conversation, scheduled into every contract longer than six months, before anyone knows what it will need to address. Ours sits at the midpoint. It is not a QBR with slides about partnership; it has exactly three agenda items, driven by data:

The drift memo. One page, prepared, factual: scope as written versus scope as delivered. Hours, deliverables, response expectations — the deltas, with numbers. No grievance tone; the memo’s power is that it reads like an audit, not a complaint. Most clients are genuinely surprised — drift is invisible from their side too, because it arrived as a hundred small favors, not a decision.

The honest reprice. Three doors, all legitimate: scope returns to contract; scope stays expanded and the price follows it; or — the door that makes the whole conversation credible — something in the original scope turned out not to matter, and we trade it away. Offering to remove paid work you’re happy to stop doing transforms the meeting from a vendor asking for money into two operators truing up a deal.

Expectations, renewed. What changed in their business, what’s changing in ours, what the next six months actually require. This is where the conversation earns its keep beyond margin repair — a striking share of expansion starts life in this agenda item, because it’s the only recurring moment where strategy is discussed without a renewal gun on the table.

Two operating notes from scar tissue. First, the AI complication, which makes this lesson urgent rather than evergreen: as AI changes your cost base, clients read about it and wonder, reasonably, why the price is unchanged. The reset is where you handle that honestly — here’s what’s cheaper now, here’s the gain we’re passing through, here’s the one we’re keeping and what it buys you. Address it proactively and you’re trustworthy; wait until procurement raises it and you’re repriced by someone else’s spreadsheet. Second: some clients punish honesty. They liked the absorbing version of you, and the reset reveals the relationship was a subsidy wearing a logo. Painful — and the cheapest possible way to learn it. An account that only retains when you eat drift isn’t an account; it’s churn on a payment plan.

The deeper principle is the one this site keeps finding in different rooms: trust compounds through maintenance, not grand gestures — and maintenance means saying true things on a schedule, while they’re still small. The reset conversation is just that, productized. Clients don’t leave because you raised an issue at month six. They leave because you didn’t, and month eighteen arrived anyway.


Sources & further reading