You have nothing to say to a paying customer. Send something anyway.

Dongyun Lee·Aug 6

It is 4:47 on Friday. Your CRM says a customer follow-up is due, the last thread ended cleanly, and you have no launch, problem, or renewal to discuss. Do not send a check-in. Send one piece of account evidence and a small next move.

You have more material than you think. A paying customer leaves a trail that a prospect does not: usage changed, a contract date moved closer, a stakeholder disappeared, a support pattern emerged, or a request they made is now possible. The work is finding the signal before you start writing.

What should you send when there is no obvious reason?

Send an observation the customer can confirm, correct, or act on.

That observation should come from the relationship, not from a content calendar. You are not trying to manufacture news. You are showing that you remember what the customer is trying to do and have noticed something relevant since the last conversation.

A useful message usually has three parts:

One specific thing you observed.
Why it may matter to the outcome the customer wanted.
One easy question or proposed action.

For example:

Your team added 14 accounts to the renewal workflow this month, but the four accounts above $50,000 still have no executive contact attached. You wanted those relationships mapped before September planning. Should I send a first pass based on the contacts already in the account history?

There is no announcement in that email. Nothing is on fire. The message earns attention because it connects a current fact to an outcome the customer already cares about.

Compare it with this:

Just checking in to see how things are going. Let me know if there is anything I can help with.

The second message sounds harmless. It also asks the customer to remember the relationship, choose a topic, identify a problem, and invent the next step. You used 16 words to hand them four jobs.

Where do you find something worth saying?

Start with changes, dates, gaps, and promises. You do not need a perfect customer health model. You need enough account memory to notice what is different.

Look for a behavior that changed

Usage does not have to collapse before it becomes useful context. A team may be active overall while one important workflow fades. A weekly process may shift from Monday to Thursday. One department may adopt while another never starts.

Describe the behavior without diagnosing it from a distance. "Usage is down because your team is disengaged" is a claim. "Nine people used the workflow last week, compared with 17 in each of the previous two weeks" is evidence.

Then connect the evidence to the customer's operating rhythm:

Nine people prepared accounts before Monday's review last week, down from 17 in each of the previous two weeks. The gap is concentrated in the new EMEA team. Did their review move, or should we look at the setup for those eight users?

That question gives the customer two plausible explanations and a small response surface. They can answer in one sentence.

Look for a date that changes the next decision

Contracts, planning cycles, launches, board meetings, hiring dates, and seasonal peaks create legitimate reasons to re-enter a conversation. The useful date is not always your renewal date. It is the customer's decision date.

Suppose the annual contract renews in 82 days, but the customer's budget proposal is due in 26. Waiting for a standard 60-day renewal task means arriving after the real decision. A useful follow-up names the earlier event:

Your budget proposal is due on 1 September, which is earlier than our normal renewal review. I can send a one-page summary of adoption and the open rollout items this week so you have it before the proposal is locked. Would that be useful?

The calendar did not create urgency. The customer's process did.

Look for a missing or new stakeholder

Relationships change quietly. A champion stops joining calls. An executive sponsor moves to another company. A new manager inherits the team but never receives the original business case.

Do not turn a personnel change into a surveillance trick. Use public or customer-provided information, and make the transition easier.

I saw that Priya is now leading Revenue Operations. The original rollout was built around the forecast process her team owns, but she was not part of those early decisions. I can send a short recap of the goal, what is live, and what is still open. Should I include you both?

When a champion leaves, the silence itself may be the signal. The next message should rebuild ownership before asking for progress. That is one reason a lost champion can make a healthy customer go quiet.

Look for a request that changed state

Customers tell you what would make the relationship more useful. Those requests end up in call notes, support tickets, product boards, and inboxes. When one ships, becomes possible through a workaround, or is explicitly declined, close the loop.

The follow-up should remember the original context, not only announce a feature:

In March, you asked whether regional managers could review their accounts without seeing the full company pipeline. That permission is now available. You said the UK rollout was waiting on it, so I can help configure that group first. Is the same manager still owning the rollout?

This works even when the answer is no. The customer can update your understanding without scheduling a meeting.

