Replacing an Internet Protocol television (IPTV) or over-the-top (OTT) platform makes business sense when the value of changing exceeds the full cost and risk of transition. A lower software licence price helps, but the investment decision also depends on what the operator can retire, how the service will compete and whether subscribers can move without damaging the wider customer relationship.

For the CFO sponsoring that decision, the most useful starting point is a costed comparison: continue with the current platform, modernize selected components, or replace the platform. Each option needs the same planning horizon, service obligations and demand assumptions. Retention and new revenue can strengthen the case, provided their contribution is explicit and supported by operator evidence.

A credible proposal should answer three questions: What becomes cheaper or commercially possible? What must happen before that value is realized? How much downside can the business absorb if delivery or adoption disappoints?

Define the business problem before selecting the platform

An aging platform may still deliver reliable television. Its age alone does not justify replacement. The investment trigger is a business constraint: support becoming unsustainable, repeated integration costs, a device estate approaching a support deadline, or an inability to deliver a proposition customers will choose.

Make that constraint measurable. “We need a better user experience” is too broad for an investment request. A more useful objective is to reduce failed activations, shorten the time needed to launch a package, or bring existing customers onto supported applications without a universal device swap. Record the baseline, target, deadline and accountable owner before assessing suppliers.

Market evidence helps frame the service requirement. Ofcom’s Media Nations 2026 report records that broadcaster content represented 53% of measured in-home video viewing among UK individuals aged four and over in 2025. That category includes live television, recorded playback and broadcaster video-on-demand. Streaming is changing the viewing mix, while broadcaster content remains important. This is UK evidence, rather than a global forecast.

For an operator, the implication is to test how well the proposed service supports the viewing journeys its own households value. Preserving dependable live TV may matter alongside improving catch-up discovery and app access. A replacement that adds fashionable features while making familiar journeys harder can undermine its own commercial case.

Deutsche Telekom’s 2025 annual report describes MagentaTV as combining linear television with access to major streaming services, and reports 109,000 additional TV customers in Germany during the year. This illustrates an operator’s continued investment in an integrated entertainment proposition. It does not isolate platform software as the cause of subscriber growth or establish a transferable return on investment.

Compare three credible options

Continue with the current platform

Continuation can be rational when the service meets customer needs, support is secure and required changes remain affordable. Cost it as a forward plan: renewals, security maintenance, infrastructure refresh, device support and essential development. A frozen version of last year’s budget is a weak baseline if known obligations are approaching.

Give continuation a review date and an exit plan. It may buy time for content negotiations, a broadband programme or a device refresh. It also leaves existing constraints in place, so document which opportunities the operator is choosing to defer and which risks require mitigation.

Modernize selected components

A targeted upgrade may solve the binding problem at lower transition cost. Examples include replacing applications, improving monitoring or moving a particular workflow while retaining service management and delivery systems. This approach fits when the retained foundation is supportable and integration costs remain proportionate.

Its financial test is whether it removes enough cost or constraint. An improved interface can be valuable, but it does not automatically eliminate expensive backend processes. Budget for continued interfaces, release coordination and responsibility across suppliers. Otherwise, modernization may add another system while leaving the old operating cost intact.

Replace the platform with selective reuse

Replacement deserves consideration when the current foundation blocks several priority objectives, sustainable support is unavailable, or targeted upgrades would perpetuate excessive complexity. Define the replacement boundary component by component. Existing billing, identity, content delivery or devices may remain useful, subject to validation.

Choose the operating model alongside the technology. A managed service can transfer specified tasks to a partner, while the operator still needs service governance and commercial ownership. A more internally operated model preserves direct control but requires people, tools and lifecycle investment. Compare the same responsibilities in both proposals.

For example, UniqCast’s September 2026 Sappa announcement describes replacement middleware working with both vendor-supplied applications and Sappa-developed clients, with content delivery provided by a partner. It demonstrates a selective replacement boundary. The announcement does not provide a quantified savings or retention result.

Device reuse also needs specific evidence. The Amino and UniqCast announcement identifies integration with Kamai 7x and A650m Linux set-top boxes. For another operator, compatibility, firmware, content protection and the remaining support period would still need assessment. Retaining hardware is valuable only if it supports the required service at an acceptable ongoing cost.

Build the total cost of ownership around real responsibilities

Total cost of ownership (TCO) should cover the resources needed to deliver the agreed service over a common horizon, often three to five years for an initial comparison. Separate the recurring operating cost from the cost of changing. Use monthly cash flows during transition, when overlap and delays matter most.

