How much of your Canadian operator SaaS spend nobody actually notices?

You run a 75-person Canadian oil and gas operator. You hired your fifth Vice President last quarter. Headcount has grown 4× since 2021. So has your software footprint - but nobody has counted it.

The audit finding is consistent across mid-market operators we've worked with: 15-30% of SaaS spend is consumed by software nobody knew existed, nobody is using, or that duplicates something else. Here's the structural reason it accumulates, the audit pattern that finds it, and what to do about it.

Why vendor stacks balloon (the structural reasons)

SaaS sprawl is not a discipline problem. It is a structural outcome of three forces that operate constantly in growing organizations:

One: each new hire brings tool preferences from their last role. The new VP of Engineering used Asana at her last company. Three months in, Vencer is now paying for Asana, Microsoft Project (the original tool), and Smartsheet (which a different team brought in). Nobody decided to add Asana. Nobody decided to keep Project. The sprawl just happened.

Two: contracts auto-renew on schedules nobody is tracking. The 2023 contract for the document signing tool came with a 12-month renewal. It renewed in 2024. It renewed in 2025. By 2026, the operator has been paying for it for three years - and the team that originally used it moved to a different tool two years ago.

Three: vendor invoices flow through AP without category-level review. The CFO sees "SaaS expense: $187K this quarter." That's it. Nobody is looking at the line items. Nobody is asking whether the $4,800/year platform is still in use.

The audit framework - eight categories, two hours each

The audit is straightforward but methodical. Eight categories, two hours per category, two days of work total. Best done as a working session between the CFO and IT lead.

For each category, the audit asks four questions:

1. What are we paying for? Pull every line item, list every product, list every annual cost.
2. Who is using it? Get actual user counts from each vendor's admin console. Many "50-seat" licenses are actually used by 12 people.
3. What does it do that we couldn't do another way? Genuine specialization is worth paying for; duplication isn't.
4. What is the renewal date and the termination notice required? Some contracts require 90+ days advance notice to terminate. Plan around it.

The eight categories to work through:

• Identity & access - SSO, MFA, password managers, PAM
• Productivity - Microsoft 365, Google Workspace, document signing, project management, communication tools
• Accounting & finance - production accounting, JIB platform, ERP, expense management, payroll
• Communications - email security, video conferencing, messaging, file sharing
• Security - EDR, email security, vulnerability scanning, SIEM, backup
• Infrastructure - cloud platforms, monitoring, automation, database tools
• OT / field - SCADA, historians, field data capture, mobile workforce tools
• HR & operational - HRIS, scheduling, training, compliance management

What the audit typically finds

Patterns across operators we've audited:

Duplicate tooling in productivity. Microsoft Teams + Slack + sometimes Google Meet. Microsoft Project + Asana + Smartsheet. The cost of duplication is usually 3-5% of total SaaS spend.

Abandoned licenses. 50-seat license, 12 active users. Often discovered in identity, security tools, and the older project management platforms. Cost of waste: 5-10% of total SaaS spend.

Auto-renewed pilots. A tool brought in for a 90-day evaluation in 2024, still being paid for in 2027, used by zero people. Cost of waste: 1-3% of total SaaS spend.

Overlapping security tools. Often the most expensive category. Multiple email security tools layered without coordination. EDR plus traditional antivirus running on the same endpoints. Vulnerability scanners from two different vendors. Cost of waste: 5-15% of total SaaS spend.

The consolidation playbook

Once the audit is done, the consolidation work has its own discipline. Five rules:

1. Don't cut in the same quarter you audit. Use the quarter after the audit to communicate, plan migrations, and respect notice periods. Surprise cuts create operational disruption that costs more than the savings.
2. Prioritize duplication over abandonment. Consolidating two tools into one (when one already covers the other's job) is the highest-leverage move. Sunsetting truly unused tools is easier to execute but lower-impact.
3. Negotiate before terminating. Once a vendor knows you're consolidating, they will often offer a meaningful discount to keep your business. The renegotiation is worth doing first - sometimes the consolidation isn't needed after the new price.
4. Document the new vendor stack. Build a vendor inventory with category, owner, renewal date, contract term, and termination notice. This becomes the basis for quarterly governance.
5. Build the quarterly review into the rhythm. Once a quarter, the CFO and IT lead spend an hour reviewing the inventory. New tools added? Old tools sunset? Renewals approaching? This single discipline prevents the sprawl from returning.

The full vendor audit framework, including the category-by-category workbook, lives in The Operating System - the operational depth complement to Crude Truth. Chapter 5 specifically covers vendor stack rationalization.

If you'd rather have someone run the audit alongside you, the IT-and-the-Cycle Assessment includes a vendor stack audit as part of the structured review - three to five days, written report, no obligation.