Most client projects do not go wrong in the middle. They go wrong at the edges: a fuzzy brief that everyone nodded through, a handoff where the deliverable arrived but the context did not, a close-out that skipped the retrospective so the same mistake happened on the next project. Heroics can rescue a project once. A repeatable phase structure prevents the crisis from forming.
The five phases every client project needs
Every client engagement, from a three-week website refresh to a six-month brand build, benefits from the same five-phase skeleton. The phases scale up or down in duration, but their function is constant.
| Phase | Primary output | Who drives it |
|---|---|---|
| 1. Brief | Signed scope document, success criteria, constraints | Account lead |
| 2. Plan | Task list with owners and dates, kickoff meeting held | Project lead |
| 3. Build | Iterative deliverables with scheduled review checkpoints | Delivery team |
| 4. Review | Client feedback consolidated and resolved | Account lead + delivery team |
| 5. Deliver and retro | Final files transferred, retro notes filed | Project lead |
The phase boundary is a gate: you do not start Plan until Brief is signed, and you do not move to Build until the plan has owner names and dates on every task. Gates are not bureaucracy. They are the mechanism that prevents scope drift and the “I thought you meant X” conversation at week four.
Phase 1: Writing a brief that actually constrains the project
A brief is not a wish list. It is a constraint document. Its job is to make it impossible to misunderstand the goal, the boundaries, and how you will both know the work is done. A brief that takes 45 minutes to write saves 10 hours of mid-project renegotiation.
- The goal in one sentence. What does the client want to be true after this project that is not true today? One sentence forces clarity. Two sentences usually means two projects.
- Success criteria. Three to five measurable or observable outcomes. “A new website” is not a success criterion. “A website that converts visitors to demo bookings at a rate above 3 percent” is.
- Explicit exclusions. What is out of scope? List it. This one section prevents more scope creep than any contract clause.
- Constraints. Budget ceiling, hard deadline, technical limitations, stakeholders who must approve. Named constraints are negotiable. Unnamed constraints are landmines.
- Approval path. Who signs off on each deliverable? If the answer is “the committee,” find out who on the committee has final authority before the project starts.
Send the brief to the client as a shared document before the kickoff meeting, not during it. Give them 48 hours to read it. The kickoff meeting is for resolving gaps, not for reading the brief aloud.
The kickoff agenda that sets the right tone
A good kickoff meeting runs 45 to 60 minutes, ends with the client feeling confident, and results in one document everyone has signed off on. Here is a proven agenda.
- Introductions and roles (5 minutes) Name every person in the room and their role on the project. This sounds obvious but is skipped constantly. Clients who do not know who to contact for what will contact everyone, which means nobody is accountable.
- Brief review: confirm goal and success criteria (10 minutes) Walk through the brief. Ask the client: “Is there anything here that does not match what you intended?” Not “Does this look right?” Open questions surface disagreements. Closed questions get nodded through.
- Review the explicit exclusions (5 minutes) Read the out-of-scope list aloud. Clients often discover things they expected to be included. Better to find that here than in week five.
- Walk through the phase timeline (10 minutes) Show the five phases with approximate dates. Identify the two or three review points where the client needs to be available and responsive. Slow client reviews are the single biggest source of project slippage.
- Communication norms (5 minutes) How will you communicate? Weekly status email, Loom video updates, or a shared project portal? Who is the single point of contact on the client side? Establish this now.
- Open questions (10 minutes) What does the client still need to provide? Assets, logins, brand guidelines, copy. Build a list, assign a due date, and confirm who on the client side owns it. Waiting on client assets is the other major source of slippage.
- Next steps (5 minutes) Close with a written list of who does what before the next touchpoint. Read it aloud. Send it as a follow-up within one hour of the meeting.
The status cadence clients trust
Clients who feel out of the loop send status emails. Those emails interrupt the team, cost time, and signal a trust problem. A proactive status cadence eliminates most inbound check-ins before they happen.
The most reliable format is a brief weekly status update sent every Monday morning. It answers four questions in under 200 words: what was completed last week, what is happening this week, what is at risk, and what you need from the client. Short, specific, and sent before the client has time to wonder.
- Completed last week: Three to five bullet points. Specific deliverable names, not “worked on the website.”
- This week: What the team will complete by Friday. Sets a commitment the client can hold you to.
- At risk: Honest flagging of anything that might affect the timeline. Clients can handle problems. What they cannot handle is surprises.
- Needed from you: A numbered list of outstanding client inputs with due dates. Makes it easy for the client to action.
For teams using Studio Craft, the project portal surfaces this status automatically from task progress, so the Monday email becomes a five-minute copy-paste rather than a 30-minute reconstruction.
The handoff checklist that closes projects cleanly
A clean project close matters because half of new business comes from returning clients. A messy handoff is the last thing a client remembers. Run through this checklist before calling any project done.
- Final files transferred. All deliverables sent in the agreed format to the agreed location. Not “available on request.” Transferred.
- Logins and credentials handed over. Any accounts created during the project should transfer to the client. Remove your own team’s access unless the contract specifies ongoing access.
- Documentation delivered. Any instruction guides, brand guidelines, or technical documentation that helps the client use what you built. A deliverable without instructions is half a deliverable.
- Invoices settled. Confirm final invoice is sent and payment timeline agreed before the project file is archived.
- Client confirmation in writing. An email reply saying “received, all looks good” is enough. You want a paper trail that the client accepted the deliverables.
- Testimonial or review request. The best time to ask is at handoff, when the work is fresh and the client is satisfied. Not three months later.
The retro that compounds over time
Most agencies skip the retrospective. This is why they make the same mistakes on every fifth project. A 20-minute internal retro after each project is the mechanism by which the team gets materially better, not just more experienced.
Keep it simple. Three questions, answered honestly by everyone who worked on the project.
- What worked and should be repeated? Name specific practices, not general feelings. “The Monday status email kept the client calm” is actionable. “Communication was good” is not.
- What slowed us down or should not be repeated? Be specific and blameless. “We waited five days for the client to provide brand assets before we followed up” identifies a process gap. “The client was slow” identifies a scapegoat.
- What one change would we make if this project started again today? One change per retro. Teams that try to fix ten things fix zero. One change, assigned to one person, with a due date.
File the retro notes where they are findable before the next project of the same type. The value is not the notes. The value is that they get read at the next kickoff.
Key takeaways
- Five phases (Brief, Plan, Build, Review, Deliver and retro) with hard gates between them prevent most mid-project disasters.
- A brief is a constraint document. Include explicit exclusions, success criteria, and a named approval path.
- Send the brief 48 hours before kickoff. Use the meeting to resolve gaps, not to read the document.
- A weekly Monday status email with four sections (completed, this week, at risk, needed from you) eliminates most inbound client check-ins.
- A 20-minute retro after every project compounds into measurable team improvement within six months.
Common questions
What if the client wants to skip the brief and just get started?
Frame the brief as protecting both parties: “This is how we make sure we build exactly what you want and do not end up rebuilding it at our own cost.” A 45-minute brief investment is a compelling trade against a two-week scope-creep conversation.
How do we handle scope changes mid-project?
Acknowledge the request, document it in writing, and respond within 24 hours with two options: incorporate it now with an adjusted timeline and cost, or log it for a phase two. Never say yes without a written change order.
Our clients are slow to provide feedback during the Review phase. How do we protect the timeline?
Set a review deadline in the brief. Something like: “Client feedback must be consolidated and submitted within five business days of each review delivery. If feedback is not received within this window, the project timeline moves by the same number of days.” Put it in writing before the project starts.
Do we need a retro for small projects?
Yes, but scale it down. For a one-week project, a three-question async Slack thread takes 10 minutes total and still captures what matters. The habit is more important than the format.
