Client management

How often should I follow up with clients? A freelancer's cadence guide

A specific, defensible follow-up schedule for active projects, paused projects, and past clients — built from what actually works for solo operators.

11 min read

Most advice on follow-up cadence is useless because it gives you a feeling instead of a schedule. "Don't be pushy." "Stay on their radar." "Be valuable, not annoying." Cool. How often is that, exactly?

This article gives you a specific, defensible cadence — different for active projects, paused projects, and past clients — that you can lift directly into your calendar. It's the cadence I wish I'd been using two years ago when I quietly lost four retainer clients in a single quarter, not because they were unhappy, but because I forgot to follow up at the moment they were deciding whether to renew.

The short version: the right follow-up frequency is shorter than you think for active work, longer than you think for past clients, and the difference between a freelancer who keeps clients and one who doesn't is almost entirely what they do in the second category.

The four follow-up scenarios (and why one schedule can't cover them)

Every "how often should I follow up?" question is actually four different questions stacked on top of each other. Until you separate them, no cadence makes sense.

  1. Active project follow-up — you're delivering work right now and need to keep the client informed without becoming background noise.
  2. Awaiting-response follow-up — you sent a deliverable, an invoice, a proposal, or a question, and they've gone quiet.
  3. Between-projects follow-up — the engagement is over, the relationship isn't, and you'd like to be the first person they think of when the next thing comes up.
  4. Past-client re-engagement — it's been more than six months, the professional momentum is gone, and you have to rebuild context before you can re-pitch anything.

Each one has a different right answer. Let's do them in order.

Scenario 1: Active project follow-up

Rule: one unprompted update per week, plus same-day responses to anything they send. No exceptions, no skipping a week because "nothing's changed" — if nothing has changed, that's the update.

The weekly update is the single most underrated freelance practice I know. It costs ten minutes and replaces the entire category of client anxiety where they're trying to decide whether to email you and ask what's going on. If they know an update is coming Friday, they don't email Wednesday.

The structure of a weekly update — write it as four short sentences:

  • What I did this week. One sentence, concrete.
  • What I'm doing next week. One sentence, concrete.
  • What I'm blocked on, if anything. One sentence, or "Nothing right now."
  • One thing I'd like your input on. Even if small — this protects against the conversation going quiet.

The "one thing I'd like your input on" line is the cheat code. It gives the client a reason to reply that isn't "approve my work or stay silent." Send the update Thursday afternoon or Friday morning so it arrives when they're winding down and have bandwidth to read it.

If the project is shorter than two weeks, switch to a single mid-project update at the ~40% mark and a final delivery email. Anything longer than three weeks, run the weekly cadence.

Scenario 2: Awaiting-response follow-up

Rule: 3 / 7 / 14 / done. Send your first nudge three business days after the original message. If they don't reply, send a second nudge a week after that. A third and final nudge two weeks after the second. Then stop until they re-engage.

This works for every awaiting-response scenario — approval pending, invoice unpaid, scope question unanswered, deliverable received but not acknowledged. The intervals lengthen on purpose, because the cost of being annoying compounds and the marginal probability that they'll reply decreases.

What changes is the tone of each nudge, not the schedule.

  • Nudge 1 (day 3): Casual, assumes a missed email. "Wanted to bump this in case it got buried — any thoughts on the proposal I sent Monday?"
  • Nudge 2 (day 10): Adds slight urgency, restates value. "Following up on the proposal — happy to walk through it on a call if that's easier than reviewing in writing. Mentioned because I want to make sure we can still hit your June launch."
  • Nudge 3 (day 24): Closes the loop, removes pressure. "Going to stop nudging on this — if the timing isn't right, no worries at all. Whenever you're ready to pick it back up, just reply to this thread."

The third nudge is the one most freelancers skip and shouldn't. It does three things at once: it makes you look secure rather than desperate, it gives the client an off-ramp from the awkwardness of having ghosted you, and it leaves an obvious thread to reply to when their priorities shift back. About a third of my closed-then-revived projects come back via nudge 3.

Scenario 3: Between-projects follow-up

This is the cadence almost nobody runs, and it's the one that determines whether you have a freelance business or a string of one-off projects. The rule:

Once every three weeks for the first six months after a project closes, then once a quarter after that — for as long as the relationship has value to both of you.

Three weeks is the magic interval. Two weeks is too frequent — it feels like you're circling. Four weeks is too long — the professional context gets stale. Three weeks is close enough to feel current, far enough to feel respectful. After six months, the relationship has stabilized enough that quarterly is fine.

What goes in a between-projects message? Not a sales pitch. The whole point is that you're not selling. The five-message rotation that works:

  1. The relevant link. Something you read that's directly useful to their work or industry.
  2. The check-in. "How did the launch land?" — refers to something specific from your engagement.
  3. The portfolio share. "Just shipped something similar to what we built — thought you might want to see how it evolved."
  4. The introduction offer. "I know someone in [their industry] who might be useful to you — want me to introduce you?"
  5. The honest update. "We're building [thing] next quarter. Not pitching — just wanted you to know in case it comes up."

Rotate through them. Skip any that don't fit the moment. The cumulative effect over twelve months is that you've sent your client four to five low-pressure, useful messages — and when they need someone, you're who they think of, because nobody else has been doing this.

Why this is the highest-ROI thing you can do: Acquiring a new client costs you somewhere between 3x and 25x more in time than retaining a past one. Yet most freelancers spend 100% of their marketing energy on net-new acquisition. The three-week cadence is dirt cheap and almost nobody runs it consistently.

Scenario 4: Past-client re-engagement

Past clients are clients you haven't spoken to in more than six months. The cadence collapses to once every six months indefinitely, but the content has to acknowledge the gap. Pretending no time has passed is the failure mode here.

The structure of a re-engagement message:

  1. Acknowledge the gap honestly. "I realized it's been almost a year since we wrapped the redesign — wanted to reach out."
  2. Reference something specific from your engagement. Proves you remember them as a person, not a customer.
  3. One useful thing. An article, a tool, a piece of information — same as the between-projects pattern.
  4. A soft door-opener. "If anything's come up that I might be able to help with, I'd love to hear it. Otherwise just wanted to say hello."

Expect about 20% of these to result in a real reply, 5% to result in immediate work, and 30% to plant the seed that brings them back six months later. The math works as long as you're not blasting them — which is why six-month intervals matter.

The full cadence at a glance

  • Active project: weekly update + same-day response. Indefinitely.
  • Awaiting response: 3 / 10 / 24 days, then stop.
  • Between projects (0–6 months out): every 3 weeks.
  • Between projects (6+ months out): quarterly.
  • Past client (12+ months silent): every 6 months with re-engagement framing.

That's it. Five rules. Print them. Tape them to your monitor.

The two things that derail this

The first is volume. Running this cadence by hand for one client is easy. Running it for twelve clients, across four scenarios, with five different message templates rotating, requires either an unreasonable amount of mental bandwidth or a system. Most freelancers I know have tried the "Notion doc + recurring calendar reminder" approach. It works for a month, then drift starts.

The second is the "I'll reach out when I have something to say" instinct. This is the single most expensive habit in freelance work. The whole point of the three- week between-projects cadence is that not having something to say is irrelevant. The relevant link, the honest check-in, the portfolio share — none of them require you to have news. They just require you to remember.

If you find yourself skipping a follow-up because nothing new has happened, you've already lost. The skip is the failure mode, not the absence of news.

What we built to make this easier

The reason ClientsPulse exists is that I needed this cadence to run on autopilot. The product watches days-since-contact for every client, flags the ones approaching their cadence threshold, and drafts a follow-up message in your voice that you review and approve in about ten seconds. The system handles the remembering. You handle the deciding.

That's the whole pitch. Same cadence as above — three weeks for active relationships, quarterly for cooler ones, six months for past clients — but you stop having to track it in your head.

You don't need our tool to run this cadence. A spreadsheet with five columns (client name, last contact date, cadence target, next scheduled, message type) plus a Friday-morning ten-minute review works fine for the first twenty clients. Past that, the math gets embarrassing and a real tool starts to pay for itself in time saved.

The one thing this article didn't tell you

I didn't tell you what time of day or week to send the messages. There's a lot of conflicting advice about Tuesday 10 AM versus Thursday 3 PM versus avoiding Mondays. Here's the truth: it doesn't matter nearly as much as the cadence itself. If you have to choose between sending a perfectly-timed Tuesday-10-AM email three weeks late or a whatever-time email three weeks on schedule, send the second one every time.

For what it's worth: Tuesday and Wednesday mornings are slightly better than Mondays (decision fatigue) and Fridays (people are checking out). But the variance from timing is small. The variance from actually sending the follow-up is enormous.

Run the cadence. Send the message. The rest is noise.


Want to read more on this? The 3-week rule for stopping client drift is the structural follow-up to this piece, and the client health score explains how to know which clients to prioritize when your list grows past ten.

Stop running this in your head.

ClientsPulse is the post-sale CRM for freelancers, consultants, and small agencies. Smart timeline, AI-drafted nudges, no-login portals. 14-day trial, no card.