Cost Optimization Execution Recipe: SaaS Audit, Cloud Right-Sizing, and Vendor Renegotiation

Purpose

This recipe produces a measurable cost reduction of 20-35% across SaaS subscriptions, cloud infrastructure, and vendor contracts — with a documented savings tracker, renegotiated agreements, and a FinOps governance dashboard for sustained control. The average enterprise wastes $19.8M annually on unused SaaS licenses (only 54% utilization), 61% of discovered applications operate as shadow IT outside formal oversight, and 28-35% of cloud spending goes to idle or overprovisioned resources. [src1] [src6] [src4] This recipe systematically identifies, captures, and sustains those savings without cutting capabilities that drive revenue.

Prerequisites

• SaaS vendor inventory — complete list of subscriptions with cost, owner, renewal date, and user count
• Cloud billing data (12 months) — from AWS Cost Explorer, GCP Billing, or Azure Cost Management
• Contract renewal calendar — all vendor contracts with renewal dates, auto-renewal terms, and opt-out windows
• SSO/IdP admin access — Okta, Azure AD, or Google Workspace for 90-day login data
• Expense report access — read access to corporate card statements for shadow IT discovery
• Revenue growth confirmed — leadership confirms revenue is not constrained — Revenue Growth Action Plan

Constraints

• Only 54% of SaaS licenses are actively used — 46% represent $19.8M in average annual enterprise waste. Always pull SSO login data before cutting. [src1]
• 61% of discovered applications qualify as shadow IT, outside formal IT oversight. Procurement records capture less than 40% of the real portfolio. [src6]
• Business units control 81% of SaaS spend; IT manages just 15%. Decentralized purchasing is the norm. [src1]
• Vendor renegotiation must start 90-120 days before renewal. 83% of successful negotiations begin 120+ days out. [src5]
• Right-size instances BEFORE purchasing reserved capacity — cover only the 70-80% baseline that runs 24/7. [src8]
• Only 43% of organizations track cloud costs at the unit level — invest in tagging before cutting. [src3]
• Never cut customer-facing tooling without churn impact analysis — a 2% churn increase destroys more value than savings.

Tool Selection Decision

Which path?
├── Small company (under 100 employees) AND budget-conscious
│   └── PATH A: Manual Audit — spreadsheets + cloud-native tools + direct negotiation
├── Medium company (100-500 employees)
│   └── PATH B: SMB Tooling — Torii/Zluri + cloud-native tools + Spendflo
├── Large company (500+ employees) AND SaaS-heavy
│   └── PATH C: Enterprise SaaS — Zylo/Productiv + Vendr + FinOps platform
└── Any size AND primarily cloud infrastructure costs
    └── PATH D: FinOps-First — Vantage/nOps/Sedai + cloud-native + manual SaaS audit

Execution Flow

Step 1: SaaS Discovery and Shadow IT Audit

Duration: 1-2 weeks · Tool: SSO logs + expense reports + SaaS management platform

Build a complete SaaS inventory by cross-referencing three data sources: (1) procurement records, (2) SSO/SAML login logs (90-day usage), (3) expense reports and corporate card statements for shadow IT. The average enterprise runs 830+ apps with 61% outside formal IT oversight — procurement records alone capture less than 40%. AI-native app spend grew 393% YoY in large enterprises — search expense reports for individual AI tool purchases. [src1] [src6]

SaaS Audit Spreadsheet — required columns:
| Vendor | Annual Cost | Renewal Date | Auto-Renew? | Opt-Out Window | Owner |
| Licenses Purchased | Active Users (90d) | Utilization % | Category | Overlap? | Action |

Shadow IT discovery:
1. Export SSO/SAML login events (90 days) — list all apps with at least 1 login
2. Export corporate card line items: "software", "subscription", "SaaS"
3. Check AI-native apps — spend up 393% YoY
4. Cross-reference: apps in expenses NOT in SSO = shadow IT
5. Cross-reference: apps in SSO with zero 90-day logins = unused

Verify: Inventory covers 90%+ of IT spend; shadow IT audit adds 20-30%+ more apps than procurement records · If failed: Use browser-based discovery (Nudge Security, BetterCloud) or analyze corporate card data manually

Step 2: Cloud Infrastructure Cost Audit

Duration: 1-2 weeks · Tool: AWS Cost Explorer / GCP Billing / Azure Cost Management

Analyze 12 months of cloud billing. Identify: instances below 30% CPU utilization, unattached storage, idle load balancers, reserved instance coverage gaps, cross-region data transfer, and non-production running 24/7. Enterprises waste 28-35% of cloud spend on idle or overprovisioned resources. Reserved instances save up to 72% vs. on-demand; non-production scheduling saves 65%. [src4] [src8]

