I once watched a digital agency lose a 200,000 dollar client before the first invoice was even sent. They did not lose them to bad creative work. They lost them because nobody sent the welcome email.
The contract was signed on a Tuesday. The account manager put it in the CRM and moved on to other things. The creative director assumed the account manager handled onboarding. The account manager assumed the creative director was setting up the project. Wednesday passed. Thursday passed. Friday morning the client emailed: Just checking in — when do we get started?
That was bad. Here is worse.
A marketing agency onboarded a new SaaS client. The kickoff call went great. The shared folder was set up. The project was in the system. But someone had used an old naming convention for the folder structure. The creative team spent the first week working in a folder nobody else could find. The client asked for an update. The account manager could not locate the work. It was there — just in the wrong place with the wrong label. The client did not leave. But they never fully trusted the agency again.
And the worst one.
A consulting firm brought on a new client during a busy month. The partner who normally handled onboarding was on vacation. The backup plan was ask Steve — except Steve had left the company three weeks earlier. The client went through four different points of contact in their first month. Each one asked them to re-explain their business. By the time someone took ownership, the client had already started looking for a new firm.
Here is what all three disasters had in common: nobody was incompetent. Everyone was talented. The problem was not skill. It was that the onboarding process lived in people's heads instead of a template that anyone could follow.
A four-phase onboarding template would have prevented all three disasters. Setup within 24 hours. Kickoff within 48 hours. Steady state communication cadence. Offboarding with lessons learned. Fill once. Anyone can follow it. Nobody has to remember it.
I built that template after watching too many of these disasters. It is part of the SOP Template Pack on Fieldwork. The Daily Operations Checklist is free if you want to start with something simpler.
Top comments (1)
the pattern that kept hitting me in your three stories: the disaster was always invisible until the client surfaced it. tuesday → friday morning "just checking in" — the agency had four days of silence and no internal signal that silence was the problem.
i ended up building the receiver-side mirror of your sender-side template, specifically because of that. once a thread is silent past N days (or past the contracted cadence) it should automatically appear on a Friday triage list — not so you cold-pitch them again, but so you know before they email "just checking in". flips the burden of detection off the client.
tagged by original-pain instead of by date works better for re-entries too, because event-triggered messages ("saw your X announcement — does the Y question we talked about still apply?") pull at a wildly higher rate than calendar-cadence ones.
i actually packaged this as a tiny gmail tool and just added a $99 done-for-you tier where i run the scan on someone else gmail and send a 1-page report of which threads are silent past their SLA + suggested re-engage angle. happy to do it on yours at $49 if you want a paired view alongside the SOP template — DM via dev.to or hit my profile.