Why consolidation cases overstate the saving
The pitch is always the same: five tools at $148,000 replaced by one suite at a lower total, so the saving is the difference. Two things make that arithmetic wrong in practice, and both are predictable.
The first is seat count. Point tools are bought by the team that needs them, so a design tool has forty seats and a project tool has ninety. A suite is bought for everyone who touches any of those workflows, and the seat count is frequently larger than the largest tool it replaces. A lower per-seat price multiplied by a much larger seat count is not automatically cheaper, and this is where most consolidation cases quietly break.
The second is the capability gap. Suites cover the common eighty percent of several tools and rarely all of any one, so a specialist tool survives for the team that depends on it. That retained cost sits on the consolidated side of the ledger permanently, and leaving it out inflates the saving by exactly its value every year.
Migration effort then determines whether a real saving is worth capturing this year or next. Data migration, rebuilt integrations, recreated reports, retraining and a period of running both systems in parallel are all internal hours at a fully loaded rate. They do not recur, which is why they belong in a payback period rather than in the annual saving.
Three lines, one break-even rate
Consolidated spend is seats × rate × 12 + retained. Net annual saving is current spend minus that. Migration cost is hours × blended hourly cost, and payback in months is the migration cost divided by one month of the saving.
The most decision-useful figure here is the break-even suite rate, (current − retained) / (seats × 12). It is the highest per-seat price at which consolidation does not raise your annual bill, and it is the number to walk into the vendor conversation with. Anything above it means the case has to rest on simplification, risk reduction or capability rather than on money — which is a legitimate case, but a different one.
Payback is deliberately undefined when the saving is zero or negative. A migration with no recurring saving behind it never repays itself, and reporting a very large payback figure instead of a blank invites the reader to imagine it eventually does.
The multi-year net, saving × years − migration, is the summary line for an approval. Note that it treats a dollar in year three as equal to a dollar today. If the migration is large relative to the saving, discount the flows properly — the ordering rarely changes, but the magnitude does.
Worked example: five tools at $148,000 into one suite
You spend $148,000 a year across five overlapping tools. The suite would need 240 seats at $32 a seat a month. One specialist tool survives at $18,000 a year. Migration is estimated at 600 hours at a blended $95 an hour, and you want a three-year view.
- Suite licence cost. 240 × $32 × 12 = $92,160 a year.
- Consolidated annual spend. $92,160 + $18,000 retained = $110,160.
- Net annual saving. $148,000 − $110,160 = $37,840 a year, which is 25.6% of current spend.
- Migration cost. 600 × $95 = $57,000, a one-off.
- Payback. Monthly saving is $37,840 ÷ 12 = $3,153.33, so $57,000 ÷ $3,153.33 = 18.1 months.
- Three-year net. $37,840 × 3 − $57,000 = $113,520 − $57,000 = $56,520.
- Break-even suite rate. ($148,000 − $18,000) ÷ (240 × 12) = $130,000 ÷ 2,880 = $45.14 per seat a month.
- Current cost per seat. $148,000 ÷ 240 = $616.67 a year, against $384 a year on the suite.
Step 7 is what turns this into a negotiation. You have $13.14 a seat a month of room between the quoted $32 and the $45.14 break-even, which is where the vendor's discount conversation actually sits. And step 5 says the case survives an 18-month payback — comfortably inside a three-year contract, but not inside a one-year one, which is worth knowing before agreeing the term.
Reading the result honestly
Judge the payback against the contract length, not against a generic threshold. A payback under twelve months survives almost any change of plan. Between twelve and twenty-four months it needs the suite contract to run at least three years, because a renegotiation in year two can remove the saving you were repaying with. Beyond twenty-four months the case depends on assumptions about year three that nobody can defend, and the calculator flags it.
Check the sensitivity to seat count before anything else. Seats multiply the largest term in the consolidated cost, so a 20% miscount moves the answer far more than a 20% error in the migration estimate. Count the seats from the identity provider, listing everyone who has access to any of the tools being replaced, rather than from the sum of the tools' own seat counts — people hold licences on several.
Treat the migration estimate as the least reliable input and test it. Doubling it in the calculator shows how much of the case rests on delivery going well. If doubling migration hours pushes payback past the contract term, the case is a delivery risk rather than a pricing decision, and the mitigation is a smaller first phase.
Finally, separate savings you will actually book from savings you merely calculate. A retired contract is cash; reclaimed admin time is not, unless a role changes. State which is which in the business case, because the finance team will ask, and a case that claims soft savings as hard ones loses the argument on the first line.
How the case moves with the suite price
| Suite rate per seat per month | Consolidated annual | Net annual saving | Payback (months) |
|---|---|---|---|
| $20 | $75,600 | $72,400 | 9.4 |
| $25 | $90,000 | $58,000 | 11.8 |
| $30 | $104,400 | $43,600 | 15.7 |
| $32 | $110,160 | $37,840 | 18.1 |
| $35 | $118,800 | $29,200 | 23.4 |
| $40 | $133,200 | $14,800 | 46.2 |
| $45 | $147,600 | $400 | 1,710.0 |
Payback is not linear in the price. Between $20 and $32 a seat it roughly doubles; between $40 and $45 it collapses entirely, because the saving in the denominator is approaching zero at the $45.14 break-even rate.
Costs consolidation cases routinely omit
- Overlapping subscriptions during cutover. You will pay for both the old tools and the new suite for a period, and old contracts rarely terminate on your timetable.
- Rebuilt integrations. Every automation, webhook and report pointed at a retired tool needs rebuilding, and this is usually the largest single block of migration hours.
- Data migration and history. Moving records is one problem; keeping searchable history without the old tool is another, and the answer is often an export and an archive nobody budgeted for.
- Retraining and lost productivity. Even a straightforward switch slows a team for weeks. It is a real cost even though no invoice arrives.
- Early termination charges. Contracts cancelled mid-term may still be payable in full. Check every end date before committing to a cutover date.
- The specialist team that refuses. If one team's workflow genuinely needs the retired tool, you keep paying for it, and the saving falls by that amount permanently rather than temporarily.
Consolidation buys things that are not savings
Fewer vendors means fewer renewals, fewer security reviews, fewer data processing agreements, fewer access reviews and one identity integration instead of five. Those are real reductions in work and in risk surface, and they are the reason consolidation is often right even when the money is flat. They belong in the case as stated benefits with an estimate of hours, not folded into the financial saving — mixing them is what makes finance teams discount the whole business case.
Deciding before you negotiate
Do the cheap work first. Overlapping tools usually contain a lot of unused licences, and right-sizing seats across the existing estate frequently captures a large share of the consolidation saving with none of the migration risk. Run that before comparing suites, because it also gives you the accurate seat count the suite quote depends on.
Then check the pricing model rather than only the price. A suite quoted per seat may be far more expensive than the same capability quoted on consumption for an estate where most people are occasional users; the per-seat versus usage comparison is worth running for any suite that offers both. And whichever way the licence lands, the multi-year cost is driven by the escalation clause, so price the term with the renewal uplift calculator before signing.
Where the consolidation target is something you could build internally, or where the suite would replace an in-house tool, the comparison belongs in a build versus buy frame instead, and the full ownership cost — admin time, training, integration, exit — is the fair basis for either decision.