Compliance & Legal

How to review a vendor contract as Small IT and ITOps Teams

Compliance & LegalFor Small IT and ITOps Teams3 apps10 steps~20 min to set up

You're a 2-person IT team and vendor contracts live in a shared Google Drive folder nobody has organized since 2023. The Okta renewal snuck up on you last quarter — 30% price increase, auto-renewed, and you found out when the invoice hit the company card. Jira, Jamf, Datadog, Zoom, Kandji — each one has a different renewal date, a different account rep, and a different set of usage clauses you half-remember agreeing to. You don't have a legal team. You don't have a procurement team. You have a spreadsheet someone started and stopped updating, and a calendar reminder that says 'Okta renewal???' that you snoozed.

Build this on Starch → See the apps used

Compliance & LegalFor Small IT and ITOps Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A centralized vendor contract tracker that surfaces renewal dates, auto-renewal clauses, and spend totals across your entire IT SaaS stack — built by describing what you need, not dragging widgets around

An automated alert system that pings you in Slack or Gmail 60, 30, and 7 days before any contract renewal — no more surprises on the company card

A review workflow that pulls contract PDFs, extracts key terms, and drafts a plain-English summary of risk clauses so you can walk into a renewal negotiation actually knowing what you agreed to last time

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Contract Lifecycle Management Email Agent Knowledge Management

Data sources & config

Connect Gmail as a scheduled-sync provider — Starch syncs your Gmail messages on a schedule and scans for contract-related threads, vendor invoices, and pricing change notices. Connect Slack from Starch's integration catalog; the agent queries it live to deliver renewal alerts to your IT channel. Connect Notion as a scheduled-sync provider so contract summaries and vendor runbook pages stay current. Browser automation handles any vendor portal — vendor self-service portals, DocuSign or PandaDoc signing pages, and SaaS admin consoles that don't expose an API — no API needed. Contract Lifecycle Management (coming soon) will handle end-to-end CLM once live; today, this recipe uses Email Agent and Knowledge Management together to replicate the core review-and-track workflow.

Prompts to copy

Build me a vendor contract tracker for my IT stack. I need to track renewal dates, auto-renewal windows, contract value, and any usage or data-processing clauses for tools like Okta, Jamf, Datadog, Zoom, and Jira. Alert me in Slack 60, 30, and 7 days before each renewal. Pull contract details from Gmail threads and flag any emails where a vendor is referencing pricing or terms changes.

When a new vendor contract PDF lands in my Gmail, summarize the key terms in plain English: contract length, auto-renewal clause, price escalation terms, termination notice window, and any data residency or security obligations. Draft a short internal summary I can paste into our Notion runbook.

Create a knowledge base page for each vendor in our IT stack. Auto-populate it with: contract expiry, last renewal cost, account rep contact, SLA commitments, and a link to the contract file. Detect when any page hasn't been updated in 90 days and flag it for review.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Gmail to Starch as a scheduled-sync provider. Starch syncs your inbox on a schedule and the agent scans for messages from known vendors, finance team flagging invoices, and any thread containing words like 'renewal,' 'price increase,' or 'updated terms.'

2 Upload your existing vendor contracts as PDFs or paste links to Google Drive folders. Describe to Starch: 'Parse each of these contracts and extract vendor name, contract start/end date, auto-renewal date, annual value, termination notice window, and any data processing or security clauses.'

3 Starch builds a vendor contract tracker app. Each row is a vendor; columns include contract value, renewal date, auto-renewal window, days until renewal, and a plain-English risk summary. You can sort by 'renewal within 90 days' to see what's urgent right now.

4 Set up automated alerts: describe the automation as 'Every morning, check my vendor tracker for contracts renewing within 60, 30, or 7 days. If any exist, send me a Slack message in #it-ops with the vendor name, renewal date, annual spend, and auto-renewal clause.' Starch builds and schedules this.

5 For each upcoming renewal, trigger a contract review: 'Pull the most recent contract for [Vendor]. Summarize the key commercial terms, flag any clauses where the vendor has unilateral rights to change pricing or data handling, and draft a 5-bullet summary I can send to our CFO.'

6 Use browser automation to check vendor portals for usage data before renewals. Describe: 'Log into our Zoom admin console and pull the number of active licensed users from the last 90 days. Compare to the seats we're paying for and flag any overage or underutilization.' Starch automates this through your browser — no Zoom API configuration needed.

7 Wire your Notion knowledge base to Starch as a scheduled-sync provider. For each vendor, auto-create or update a page with: contract terms summary, account rep name and email, SLA commitments, last renewal cost, and a link to the contract file stored in Drive.

8 After each review, log the outcome: 'Update the Okta page in Notion with the outcome of the March 2026 renewal — new contract value $18,400/year, 12-month term, auto-renews April 1 2027, 30-day cancellation window. Set a Slack alert for March 1 2027.'

9 Build a 'contracts expiring this quarter' dashboard. Describe: 'Show me all vendor contracts renewing in the next 90 days, sorted by annual spend, with a column for whether I've started the review yet and whether the auto-renewal window has already opened.'