Establish the current-state baseline

Bring Finance, TV Product, Technology and Operations together to reconcile invoices, contracts and internal workload. Capture software and support, infrastructure, hosting, streaming and content delivery network (CDN) charges, applications, device maintenance, monitoring, external services and the staff effort needed to operate and change the service.

Distinguish avoidable expenditure from allocated overhead. Removing manual work may free a team to improve the service without reducing payroll. That is useful capacity, but it should not appear as a cash saving unless expenditure actually falls or a planned hire is avoided. Apply the same discipline to data-centre and shared-network allocations.

Include the entire transition

The programme budget needs discovery, integration, data preparation, testing, project management, training, subscriber communication, device logistics, temporary support and decommissioning. Include termination fees, minimum commitments and dual running. Assign contingency to identifiable uncertainties such as incomplete subscriber data or untested device variants.

Record when each saving can start. A new platform going live does not end an incumbent contract. A server is not a saving until its associated expenditure stops. A supplier should explain the dependency between its delivery milestones and the operator’s ability to retire systems and contracts.

Keep the accounting boundary consistent

Separate platform TCO from the full television profit and loss account. Content rights, marketing and customer acquisition remain essential to service economics even when they are unchanged by the platform decision. Show these common costs separately. Include any incremental rights, metadata, storage, delivery or commercial costs associated with the proposed product changes.

Test volume assumptions in both directions. Lower subscriber numbers can make minimum commitments expensive per household. Higher viewing can increase delivery and storage consumption even if subscriber growth is modest. Ask suppliers to specify the charging unit, minimums, renewal terms, change costs and exit obligations, then run the expected demand profile through those terms.

Treat retention and differentiation as testable value

TV may contribute to the value of a broadband or mobile bundle. The business case must establish how much incremental contribution the proposed change could protect. Lower churn among existing TV households is useful evidence to investigate, but those households may also differ in contract tenure, discounts, income or service needs.

Measure TV cancellation separately from loss of the broadband household or associated mobile lines. Compare similar customer cohorts, and use a controlled or carefully matched pilot where practical. An increase in viewing or satisfaction can support the hypothesis, but neither is itself proof of incremental margin.

A transparent retention estimate is: eligible households × assumed reduction in household exits × contribution preserved per retained household over the stated period. Use percentage points correctly. Moving annual churn from 12% to 11.5% is a 0.5 percentage-point change. Apply the assumption to the relevant household base, then account for when those households would have left.

Illustratively, 100,000 eligible households multiplied by a 0.5 percentage-point reduction means 500 fewer exits over a year. If each preserves an average of six months at €20 monthly contribution within that year, the benefit is €60,000. These are invented planning assumptions, not a customer result or an industry benchmark. A cohort model is needed to extend the effect across later years.

Count contribution after associated costs and discounts. Avoid crediting the same household through both a lifetime retention estimate and a separate recurring margin line. Include acquisition savings only where spending would actually be avoided.

Evaluate differentiation with equal discipline. Easier package changes, better discovery or partner aggregation can create opportunities, but they need attractive content, rights, usable metadata, commercial agreements and effective marketing. Attach each proposed benefit to an owner, a delivery dependency and a test. Keep unvalidated opportunities outside the core cost case or show them as a separate scenario.

Make the financial case survive a downside scenario

Consider a hypothetical operator whose current platform costs €1.8 million a year to run. Assume the replacement would cost €1.4 million a year after transition, with €1 million of one-time programme expenditure. The annual operating saving would be €400,000.

For this simplified illustration, all transition expenditure occurs at time zero and operating savings arrive at each year-end for three years. The subscriber base and service scope are constant. Unchanged content costs cancel from the comparison. The figures exclude tax, inflation, financing, terminal value and commercial uplift. The one-time budget is assumed to include migration and overlap costs. These are illustrative inputs, not UniqCast pricing.

The base case produces €1.2 million of undiscounted savings against €1 million of expenditure, leaving €200,000. At an illustrative 10% discount rate, its net present value (NPV) is approximately minus €5,000. NPV here means discounted incremental cash benefits less incremental expenditure. The operator should use its own approved investment assumptions and a horizon that captures relevant renewals and replacements.

The following scenarios change only the stated inputs. They show why a positive undiscounted total may offer little protection against delay or cost overruns.

