Client communication, delivery, revisions, difficult clients and getting reviews
Clients rarely leave because the work was 5% worse than perfect. They leave, or leave bad reviews, because they felt ignored, surprised or confused. Great communication turns average projects into repeat clients and referrals. This lesson covers the whole delivery journey.
The golden rules
- No surprises. Bad news early is a problem solved together; bad news on the deadline is a broken promise.
- Respond within one working day, even if it's just "Got it, I'll reply properly by tomorrow noon."
- Write things down. Decisions made on calls get summarised in writing afterwards.
- Under-promise, over-deliver. Quote realistic deadlines and deliver a little early.
- Be the calm professional, even when the client isn't.
Onboarding: start strong
Within 24 hours of the deposit:
- Send a welcome message: thank them, confirm the timeline, list what you need from them and by when, and how updates will work.
- Share a content checklist (logo files, photos, text, logins) with a deadline.
- Set up a shared space: a Google Drive folder, a Trello board, or a simple shared document with the plan.
- Agree communication channels: e.g. WhatsApp for quick questions, email for approvals and files, a weekly 15-minute call for bigger projects.
Example welcome message:
Hi Grace, deposit received, thank you! We're officially started. Here's what happens next: 1. By Friday I'll share the homepage design for your feedback. 2. I need your menu, prices and 5–10 photos by Wednesday (upload them here: [Drive link]). 3. I'll send a short progress update every Monday and Thursday. If anything changes on your side, just let me know. Excited to build this!
Progress updates
A short update twice a week (or at every milestone) prevents anxious "any progress?" messages:
Update (Thursday): Done: homepage and menu page designed. Next: contact page and WhatsApp ordering (by Monday). Need from you: delivery areas and fees. On track for launch on the 20th.
Done, next, needed, status. Four lines. Clients love it.
Getting feedback that's actually useful
Vague feedback ("make it pop", "I don't like it") is common. Guide it:
- Share work with specific questions: "Is the menu order right? Do these colours match your brand? Is anything missing on the first screen?"
- Ask for feedback in one consolidated message per round, not 15 separate ones over a week.
- For visual work, tools like Google Docs comments, Figma comments or annotated screenshots keep feedback clear.
- When feedback is unclear, ask: "Can you show me an example you like?" or "What should a visitor feel or do here?"
Revisions within scope
- Remind kindly how many rounds are included: "This is revision round 1 of 2."
- Group changes and do them in one go.
- If requests go beyond the agreed scope, use the scope creep script from discovery, quotes and contracts.
Delivering the work
A professional delivery includes:
- The deliverables, clearly named and organised (folders, file formats they asked for).
- A short summary: what's included, how to use it, any logins (shared securely, not in public channels).
- Instructions or training: a short video (screen recording) or guide on how to update or use it.
- Next steps: final invoice, support period, care plan or ongoing services.
Hi Grace, your website is live: [link] 🎉 - Admin login details are in the secure note I just sent. - Here's a 6-minute video showing how to update prices and photos: [link] - Your final invoice is attached (due in 7 days). - Support: any bugs in the next 30 days are fixed free. It was a pleasure working on this. If you're happy with the result, a short review would mean a lot: [Google review link]
Asking for reviews and testimonials
- Ask right after a successful delivery, when the client is happiest.
- Make it easy: send the direct link (Google Business review link, platform review, or "reply to this message with two or three sentences I can quote").
- Prompt them with questions: "What was the problem before? What changed? Would you recommend me, and to whom?"
- Ask permission to use their name, business name and logo in your portfolio.
- Never write fake reviews or pay for them.
Difficult situations (and what to say)
| Situation | What to do |
|---|---|
| Client goes silent for days | Friendly reminder at 3 days, another at 7 days explaining the timeline will move: "Since we're waiting on the content, the launch date moves to the 28th." Put the project on pause politely after that. |
| Client keeps changing their mind | Summarise the latest decision in writing; point to the agreed scope and revision rounds; quote extra work. |
| Client is rude | Stay calm and factual. Don't reply angrily; wait an hour. If abuse continues, finish the current milestone and end the project professionally. |
| You made a mistake | Own it quickly, fix it, explain how you'll prevent it. Clients forgive honesty much more than excuses. |
| You'll miss a deadline (illness, power outage) | Tell the client as soon as you know, with a new realistic date and what you've done so far. |
| Client won't pay | Send a polite reminder on the due date, a firmer one after 7 days referencing the agreement, then a final notice. Keep final files until paid. On platforms, use their dispute process. |
| Client asks for unpaid "small extras" after the project ended | "Happy to help! That's outside the original project. I can do it for KSh X, or include it in a monthly care plan." |
Ending a project well (and turning it into more work)
- Close properly: confirm everything is delivered, payments complete and access handed over.
- Offer ongoing value: maintenance, monthly content, social media management, SEO, support (retainers and scaling).
- Check in after 30–60 days: "How is the website working for you? Anything you need?" Many repeat projects start with that message.
- Write the case study for your portfolio while details are fresh.
Professional habits that set you apart
- Proper greetings, clear grammar, no voice notes for important decisions (send text so there's a record), and respect for the client's time zone and working hours.
- Use the client's name and refer to their business goals, not just tasks.
- Keep your own notes for each client: preferences, logins (in a password manager), decisions.
- Protect client data: strong passwords, 2FA, don't share their files or logins with anyone else (passwords and 2FA).
Summary
- Onboard clearly, send short regular updates (done, next, needed, status) and write decisions down.
- Guide feedback with specific questions; handle revisions within scope.
- Deliver with files, instructions, invoice and next steps; ask for reviews right away.
- Handle silence, changes, mistakes and late payments calmly and in writing; end projects in a way that brings repeat work.
Check yourself
What are the four parts of a good progress update? Write them separated by commas.
Show answer
done, next, needed, status
When is the best time to ask for a review? (right after ___)
Show answer
delivery
Should important decisions be sent as voice notes or as written text?
Show answer
written text
Within how long should you respond to a client message? (one working ___)
Show answer
day