Client communication after the build is handed over

The gap that costs agencies work

A build finishes, the invoice is settled, and communication stops. Nine months later the client emails with a problem, and neither side has spoken since. The agency has to reconstruct what was built, the client has to explain what has changed, and a conversation that should take ten minutes takes two days.

Worse, by then the client has often already asked somebody else. The relationship did not end because of dissatisfaction. It ended because nothing kept it alive and the agency had no visibility into the moment when help would have been welcome.

This is a communication design problem rather than a sales one, and most of it is solved at handover.

What handover actually has to transfer

Three things move at the end of an engagement, and agencies routinely transfer only the first.

The artefacts. Files, credentials, documentation, access. Usually handled well, because it is concrete and everyone remembers to do it.

The reasoning. Why things were built the way they were. This is what expires fastest and costs most to recover, because it exists only in the heads of people who are about to move onto other work.

The relationship. Who the client contacts, for what, and how. Almost never made explicit, which is why the answer defaults to nobody.

The handover document that keeps working

Not a specification, which nobody reads. A short document answering the questions the client will actually have in six months.

• What is running unattended. Automations, scheduled jobs, integrations. Anything that will keep working until it does not, at which point the client needs to know it existed.
• What we deliberately did not do, and why. This prevents the most common awkward conversation, where a client discovers an omission and assumes it was an oversight.
• What will need attention, and roughly when. A theme that will need updating, an integration with a version deadline, a plan limit they will grow into.
• Who to contact, for what. Split into what they can do themselves, what needs you, and what needs somebody else entirely.

The third item is the one that generates future work, and it does so honestly: you are telling them what is coming rather than waiting for it to break.

Keeping a channel open without keeping a retainer

Most clients do not want a retainer and most agencies would rather not sell one. That does not mean the only alternative is silence.

A shared room that stays open after the engagement ends costs nothing to maintain and changes the economics of the next conversation. The client asks a small question rather than sitting on a problem until it is large. You see the small question and can say whether it is a ten-minute job or a project.

The risk everyone raises is scope creep, and it is real if the boundary is left implicit. State it once, at handover: questions about what we built are welcome, new work goes through the usual route. Said plainly at the start it is unremarkable, and it gives you something neutral to point at rather than improvising a refusal later.

The practical version is a room the client keeps access to, scoped to the engagement, with your team still in it. The mechanics of setting that up are in giving clients visibility without giving them admin.

The check-in that is not a sales call

One message, three months after handover, asking a specific question rather than a general one.

"How is the checkout change holding up?" produces an answer. "Just checking in to see how things are going" produces silence, because it asks the client to do the work of deciding what you meant and whether anything is worth mentioning.

Ask about something concrete you built. If it is fine, the exchange takes thirty seconds and you have stayed present. If it is not, you have found a problem before it became urgent, which is worth considerably more than a scheduled call.

The agencies that get repeat work are rarely the ones that follow up most often. They are the ones present at the moment the client first notices a problem.

What to do when the client goes quiet

Silence is not usually dissatisfaction. It is that nothing has prompted contact and the client has no idea what would be reasonable to ask about.

The move that works is giving them a reason that costs them nothing: a note when something relevant changes in the platform, a heads-up about a deadline that affects their setup, an observation about something you noticed. Each of these is useful on its own terms and none requires the client to reciprocate.

What does not work is a newsletter. Generic contact reads as marketing and gets filtered, whereas a specific note about their store reads as attention.

Writing it down before the team forgets

The internal half of this is the part that decays. Six months on, the person who built it has moved on and nobody remembers why the shipping logic works the way it does.

Capture it at close-out, while it is cheap: what was built, what was rejected and why, what is fragile, and what the client was told. Fifteen minutes at the end of an engagement, and it is the difference between answering a returning client in ten minutes and quoting for a discovery session.

If you run several client engagements, keeping each one in its own room with that summary posted at the end means the record is searchable rather than living in one person's memory.

The three months after handover

Most of the relationship is decided in this window, and most agencies treat it as finished.

Week one. The client is using what you built for the first time under real conditions. Small things surface: something is slower than expected, a workflow does not match how they actually work. These are cheap to fix now and expensive later, and they are the moments that determine whether the client feels supported or abandoned.

Week four. The novelty has gone and habits are forming. This is when a client discovers they do not know how to do something you assumed was obvious, and when a well-aimed question finds real gaps.

Month three. The first genuinely new requirement appears, because the business has moved on. Whoever is present at that moment gets the work, and presence at month three is the entire argument for staying in touch.

You do not need to be actively working during any of this. You need to be reachable and to have asked one question at each point.

What to do when they hire someone internally

A common and awkward transition. The client hires a developer or an operations person, and the agency assumes the relationship is over.

Sometimes it is. Often it is not, and the agencies that handle it well end up with more durable work rather than less.

The move is to help the new person rather than compete with them. Offer a handover session, share the reasoning documents, answer their questions without billing for the first hour. An internal hire who understands what you built and likes dealing with you becomes an advocate; one who inherits an undocumented system from an agency that went quiet becomes the person arguing to replace you.

The work that follows tends to be different: specialist pieces rather than general delivery, which is usually higher value per hour and less demanding on your capacity.

The one-page summary worth sending

At close-out, send the client a single page rather than a folder. Folders get saved and never opened; one page gets read once, which is enough.

Four short sections: what we built, what to watch, what you can do yourselves, and how to reach us. Under 500 words. Anything longer becomes a reference document, and reference documents are consulted only by people who already know what they are looking for.

Send it as the last thing in the engagement room rather than as an email attachment, so it stays findable in the place the client already associates with the project. Nine months later, that room is where they will look first.

Common questions