Client stories
Words from operators who asked us to sit with their renewal calendars, cancellation notes, and awkward cohort questions.
They spent the first week on our pause requests rather than the dashboard we expected. The workshop then showed our care leads exactly which tickets lined up with later cancellations. We still wish the data extract had been faster on our side — that delayed the final report by a few days — but the findings were specific enough to rewrite two renewal scripts.
I had been comparing January intakes to July intakes as if they were the same shoppers. The annotated cohorts made the seasonal gap obvious, and the briefing note gave me language for our board without overselling certainty.
Our product and care teams had been arguing past each other for months. The half-day session forced us to read the same cancellation notes together. We left with three experiments, not a longer complaint list.
The quarterly pack is short on purpose. Each memo points to one or two movements worth a meeting, which is healthier than a forty-slide deck nobody finishes.
Visiontempobase linked late deliveries in our Eastern Seaboard routes to a spike in holds before billing. That connection was sitting in our tickets the whole time; we needed someone outside the weekly firefight to place it on the calendar.
Extended note · Wellness membership diagnostic
A Bangkok wellness club approached us after three consecutive months of rising holds before renewal. Care believed the issue was class availability; finance believed it was pricing. The diagnostic mapped pause requests against class waitlists and against a mid-year fee change.
The fee change explained part of the movement, but a denser cluster sat with members who had failed to book a preferred instructor twice in the fortnight before billing. The club rewrote the pre-renewal outreach to offer a booking assist rather than a discount code. Holds eased in the following two cycles — not dramatically, but enough that leadership kept the script.
This kind of story is typical of our work: retention rarely has a single villain, and the useful answer is usually a calendar-tied action rather than a new report template.