Cloud Waste Categories:
- Idle compute (< 10% utilization)        → Terminate or schedule     [save 100%]
- Overprovisioned (10-30% utilization)     → Right-size one tier down  [save 30-50%]
- Non-production running 24/7              → Schedule business hours   [save 65%]
- On-demand with stable baseline           → Reserved / Savings Plans  [save up to 72%]
- Unattached storage volumes               → Delete after backup       [save 100%]
- Old snapshots and unused AMIs            → Archive to cold storage   [save 80-90%]

Right-sizing: step down ONE size at a time, monitor 7 days in staging before production

Verify: Waste >20% of cloud spend identified (28-35% is typical); all idle resources validated with engineering · If failed: Enable cost allocation tags first; re-run after 2 weeks with 80%+ tagging compliance

Step 3: Categorize and Prioritize Savings

Duration: 3-5 days · Tool: Spreadsheet or dashboard

Rank every opportunity by annualized savings, implementation effort, risk, and time to capture. Organize into three tiers: Tier 1 (quick wins, weeks 1-4), Tier 2 (negotiations, weeks 4-10), Tier 3 (structural, weeks 10-16). [src5]

Tier 1 — Quick Wins (Week 1-4, low risk):
  Cancel zero-usage subs, remove departed employee licenses,
  delete unattached storage, schedule non-prod, downgrade premium tiers

Tier 2 — Negotiation (Week 4-10):
  Renegotiate top 10 vendors, right-size cloud instances,
  consolidate overlapping tools, convert to reserved instances

Tier 3 — Structural (Week 10-16):
  Vendor consolidation, architecture optimization, headcount efficiency,
  FinOps practice, zero-based SaaS budgeting

Verify: Each opportunity has dollar estimate, owner, and target date · If failed: Use benchmarks: 46% SaaS waste [src1], 28-35% cloud waste [src4]

Step 4: Execute Quick Wins (Tier 1)

Duration: 2-4 weeks · Tool: SaaS admin consoles + cloud console

Cancel zero-usage subscriptions (notify owners 2 weeks ahead). Downgrade unused premium licenses. Remove departed employee licenses. Delete unattached cloud storage after backup verification. Schedule non-production to business hours (saves 65%). Reclaim individual AI tool subscriptions. License cleanup alone recovers 15-25% of SaaS spend; automated reclamation recovers $1,500-$3,000 per unused license. [src1]

Tier 1 execution checklist:
☐ Cancel zero-usage subs (2-week grace period)
☐ Downgrade premium-to-standard (verify no critical feature dependency)
☐ Deactivate departed employee licenses (cross-reference HR system)
☐ Delete unattached storage volumes (verify no pending snapshots)
☐ Configure auto-shutdown for dev/staging/QA (8am-8pm)
☐ Consolidate individual AI tool purchases to enterprise agreement
☐ Document all actions in savings tracker with before/after costs

Verify: 10-15% savings captured; no service disruptions within 1 week · If failed: Restore canceled tool immediately; reclassify as Tier 2 consolidation candidate

Step 5: Negotiate Vendor Contracts (Tier 2)

Duration: 4-8 weeks · Tool: Vendr/Spendflo (benchmarks) or manual negotiation

For each vendor 90-120 days from renewal: prepare usage data, competitive alternatives, and desired outcome. 78% of IT leaders reported unexpected charges from consumption-based or AI pricing models — scrutinize new structures. Lead with utilization data, present competitive alternatives (reopens 80% of stalled negotiations), align with vendor quarter-end, and negotiate multi-year with price caps for 20-30% discounts. [src5] [src1]

Negotiation tactics:
1. Lead with usage: "We use 54% of licenses — we need to right-size"
2. Present 2-3 competitive alternatives with pricing
3. Time meeting to vendor's fiscal quarter-end
4. Trade multi-year commitment for 20-30% discount + price caps
5. Eliminate auto-renewal; require 90-day notice window
6. Push for termination-for-convenience at <25% remaining value
7. Request performance review clauses for quality degradation

Right-size cloud in parallel: test one tier down in staging for 7+ days. Convert stable on-demand to Savings Plans / Reserved Instances (up to 72% savings). Cover only 70-80% baseline. [src8]

Verify: Renegotiated contracts documented with before/after pricing; cloud right-sizing tested · If failed: Present competitive PoC to vendor VP Sales; plan migration at renewal if refused

Step 6: Implement Structural Changes (Tier 3)

Duration: 4-8 weeks · Tool: FinOps platform + cloud-native + HR/Finance

Consolidate overlapping vendors (20-30% reduction unlocks volume discounts). Implement cost allocation tagging on all cloud resources. Set up unit cost tracking (per customer, per transaction). Move cold data to archive tiers (80-90% storage savings). For headcount: 42% of CFOs anticipate AI-driven SG&A reduction; evaluate open positions before backfilling; automate repetitive tasks. 64% of CFOs target SG&A growth slower than revenue in 2026. [src2] [src7]