10 For SOC 2 or compliance audit prep, generate a vendor inventory report: 'List all vendors with access to employee data or customer data, their contract expiry dates, whether we have a DPA on file, and any security review date. Format it as a table I can share with our auditor.'

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 IT Contract Renewal Sprint — 4 vendors, $94,000 in annual spend

Sample numbers from a real run

Okta (SSO + MFA, 310 seats)	38,200
Jamf Pro (MDM, 285 devices)	21,600
Datadog (infra monitoring, 8 hosts)	19,400
Zoom (video, 40 licensed seats)	14,800

In January 2026, you run the contract tracker query and surface four renewals hitting between March and April. The Okta contract auto-renews March 15 — the auto-renewal window opened January 14, which you've already missed if you wanted to cancel, but you still have 30 days to negotiate terms. Starch's Gmail sync catches a thread from late December where Okta's account rep mentioned 'updated pricing tiers for 2026' — you'd missed it at the time. The agent summarizes: 'Okta's email on December 19 references a 12% price increase on the Professional tier for renewals after February 1. Your current contract is $33,200; the new rate applied to 310 seats would be $38,200.' That's a $5,000 delta you now have three weeks to push back on. For Jamf, the browser automation logs into the Jamf console and confirms 261 of your 285 licensed devices have checked in within the last 60 days — 24 seats potentially recapturable. Starch drafts a vendor summary for your CFO: four renewals, $94,000 total, two with active negotiation levers (Okta pricing increase, Jamf seat reduction), one DPA that hasn't been updated since 2023 (Datadog). The whole sprint — which previously took a week of calendar spelunking and inbox archaeology — runs in an afternoon.

Measurement

How you'll know it's working

Days of advance notice before auto-renewal window closes (target: 60+ days for any contract over $10K/year)

Percentage of IT SaaS contracts with a current DPA or security review on file (audit readiness)

Unused license ratio per tool — seats paid vs. seats active in the last 90 days (Zoom, Jamf, Okta)

Annual IT SaaS spend delta year-over-year, broken down by vendor price increases vs. headcount growth

Time to complete contract review from kick-off to CFO summary (target: under 2 hours per vendor)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Drive folder + spreadsheet tracker

Free and you already have it, but the tracker is always stale, nobody updates it after the renewal, and it won't alert you when an auto-renewal window opens.

Ironclad or Contractbook (dedicated CLM)

Built specifically for contract lifecycle management, but priced for legal teams at $500–$1,500/month — hard to justify for a 2-person IT team that doesn't originate contracts, just tracks them.

Notion + manual calendar reminders

Decent for a knowledge base, but the reminders are only as good as whoever last touched the page, and it won't parse a PDF contract or pull Gmail threads automatically.

Vendr or Spendflo (SaaS procurement platforms)

Useful if you want a managed buying service, but they take a cut of savings and are designed for larger procurement volumes — overkill if you're just trying to not miss your Okta renewal.

On Starch RECOMMENDED

One platform — contract lifecycle management, email agent, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Starch isn't SOC 2 certified — should I be putting contract PDFs into it?

Honest answer: Starch is not SOC 2 Type II certified today. If your contracts contain highly sensitive data (customer PII, trade secrets) and your company's security policy requires SOC 2 for any SaaS tool handling that data, check with your CISO before uploading. For most IT vendor contracts — SLAs, pricing, renewal terms — the risk profile is lower. Starch does not store contract files itself; it processes them at the time of review and writes summaries to your connected Notion or Google Drive.

Can Starch actually read a PDF contract and pull out the right clauses?

Yes. You describe what you want extracted — 'pull the auto-renewal clause, termination notice window, and any price escalation language' — and the agent parses the document and returns those fields. It won't always be perfect on dense legalese, which is why the output is a draft summary for you to review, not a final legal opinion. Think of it as turning a 40-page PDF into a 5-bullet brief you can actually act on.

What if my vendors use a portal for contract access instead of emailing PDFs?

Starch automates browser-reachable portals — no API needed. If you can log into a vendor's contract portal and download a PDF manually, describe the steps to Starch and it automates them through your browser. Works for DocuSign, PandaDoc, and most vendor self-service portals.

Does Starch have a dedicated contract management app right now?

Contract Lifecycle Management is coming soon — request beta access on the Starch site to get notified when it launches. Today, you build the same core workflow by combining the Email Agent (Gmail sync for contract threads and vendor alerts) and Knowledge Management (Notion-connected vendor runbooks) as a custom Starch app. The prompts in the recipe above are exactly how you'd describe it.

We already use Jira Service Management for IT tickets — does Starch replace that?

No, and it shouldn't try to. You keep Jira for ticket management; Starch connects to Jira from its integration catalog and queries it live when an app or automation needs that data. A practical example: an automation that detects a vendor renewal is approaching and automatically opens a Jira ticket in your IT project with the review checklist attached. Starch builds the in-between logic; Jira stays the system of record for ticketing.

Can Starch alert me in Slack when a renewal is approaching?

Yes. Connect Slack from Starch's integration catalog; the agent queries it live to send messages. Describe the alert exactly as you want it: channel, frequency, what information to include. A common setup is a daily 9am check of the contract tracker that posts to #it-ops only when a renewal is within 30 days — quiet until it matters.