RenewalRadar — The Vendor Contract Expiry Monitor That Stops Your SaaS Stack From Auto-Renewing Into a Budget Crisis
Every ops manager has a horror story about a $30k annual contract that auto-renewed while they were on holiday. RenewalRadar ingests your vendor contracts via email forward or PDF upload, extracts renewal dates and cancellation windows with Claude, and pings you 90, 30, and 7 days before you lose the option to renegotiate. It is the fire alarm you install before the fire.
Difficulty
beginner
Category
Business Automation
Market Demand
High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
5/10
What is it?
Bootstrapped companies and SMB ops teams track vendor renewals in a shared Google Sheet that nobody updates. Contracts live in inboxes, Dropbox folders, and DocuSign archives. By the time someone notices the renewal, the cancellation window has closed and finance is furious. RenewalRadar solves this with a simple two-step flow: forward any vendor contract email or upload a PDF, and Claude extracts the vendor name, contract value, renewal date, cancellation notice period, and auto-renewal clause. The system calculates alert windows automatically and sends Slack or email nudges on schedule. At $49/month for teams managing 10+ vendors, this pays for itself by catching one auto-renewal per year. Buildable in 2 weeks with Next.js, Claude for PDF extraction, Supabase, and Resend. The email parsing approach mirrors how Missive and Superhuman handle structured email data — proven, stable APIs.
Why now?
The June 2026 SaaS consolidation wave has ops managers actively auditing their vendor stacks after budget cuts — there is a peak moment of intent to track renewals that makes this a pull rather than push sale right now.
- ▸PDF and email forward ingestion with Claude extraction of renewal date, value, and cancellation window
- ▸Automated alert schedule: 90, 30, and 7 days before cancellation deadline, not renewal date
- ▸Slack and email nudge delivery with one-click snooze or mark-as-reviewed
- ▸Dashboard showing upcoming renewals sorted by days remaining and contract value at risk
Target Audience
Ops managers and finance leads at SMBs with 10-200 employees managing 10+ SaaS and vendor contracts — estimated 500k such businesses in the US
Example Use Case
An ops manager at a 40-person startup uploads 15 vendor contracts on Monday, RenewalRadar surfaces three renewals in the next 90 days including one $24k annual tool they planned to cancel, and the team cancels in time saving $24k.
User Stories
- ▸As an ops manager, I want to upload a vendor contract PDF and have renewal and cancellation dates extracted automatically, so that I never manually read another contract to find the auto-renewal clause.
- ▸As a finance lead, I want a Slack alert 30 days before any contract cancellation window closes, so that I have time to evaluate and cancel before being locked into another year.
- ▸As a team admin, I want to see all vendor renewals sorted by days remaining and dollar value at risk, so that I can prioritize which renewals need renegotiation this quarter.
Done When
- ✓PDF extraction: done when uploading a contract PDF shows extracted vendor name, dollar value, renewal date, and cancellation deadline in editable fields within 20 seconds.
- ✓Alert delivery: done when a contract with a 30-day deadline triggers a Slack message containing vendor name, contract value, and a link to the dashboard card.
- ✓Dashboard view: done when all confirmed contracts appear sorted by days_until_cancel_deadline with a red/amber/green color indicator per urgency tier.
- ✓Billing: done when a free user with 4 contracts is prompted to upgrade, completes Stripe checkout, and immediately sees all contracts without the paywall.
Is it worth building?
$49/month x 100 teams = $4,900 MRR at month 4. $99/month x 50 larger teams = $4,950 MRR. Math assumes 4% conversion from cold outreach to ops managers on LinkedIn at a 10% reply rate.
Unit Economics
CAC: $40 via LinkedIn cold outreach at 5% conversion. LTV: $1,176 (24 months at $49/month). Payback: 1 month. Gross margin: 91%.
Business Model
SaaS subscription
Monetization Path
Free: 3 contracts. $49/month: unlimited contracts, Slack integration, 3 team members. $99/month: custom alert rules, CSV export, 10 seats.
Revenue Timeline
First dollar: week 3 via cold outreach conversion. $1k MRR: month 2. $5k MRR: month 6.
Estimated Monthly Cost
Claude API: $35, Supabase: $25, Vercel: $20, Resend: $15. Total: ~$95/month at launch.
Profit Potential
Full-time viable at $5k MRR given low churn from sticky ops workflows.
Scalability
High — add contract negotiation benchmarks, spend analytics, and a B2B reseller tier for accounting firms managing clients.
Success Metrics
Week 3: 10 paying teams. Month 2: 40 teams. Month 4: less than 5% monthly churn.
Launch & Validation Plan
Cold email 50 ops managers at Series A startups offering free setup for their entire vendor stack, aim for 10 yes replies before writing code.
Customer Acquisition Strategy
First customer: DM 30 ops managers in the Lenny's Newsletter Slack and Operations Nation community offering free onboarding for their full contract stack in exchange for a 20-minute feedback call. Ongoing: LinkedIn content about auto-renewal horror stories, ProductHunt launch, r/startups, accounting firm partnerships.
What's the competition?
Competition Level
Medium
Similar Products
Ironclad (enterprise CLM, $500+/month), ContractSafe ($99+/month, no AI extraction), Google Calendar reminders (manual, zero extraction) — none combine AI extraction with cancellation-window-aware alerts for SMBs.
Competitive Advantage
Alerts on cancellation deadline not renewal date — the critical distinction competitors miss. Simpler than Ironclad or ContractPodAi which cost $500+/month for SMBs.
Regulatory Risks
Contract PDFs may contain confidential data — must document that files are processed by Claude API and not stored beyond extraction. GDPR: EU contract data requires documented processing agreement. Low regulatory risk beyond standard SaaS data handling.
What's the roadmap?
Feature Roadmap
V1 (launch): PDF extraction, review step, alert schedule, Slack and email delivery, Stripe billing. V2 (month 2-3): email forward ingestion, spend analytics dashboard, CSV export. V3 (month 4+): multi-language contracts, negotiation benchmark data, accounting firm reseller tier.
Milestone Plan
Phase 1 (Week 1-2): extraction API, review UI, cron alert engine, Supabase schema live. Phase 2 (Week 3-4): Slack integration, Stripe billing, 5 beta teams onboarded. Phase 3 (Month 2): ProductHunt launch, 30 paying teams.
How do you build it?
Tech Stack
Next.js, Claude API for PDF and email extraction, Supabase, Resend for alerts, Slack API for nudges — build with Cursor for extraction logic, v0 for dashboard UI
Suggested Frameworks
pdf-parse for PDF text extraction, LangChain for structured output from Claude, Resend SDK
Time to Ship
2 weeks
Required Skills
PDF text extraction, Claude structured output, Next.js, Supabase, Resend webhooks.
Resources
Anthropic API docs, pdf-parse npm docs, Resend docs, Slack API webhooks, Supabase storage.
MVP Scope
app/page.tsx (landing), app/dashboard/page.tsx (contract list sorted by renewal), app/api/upload/route.ts (PDF ingest + Claude extraction), app/api/alert/route.ts (Resend/Slack trigger), lib/extract.ts (Claude structured output for contract fields), lib/db/schema.ts (contracts, alerts, users, teams), components/ContractCard.tsx (renewal timeline card), scripts/cron.ts (daily alert check via Vercel cron), .env.example (SUPABASE_URL, ANTHROPIC_KEY, RESEND_KEY, SLACK_WEBHOOK)
Core User Journey
Upload contract PDF -> Claude extracts renewal and cancellation dates -> review extracted data -> confirm -> receive Slack alert 30 days before deadline.
Architecture Pattern
PDF upload -> Supabase Storage -> Claude API extracts fields -> structured data stored in Postgres -> Vercel cron runs daily -> computes days until cancellation deadline -> Resend or Slack webhook fires alert.
Data Model
User belongs to Team. Team has many Contracts. Contract has vendor_name, value, renewal_date, cancellation_deadline, status. Contract has many Alerts with scheduled_at and sent_at.
Integration Points
Claude API for PDF and email text extraction, Supabase for contract and alert storage, Resend for email alerts, Slack API for channel nudges, Stripe for billing, Vercel cron for daily alert checks.
V1 Scope Boundaries
V1 excludes: contract negotiation, spend analytics, e-signature integration, mobile app, multi-language contracts, API access for third parties.
Success Definition
An ops manager at a company the founder has never contacted finds RenewalRadar via Google, uploads their contracts, sets up Slack alerts, and pays $49/month without any onboarding help.
Challenges
The hardest non-technical problem is convincing ops managers to trust an AI extraction of legally important dates — requires a clear human-review step before alerts go live, or adoption stalls from the first wrong date.
Avoid These Pitfalls
Do not skip the human review step before alerts go live — one wrong date causes a missed renewal and destroys trust instantly. Do not store raw PDFs longer than 24 hours after extraction — legal sensitivity of contract data makes customers nervous. Do not auto-calculate cancellation deadlines without surfacing the source clause so ops managers can verify.
Security Requirements
Supabase Auth with Google OAuth, RLS on all team-scoped tables, PDFs deleted from storage after 24 hours post-extraction, rate limit 20 uploads/hour per team, GDPR data deletion endpoint.
Infrastructure Plan
Vercel for Next.js and API routes, Supabase for Postgres and temporary file storage, Vercel cron for daily alerts, Sentry for error tracking, GitHub Actions for CI, ~$95/month.
Performance Targets
200 DAU at launch, 500 req/day, Claude extraction under 8 seconds per PDF, dashboard load under 1s with Supabase indexed queries on team_id and cancel_deadline.
Go-Live Checklist
- ☐RLS verified on contracts and alerts tables.
- ☐Stripe tested on free-to-paid upgrade flow.
- ☐Sentry configured and receiving test errors.
- ☐Vercel cron verified firing daily at 9am UTC.
- ☐Custom domain with SSL live.
- ☐Privacy policy covering PDF processing and deletion published.
- ☐5 beta ops managers confirmed extraction accuracy on real contracts.
- ☐Rollback: Vercel instant rollback available.
- ☐Launch post drafted for Lenny Slack and LinkedIn.
First Run Experience
On first run: three demo vendor contracts are pre-loaded showing upcoming renewals at 85, 28, and 6 days. User can immediately see the color-coded urgency dashboard and click any card to see extracted fields. No manual config required: demo data populates without login, Slack and email alerts configurable after sign-in.
How to build it, step by step
1. Define Supabase schema: contracts(id, team_id, vendor, value, renewal_date, cancel_deadline, status), alerts(id, contract_id, scheduled_at, sent_at, channel). 2. Build /api/upload POST route that accepts PDF, extracts text with pdf-parse, sends to Claude for structured JSON extraction of vendor, value, dates, and cancellation window. 3. Create review UI where users see extracted fields and can edit before confirming. 4. Write scripts/cron.ts that runs daily, queries contracts where cancel_deadline is 90, 30, or 7 days away, and queues alerts. 5. Implement /api/alert route that sends Resend email and optional Slack webhook per alert. 6. Build dashboard page with ContractCard components sorted by days_until_deadline. 7. Add Supabase Auth with Google OAuth and team invite via email. 8. Add Stripe billing with free 3-contract tier and $49/$99 paid tiers. 9. Configure Vercel cron job for daily alert check at 9am UTC. 10. Deploy and walk full journey: upload a real contract PDF, verify extracted dates, wait for cron to fire, confirm Slack message arrives.
Generated
June 20, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.