How to run a SaaS spend audit and map records before you cancel tools

Why a SaaS spend audit is the moment to map company records

A SaaS spend audit finds every software subscription the company pays for and decides which to keep, consolidate, downgrade or cancel. It is also the last time someone with budget authority looks at each tool before it is switched off, which makes it the right moment to note what history each system holds and to export anything worth keeping.

Cancelled tools take their history with them. A help desk dropped at renewal, a CRM replaced after an acquisition or a chat workspace moved to a cheaper plan can each remove years of records that later matter for audits, disputes, the company's own AI projects and, for some companies, a data license. The guide on checking message history before downgrading Slack or Teams shows how that happens with chat. Because the audit already produces a systems list, adding a few records columns costs very little.

Where to find every system the company pays for

No single source catches everything, so combine them.

How to turn the vendor ledger into a records map

1. Export two years of software spend. Pull general ledger detail for software, hosting and storage accounts, then add card and expense data. Normalize vendor names so each tool is one row.
2. Tag each tool by function. Finance, sales, support, engineering, operations, HR, communication or storage.
3. Add the records columns. For each tool, note what it holds, the earliest year of history, the admin owner, whether a full export works, the renewal date and the notice period.
4. Mark a decision. Keep, consolidate, downgrade or cancel. Every downgrade or cancellation gets an export decision before notice goes out.
5. Find the retired systems. Ask about tools cancelled in earlier years whose exports, backups or archived mailboxes still exist; these often hold the oldest history the company has.
6. Give the map to the owner. The result is a one-page view of what the company runs and what it remembers.

An Illustrative row from a finished map looks like this:

For the finance side of the map, the finance systems inventory template for fractional CFO onboarding provides a column layout.

SaaS audit timeline: what to do before and after cancelling

Work backward from each renewal date so no tool lapses before its records are dealt with.

Who to talk to

• Controller or AP lead: the vendor ledger, card data and the renewal calendar.
• IT lead or managed service provider: admin access, the SSO list, export mechanics and storage.
• Department heads: what each tool holds, what is still used and what was retired.
• Counsel: legal holds, contract terms on data, recordings and personal data.
• Owner or CEO: final calls on archive cost and anything with value beyond day-to-day operations.

What to say to department heads

What to preserve before a tool is cancelled

• A full export of records with attachments, comments and timestamps
• User and team mapping, so records can be tied to roles later
• Audit logs and admin settings, including any retention rules
• The status of any legal hold or retention obligation
• The contract, order form and data processing terms
• For call and meeting recording tools, the consent notices and settings in force when calls were recorded

Recordings need extra care. Federal law generally allows a recording when one party to the communication consents, under the Wiretap Act, 18 U.S.C. 2511, but California requires the consent of all parties to record a confidential communication under Penal Code section 632, and other states set their own rules. Keep evidence of how consent was captured alongside the export. This is general information, not legal, tax or financial advice. Ask your own counsel before relying on recordings for any purpose.

Where data licensing fits after the audit

A finished records map answers most of the first questions SourceX asks when it qualifies a company: size, history, data breadth and rights. Strong candidates usually run 10-15 or more systems with several years of connected history. If headcount reached 50+ full-time employees at peak (contractors excluded) and the map shows that kind of depth, the owner may want to consider licensing some records to AI labs and data buyers before the oldest systems are switched off. The who qualifies page sets out the baseline, and the company fit checker offers an early, non-binding indication. One-time proceeds can also help pay for the company's own AI work, which the guide on how to fund AI initiatives at a mid-sized company covers.

Fractional CFOs who run these audits across several clients are well placed to make introductions. A partner only introduces the company and passes on basic fit information; the partner never exports, uploads or describes its records. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards are payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed.

Next step

Run the audit on next quarter's renewals and build the records columns in from the start. If a client's map looks deep, the fractional CFO referral page explains what happens next, and you can register as a partner whenever you are ready.