Compliance & Legal

How to review a vendor contract as Chief of Staff and Founder's Office

Compliance & LegalFor Chief of Staff and Founder's Office3 apps12 steps~24 min to set up

Vendor contracts land in your Gmail, get saved to a Google Drive folder someone named 'Contracts_FINAL_v3', and then live there untouched until a renewal date sneaks up on you or legal asks for the original MSA from 18 months ago. As chief of staff, you're the one who actually chases down the signed copies, reminds the CFO that the SaaS tool you're paying $4,200/month for auto-renews in 11 days, and manually tracks which vendors have NDAs in place before procurement conversations go too far. There's no system — there's you, a spreadsheet you made in 2024, and a calendar reminder that fires at the wrong time.

Build this on Starch → See the apps used

Compliance & LegalFor Chief of Staff and Founder's Office3 apps12 steps~24 min to set up

Outcome

What you'll set up

A vendor contract tracker that surfaces renewal dates, contract values, and approval status across all active vendor relationships — built as a custom Starch app on top of your connected Gmail and Notion data

Automated renewal and obligation alerts that Slack you (and the right owner) 60 and 30 days before any contract expiration, without you manually managing the calendar

A searchable contract log where you can ask 'which of our vendors have liability caps below $500k?' and get an answer in seconds instead of opening 14 PDFs

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 Knowledge Management

Data sources & config

Starch syncs your Notion databases on a schedule (pages, databases, users) and connects directly to Gmail to surface contract-related threads. Slack is connected from Starch's integration catalog and queried live when automations send alerts. Google Drive contract PDFs are reached through browser automation — no separate API needed. For any contract tool your team uses that isn't one of these, connect it from Starch's integration catalog of 3,000+ apps.

Prompts to copy

Build me a vendor contract tracker that pulls contract metadata from our Notion database — vendor name, contract value, renewal date, owner, and NDA status — and shows me everything expiring in the next 90 days sorted by ARR impact

Every Monday morning, check which vendor contracts are expiring in the next 60 days and send me a Slack summary with the vendor name, contract value, auto-renewal clause (yes/no), and the internal owner

Create a searchable knowledge base of our active vendor contracts — I'll paste in the key terms for each one — so anyone on the exec team can ask 'do we have an MSA with Greenhouse?' and get an answer without pinging me

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

Walkthrough

Step-by-step

1 Connect Notion to Starch (scheduled sync) — if your contracts or vendor records already live in a Notion database, Starch pulls that schema automatically and you can start querying against it immediately.

2 Connect Gmail to Starch (scheduled sync) — Starch syncs your inbox so the agent can find contract-related threads: executed agreements sent by vendors, countersigned docs, amendment emails, and renewal notices.

3 Tell Starch: 'Build me a vendor contract tracker app with fields for vendor name, contract value, start date, end date, auto-renewal clause, internal owner, and NDA status.' Starch generates the app — you don't drag fields into a form builder.

4 Populate the tracker by pasting or uploading your existing contract inventory. If contracts are stored in Google Drive, Starch reaches those pages through browser automation and can extract key metadata without an API.

5 Set up the 60-day and 30-day renewal alert automation: 'Every Monday, check all vendor contracts expiring in the next 60 days and Slack the contract owner with the vendor name, contract value, and auto-renewal date.' Starch builds and schedules this in one prompt.

6 Add an NDA coverage check: tell Starch to flag any vendor with contract value above $10,000 that doesn't have a signed NDA on record — surface that as a red flag column in the tracker dashboard.

7 Use the Email Triage app (live in the App Store as Founder Inbox) to route inbound vendor contract emails — countersigned docs, amendment requests, renewal notices — into a labeled queue so they don't get buried under other exec comms.

8 Build the searchable contract knowledge base: 'Create a knowledge base where I can store contract summaries and clause notes for each vendor, and let me search by clause type, vendor category, or liability limit.' Starch sets this up using your connected Notion data as the backing store.

9 Wire up the approval workflow by connecting Slack from Starch's integration catalog: when a new contract is logged in the tracker above a threshold value (say, $25,000), Starch posts a Slack message to the CFO and general counsel for sign-off.

10 Test the renewal alert end-to-end by backdating a contract's expiration date to within 60 days and confirming the Monday automation fires the right Slack message to the right owner.

11 Once the Contract Lifecycle Management app launches (currently in development — request beta access), migrate the tracker into it to get AI-assisted clause review, e-signature workflows, and a full audit trail without rebuilding from scratch.

12 Run a quarterly contract audit: tell Starch 'list all vendor contracts where the renewal date is in the next 12 months, the contract value is over $5,000, and the auto-renewal clause is yes — sort by contract value descending.' Use that output for your Q-end vendor review with the CFO.

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

Q2 2026 Vendor Renewal Audit — 7 contracts, $380,000 in ARR at stake

Sample numbers from a real run

