Your consulting revenue is coupled to your client's inbox. Uncouple it.

Contents

1. The coupling problem nobody names
2. The day 3 / 7 / 14 sequence
3. Timeline-shift language that actually lands
4. Making velocity independent of client busyness
5. Where this fits in a consultant's stack
6. Manual vs automated follow-ups

1. The coupling problem nobody names.

When consultants talk about why the work is wearing them out, the story usually goes: clients are flakier, budgets are tighter, AI is eating the lower tier, retention is harder. Those are all partially true. None of them are the thing that quietly kills a consulting practice.

The thing that kills it is that your revenue timeline is coupled to your client's velocity. You finish deliverable 2 on a Tuesday. You email it over. The client is in back-to-back meetings Wednesday, flying Thursday, off Friday. Monday they will get to it. Monday they do not. Two weeks later, you are still unpaid on that milestone, and milestone 3 cannot start, so the cascade is now your entire quarter.

You did the work. The invoice is waiting on a reply. The reply is waiting on a moment of quiet that the client's calendar is not producing. From the outside, it looks like a pipeline problem. From inside the business, it is closer to being a kite stuck on a branch.

The fix is not more polite follow-ups sent by you when you remember. The fix is decoupling the timeline. The client's quiet week stops being your quiet week. That is what a proper milestone sequence does.

The anchor pattern

2. The day 3 / 7 / 14 sequence.

Three messages, tied to the deliverable, sent automatically if the client has not responded. Each one has a different job. Each one is written once, per milestone type, and reused.

Day 0   Deliverable sent: "Positioning brief v1"
Day 3   check-in (light)
        "Quick nudge on the positioning brief. No rush, just making
         sure it didn't land in a spam folder."
Day 7   direct ask
        "Following up on the positioning brief. Any blockers on your
         side I can help with? Happy to jump on a 15 min call to walk
         it through if that's easier."
Day 14  timeline-shift
        "I want to keep your launch on track. If I don't have feedback
         by Friday, milestone 3 slides a week, which pushes the wrap-up
         from May 5 to May 12. Want to hold that slot, or shift it?"

(auto-pauses on any reply; resumes only if client goes quiet again)

3. Timeline-shift language that actually lands.

The day 14 message is the one everyone writes badly. Too soft, it gets ignored again. Too hard, it becomes the message the client remembers when they decide not to renew. The version that works is almost boring. It does not threaten. It does not moralize. It states arithmetic.

The ingredients of a timeline-shift message that works:

• A protective frame. "I want to keep your launch on track" positions you as the one trying to defend their outcome, not collect your invoice.
• A concrete trigger. "If I don't have feedback by Friday", not "soon", not "this week". A specific date is what makes the message legible.
• A specific consequence. "Milestone 3 slides a week, wrap-up moves from May 5 to May 12." Numbers are doing the work. Vague consequences ("it will delay things") do not produce replies.
• A choice. "Want to hold that slot, or shift it?" Either answer is useful to you. Either answer gets you out of limbo.
• No guilt, no apology, no caveat. This is the hardest part to enforce, especially if you are writing the message at 11pm after a long week. It is why loading the template once, calmly, and letting automation send it is such a large unlock.

Rough rule: if a client reads the day 14 message and is not sure whether they owe you a reply, the message is too soft. If they read it and feel scolded, it is too hard. The midpoint is shorter than most consultants guess.

4. Making project velocity independent of client busyness.

Once the sequence is running, something quiet happens. Your week stops being shaped by who has and has not replied. The day 7 and day 14 messages go out whether you are in a workshop, on a plane, or asleep. Client calendars are no longer in charge of your calendar.

What this looks like in practice:

• Approvals that would have landed in 12 days land in 5 or 6 on average, because the day 14 message is producing replies.
• Your Monday mental load drops, because you are no longer holding in your head the list of clients you "should probably ping today".
• Your cash flow stops lagging project progress by two to three weeks.
• You stop sending irritated follow-ups. The tone stays consistent because the tone was written once, on a good day.
• When a client does genuinely need to slip a milestone, it surfaces in week 2 rather than week 4. You can re-plan around it.

The goal is not to hound clients faster. The goal is to make the cost of their silence visible to them as early as possible, so you both deal with it while the engagement is still cheap to re-plan.

5. Where this fits in a consultant's stack.

Milestone follow-ups are one of about six operational loops a consulting practice actually runs. You can wire each one yourself, outsource them to a VA with good SOPs, or run them through an automation layer. The mechanics matter more than the tool.

1. 1. Onboarding

   Countersigned SOW triggers welcome email, kickoff scheduling link, shared folder creation, CRM stage move to "Active". Day 0 of the engagement.

2. 2. Kickoff

   Pre-kickoff questionnaire, agenda prefill, post-kickoff recap with decisions and dated deliverables. This is the cadence the rest of the engagement inherits.

3. 3. Milestone follow-up (this guide)

   Day 3 / 7 / 14 per deliverable. The highest-leverage loop in a project-based practice because it sits directly on the revenue critical path.

4. 4. Approval-to-invoice

   The moment "approved" lands in the thread, a draft invoice is created with the right line items and sent within an hour. No Tuesday admin block required.

5. 5. Mid-engagement check-in

   A short pulse at the midpoint that either confirms trajectory or surfaces scope creep early. Most renewals are won or lost here.

6. 6. Wrap and renewal

   Final deliverable, retrospective, case study consent, renewal proposal pre-drafted with the next logical engagement. Not a cold ask at the end, a continuation of the loop.

Clone is one of several ways to run these loops. It is an AI that drives the apps you already use (Gmail, QuickBooks, HubSpot or a Google Sheet CRM, Notion, Drive) to execute each of these sequences on the relevant trigger. $49 a month for solo, $129 per seat for boutique teams. If you prefer wiring it yourself, Zapier plus a Google Sheet plus mail-merge can get the milestone sequence (loop 3) running in a weekend, which is already most of the value. The point is to implement the pattern, not to buy a specific product.

6. Manual vs automated follow-up, side by side.

The row that matters is "fires without you remembering". Every other advantage follows from that one.

Common questions.