Calculation: NPV = −initial expenditure + year-one saving ÷ 1.10 + year-two saving ÷ 1.10² + year-three saving ÷ 1.10³. Figures are rounded to the nearest €1,000. In the delay scenario, the expenditure remains at time zero, with no net operating saving in year one. Any extra overlap expenditure beyond the assumed budget would worsen that result.

The lesson is to identify what changes the decision. In this example, evidence that contracts can end on schedule and that operating savings are achievable matters more than an ambitious feature list. Extending the horizon might change the result, but would also require adding the costs and obligations that arise in those later years.

Keep a separate continuity case if replacement is needed to address an unacceptable support or security exposure. Describe the exposure, alternatives and mitigation cost directly. Do not manufacture a churn uplift or a failure probability to make an essential investment appear financially attractive.

Make migration controls part of the investment approval

Migration risk affects cash flows as well as service continuity. Billing errors, failed entitlements, incompatible devices or missing familiar functions can create support costs, credits and cancellations. Coexistence can reduce cutover exposure while extending dual-running cost. The plan needs both a service safeguard and a financial limit.

Use evidence-based approval gates rather than a single launch date. During discovery, confirm the system inventory, data quality, contractual exits and reusable devices. During integration testing, demonstrate identity, billing, entitlements and the key viewing journeys. During the pilot, validate service quality and support demand on representative devices, networks and customer groups.

Before expanding migration, agree thresholds for activation success, playback failures, billing reconciliation and support contacts. Define who can pause a wave, the conditions for rollback and how subscriber changes will be reconciled if systems run in parallel. Protect major viewing events when choosing migration windows.

Finally, make decommissioning an explicit milestone. Name the owner who confirms that contracts have ended, infrastructure expenditure has stopped and retained data remains accessible under the operator’s policies. Finance should reconcile realized savings against the baseline after each agreed reporting period.

The operator retains responsibility for its proposition, content rights, customer communication and investment decisions. Platform vendors and other partners need defined responsibilities for delivery, testing, operations and escalation. UniqCast can be evaluated for the platform and integration scope relevant to that plan; the precise boundary and retained operator tasks belong in the proposal and contract.

A reusable business-case worksheet

Use the following worksheet to prepare the executive discussion. Replace every blank with an operator input or an explicitly labelled assumption. Record the source, date, confidence level and owner beside each financial input.

1. Decision and scope: We need to decide [continue / targeted modernization / replacement] by [date] because [measurable constraint]. The service covers [households, devices, markets and viewing journeys].
2. Comparable alternatives: For each option, specify [service scope], [operating responsibilities], [support horizon], [retained components] and [commercial limitations]. Explain why any option is excluded.
3. Baseline and expenditure: Use [planning horizon], [monthly transition profile], [recurring current cost], [essential refresh costs], [new recurring cost], [transition budget], [contingency] and [contract exit dates]. Separate cash savings from released capacity.
4. Commercial value: State [eligible cohort], [retention or conversion assumption], [contribution per household], [realization timing] and [validation method]. Record incremental content, delivery, discount and marketing costs. Mark unproven benefits separately.
5. Financial tests: Show [incremental cash flows], [NPV using the approved rate], [payback if reached], [peak funding need] and [downside result]. Test delay, lower volumes, consumption growth, cost overruns and zero commercial uplift.
6. Delivery gates: Assign [owner], [required evidence], [acceptance threshold], [decision date] and [pause or rollback action] for discovery, pilot, migration waves and decommissioning.
7. Benefits review: Agree [baseline period], [data source], [reporting frequency] and [accountable executive] for cash expenditure, activation, service quality, support workload, package-launch time and household retention.

The board should be able to see what is being approved now, which later spending depends on evidence, and what would trigger a change of course. Set financial hurdles and acceptable service risk before supplier selection, so evaluation follows the business priorities.

Approve the outcome and the route to it

A strong replacement case connects service ambition to an executable operating model. It shows which costs disappear, which capabilities matter commercially and which assumptions still need proof. It also makes the cost of waiting visible without assuming that replacement must win.

If the decision depends heavily on speculative retention gains or an untested migration timeline, the next investment may be a focused pilot or feasibility assessment. If the economics, responsibilities and acceptance gates are credible, management can authorize the programme with a clear basis for measuring success.

To apply this framework to your service, request an operator-specific business-case workshop with UniqCast. Bring the current cost baseline, key contractual dates and the service changes you need to deliver.

‍