Data Centre Pricing Models
Executive Summary
Key Takeaways
- ✓ Pricing strategy, list price versus negotiated discount, term-based discounting, and competitive benchmarking, should be modelled as a distinct layer from the per-unit billing mechanics covered in rack revenue modelling.
- ✓ List price should be modelled as the ceiling rate, with an explicit, tracked discount assumption applied to reach the actual achieved rate, rather than modelling achieved rate directly as an unexplained figure.
- ✓ Longer contract terms typically command a larger discount off list price in exchange for revenue certainty, and this trade-off should be modelled explicitly rather than assumed uniform across term lengths.
- ✓ Competitive benchmarking against comparable facilities should inform the pricing assumption's reasonableness, but should not replace the facility's own achieved-rate evidence where a track record exists.
Objective¶
This guide sets out how to model data centre pricing strategy within Data Centre Financial Modelling, as a distinct layer from the billing mechanics covered in Rack Revenue Models.
List Price and Negotiated Discount¶
Achieved rate should be modelled as list price less an explicit, tracked negotiated discount assumption, rather than as a single unexplained achieved-rate figure. This decomposition lets the model show whether a change in achieved rate is coming from a change in list price itself, a change in typical negotiated discount, or a shift in the underlying deal mix.
Term-Based Discounting¶
Longer contract terms typically command a larger discount off list price in exchange for the revenue certainty they provide the operator. The model should apply an explicit discount schedule by contract term length rather than assuming a uniform discount across the portfolio, since a shift toward longer-term contracts can lower average achieved rate even as list price and market positioning remain unchanged. See Data Centre Customer Contract Models for the underlying contract structure this discount schedule applies to.
Competitive Benchmarking¶
Pricing assumptions should be checked against comparable facilities in the same market as a reasonableness test, but competitive benchmarks should not replace the facility's own achieved-rate track record where one exists, since a benchmark facility's cost structure, density mix, and market positioning may differ materially.
Common Construction Pitfalls¶
Achieved rate modelled directly without a list-price/discount decomposition. Conceals whether a rate change reflects list price movement, discount policy change, or deal mix shift.
Uniform discount assumed across all contract term lengths. Misses the term-length-driven discount trade-off and can misstate revenue if the term mix shifts.
Pricing benchmarked solely against market comparables, ignoring the facility's own track record. Can produce an assumption disconnected from the facility's actual achieved pricing history.
Recommended Practices¶
- Decompose achieved rate into list price and an explicit, tracked discount assumption.
- Apply a discount schedule by contract term length rather than a uniform discount.
- Use competitive benchmarking as a reasonableness check, not a replacement for the facility's own track record.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
How does pricing modelling differ from rack revenue modelling?
Rack revenue modelling covers the billing mechanics, how price per unit of committed capacity converts into revenue. Pricing modelling covers the strategic assumptions behind that price itself, list rate, negotiated discount, term-based discount structure, and competitive positioning.
Why should list price and achieved discount be modelled separately?
Because modelling achieved rate directly as a single unexplained figure conceals whether a rate change is coming from a change in list price, a change in typical negotiated discount, or a shift in contract term mix, each of which has a different implication for the durability of the pricing trend.
How should term-based discounting be modelled?
As an explicit discount schedule by contract term length, since longer terms typically command a larger discount off list price in exchange for revenue certainty, and this trade-off should not be assumed uniform across all term lengths in the portfolio.
What role does competitive benchmarking play in pricing modelling?
It informs the reasonableness of the pricing assumption relative to comparable facilities in the same market, but should not replace the facility's own achieved-rate evidence where a genuine track record exists, since market benchmarks reflect a different facility's specific cost structure and positioning.
Related Articles
Data Centre Financial Modelling
Data centre financial modelling is the discipline of modelling a data centre operator's revenue, cost, and capital structure from its capacity-denominated drivers, power, space, and cooling capacity, rack density, and tenant contract structure, rather than the generic market-price and headcount-growth drivers used in most corporate models, or the pure occupancy-and-lease-term drivers of conventional commercial real estate. This page is the hub for the Knowledge Centre's data centre financial modelling content: how colocation, hyperscale, and enterprise business models each require a distinct model architecture, how rack revenue and occupancy are decomposed into their separable underlying drivers, and how capacity planning and financial KPIs tie the model together, as this domain expands to cover operations, revenue, investment, and governance practice across the sector.
Rack Revenue Models
Rack revenue is the core billing unit of colocation data centre revenue, priced per rack, per kW of committed power, or a hybrid of the two, with premium pricing for higher-density racks. This guide sets out the mechanics of rack-based pricing, density tiering, and how to model power draw billing and contract escalation without conflating them into a single blended average rate per rack.
Data Centre Customer Contract Models
Data centre customer contracts carry specific structural provisions, SLA-linked service credits, renewal options, fixed annual escalators, and early termination rights, that materially affect revenue durability and should be modelled explicitly rather than assumed away in a simplified revenue growth curve. This guide sets out how to model each provision's financial effect and why contract-level detail matters more in this sector than in a generic subscription revenue model.
Colocation Financial Models
Colocation financial models project revenue from a diversified base of tenants leasing space and power in defined units, per rack or per kW of committed capacity, rather than a single anchor contract. This guide sets out how colocation revenue is decomposed into space/power revenue, cross-connect and ancillary fees, and how occupancy, pricing, and churn assumptions should be modelled as separable drivers rather than a single blended revenue-per-tenant figure.