Finance playbook · AI Employee: Fin

License Cost & Renewal Tracking

Zero surprise renewals; utilisation drives negotiation

Install this playbookBack to marketplace
The problem

SaaS spend is a compounding invisibility. Every team buys its own tools, credit cards go through finance without any tracking of what was bought, and by year three the company has 340 SaaS contracts spread across 60 owners with total spend nobody knows. Auto-renewals fire on contracts nobody remembers signing. Consolidation opportunities die because nobody sees the sprawl. Finance discovers a lapsed enterprise agreement two weeks after the retention window closes.

At a glance
Trigger
Cron (monthly)
Approvals
None
What it does
Read-only
Systems
SaaS management · NetSuite · Ramp
How it feels in production

An hour-by-hour walkthrough.

Every night, Fin syncs the SaaS spend picture from multiple sources: procurement (Coupa / Ramp / Airbase), corporate cards, direct integrations to SaaS management tools (Torii / Zylo / Cledara), the identity provider (Okta / Entra shows what's actually being logged into), and finance's own AP ledger. For every SaaS contract, Fin resolves: vendor, product, contract value, term, renewal date, auto-renew status, notification-required window, contract owner (with fallback to procurement requester), current active-user count from SSO signals. 60 days before every renewal, Fin proactively opens a review packet for the contract owner: - Contract: Notion Enterprise, 200 seats, $48K/year, renews Nov 15, auto-renew ON, 30-day notification required - Active users last 90 days: 143 of 200 (72% utilisation) - Cost per active user: $335/year vs. peer benchmark $180-260 - Recommendation: negotiate down to 175 seats, request 15% loyalty discount, evaluate consolidation with Confluence contract also renewing this quarter Owner reviews. Approves the negotiation position. Fin prepares the outreach template for the vendor's account team, coordinates with legal for redlines, and tracks the negotiation through to signature. Renewals that shouldn't happen get cancelled with correct notice; renewals that should happen get better terms. Weekly finance digest: upcoming renewals by month, utilisation trends, top over-spend candidates, savings realised.
How it works

Step by step.

  1. 01

    Nightly sync of every SaaS contract + spend event

    Procurement, corporate cards, SMP tools, identity-based usage, AP ledger. Deduplicate the same contract across sources (same vendor + product + amount). Resolve owner from procurement requester + fallback to corporate-card holder.

    Coupa · Ramp · Airbase · Torii · Zylo · Okta · AP ledger
  2. 02

    Compute utilisation + cost efficiency

    Active-user signals from SSO + direct integration. Utilisation = active users / licensed users. Cost per active user vs. published peer benchmarks or your historical negotiated rates.

    Okta · Vendor APIs · Benchmark database
  3. 03

    Proactive renewal review 60 days out

    Every renewal within 60 days: assemble the review packet with contract, utilisation, cost efficiency, negotiation recommendations, and consolidation opportunities with adjacent-renewing contracts.

    Slack · Teams · Renewal calendar · Review UI
  4. 04

    Owner decision + negotiation coordination

    Owner approves cancel / renew-as-is / renew-with-changes / consolidate. Approved negotiation triggers coordinated outreach template to vendor, legal loop for redlines, procurement approval per matrix.

    Slack · Vendor communication · Legal review · Procurement
  5. 05

    Execute + track outcome + digest

    Execute: cancel with correct notice, sign renewal, adjust seat counts. Track outcome (savings realised, seats reduced). Weekly digest to CFO with upcoming renewals, savings pipeline, sprawl metrics.

    Contract management · Analytics · CFO digest
Systems and wiring

What you connect to make this run.

Coupa · Ramp · Airbase · Bill.com

read+write

Procurement + AP source of truth for contract + spend. Read new POs + card charges; write vendor-management notes + renewal-status flags.

Torii · Zylo · Cledara · Vendr

read+write

SaaS management platforms for direct-integration signals (usage, license counts, cost). Write utilisation + renewal-outcome events. Some (Vendr) also handle the negotiation on your behalf.

Okta · Google Workspace · Microsoft Entra

read

SSO-based active-user signals. Which users have logged in via SSO in the past 90 days is a stronger utilisation signal than app-reported login (which can include automated / integration accounts).

Ironclad · DocuSign CLM · Google Drive

read+write

Contract vault. Read contract terms, notification windows, auto-renew flags. Write signed renewals + cancellation records + amendments.

What changes

Before and after, honestly.

Contracts renewed without owner review
Before
40-70%
After
Under 5% (proactive 60-day nudge catches all)
SaaS spend visibility (% attributable)
Before
50-70%
After
95%+
Annual SaaS savings from utilisation-driven negotiation
Before
0-3% (spreadsheet effort)
After
12-25% (data + timeline enforced)
Lapsed enterprise-agreement notifications
Before
1-4 per year (missed windows)
After
Zero
Related

Playbooks that pair with this one.

IT

License Reclamation

Reclaimed licences from inactive users feed the utilisation signal here.

Finance

Vendor Intake & Onboarding

New-vendor intake ensures the contract enters this tracking system from day one.

Finance

Spend Monitoring Detection

Anomaly-driven spend detection surfaces contracts this playbook may have missed.

Frequently asked

Answers about this playbook.

What if the vendor doesn't offer API-based license counts?

Fin falls back to SSO-based active-user signal + owner attestation. Where neither is available, the recommendation includes "utilisation-unknown" and asks the owner to survey usage before renewal.

How does it handle multi-year contracts?

Multi-year contracts get reviewed at each anniversary for utilisation, and 60 days before the multi-year term ends. Mid-term reductions are flagged as opportunities where the contract allows.

Can it handle open-source / freemium tools?

Yes — freemium usage is tracked for upsell risk (when will we cross into paid tier). Open-source with paid support tiers surfaces the support-renewal window separately.

What about enterprise-agreement bundles (Microsoft, Adobe)?

Bundled contracts get parent-child tracking. Line-item utilisation surfaces separately even when the parent is a single contract. Consolidation recommendations respect bundle structure.

How does it interact with our procurement team?

Procurement approves per the matrix. Fin surfaces the review packet + negotiation position to procurement for large renewals. Procurement can override negotiation strategy; Fin executes their decision.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore Finance playbooks