Build a single source of truth for SaaS vendors, owners, renewal dates, seat counts, billing sources, and contract terms.
Run the OperationCoreStarter Kit60-120 minProcurement and Ops, Finance
If you do not have a SaaS inventory, you do not control SaaS spend. You are reacting to it.
This starter kit helps a beginner build a single source of truth for:
what tools you pay for
who owns each tool
how billing works
where contract terms live
when renewals and notice windows happen
how many seats are paid vs used
What you will produce
By the end, you should have:
A SaaS Inventory Table (single spreadsheet or database)
A clear owner map (business plus technical owners)
A renewal feed (so nothing silently renews)
A Top 10 action list (quick wins plus risks)
A lightweight monthly governance cadence
Who should own this
Ideal owners (choose one accountable owner, not a committee):
Procurement Ops (common)
Finance Ops (common)
IT Ops (works well if finance partnership exists)
You will also need contributors:
IT (SSO, access, provisioning)
Finance/AP (billing sources)
Department owners (tool ownership and justification)
Time and effort
Setup: 60–120 minutes to build v1
Then: 30 minutes per week for 2–4 weeks to stabilize coverage
The goal is not perfection. The goal is a working truth system.
Beginner-safe definitions
Inventory: A complete list of what you pay for. Business owner: The person accountable for why the tool exists and the budget. Technical owner: The person accountable for configuration, access, SSO, and risk. Billing source: Corporate card, AP invoice, marketplace, or reseller. Renewal risk: Anything renewing inside 120 days with unclear terms or no owner.
Step-by-step instructions
Step 1: Pull a raw vendor list (do not overthink)
Start with any two sources. You can add more later.
Recommended sources:
AP/ERP export (vendor, amount, date range)
corporate card statements (merchant names)
SSO or identity provider app list (Okta, Azure AD, Google)
expense reports (tools reimbursed by employees)
If you already have a spend export, use to clean and categorize it.
Step 2: Normalize vendor names (this is more important than it sounds)
Problem: "Slack", "Slack Technologies", "SLACK*BILLING" might be the same thing.
Copy-ready request email to owners (beginner-safe)
Copyable template (TEXT)
Subject: SaaS Inventory and Ownership Confirmation (Action Required)
Hi team,
We are building a single SaaS inventory so we can manage renewals, prevent accidental auto-renews, and eliminate unused seats.
Please reply with:
1) Are you the BUSINESS owner for [Tool Name]? If not, who is?
2) What team uses it and for what purpose?
3) Do you know the renewal date and whether it auto-renews?
4) Any known seat or utilization issues (unused seats, wrong tier, duplicates)?
If you do not respond by [DATE], we will assign a temporary owner and follow up.
Thanks,
[Name]
Common pitfalls (avoid these)
trying to perfectly categorize everything before you assign ownership
mixing billing sources without capturing the billing source column
tracking renewals but not tracking notice windows
tracking "seats paid" without ever checking "seats active"