Look for an unresolved promise

The easiest follow-up reason is often one your team already created. Someone promised an analysis, introduction, configuration change, answer, or review. Small promises are easy to lose because they rarely become formal projects.

Read the last two meaningful call notes and email threads. Search for "I will," "we can," "next time," and "after." If you find a commitment, resolve it before asking the customer for anything new.

An overdue promise does not need polished language:

I said I would compare the two rollout paths after your pilot and never closed that loop. Based on the first 36 seats, I recommend expanding by region instead of role because the regional managers already run the weekly review. I attached the three-step version. Is there a constraint I missed?

Ownership is more credible than a vague apology followed by another ask.

What if nothing has changed?

Sometimes there is no meaningful product event, usage shift, stakeholder move, deadline, or open commitment. Do not invent one. Change the type of value you send.

Summarize what has become clearer across the account. A synthesis can be useful even when the underlying facts are not new.

Imagine a 36-seat customer. Twenty-two people used the core workflow weekly after onboarding. Three weeks later, 14 do. The champion has not logged in for 12 days, but support conversations are normal and no one has complained. The raw facts are ordinary. Together, they suggest a focused question:

The workflow is still active, but weekly participation moved from 22 people to 14 over the last three weeks. Most of the change is in the team that joined after onboarding, while support volume stayed flat. That looks more like a rollout gap than a product issue. Should we run one 20-minute session for that group, or leave the current team as the intended scope?

The value is the compression. You collected several weak signals, removed the noise, and proposed two credible interpretations.

If even that is unavailable, ask a narrow question tied to the customer's stated goal. "Has the priority changed?" is better than "How are things?" because it gives the customer a specific premise to accept or correct.

You originally wanted every strategic account to have a dated next action before the Monday forecast. Is that still the operating goal for this quarter, or has the team moved to a different review process?

You are not pretending to bring news. You are maintaining the account's shared memory.

How do you avoid sounding like you made up a reason?

Do not inflate the signal.

A small usage change is not a churn warning. An approaching planning date is not an emergency. A new stakeholder is not proof that the account is at risk. State what you know, mark your interpretation as a hypothesis, and let the customer correct it.

Useful phrases include:

"I noticed..."
"This may matter because..."
"My read is..."
"Is that still true?"
"Did the process change, or..."

Avoid language that turns normal account movement into manufactured urgency. "I wanted to make sure this did not slip through the cracks" is often your anxiety dressed as concern. "This is time-sensitive" means nothing without a customer-owned date.

Frequency matters less when the reason is real, but relevance is not permission to ignore stop signals. The same standard from following up without being annoying applies to customers: every message should carry the relationship forward, reduce work, or close a loop.

How do you build a repeatable reason to follow up?

Store the ingredients before the reminder appears.

For each account, keep five short fields:

The outcome the customer bought.
The operating rhythm tied to that outcome.
The next customer-owned date or event.
Open requests and promises.
The last meaningful change in behavior or ownership.

Then make the reminder describe the reason, not the activity. "Follow up with Acme" leaves the hardest work for Friday at 4:47. "Budget planning starts in 26 days. Send adoption summary and confirm owner" makes the task executable.

This is also why the first follow-up after implementation needs more than an elapsed-time trigger. The account should retain the buying reason, success criteria, and promises after the project closes. The same context behind a strong post-onboarding follow-up keeps later customer messages from collapsing into check-ins.

A lightweight weekly review can surface enough material:

Which accounts changed this week?
Which customer-owned dates are approaching?
Which requests or promises changed state?
Which relationships lost an owner?
Which accounts have no next reason recorded?

The fifth question matters. If you wait until the follow-up is due to search for a reason, you will default to whatever is easiest to write. Usually that is "just checking in."

The customer is the reason

You do not need a company announcement every time you contact a paying customer. You need evidence that the relationship still has memory.

Find one thing that changed. Connect it to the outcome they chose. Make the next move smaller than the silence.

If nothing changed, synthesize what you know or verify whether the original priority still holds. Do not perform interest. Do the account work, then write the sentence.