Handoff, enablement and expansion
An engagement isn't finished when the software is live. It is finished when the customer can run it without you, value is documented, and everyone knows what comes next. A clean handoff protects the deployment — and makes the next engagement with that customer much easier to win.
Define "done" for the handoff
Agree explicit handoff criteria during scoping, for example:
- The customer's team has run the system for two weeks without FDE intervention.
- Runbooks are reviewed and accepted by the support team.
- Monitoring alerts reach the customer's on-call rotation.
- Ownership for each component is named and accepted.
- A success review has been held with the sponsor.
Documentation that actually helps
| Document | Audience | Contents |
|---|---|---|
| Architecture overview | Engineers and IT | Components, data flows, dependencies, deployment |
| Runbook | Support and on-call | Common alerts and fixes, restart and rollback procedures, escalation contacts |
| Operating guide | Process owners | How to update prompts, content or configuration safely; how to read the evaluation report |
| User guide | End users | How to use it, its limits, how to give feedback |
| Decision log | Everyone | Why key choices were made |
Keep documents short and close to the system. A runbook nobody can find at 2am doesn't exist.
Enablement
Train the people who will own the system, not just the people who use it. Hands-on sessions work best: have the customer's engineer perform a deployment, change a configuration, or diagnose a planted failure while you watch. Confidence comes from doing.
The goal of handoff is customer self-sufficiency. If the deployment quietly depends on you, it is fragile — and you can't move on to the next problem.
The success review
Hold a formal review with the sponsor a few weeks after launch:
- The original problem and baseline.
- Results against the success metric, with the quality metric.
- Adoption and user feedback.
- Costs against forecast.
- Lessons learned.
- Opportunities for what's next.
Write it up. This document is what your sponsor forwards to their leadership — and what your company uses as a case study.
Expansion
A successful deployment creates credibility to tackle the next problem. Discovery has usually already surfaced candidates; revisit them with the sponsor, prioritised by value and feasibility. Expansion within an existing customer is typically far easier than winning a new one — and it is one of the main reasons companies invest in FDEs.
Ask satisfied stakeholders whether they'd be a reference or join a case study. Do it right after the success review, when the value is fresh.
"How do you know when your work with a customer is done?" Talk about handoff criteria, self-sufficiency, a documented success review, and identifying the next opportunity.
Senior Full-Stack Engineer · AI & AWS. I turn ambiguous customer problems into production systems — cloud, data and AI.