Client Handoff
Hand a finished website to the client cleanly, with everything they need to run it.
#Business goal
Leave clients confident and self-sufficient after launch.
#When to use this
When a website project completes.
#At a glance
| Detail | Value |
|---|---|
| People involved | Delivery lead, developer, client |
| Departments used | Delivery, Marketing |
| Modules used | Projects, Website CMS, Deliverables |
| AI used | Content Writer Agent drafts copy; you review |
| Recommended timeline | At project close |
| Prerequisites | Projects and Website CMS access; A connected WordPress site for publishing |
#Step-by-step process
1
Deliver final assets
Share final deliverables through the portal.
2
Confirm approvals and invoices
Ensure deliverables are approved and invoices are settled.
3
Orient the client
Show them what they can manage in the CMS.
4
Set support expectations
Agree how future changes and support work.
#Decision points
Decisions to make along the way
- What can the client manage themselves?
- What is in scope for ongoing support?
#Approval points
No formal approval gate
This routine has no separate sign-off step, but review your work before it affects clients or finances.
#Success metrics
- Clean project closure
- Fewer post-launch questions
#Best practices
- Confirm invoices are settled at handoff.
- Be clear about what the CMS can and cannot do.
#Common mistakes
- Handing off with open invoices.
- Overpromising CMS capabilities (e.g., a blog manager).
#Realistic example
In practice
At handoff the client approves the final deliverable, settles the invoice via the portal, and learns which site sections they can edit in the CMS.
#Related documentation
Invoice Management
Get paid.
Website CMS
What clients can edit.
Business Workflows
Underlying step-by-step flows.
Contact Support
Reach the DevSphere OS team.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?