Notes from a retainer that did not renew
Honest reflections on a quarterly retainer that ended at the planned end date, and what we learned that has changed how we run kickoffs.
A retainer we started last summer ended cleanly at the planned end date. The team had taken on the work we had recommended in the first month, run with it, and arrived at a place where they did not need monthly external review. That was the right outcome, but it also left us with five months of retainer scope that quietly underdelivered against the original plan.
In retrospect, we could have caught this earlier. The signal was visible by week six: the team was completing more of the agenda items between sessions than during them. We kept the original scope through the rest of the engagement out of habit. We should have renegotiated.
We have changed the kickoff template since. There is now an explicit conversation in week four about whether the engagement should slim down, change shape, or wind down early. It is awkward to bring up but it has produced one early-wind-down and three scope adjustments since we added it.
This is not a marketing post. It is a small piece of self-correction that we want to publish openly because it shapes the behaviour of our advisory team. We bill for the engagement we run, not the engagement we sold.
Other recent blog notes
A short note on what "refactoring" should mean in 2025
A working definition we keep coming back to during advisory kickoffs, and the three distortions of the term we politely refuse to accept.
2026-03-11Why we publish the limitations section first in every briefing
A small editorial discipline that has shaped the way our advisory clients respond to long briefings.
2026-02-08Five questions we ask before recommending a platform investment
A short, repeatable diagnostic we use during retainer kickoffs to keep platform conversations honest.