The Digital Signage Buyer's Guide.

Buying digital signage software should be straightforward: you need screens, you need content on those screens, you need a way to manage it. And yet, the majority of businesses that purchase a digital signage platform end up switching vendors within 18 months. Not because the technology failed, but because the evaluation process failed. They asked the wrong questions, ignored the contract details, and discovered too late that the slick demo bore no resemblance to the daily reality of running a signage network.

This guide is written from the buyer's side. No vendor spin, no feature comparisons dressed up as objectivity. Just the hard-won knowledge from hundreds of procurement cycles — what actually matters, what doesn't, and what will bite you if you don't catch it before signing.

Why most evaluations fail

The typical digital signage evaluation goes something like this: someone in marketing or facilities decides the company needs screens. They Google "digital signage software," visit five websites, book three demos, and pick the one with the nicest interface. Six months later, they discover the platform can't handle their network architecture, the "unlimited" plan has a fair-use cap of 2GB per screen, and the annual contract auto-renewed while they were still arguing about whether to switch.

Evaluations fail for three consistent reasons:

• Feature fixation: Buyers compare feature lists instead of operational fit. Every vendor claims to support "multi-zone layouts" and "scheduling," but the implementation quality varies wildly. A feature checkbox tells you nothing about whether it actually works well enough for daily use.
• Demo blindness: Demos are rehearsed performances on ideal hardware with pre-built content. They don't show you what happens when your intern uploads a 4K video on a 2Mbps connection, or when your Fire TV Stick loses Wi-Fi at 2am and needs to recover gracefully.
• Ignoring total cost: The monthly subscription is never the full cost. Hardware, installation, content creation, training, and the ongoing operational time to manage the system all factor into what you actually spend. A platform that costs £3 less per screen but requires twice the management time is not cheaper.

The 7 questions every buyer should ask

These are not the questions vendors expect. They are the questions that separate platforms built for real deployments from those built for demo rooms.

1. What happens when a screen loses internet for 48 hours? Does it keep playing cached content? Does it show a black screen? Does it display an error message? The answer reveals the platform's offline architecture — arguably the most important technical consideration for any deployment outside a data centre.
2. Can I export all my content and playlists if I leave? If the answer is no, you are building on rented land. Your content — images, videos, layouts, schedules — should be yours. Data portability is non-negotiable.
3. What is the actual bandwidth consumption per screen per month? Not the theoretical minimum. The real number, with typical content (a mix of images, videos, and widgets). This determines whether your existing network can support the deployment or whether you need infrastructure upgrades.
4. How many API calls are included, and what happens when I exceed them? If you plan to integrate with POS, room booking, or data feeds, API limits matter. Some platforms throttle or charge overage fees that dwarf the base subscription.
5. Can I see your uptime history for the last 12 months? Not a promised SLA. Actual historical uptime. A 99.9% SLA means nothing if their real uptime is 98.5%. Ask for a status page URL or incident history.
6. What is the longest contract term you offer, and is there a month-to-month option? This tells you whether the company is confident enough in its product to let you leave at any time, or whether it relies on contract lock-in to retain customers.
7. What happens to my screens if your company shuts down? Ask about the player's dependency on the cloud. If the player is a thin client that streams everything in real time, your screens go dark the moment the servers do. If it caches locally and can operate independently, you have a safety net.

Pricing models compared

Digital signage pricing falls into three primary models. Each has tradeoffs, and vendors are not always transparent about which model they actually use.

The per-screen model is the most transparent for the majority of deployments. You know exactly what each screen costs, budgeting is linear, and you only pay for what you use. Be wary of "enterprise" pricing that requires a sales call — this is usually the starting point of a negotiation designed to charge you as much as the vendor thinks you'll accept.

Contract red flags

Every digital signage contract should be read in full before signing. These are the clauses that cause the most pain:

• Auto-renewal with short notice windows: A 12-month contract that auto-renews for another 12 months unless you cancel 60-90 days before expiry. Mark your calendar the day you sign, or you'll be locked in for another year by accident.
• Price escalation clauses: "We reserve the right to adjust pricing with 30 days' notice." This means your £5/screen/month can become £8/screen/month with a single email. Insist on price-lock language for the contract term.
• Storage and bandwidth limits buried in fair-use policies: The plan says "unlimited storage," but the acceptable-use policy caps you at 5GB per screen. Read the AUP as carefully as the main agreement.
• Hardware purchase requirements: Some platforms require you to buy their branded hardware or "certified" devices at significant markups. If the platform only works on hardware the vendor sells, that's not a software platform — it's a hardware sales funnel.
• Termination penalties: Some contracts charge the remaining balance of the term as an early termination fee. A 36-month contract with 24 months remaining means you owe two full years of fees to leave.

Hardware lock-in traps

Hardware lock-in is the most insidious trap in digital signage procurement. It works like this: the vendor offers a "free" or heavily subsidised media player when you sign up. The player runs proprietary firmware that only works with their platform. Two years later, when you want to switch vendors, you discover that your 200 media players are expensive paperweights — they can't run any other signage software.

The antidote is simple: choose platforms that run on standard, open hardware. A platform that works on Raspberry Pi, Fire TV, Android devices, and web browsers is one that you can always switch away from without replacing a single piece of hardware. Your screens and players remain useful regardless of which CMS you're running.

Questions to ask about hardware independence:

• Does the player app run on off-the-shelf devices I can buy from any retailer?
• Can I switch the CMS without replacing the media player hardware?
• If I buy hardware from you, can I repurpose it with other software later?
• Is the player application available in a public app store, or only through your provisioning process?

Proof of concept best practices

Never commit to a large deployment without a proof of concept (PoC). A PoC is a controlled trial of 3-10 screens in a real environment — not a demo room — running for at least 30 days. Here is how to structure one that actually tells you what you need to know:

1. Use your real content. Not the vendor's sample content. Upload your actual images and videos, build your real playlists, and create the schedules you'll actually use. The goal is to test the workflow, not admire stock photography.
2. Use your real hardware. If you plan to deploy on Raspberry Pi, test on Raspberry Pi. If you plan to use Fire TV Sticks, test on Fire TV Sticks. Performance on the vendor's demo hardware is irrelevant.
3. Use your real network. Deploy the PoC screens on the same network your full rollout will use. If your retail locations have 5Mbps connections, don't test on your office's 1Gbps fibre.
4. Involve the actual operators. The person who will manage the screens day-to-day should be the one running the PoC, not the IT director or the project manager. You need to know whether regular staff can use the platform without constant support.
5. Define success criteria in advance. Write down exactly what "success" looks like before the trial starts: content upload time under X seconds, screen recovery after network loss within Y minutes, Z percent of scheduled content playing on time.
6. Simulate failure. Unplug the network cable. Kill the Wi-Fi. Reboot the player. Cut the power and restore it. You need to know how the system behaves when things go wrong, because in a real deployment, they will.

Vendor scoring template

Use this template to score vendors objectively. Weight each criterion based on your priorities (the weights below are starting suggestions), and score each vendor from 1 to 5 during your evaluation.

To calculate the weighted total: multiply each score (1-5) by its weight, sum all results. Maximum possible score is 455. Any vendor scoring below 300 has significant gaps. Below 250, walk away.

Decision timeline

A well-run digital signage procurement takes 6-10 weeks from initial research to signed contract. Rushing the process leads to regret; dragging it out leads to analysis paralysis. Here is a realistic timeline:

The most important thing you can do for your organisation is slow down during weeks 5-8. The proof of concept is where the truth lives. Every vendor looks good in a demo. Very few look good after 30 days of real-world use by real operators on real networks. That's the test that matters.