How a project ends shapes whether a client comes back and whether they leave a good review — closing well is worth as much attention as starting well.
| Step | Why it matters |
|---|---|
| Confirm final deliverables against the original scope | Catches any gap before the client has to point it out |
| Get explicit sign-off ("looks good, approved") | A clear, written approval — not silence — is what actually closes a project |
| Send the final invoice (or release the milestone payment) | Covered in the earlier invoicing lesson — do this immediately, not "eventually" |
| Hand over all files and access cleanly | Source files, credentials, admin access — organized, not scattered across old messages |
| Ask for a review or testimonial | The moment right after a happy delivery is the best time this will ever come — covered in depth next lesson |
A client's final impression is what they remember when deciding whether to hire again or refer someone — a project that delivers great work but ends messily (a slow handover, an awkward final invoice) leaves a worse impression than the actual work quality deserves.
A small habit worth keeping
A short, warm closing message — thanking the client and noting availability for future work — costs a minute and quietly keeps the door open for repeat business.