Auto-Renewal Notice & Opt-Out Workflow
Build an internal tool that tracks contractual renewal-notice deadlines, drafts the required notice, routes it for human approval, sends it via email, and logs delivery plus any customer opt-out - so legally required notices go out on time and you have proof.
A login-protected tool where you import contracts, see exactly which renewal notices are due, review and approve each AI-drafted notice, send it, and keep a tamper-evident log of who was notified, when, and whether they opted out.
Before you start
- A contracts export you can download (CSV or Google Sheet): customer, term dates, auto-renew terms, notice period, owner
- Your notice templates and the notice rules per contract type
- Free accounts: Vercel, Supabase, Resend
- A computer with Claude Code installed
The problem this kills
Auto-renewing contracts come with a clock you can't see. Most agreements require you to notify the customer a set number of days before they renew - "60 days' written notice" - and if that notice slips, you either miss a renewal you were owed or, worse, trap a customer in a renewal they could legally have escaped. Either way you have a dispute, and you have no proof of what was sent or when.
Today that clock lives in a spreadsheet someone forgets to open, a calendar reminder that got snoozed, and a pile of "I'm pretty sure we emailed them" guesses. The notice math is fiddly - business days, time zones, different notice periods per contract type - and one missed deadline can cost you a renewal or a lawsuit.
What you'll build
A small internal web app that does the watching for you. You import your contracts, and the tool computes the exact notice deadline for each one. When a notice comes due, it drafts the required wording from the actual contract terms, hands it to the owner to review, and only sends it after a human approves. Every send is logged with proof of delivery, and when a customer asks to opt out, that request is reviewed and flips the renewal status so nobody renews them by mistake.
What's inside the Implementation Plan
The plan is a complete, paste-and-go runbook for Claude Code. It opens by interviewing you about your business - your contract types, your notice rules, how your dates and customer IDs are actually named, your real and peak volumes, and your messy edge cases - then it reads back a short tailored spec for your thumbs-up before it builds anything. That is the difference between a generic template and a tool that fits how you actually work.
From there it walks the agent through the build step by step, each step ending in a ready-to-paste prompt: the data model and import, the notice-deadline math (business days and time zones handled correctly), the AI draft, the human approval gate, sending via Resend with delivery logging, opt-out capture, and a full audit + CSV export. It also includes a "No API yet?" path so you can run the whole thing from a Google Sheet today, even with no integration to your CRM or contract system.
The governance it includes (this is the point)
This is not a "blast emails from a script" tool. It is built so a careful renewals team can stand behind every notice:
- Login so only your team can use it.
- Row-level security so each person and org only sees their own contracts and notices.
- A complete audit trail - who drafted, who approved, what was sent, and when.
- A hard human approval gate before any notice leaves the building - the AI drafts, a person checks the terms, dates, and recipient, and only then does it send.
- Duplicate guards keyed on contract + term, so the same renewal cycle can never get two notices.
- Proof of delivery stored against every notice, and opt-outs that actually change the renewal record.
Who it's for
Renewals and ops teams and account managers at companies with auto-renewing contracts and notice obligations - anyone who has ever lost sleep over a 60-day notice window or had to prove, after the fact, that a notice really went out.
You've got this - paste the first prompt and let the agent interview you.