A CFO’s Guide to Cutting Software Costs

The instinct when software spend is under scrutiny is to cut seats or cancel tools — a blunt approach that risks cutting capability a team actually needs. The sturdier framework separates cost reduction into three distinct moves, each with a different risk profile, and applies them in order.
Move 1: Audit before you cut anything
You can’t right-size what you haven’t measured. Pull license counts, last-login data, and feature usage across your major SaaS contracts — CRM, helpdesk, project management, whatever else bills per seat. This step alone often surfaces dormant licenses and duplicate tools nobody flagged. See the step-by-step version in how to run a SaaS spend audit.
Move 2: Right-size within existing contracts
Before touching the tools themselves, match every user to the cheapest license tier that still covers their actual work. Most CRM and support platforms sell limited or view-only tiers below the full seat price — often unused simply because nobody mapped who needs what. This recovers real savings without changing anyone’s workflow.
Move 3: Restructure the per-seat users who don’t need a full platform
This is the move that changes the cost curve rather than just trimming it. A meaningful share of “users” on any per-seat platform — light internal staff, partners, clients — only touch it for a handful of narrow, repeated tasks. Moving them to a custom portal on a flat monthly fee turns a cost that scales with headcount into one that doesn’t, without removing their access to the underlying data.
| Move | Risk | Typical payoff |
|---|---|---|
| Audit | None — measurement only | Surfaces dormant seats, overlap |
| Right-size tiers | Low — no workflow change | Trims existing bill |
| Restructure to flat-fee portal | Requires a build, but keeps CRM as system of record | Decouples cost from headcount growth |
Why order matters
Cutting seats or canceling tools before auditing is how capability gets lost along with cost — someone loses access they actually needed because nobody checked usage first. Auditing and right-sizing first means the only people affected by the bigger structural move are the ones genuinely mismatched to a per-seat model, and they end up with a tool built for their actual job instead of a cheaper version of someone else’s.
For the specific case of CRM licensing — the largest per-seat line item for most mid-market companies — see reducing CRM licensing costs. To quantify what restructuring is worth for your team, use the savings calculator.
Frequently asked questions
How long does this whole process take?
The audit and right-sizing moves can happen in weeks with internal effort. A custom portal build for the restructuring move also runs in weeks at ARDN, not months, since the whole model is built around fast, flat-fee delivery.
Does this apply beyond CRM software?
Yes — the same three-move framework applies to any per-seat platform: helpdesk, project management, PSA tools, agency/AMS systems. CRM is usually the largest line item, which is why it’s the priority wedge.
Who should own this process internally?
Typically a joint effort between Finance (spend visibility, ROI case) and Ops/IT (usage data, workflow mapping) — neither side alone usually has the full picture needed to right-size accurately.
Related articles
- TCO: SaaS Add-Ons vs. Custom-Built Software
A total-cost-of-ownership framework comparing SaaS add-on licensing to a custom build — beyond the sticker price of eith…
- An IT Director’s Guide to Consolidating Shadow SaaS
A step-by-step playbook for IT directors to find, classify, and consolidate shadow SaaS tools before the next renewal cy…
- Shadow IT: The Per-Seat Cost You’re Not Tracking
Shadow IT tools bought outside procurement quietly rack up per-seat fees mid-market companies never see coming until the…
- Data Ownership: SaaS CRM vs. a Custom-Built Portal
HIPAA, GDPR, and SOC 2 govern how a vendor handles your data — not who controls where it lives. That distinction matters…