Why your five-year digital signage cost starts with the 51st screen
A site licence for digital signage is priced per estate, not per screen. That matters when the estate grows. A pilot project with 50 screens might look cost-effective if quoted on a per-screen basis, but the 51st screen changes everything.
The reason lies in how quotes are structured. A vendor pricing per screen will often offer a discount for volume. The discount reflects the work done upfront: setting up the server, configuring the network, testing the system. Once that work is done, adding more screens costs almost nothing to administer. But if the quote is per screen, the discount disappears when the next batch is ordered.
A site licence avoids this. The initial setup covers the entire estate, and the cost per screen drops as the number of devices increases. The 51st screen does not trigger a new quote or a renegotiation. It simply appears on the panel alongside the others, with no additional per-device fee.
The trap comes when a facility manager compares the upfront cost of a per-screen system against a site licence. The first 50 screens might seem cheaper under per-screen pricing, but the 51st, and every screen after, will reset the calculation. The discount evaporates, and the total cost climbs faster than expected.
This is not a theoretical risk. A site with 60 screens under a per-screen agreement will pay more than one with 100 screens under a site licence, even if the initial quote for the smaller number was lower. The break-even point arrives at the 51st screen, where the cumulative cost of per-screen pricing overtakes the flat fee.
The subscription trap: when per-screen fees outpace site licences after year three
Per-screen subscriptions look simple at first. A fixed fee per device each month means no surprises when a new screen is added. But the hidden cost appears when the estate grows. A site with 50 screens will have paid the same total for three years as a site with 100 screens under a per-site licence. After that, the per-screen model inflates. The 100-screen site pays twice as much as the 50-screen site, but the 200-screen site pays four times as much. The per-site licence, however, stays flat. The trap is not the initial price but the cumulative effect of network expansion.
The difference becomes clear when a single site adds screens over time. A per-screen subscription charges for every device from day one, even if most are idle. A site licence charges for the site, not the screens. Add 20 screens in year one, 30 in year two, and 50 in year three. The per-screen total rises with each new device, while the site licence remains unchanged.
The table below compares the total cost over five years for a site that starts with 50 screens and adds 20 each year. The per-screen model becomes uncompetitive after year three, and the gap widens with each addition.
| Year | Screens Added | Total Screens | Per-Screen Total (£) | Site Licence Total (£) |
|---|---|---|---|---|
| 1 | 50 | 50 | 9,000 | 1,200 |
| 2 | 20 | 70 | 15,120 | 2,400 |
| 3 | 30 | 100 | 23,400 | 3,600 |
| 4 | 20 | 120 | 31,680 | 4,800 |
| 5 | 30 | 150 | 41,400 | 6,000 |
The per-screen model also fails when screens are removed. A site that decommissions devices must still pay for them under a subscription, even if they are no longer in use. A site licence adjusts automatically. The inflation is not just in growth but in maintenance. A per-screen fee turns every screen into a recurring liability, while a site licence treats the entire estate as a single asset. The choice between them is not about upfront savings but about long-term control.
Hardware refreshes: where the three-year warranty leaves you exposed
The three-year warranty on a screen does not cover the cost of running the estate after it fails. A display that stops working in year four is not a one-off expense, it is the start of a phase where every device in the network becomes a risk. The warranty does not extend to the player, the mount, or the cables that may also fail before their time. Even if a screen remains physically intact, its backlight or panel may degrade unevenly, turning it into a half-functional ‘zombie’ that still consumes power and network bandwidth while displaying corrupted content.
A single replacement screen costs less than the labour of sending a technician to diagnose why the old one failed. The player, however, is often overlooked. If it is bolted to the wall behind the display, removing it requires unmounting the screen, disconnecting cables, and then remounting everything, work that takes longer than swapping the screen itself. The mount may also need replacing if the screws have seized or the bracket has corroded. By year four, the estate’s hardware is no longer a predictable cycle of planned refreshes but a series of unplanned interventions, each with its own hidden costs.
The real exposure lies in the ‘zombie hardware’ phase, where devices still appear operational but are unreliable. A screen that flickers or shows partial content forces staff to manually override it, wasting time and creating inconsistency. A player that fails to poll the server leaves the panel showing stale or incorrect information, undermining trust in the system. The cumulative effect is not just the cost of replacements but the cost of downtime, staff diverted to troubleshoot, alerts ignored because the display is not trusted, and the estate’s ability to respond to critical messages compromised.
Budgeting for hardware refreshes means accounting for the entire lifespan of a device, not just its warranty. A screen may last seven years, but if its player and mount fail in year five, the total cost of ownership is spread unevenly. The first replacement is cheap; the second, when multiple devices fail in the same quarter, becomes a bulk purchase with rushed delivery times. The estate cannot afford to treat hardware as disposable, but it also cannot afford to let failures accumulate. The solution is not to extend warranties but to plan for the point where the network’s reliability depends on proactive replacements rather than reactive fixes.
Installation costs nobody quotes: the electrician, the network engineer, and the ‘quick fix’ that lasts six months
The electrician’s invoice arrives first, and it rarely matches the estimate. A single screen needs more than a power socket, it demands a dedicated circuit if it’s mounted above a desk, or a surge protector if it’s in a factory. Worse, the cable run often reveals what the original architect overlooked: a junction box hidden behind a wall, or a ceiling void too narrow for new wiring. These costs don’t appear in a vendor’s demo. They surface when the first screen is live, and the second one requires the same work. The network engineer’s bill follows, but not for the reasons quoted in a sales pitch. A signage system that relies on constant polling, rather than a push, turns every screen into a background process competing for bandwidth. In a busy office, this means Wi-Fi drops when the printer queue spikes, or the reception TV buffers during a staff meeting. The fix isn’t a faster router; it’s isolating the signage onto its own VLAN, which adds another hour per screen. Then there’s the quick fix, the one that lasts six months. A technician bypasses the proper setup, grants the player permissions manually, or hardcodes an IP address to avoid DHCP conflicts. It works until it doesn’t: the next update breaks the workaround, or a screen reboots and loses its settings. By then, the original installer has moved on, and the estate team is left explaining why the fire drill alert didn’t appear, even though the software claims it sent one. The real cost isn’t the hardware. It’s the labour of undoing what was done wrong the first time, and the downtime that follows.
The ‘free’ content management system that locks you into a vendor for years
A ‘free’ content management system often means the vendor owns the data behind your screens. When you try to move to another platform, you cannot simply export the content. The software stores schedules, assets and metadata in its own format, and the vendor will not provide the keys to unlock it.
This is not an oversight. The system’s backend is built to hold content hostage. If you attempt to migrate, you must either recreate every schedule manually, losing any automation, or pay the vendor to convert the data for you. Some charge per screen, per hour of effort, or as a percentage of the original contract value. Either way, the cost rises sharply when the vendor realises you are leaving.
Even if you avoid migration fees, switching platforms usually requires retraining staff. The new system’s workflows differ from the old one. A facilities manager who spent months teaching colleagues how to update screens now faces another learning curve. The vendor selling the ‘free’ CMS knows this: their training materials are tied to their own software, and they will not document how to replicate its functions elsewhere.
The worst lock-in comes when the vendor changes their pricing model. A system that was free to set up suddenly demands per-screen fees, or introduces mandatory support contracts. By then, the content is trapped in their format, and the only way out is to rebuild everything from scratch, or stay with a vendor whose terms have just become far less favourable.
The ‘no upfront cost’ pitch hides the real expense: the day you realise you cannot leave.
When the ‘low-cost’ player fails at scale: the three-month breakdown that costs more than replacing it
A bulk deployment of low-cost signage often starts with a promise: screens that cost little up front, with no site licence to pay. The savings look real on day one. Three months in, the costs begin to add up elsewhere.
Cheap hardware fails in ways that disrupt the whole system. A screen with weak Wi-Fi drops its connection when a nearby printer starts a print job. The device stops polling the server, so the panel shows it as offline. Staff check the wall, nothing is wrong. The IT team spends 15 minutes diagnosing a network issue that does not exist. The screen is fine; the problem is the polling loop. This happens twice a week for six weeks. No one tracks the time, but the total adds to hours of unplanned work.
Then there are the alerts that never arrive. A fire drill message sits in the queue because the screen’s software cannot interrupt a video loop. The system logs the failure, but the panel still shows green. The person responsible for the estate does not know the drill was missed until someone reports it. The fix is simple, grant the app the display permission, but it requires physical access to every affected screen. The IT team books a block of time, only to find half the devices were already set up correctly. The other half take another visit.
Downtime compounds when content does not cache properly. A network outage at a single site halts every screen until the connection returns. No cached content means no playback. The estate manager calls the supplier for a solution. The answer is always the same: “Wait for the network to come back.” Meanwhile, staff stand in queues, or worse, leave without the information they needed.
The real cost is not the price of the screens. It is the time spent chasing failures that should not have happened, the alerts that vanish without a trace, and the unplanned support calls that pile up when the system cannot handle basic interruptions. By the time the estate manager realises how much extra work the “low-cost” choice has created, replacing the entire system would have been cheaper.
The digital signage cost nobody budgets for: the ‘we’ll fix it later’ technical debt
The moment a screen ignores an alert, it is not a one-off failure. It is the start of a chain. A fire drill announcement that never reaches the production floor means staff train with outdated routes. A network outage that silences a waiting room display leaves patients guessing when their appointment begins. These are not isolated incidents, they are technical debt, and every ignored update or deferred fix makes the next breakdown costlier.
A screen that cannot interrupt its own loop does not just miss an alert. It misses every alert until someone manually restarts it. That restart might not happen for hours, or days, or until the next power cycle. The panel flags screens that cannot draw over another app before you need them, but only if the system checks. If it does not, the debt accumulates silently. A single overlooked permission setting turns a television into a paperweight during an emergency.
Network outages expose another layer. A screen that relies on a live feed for its content will show a blank screen or an error message when the connection drops. That is not a failure of the hardware, it is a failure of design. Cached content means playback continues, but only if the system was configured to cache in the first place. A site that skips this step assumes the network will always be available, and when it is not, the cost is not just downtime. It is lost trust, compliance risks, and the unbudgeted rush to restore service.
The worst technical debt is the kind that only surfaces under pressure. A screen that has not been updated for two years may work fine in normal operation, but when a critical alert arrives, its outdated software might misroute it, delay it, or drop it entirely. The fix is not a quick reboot, it is a full refresh of every device, and the time spent hunting for the root cause is time spent without reliable communication.
The answer is not to wait until something breaks. It is to set up the system so that failures are visible before they become critical. That means verifying permissions, testing interruptions, and confirming offline playback on day one, not as an afterthought, but as part of the initial setup. The screens that work when it matters are the ones that were never allowed to fail in the first place.
Ask for a live demonstration of how alerts interrupt content, how screens report their status, and how they behave when the network vanishes. Do not accept a sales pitch. Insist on seeing the system under the conditions where it will actually be used.