Structural actions:
1. Vendor consolidation: map by category → select winner → negotiate enterprise deal
2. Cost allocation tags: team, environment, service, cost_center (enforce via cloud policy)
3. Zero-based SaaS budgeting: re-justify every subscription against business OKRs
4. Headcount efficiency: AI automation for repetitive tasks (decouple revenue from headcount)

Verify: Vendor count reduced 20-30%; tagging at 90%+; unit cost tracking live · If failed: Enforce tagging via cloud policy (AWS SCPs, GCP Organization Policies, Azure Policy)

Step 7: Establish FinOps Governance Cadence

Duration: 1-2 weeks setup + ongoing · Tool: Dashboard + calendar

Monthly SaaS reviews with department owners (they control 81% of spend). Cloud cost dashboards with unit economics. Automated alerts for >15% MoM spend increases. Quarterly vendor review. Annual negotiation calendar. Named FinOps owner with exec sponsor — 59% of organizations are expanding FinOps teams. [src2] [src1]

Verify: Dashboards operational; monthly review scheduled; alerts triggering; named owner assigned · If failed: Start with shared spreadsheet and manual monthly review — process matters more than tooling

Output Schema

{
  "output_type": "cost_optimization_report",
  "format": "spreadsheet",
  "columns": [
    {"name": "category", "type": "string", "description": "SaaS, cloud, vendor, headcount"},
    {"name": "item", "type": "string", "description": "Specific vendor or resource optimized"},
    {"name": "action_taken", "type": "string", "description": "Canceled, right-sized, renegotiated, consolidated, scheduled"},
    {"name": "tier", "type": "string", "description": "Tier 1 (quick win), Tier 2 (negotiation), Tier 3 (structural)"},
    {"name": "original_annual_cost", "type": "number", "description": "Cost before optimization"},
    {"name": "new_annual_cost", "type": "number", "description": "Cost after optimization"},
    {"name": "annual_savings", "type": "number", "description": "Dollar savings per year"},
    {"name": "implementation_date", "type": "date", "description": "Date change implemented"},
    {"name": "owner", "type": "string", "description": "Person responsible"},
    {"name": "next_review_date", "type": "date", "description": "When to re-evaluate"}
  ],
  "expected_row_count": "20-100+",
  "sort_order": "annual_savings descending",
  "deduplication_key": "category + item"
}

Quality Benchmarks

If below minimum: Re-audit shadow IT from expense reports; engage procurement consulting for negotiations; implement cloud scheduling as immediate win. If savings not sustained at 6-month review, reinstate monthly governance reviews (Step 7).

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Applying uniform budget cuts across all departments

Blanket 10% cuts punish efficient departments and reward wasteful ones. 64% of CFOs plan SG&A growth slower than revenue — but through targeted efficiency, not blanket cuts. [src7]

Correct: Cut based on waste analysis data, not blanket percentages

Use SaaS and cloud audits to target specific waste. Every cut should reference a specific finding: unused licenses, overprovisioned resources, or redundant tools.

Wrong: Renegotiating vendor contracts at renewal date

Last-minute negotiations eliminate leverage. 83% of successful negotiations start 120+ days before renewal. [src5]

Correct: Build a 12-month renewal calendar and start 120 days out

Create the calendar in Step 1. Set automated reminders at 120, 90, and 60 days. Prepare competitive alternatives and usage data before the first call.

Wrong: Cutting cloud costs without unit economics visibility

Reducing spend by 20% means nothing if capacity drops 30%. Only 43% of organizations track unit-level costs. [src3]

Correct: Implement cost allocation tagging and unit tracking first

Tag every resource. Calculate cost per customer and per transaction. Optimize worst unit economics first — this protects revenue-generating infrastructure.

Wrong: Ignoring AI-native tool sprawl as a new cost category

AI-native app spend grew 393% YoY in large enterprises, with ChatGPT now the most expensed application. Individual purchases create a new wave of shadow IT. [src1]

Correct: Include AI tools in shadow IT audit and consolidate early

Search expense reports for “ChatGPT”, “Claude”, “Midjourney”, “Copilot”. Consolidate individual subscriptions into enterprise agreements with usage caps.

When This Matters

Use when a company needs to execute a systematic cost reduction program — not plan one, but actually audit SaaS portfolios, negotiate vendor contracts, right-size cloud infrastructure, and establish governance to sustain savings. Especially critical for companies extending runway (burn multiple above 2x), improving margins for profitability, preparing for a financing round, or reallocating budget from low-value spend to growth investments. Requires SaaS vendor inventory and cloud billing data as inputs; produces documented savings tracker, renegotiated contracts, and FinOps practice as output.