Salesforce (CRM)	142,000
Greenhouse (ATS)	38,000
Notion (team wiki)	12,000
Rippling (HRIS)	67,000
Zendesk (support)	44,000
Loom (async video)	9,800
Sentry (error tracking)	18,200

Coming into Q2, you had seven vendor contracts with renewals due between April and June — $380,000 in combined annual value. Without a system, you found out about the Salesforce renewal ($142,000, auto-renews April 15) when the AE emailed your CEO directly two weeks before the deadline. The Starch vendor tracker, built on your Notion contract database and Gmail sync, surfaced all seven contracts in a single view sorted by renewal date. The Monday automation fired on March 31st and Slacked you a summary: Salesforce renews in 15 days with auto-renewal on, owner is your Head of Sales, no renegotiation flag set. You forwarded the alert to the CFO with one click, initiated the Salesforce renegotiation conversation with three weeks of runway instead of two days, and ended up securing a 12% discount on the renewal — $17,040 saved — because you weren't negotiating under deadline pressure. The Greenhouse contract ($38,000) had no NDA on file from the vendor, which the NDA coverage check flagged automatically. You sent the NDA request before the renewal conversation started. Total time spent on the Q2 audit: 40 minutes of setup in Starch, then two hours across the quarter responding to alerts rather than hunting for information.

Measurement

How you'll know it's working

Days of advance notice before contract renewal (target: 60+ days for contracts over $10,000)

Percentage of active vendor contracts with signed NDAs on file

Number of auto-renewals caught and renegotiated before deadline per quarter

Time from contract receipt to fully executed and logged (days)

Annual contract value under active management vs. what's still 'in the Drive folder'

Comparison

What this replaces

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

Google Drive folder + shared spreadsheet

Free and already in use, but the spreadsheet is always one person's side project — it goes stale, renewal alerts are manual calendar reminders, and there's no way to query across contract terms without opening every PDF yourself.

Ironclad or Icertis (enterprise CLM)

Purpose-built contract lifecycle tools with strong legal workflows, but implementation runs months and pricing is built for legal teams at 500+ person companies — not a 150-person company where the chief of staff is also running board prep.

Notion standalone (contract database template)

Notion works well as a structured repository, but it doesn't alert you on renewals unless you build an automation separately, can't read contract metadata out of Gmail threads, and has no AI to answer 'which vendors have liability caps under $500k?' across your database.

DocuSign CLM or PandaDoc

Strong e-signature and template workflows for contracts you're sending out, but weak on the tracking and alerting side for inbound vendor agreements — and neither connects your contract data to the rest of your operational stack (Slack, HubSpot, QuickBooks).

On Starch RECOMMENDED

One platform — contract lifecycle management, founder inbox, 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

Does Starch actually read the text inside contract PDFs, or just the metadata?

Starch can reach contract PDFs stored in Google Drive through browser automation and extract text from them — no separate API or parsing tool needed. That said, the quality of extraction depends on the PDF (scanned images are harder than text-layer PDFs). For structured metadata like renewal dates and contract values, you'll get the best results if that information also lives in a Notion database or is tagged in Gmail threads, which Starch syncs directly on a schedule.

We don't have a formal contract database yet — just files in Google Drive. Can Starch still help?

Yes, and that's actually the most common starting point. Tell Starch 'build me a vendor contract tracker with these fields' and it creates the app. You populate it by pasting in contract details, or Starch can pull metadata from your Gmail threads (counterparty name, dollar amounts, dates) where that information appears in the body of the email. You're building the system at the same time you're using it.

Is Starch SOC 2 certified? Our legal team will ask before we put contract data in it.

Not yet — Starch is not currently SOC 2 Type II certified. That's an honest limit worth knowing before you put sensitive contract data in. If your legal team requires SOC 2 Type II as a hard requirement today, that's a fair reason to wait. It's on the roadmap.

What happens when Contract Lifecycle Management launches? Do I have to rebuild everything?

The Contract Lifecycle Management app is currently in development — you can request beta access to get notified when it launches. When it does, it will add AI-assisted clause review, e-signature collection, and approval routing on top of the same connected data you're already using in Starch. The tracker and automations you build today will work alongside it, not get replaced by it.

Can Starch send renewal alerts to someone other than me — like the contract owner or the CFO?

Yes. When you set up the renewal alert automation, you tell Starch who to notify: 'Slack the contract owner listed in the tracker, and CC the CFO if the contract value is over $50,000.' Starch queries your Slack workspace live from its integration catalog when the automation runs. You can set different rules for different contract categories or value thresholds.

We use Salesforce, not HubSpot, for vendor relationship tracking. Does that work?

Yes — Salesforce is available from Starch's integration catalog of 3,000+ apps and the agent queries it live when your apps run. You can build the vendor contract tracker to pull counterparty data from Salesforce accounts rather than Notion if that's where your vendor records actually live.