APRIL 2026 — CONSUMER BILL AUDIT EDITION — DIGITAL SIGNET — FOR FINANCE TEAMS
The finance-team playbook: auditing telecom, SaaS, and cloud as one project.
By Oliver, Digital Signet — Last verified April 2026
10 min readYour telecom, SaaS, and cloud bills all creep through the same mechanism. A promotional telecom rate expires after 12 months and the account auto-upgrades to standard pricing. A SaaS contract auto-renews for the same seat count even though the team has shrunk. A Reserved Instance lapses and AWS silently charges on-demand rates for the same workloads. The mechanism is identical. The opportunity is also identical: a systematic line-by-line audit, followed by a scripted negotiation, followed by a quarterly review cadence to prevent the creep from returning.
The mistake most finance teams make is treating these three categories as separate projects in separate spreadsheets, owned by different teams (IT owns SaaS, DevOps owns cloud, ops owns telecom). This creates three separate review cadences, three separate renewal calendars, and three opportunities to miss the cross-category pattern. Running them as one project reveals the total company exposure and allows prioritisation by dollar impact.
The 30-60-90 plan
Days 1-30: Discovery
- •Collect all active contracts for telecom (lines, internet, conferencing), SaaS (every vendor with a recurring invoice), and cloud (AWS, Azure, GCP account summaries).
- •Export 90 days of usage data per category: telecom (active lines, call records), SaaS (seat utilisation per tool from SSO logs or admin consoles), cloud (Cost Explorer or equivalent).
- •Build the unified spend inventory: one spreadsheet with vendor, category, monthly cost, contract end date, owner, and 90-day utilisation.
- •Identify shelfware candidates: SaaS tools under 20% active seat utilisation; cloud instances with under 10% CPU utilisation; telecom lines with no activity in 30+ days.
Days 31-60: Rationalisation and negotiation
- •Cancel or downgrade identified shelfware tools. Get written confirmation from each vendor before the next billing cycle.
- •Negotiate the top 5-10 highest-value renewals using the negotiation-scripts playbook. Prioritise any renewal within 90 days.
- •Purchase Reserved Instances or Savings Plans for stable cloud workloads (70-80% of stable compute baseline). Do not commit to 100%; leave headroom.
- •Right-size over-provisioned cloud instances using AWS Compute Optimizer, Azure Advisor, or GCP Cost Recommender.
- •Negotiate telecom contracts. For mobile, compare Verizon/AT&T/T-Mobile effective per-line costs including all surcharges. For internet/cable, call retention with a competitive quote.
Days 61-90: Process implementation
- •Build the three-metric dashboard (see below). Review it in a 30-minute cross-functional weekly standup.
- •Assign a named owner for every contract renewal date. Set calendar alerts at T-90 and T-30 for every contract above $1,000/year.
- •Implement a SaaS request and approval workflow to prevent shadow IT from rebuilding the shelfware problem.
- •Schedule the quarterly review: one 2-hour session per quarter per category. Total ongoing commitment: 6-8 hours per quarter to maintain the savings.
The three-metric dashboard
| Category | Metric 1 | Metric 2 | Metric 3 |
|---|---|---|---|
| Telecom | Total monthly spend | Cost per active employee | % lines active in 30 days |
| SaaS | Total annual contract value | Active seat utilisation % (target >80%) | Tools with functional overlap |
| Cloud | Total monthly spend | Commitment coverage % (target 70-80%) | Waste % (target <20%) |
CFO memo template
Subject: Q2 Technology Spend Audit Results
To: [CFO / Board]
We completed a 60-day audit of telecom, SaaS, and cloud spend. Key findings:
- Telecom: Cancelled [X] idle lines. Negotiated [X] carrier contracts. Monthly saving: $[X]/mo.
- SaaS: Identified [X] shelfware tools representing [X]% of SaaS spend. Cancelled [X]. Renegotiated [X]. Annual saving: $[X].
- Cloud: Purchased [X]-year Savings Plans for [X]% of stable compute. Right-sized [X] instances. Monthly saving: $[X]/mo.
Total annualised saving: $[X]. Return on audit investment: [X]x in year one.
Recommended next step: implement quarterly review cadence. Assign named owner per category. Budget [X] hours/quarter to maintain.
Drowning in SaaS and telecom creep?
Digital Signet runs two-week bill-and-subscription audits. We map every line item, score every contract, and deliver the memo your CFO will sign.
See the engagement formatFrequently asked questions
Why should telecom, SaaS, and cloud be audited as one project?+
All three creep through the same mechanism. Running them as one project reveals total exposure and allows prioritisation by dollar impact. Treating them as separate projects with separate owners means no one sees the full picture.
What metrics should a finance team track for recurring technology spend?+
Three per category. Telecom: total spend, cost per employee, % lines active. SaaS: total ACV, active seat utilisation (target >80%), overlap count. Cloud: total spend, commitment coverage (target 70-80%), waste % (target <20%).
How long does a full audit take?+
A 30-60-90 day structure is typical. Days 1-30: discovery and inventory. Days 31-60: rationalisation and negotiation. Days 61-90: process implementation and dashboard. After day 90, a quarterly review of 6-8 hours total maintains the savings.
What is a realistic savings expectation?+
For a company that has not audited in 12+ months, realistic first-audit savings are 15-30% of total recurring technology spend. The case studies on this site document 30% (SaaS), 31% (cloud), and 38% (consumer) reductions. First audits find the largest savings; subsequent years yield 8-15% incremental.