Agency automation 20 of 25
Retainer Renewal Reminder: A 60, 30 and 14 Day Timeline for Agencies
A retainer renewal reminder works best when it starts 60 days before the contract ends. At 60 days, your account lead gets an internal brief and a prep task. At 30 days, a draft renewal email with a results recap is ready to send. At 14 days with no signed renewal, the owner is alerted and a nudge is drafted. Count from the notice date, not the end date, when a contract renews unless someone cancels. n8n checks your contract sheet every morning, Claude drafts the brief and the email from facts you supply, and a person sends every message. This page gives you the timeline, the notice-date rule and a short sample email to adapt. Check your contract's notice period before you set any dates, because notice rules vary by agreement.
How the automation runs
A retainer renewal reminder starts the renewal conversation weeks early. n8n checks contract dates daily: 60 days out brings internal prep, 30 days a draft client email, and 14 days an owner alert. A person sends every email.
What is a good retainer renewal reminder timeline?
A workable timeline has three stages. This is a starting design, not a rule, so change the days to fit your contracts.
The automation keeps a stage column in your contract sheet. It sends a reminder when the days left are at or below a stage and that stage has not been recorded yet. If n8n is down for a day, the next run still catches the stage, so no reminder is skipped.
| Days before | Stage | What happens | Who acts |
|---|---|---|---|
| 60 | Internal prep | The account lead gets an internal brief and a prep task | Account lead |
| 30 | Client draft | A draft renewal email with a results recap is saved in Gmail | Account lead reviews and sends |
| 14 | Owner escalation | If there is no signed renewal, the owner is alerted and a nudge is drafted | Owner |
Why does the notice date beat the contract end date?
The real deadline is often the notice date. Say a contract renews on its own unless someone cancels 30 days before the end. A 60 day reminder counted from the end date lands 30 days before the notice deadline, and a 14 day reminder lands 16 days after it.
Store both dates in your contract sheet: the end date and the notice period in days. When auto-renew is on, count the timeline from the notice date. When it is off, count from the end date. Notice rules vary by agreement and jurisdiction, so read your own contract or ask your lawyer.
What do rules do and what does Claude do?
Rules do the timing. n8n reads the contract sheet each morning at 8 am, works out the days left, picks the stage and updates the stage column.
Claude drafts two things from facts you supply: the internal brief and the client email. The facts come from your weekly report summaries and client health scores. Claude must not invent results or pricing. n8n saves the email as a Gmail draft and never sends it. A person reviews and sends every message.
Why not use Stripe's upcoming invoice event as the reminder?
Stripe's invoice.upcoming event is sent a few days before renewal, set by the Upcoming renewal events setting in the Dashboard. It only fires for subscriptions that charge automatically. That is too late for a renewal conversation, so drive reminders from the contract end date and use Stripe for payment events.
Stripe also documents a subscription_schedule.expiring event, sent 7 days before a schedule expires. We have not tested it as a renewal trigger, so check it before you rely on it.
What does your contract sheet need?
Add one row per retainer with these columns: client, monthly value, start date, end date, notice period in days, auto-renew yes or no, account lead, and a stage column that records the last reminder sent.
You can also read dates from HubSpot or Pipedrive deals. Check this first: we have not confirmed that custom end-date fields work through their n8n nodes, so test one before you move the dates out of the sheet.
Our estimate: 4 to 6 hours to build, based on one sheet read, one stage rule, one prompt, one draft step and one Slack step. If you want this built for your agency, book a free call.
Sample email
Subject: Planning your next retainer term
Hi [Client first name],
Your retainer runs until [end date]. I would like to plan the next term with you before then.
Over the last [number] months we [result 1] and [result 2]. [Metric] moved from [start value] to [current value].
For the next term, I suggest [term length] with [what is included]. Could we find 20 minutes in the next week to talk it through?
Thanks, [Your name]
Frequently asked questions
How many days before a retainer ends should I send a renewal reminder?
A workable timeline is 60 days for internal prep, 30 days for the client proposal and 14 days for the owner follow-up. Check your contract's notice period first, because the notice date may come before the end date.
Why count from the notice date?
A contract that renews unless cancelled 30 days before the end has a deadline earlier than the end date. Store both dates and count the timeline from the notice date when auto-renew is on.
Can Stripe send retainer renewal reminders for me?
Not well. Stripe's invoice.upcoming event is sent a few days before renewal and only for subscriptions charged automatically. That is too late for a renewal conversation.
Does Claude send the renewal email?
No. Claude drafts the email from facts you supply, and n8n saves it as a Gmail draft. A person reviews and sends every message.
Related automations
Weekly client report
Report draft waits in Gmail
Client health checks
Weekly score, red flags first
Payment reminders
Late invoices get a reminder
Upsell triggers
Upsell drafts you approve
Invoice on signature
Invoice sent the same day
Want these running in your agency?
Book a free call. We look at your process, pick the automations that fit and tell you what the build involves. There is no price on this page, because it depends on what you need.
Book your free call
Tell us a little about your agency. After you send it, you pick a time on the calendar.
Build times and time saved are estimates, tool plans and features change, so test every automation on your own plan before you rely on it.
