India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
Cloud TCO and Business Case: 5-Year Cost Versus Hardware Refresh
A cloud TCO and business case compares the full 3-5 year cost of running workloads in cloud with refreshing and operating them on-premises, including migration one-off costs, licences, people and exit of the current facility. NTSPL builds it from measured utilisation, models commitment and licence scenarios, and presents a CFO-ready NPV and payback with every assumption traceable to data.
Delivered on
In scope
Why Cloud Business Cases Fail Finance Review
Most cloud business cases fail in the CFO's office for one of three reasons: the on-premises side counts only hardware, ignoring power, colocation, AMC, backup licences and staff; the cloud side prices allocated rather than used capacity at on-demand rates; or migration one-off costs and 6-12 months of dual running are missing. A model that is wrong by 30 percent in either direction loses credibility with the board permanently.
NTSPL builds both sides from evidence. On-premises costs come from invoices, AMC schedules, power readings and headcount allocation; cloud costs from P95 utilisation priced in Indian regions with realistic commitment coverage. We add migration labour, dual running, training and facility exit, then run sensitivity on growth, exchange rates and commitment levels so the board sees a range, not a single optimistic number.
When a Formal TCO Is Worth Building
Signals you need Cloud TCO & Business Case
- A server, storage or data-centre refresh of ₹2 crore or more needs approval within 12 months
- A colocation or DC lease renewal of three years or longer is on the table
- A previous cloud proposal was rejected by finance as incomplete or optimistic
- The board wants NPV, payback and a cost range before approving a migration programme
When to choose something else
- Workloads already run in cloud and the bill is too high: that is a cloud cost assessment of the live estate.
- Fewer than 25 servers with no facility exit: provider calculators and a one-page comparison are sufficient.
Cost Lines in a Defensible TCO
On-premises baseline
Hardware refresh, AMC, colocation or power and cooling, DR site, backup and monitoring licences, and allocated staff effort.
Cloud run cost
P95-sized compute, storage, backup, network egress, support plan and security tooling priced in Indian regions.
Commitment and licence scenarios
Savings Plans, reservations or committed use discounts at different coverage levels, with Hybrid Benefit or BYOL where eligible.
One-off migration costs
Migration labour, tooling, dual running, training, data transfer and facility exit or early-termination charges.
Financial outputs
Five-year cash flow, NPV at your hurdle rate, payback month and sensitivity to growth and exchange-rate movement.
Evidence-to-NPV Cost Model
Evidence-to-NPV Cloud Business Case Model
Invoices and utilisation data feed two parallel cost stacks, on-premises and cloud. Scenario and sensitivity layers turn the difference into NPV, payback and a cost range the CFO can audit line by line.
Select any component
Evidence-to-NPV Cloud Business Case Model: click any of its 8 components to see its role and the design choice NTSPL makes for it, or trace the 7-step primary path.
Provider TCO Tooling and Pricing Levers
Migration Evaluator produces a utilisation-based baseline that we extend with Savings Plans coverage scenarios and licence findings from the Optimization and Licensing Assessment.
Azure Migrate's business case gives a first on-premises versus Azure view; we replace its default on-premises cost assumptions with your invoices and add Hybrid Benefit scenarios.
Migration Center generates TCO reports from discovered assets; we layer resource-based and spend-based committed use discounts and Mumbai or Delhi pricing on top.
Modelling Choices That Move the Answer
Commitment coverage to assume
Model three levels: none, 50 percent and 70 percent of steady-state compute under one- or three-year commitments. Use 50 percent as the base case for year one, rising to 70 percent once workloads have run 3-6 months. Assuming 90 percent coverage from day one flatters the case and is rarely achieved in the first year.
What belongs on the on-premises side
Include the next hardware refresh even if it falls in year four, AMC escalation, power at measured kW times your tariff, colocation, DR site, backup and monitoring licences, and staff time at fully loaded cost. Exclude sunk costs such as hardware already depreciated. Finance should sign off this stack before cloud numbers are shown.
Handling dual running
Assume 6-12 months of overlap for estates above 200 servers, with on-premises costs falling as waves complete rather than all at once. Contract exit dates matter: a colocation contract that cannot be cut by rack keeps full cost until the last rack empties, often the largest single swing in payback.
Discount rate and horizon
Use your board's hurdle rate, typically 10-14 percent for Indian mid-market firms, and a five-year horizon aligned to a refresh cycle. Three-year horizons understate cloud value when a refresh falls in year four; seven-year horizons hide technology change. Present payback month alongside NPV for non-finance readers.
Five-Week Business Case Build
Evidence collection
Invoices, contracts, power readings and staff allocation gathered with finance.
On-premises stack sign-off
Five-year on-premises cost reviewed and accepted by the finance controller.
Cloud stack and one-off costs
P95-based pricing in Indian regions, migration labour and dual running modelled.
Scenarios and sensitivity
Commitment, licence, growth and currency scenarios run.
Board pack
NPV, payback and range presented to the CFO, then to the board or investment committee.
What you receive
Financial Measures in the Board Pack
| KPI | Typical target |
|---|---|
| Assumptions traceable to a source | 100 percent |
| Year-one actual cloud spend versus model | Within 10-15 percent |
| Payback period | Typically 18-36 months for refresh-triggered cases |
| Commitment coverage achieved by month 9 | 60-70 percent of steady state |
Errors That Undermine a TCO
| Risk | How NTSPL prevents it |
|---|---|
| Cloud priced on allocated capacity | Only P95 measured utilisation is used, with headroom on named tiers only. |
| Hidden on-premises costs left out, flattering on-premises | Finance signs off a checklist of 14 cost lines before modelling begins. |
| Year-one credits presented as ongoing savings | Credits appear as a separate line and are excluded from the steady-state comparison. |
Is cloud cheaper than refreshing our own servers?
Sometimes, and the honest answer depends on three numbers: how much of your allocated capacity is actually used, whether a refresh or facility contract falls inside the next five years, and how much licence value carries over. Estates with P95 CPU under 25 percent and a near-term refresh usually show cloud 20-35 percent cheaper over five years. Estates that are already consolidated, recently refreshed and run steady 24x7 loads can be cheaper on-premises on pure infrastructure cost, and the case then rests on agility, DR or exit from a facility. A good TCO shows you which side of that line you are on.
Key facts: Cloud TCO & Business Case
Cloud TCO & Business Case in Practice
2 Cloud TCO & Business Case scenarios, from FMCG (packaged foods) and Hospitality (hotel group), plus related platform case studies.
FMCG company replaces a ₹6.2 crore refresh with an AWS case paying back in 26 months
Hotel group's TCO shows Google Cloud wins only with a colocation exit, and times it
D2C fashion brand absorbs 14x festive flash-sale traffic with zero checkout outages
EPC company vacates its owned data centre in 7 months and halves run cost
Cloud TCO & Business Case: Frequently Asked Questions
How long does a cloud TCO and business case take?
About five weeks if discovery data exists, eight if utilisation must be collected first. The pace is usually set by how quickly finance can provide invoices and contracts, not by the modelling. A first indicative range is usually available by week three for early budgeting.
What does a business case engagement cost?
Typically 15-25 consultant days. Provider TCO tools are free, and NTSPL applies for hyperscaler assessment funding where the estate qualifies, which can offset part of the effort. The model is handed over as a live spreadsheet owned by your finance team.
How is GST treated in the model?
Cloud services from Indian billing entities attract GST, usually recoverable as input tax credit for registered businesses. We model costs net of recoverable GST, and show gross figures separately where credit is restricted. Where cloud is bought through a reseller, the invoicing entity and GST terms are checked against the contract.
Does the model account for rupee exposure?
Yes. Many cloud prices track USD even when invoiced in INR, while AMC and power are rupee costs. Sensitivity shows the effect of a 5 and 10 percent rupee depreciation on five-year NPV. Exposure is shown separately for compute, storage and support so finance can judge which lines matter most.
Can the model include DR and backup?
Yes. Recovery tiers from the Backup and DR assessment are priced on both sides, because a DR site is often a large on-premises cost that cloud replaces with pilot-light or warm-standby patterns. In the models we build, DR typically represents 12-25 percent of cloud run cost.
Will the model still be useful after migration?
It becomes the baseline for tracking. We hand over a version with an actuals column so finance can compare monthly cloud spend with the model and spot drift early. A quarterly re-forecast against actuals keeps the commitment purchase plan aligned with real usage.