Never Miss a Vendor Renewal
By the end of this recipe, no contract will quietly auto-renew behind your back — Copera watches every vendor renewal and, weeks before the term rolls over, warns the owner in time to keep, renegotiate, or cancel. Because your contracts, your finance board, and your team chat all live in one workspace, the warning reaches the right person on its own instead of waiting for someone to notice a date in a spreadsheet.
Readiness: Available now (built as two Automations). The version where a single named teammate watches every renewal on its own schedule is rolling out in early access.
What it does
Most wasted vendor spend isn't a negotiation problem — it's a calendar problem. A SaaS subscription, an insurance policy, a lease, or a service agreement quietly auto-renews for another full term, often at a higher price, because the window to cancel closed while everyone was busy. By the time anyone looks, you're locked in and paying for a tool half the team stopped using.
This recipe fixes that by warning you ahead of two dates that matter, not one:
- The renewal date — when the term rolls over. You want a heads-up here early enough to actually evaluate the contract and renegotiate.
- The notice deadline — the last day you can give notice to cancel before it auto-renews. This is the real point of no return, and it usually falls 30–90 days before the renewal date. Miss it and the decision is made for you.
So the system is two automations on one Vendor Contracts board, each firing on a different date:
| When it fires | Watches | What happens |
|---|---|---|
| 90 days before the renewal date | Renewal date | Flags the contract In review, drafts a keep / renegotiate / cancel brief from the contract's own data, DMs the owner, and posts a heads-up in your finance channel. |
| 14 days before the notice deadline | Notice deadline | The last-call alarm — for any auto-renewing contract still undecided, it pings the owner and your finance lead so the cancellation window never closes on you by accident. |
The first automation gives you runway to make a good decision; the second makes sure you don't lose the chance to. Together they turn "we forgot to cancel that again" into a thing that can't happen.
Build it yourself
One-time setup
Make a board with a table for contracts. Add fields for Vendor, Owner (a people column), Category (Software, Insurance, Lease, Services…), Annual cost (a number), Renewal date (a date), Notice deadline (a date — the last day to give notice), Auto-renews? (yes/no), Status (a single-select: Active, In review, Renegotiating, Renewing, Canceling, Expired), and a Notes field for the review brief and a link to the contract. This board is your renewal watchlist and your archive in one place. See Creating a Board if you're starting fresh.
The Notice deadline is what makes this recipe more than a due-date reminder. If you know it from the contract, enter it. If all your contracts in a category share the same notice period — say every SaaS deal needs 60 days' notice — add a small automation with a Row created trigger and a Set date relative action that sets the Notice deadline to the Renewal date minus 60 days, so it fills itself in whenever you add a contract. For mixed notice periods, just enter the deadline per row.
Automation 1 — the renewal review kickoff
In Automations, add a Date reached trigger on the Renewal date field with a before offset — for example 90 days before. Because the trigger evaluates per row, it fires once for each contract, exactly 90 days ahead of that contract's own renewal. (The offset can be days, weeks, or months, so tune the lead time to how long your review actually takes.)
Add a Row filter condition so the flow continues only when Status is Active — a contract you've already put in review or lined up to cancel doesn't need to start the process over.
Add an AI → Generate step that writes a short keep / renegotiate / cancel brief from the row's own fields — the vendor, the annual cost, what it's for, and the two dates: "Summarize this vendor contract in three lines — what it's for, the annual cost, and a recommendation to keep, renegotiate, or cancel — and state the notice deadline plainly." Add an Update row action to store that brief in the Notes field so it's on the record.
Add a Set field action to move Status → In review. This is what puts the contract on the active watchlist and, importantly, stops Automation 2 from later treating it as "undecided."
Add a Send direct message to the contract Owner with the brief and a link to the row, and a Post channel message to your finance or procurement channel: "⏰ [Vendor] renews in 90 days — $[annual cost]/yr. Decide: keep, renegotiate, or cancel. Notice due by [notice deadline]." Internal messages like these send on their own — nothing here goes to the vendor.
Automation 2 — the auto-renew guard
This is the automation that actually saves the money — the last-call alarm before the cancellation window shuts.
Add a Date reached trigger on the Notice deadline field with a before offset — for example 14 days before. It fires two weeks ahead of the last day you can cancel, leaving time to act.
Add a Row filter condition with an AND group: Auto-renews? is Yes and Status is In review. That's the exact danger set — contracts that will roll over on their own and that no one has decided to keep or cancel yet. A contract already marked Renewing or Canceling has an owner on it, so it's skipped.
Add a Send direct message to the Owner with an urgent tone and the hard date: "🚨 Last call — you must give notice by [notice deadline] or [Vendor] auto-renews at $[annual cost]/yr." Add a Send notification to your finance lead (or a Post channel message to the finance channel) so a second person sees it. Now the deadline can't slip past one distracted inbox.
If you want the exit teed up, add a Send or draft email action in draft mode addressed to the vendor's contact, with a cancellation-notice draft the owner can review and send in one click. Keeping it a draft means nothing leaves for a vendor without a person approving the wording first.
Layer the lead times into a cadence. Each automation has exactly one trigger, so make each warning its own small automation on the same board: a 90 days before renewal kickoff, a 30 days before renewal nudge, and the 14 days before the notice deadline guard. Three tiny automations turn a single reminder into a real renewal cadence that escalates as the date closes in.
Or just ask Copera AI
You don't have to build the graphs by hand. Open Ask Copera AI and describe the whole thing:
"Create a Vendor Contracts board with columns for vendor, owner, category, annual cost, renewal date, notice deadline, whether it auto-renews, and a status. Then build an automation that 90 days before each renewal date sets the contract to 'In review,' drafts a keep/renegotiate/cancel brief, DMs the owner, and posts a heads-up in our Finance channel. Add a second automation that 14 days before the notice deadline — only for auto-renewing contracts still marked 'In review' — alerts the owner and our finance lead so we never miss the cancellation window."
Ask Copera AI can create the board and its columns, then assemble both automations for you. With the default Ask before acting permission mode, it shows a review card for each change before anything is created — so you approve the board and each automation before it exists. See What Copera AI Can Do for the full capability list.
You can also use it any time as an on-demand check: "List every vendor contract renewing in the next 90 days, with the annual cost and notice deadline, soonest first — and flag any that auto-renew and aren't in review yet." It reads the board and answers on the spot.
Make it a standing teammate
Standing AI teammates are rolling out gradually. When one is available in your workspace, a single named teammate — a "Vendor Watch" — can own this end to end: watch every renewal date and notice deadline, flag contracts for review, draft the briefs, keep the board's status current, and alert owners and finance, all on its own schedule and under its own identity. A teammate works inside your workspace — it can create and update rows, post to channels, and DM owners, but it never deletes data and never sends outside the workspace, so any vendor-facing cancellation email still routes through the automation's draft step for a person to send. Until teammates reach you, everything in this guide can be built today as an Automation. See AI teammates for what's coming.
Tips
Add a weekly "what's renewing" digest. Alongside the per-contract alerts, build a standing view for finance: a Schedule trigger every Monday, a Find rows action for contracts renewing in the next 90 days (or with a notice deadline coming up), an AI → Summarize step to turn them into a readable list grouped by owner and cost, and a Post channel message to your finance channel. Now the whole team starts the week looking at the same watchlist.
Give owners a one-click "Start cancellation." Place a Manual action button on each row labeled Start cancellation. When the owner clicks it, the automation can Set field Status → Canceling and add a Send or draft email in draft mode with the cancellation notice ready to review. The decision to walk away becomes a single, deliberate click with a paper trail.
Push alerts where your team already is. If procurement lives in Slack, swap the channel message for a Slack → Message action; if another system tracks spend, add a Call webhook action so the renewal signal lands there too. See Connectors for the external apps automations can reach.
Set a spend cap. Because the kickoff automation drafts a brief with AI across every contract, give it a per-automation spend cap and keep an eye on the usage dashboard, so a month full of renewals never runs past a budget you choose.
Close the loop when the decision is made. Add a small companion automation with a Field changed trigger on Status: when it moves to Renewing, use Set date relative to roll the renewal date forward a year; when it moves to Canceling or Expired, post a "✅ Dropped [Vendor] — $[annual cost]/yr saved" note to your finance channel. The board stays current on its own.
Frequently Asked Questions
Can Copera remind me before a contract auto-renews?
Yes. A Date reached trigger fires a set number of days before each contract's renewal date and before its notice deadline. Weeks ahead, the automation flags the contract for review, drafts a keep / renegotiate / cancel brief, and messages the owner — so an auto-renewal never rolls over before you've decided.
How does Copera stop a surprise auto-renewal?
With the auto-renew guard — a second automation that watches the notice deadline, the last day you can cancel before the term renews. It fires a set number of days before that deadline, but only for auto-renewing contracts no one has decided on yet, and alerts both the owner and your finance lead. That's the point-of-no-return alarm that keeps you off zombie subscriptions.
How does Copera track vendor renewal dates?
Each contract is a row on a Vendor Contracts board, with fields for the vendor, owner, annual cost, renewal date, notice deadline, whether it auto-renews, and a status. The board is your single source of truth, and the automations read those dates to warn you at the right moment.
Can I get warned at more than one lead time, like 90 and 30 days?
Yes. An automation has one trigger, so build a small one per lead time — a 90-day heads-up to start reviewing, a 30-day nudge, and a last-call alert before the notice deadline. Layering the before offsets turns a single reminder into a full renewal cadence.
Can Copera draft the cancellation notice to the vendor?
Yes. Put a Manual action button on the row; clicking it can set the status to Canceling and draft the cancellation email with a Send or draft email step in draft mode. Because it's a draft, a person reviews and sends it — nothing ever leaves for a vendor without human sign-off.
Where do the contracts come from?
You enter them as rows, import them, or have new contracts land as rows from a form your team fills in when a deal is signed. However they arrive, the board keeps the renewal date and notice deadline in one place for the automations to watch.
Related
- Automations — the Date reached trigger, conditions, and messaging actions this recipe is built from
- Never Miss a Renewal or Upsell — the same date-driven pattern for the customer side: your renewals and expansions
- Automate Overdue-Invoice Follow-Ups — the finance-ops cousin, for money owed to you
- An AI Deadline Concierge — the general "warn before a date" pattern for any due date
- Connectors — push renewal alerts to Slack or an external system
- What You Can Build with Copera AI — the full playbook