Over-Communication Strategy for Impatient Clients

Overview

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.

Core Principle

"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.

The Strategy

1. Send Micro-Updates Constantly

Don't batch updates into weekly reports. Send a short email every time you complete a discrete task:

• "Just updated three plugins that were flagged in the site audit."
• "Submitted the sitemap to Google Search Console."
• "Paul has drafted the first two blog topics for your review — sending shortly."

The goal is a continuous low-level signal that you're active and engaged.

2. Capture Baselines Before You Fix Anything

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.

3. Identify and Deliver Quick Wins Early

While waiting on blockers (DNS access, client approvals, third-party credentials), find things you can do and do them visibly:

The point isn't that these wins are transformative — it's that they're tangible and demonstrable while longer-horizon work matures.

4. Set Context in Meetings, Then Reference It in Updates

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.

5. Simplify the Account Team

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.

When to Apply This

• New clients in the first 60–90 days, before SEO or content work produces measurable results
• Clients who opened a meeting with a complaint about lack of visible progress
• Any engagement with a technical blocker (DNS access, CMS migration, third-party credentials) that delays the "real" work
• Results-oriented owners (vs. marketing-savvy stakeholders) who don't have context for why things take time

What Not to Do

• Don't go silent for 2–3 weeks even if you're heads-down on something important
• Don't skip the baseline screenshot — you'll regret it when you need to show progress
• Don't wait for a big update to communicate — small, frequent updates outperform infrequent comprehensive ones
• Don't over-promise timelines on blockers you don't control (e.g., "we'll have DNS by Friday" when that depends on the client)

Related

• ^[1] — primary case example for this pattern
• ^[2] — how to capture and store before/after evidence
• ^[3] — tactical items to pull from when you need visible deliverables fast
• ^[4] — related pattern for clients who question value rather than pace