Early in an engagement, clients often feel like nothing is happening — especially when foundational work (migrations, access requests, technical audits) is invisible to them. The antidote is deliberate over-communication: a steady stream of small updates that creates the perception of constant activity, buying time for the work that actually moves the needle.
This pattern emerged clearly in the [1] engagement, where owners complained after one month that they hadn't seen website changes or traffic increases — despite significant behind-the-scenes work on migration, plugin updates, and content planning.
"Every time you do anything, send an email and say, hey, just want to let you know I did this. What happens is in the background, they're just hearing this noise from you that makes them believe you're working. That's better than them going two or three weeks and not hearing anything."
— Mark Hope
Clients don't experience your work — they experience your communication about your work. Silence reads as inactivity, regardless of what's actually happening.
Don't batch updates into weekly reports. Send a short email every time you complete a discrete task:
The goal is a continuous low-level signal that you're active and engaged.
Before making any improvement, screenshot the current state. This is the most commonly skipped step, and the most valuable for demonstrating progress.
Tools to use:
- securityheaders.com — screenshot the letter grade (e.g., "F") before fixing headers
- Ahrefs dashboard — capture domain rating, keyword count, health score
- Google Search Console — export current impressions/clicks baseline
Store these in a dedicated benchmarks folder in the client's shared drive. Label them clearly with the date. When you improve the metric, the before/after comparison is immediately compelling.
Example: Cordwainer's site had an "F" security rating on securityheaders.com — fixable in under 10 minutes. But the win only lands if you have the "F" screenshot to show where you started.
While waiting on blockers (DNS access, client approvals, third-party credentials), find things you can do and do them visibly:
| Quick Win | Visibility | Effort |
|---|---|---|
| Fix security headers (F → A) | High — screenshot before/after | Low |
| Improve site health score | Medium — show Ahrefs trend | Medium |
| Submit blog topic list for approval | High — client sees deliverable | Low |
| Update outdated plugins | Low alone, medium with email update | Low |
The point isn't that these wins are transformative — it's that they're tangible and demonstrable while longer-horizon work matures.
Use client meetings to explain the work in progress (migrations, DNS setup, content strategy). Then, in subsequent emails, reference that context:
"As I mentioned in our last call, we're working on improving your health score — just wanted to share that we've moved it from 68 to 74 this week."
This makes updates feel like progress reports rather than random noise.
Multiple account managers on calls creates confusion and dilutes accountability. If a client is already impatient, a muddled internal dynamic makes it worse. Own the relationship clearly — one primary point of contact who sends all updates and runs all meetings.