A pilot in one building is a controlled experiment. The TVs were bought in one batch, the network was tuned by one engineer, and the person who configured the screens sits ten minutes away. A rollout across twenty franchise properties is none of those things, and the failure pattern is consistent: the pilot proves the concept, then deployment stalls somewhere between property three and property seven for reasons that have nothing to do with advertising and everything to do with procurement, wiring and paperwork. If you are planning multi-property deployment, budget for these five problems now, because each one is cheap to prevent and expensive to discover.
Pilots are usually built on a specific TV model, and the moment the rollout order lands, purchasing discovers that model is end-of-line or the franchise's AV supplier quotes a "equivalent". Equivalents are rarely equivalent for in-room use. The two things that actually matter are whether the platform allows managed third-party app installation and whether the set survives a daily power cycle, and both vary across model lines from the same manufacturer. We covered the platform-by-platform differences in our platform comparison, but the rollout-specific lesson is harder: write the procurement spec at the SKU level, including firmware baseline, and reject substitutions without a re-test of one sample room. One franchise group we worked with lost two months because 60 "equivalent" sets arrived locked to a hospitality mode that required a paid management licence per screen. The pilot budget did not have that line item, so nothing could be installed until the franchise agreement was renegotiated.
Franchise properties replace TVs on a capital cycle, typically five to seven years, and properties are at random points in it. A rollout that assumes every room gets a new screen on day one either forces early TV replacement, which franchisees refuse to fund, or mixes old and new platforms in the same building, which doubles the support matrix. The pragmatic answer is a phased map: deploy fully in properties due for TV replacement within 18 months, and in the rest, deploy only in the rooms already on compatible hardware, even if that is half the building. Half a property earning is materially better than a full property waiting, and it gives the franchisee visible revenue to fund their own cycle. Build that map before the rollout meeting, because the alternative is deciding it property by property in the room, which is how rollouts drift.
Your pilot building probably has post-2020 networking. Property five may have a guest Wi-Fi system installed in 2017 with client isolation on by default, a captive portal that TVs cannot log into, and a switch closet with no free PoE ports. Every one of those stops a screen deployment cold. The fix is a pre-flight questionnaire the property answers before installation is scheduled, not after the installer arrives: does the TV VLAN get DHCP, is there a captive portal, is client isolation enabled, is there a wired drop behind the TV position, and who holds the network admin password. The four questions that decide a pilot are laid out in our network readiness guide; at rollout scale the same questions just need a deadline, two weeks before install, with an escalation path when a property does not answer. Properties that cannot pass the questionnaire get remediation help, not a surprise visit.
Franchisors control in-room guest experience. Screens that show advertising are guest-facing, so somewhere in the franchise agreement there is a clause requiring brand approval for on-screen content, and it is enforced with unpredictable enthusiasm. Get the sign-off in writing before scaling, including what the screens may show, what the default-on volume policy is, and whether a brand-standard audit applies. The worst version of this problem is a pilot that runs quietly, gets noticed at the annual brand inspection, and is then switched off across the whole group pending review. That story ends with every screen dark for a quarter while the paperwork catches up. Franchisees will also want indemnity clarity on data: even if your screens show ads and do not collect guest data, put that in the agreement explicitly, because the assumption otherwise is that they do.
A screen that freezes and stays frozen for three weeks teaches guests to ignore every screen in the room, including the working ones. In the pilot, uptime is your problem because you are watching it. At scale, uptime needs a named local owner per property, usually the maintenance lead, with a simple weekly check and a defined escalation path. This is the same caretaker function we describe in the caretaker agreement guide, but at franchise scale it becomes contractual rather than informal: one clause naming the person, one page describing the check, and one number to call. Properties without a named owner drift to 80 percent uptime within six months, and at 80 percent uptime the advertiser maths stops working even though nothing appears broken. Monitoring from a central dashboard helps, but a dashboard cannot unplug and re-plug a frozen set in a locked room at 11pm, and a local owner can.
Before any multi-property commitment, run one page per property: TV models and ages by room count, network questionnaire results, brand approval status, named local owner, and a revenue forecast built with the occupancy method from our forecasting guide. Properties score green on all five and deploy in the first wave. Anything else deploys later, in a planned wave, after remediation. This turns a rollout that stalls at property five into a sequence you can actually manage, and it gives the franchisor a document that shows the whole deployment was thought through, which is often the difference between quiet tolerance and active brand support.
A healthy franchise deployment at the one-year mark is unglamorous: 90 percent-plus screen uptime, a two-wave deployment map that finished on schedule, one TV SKU in 80 percent of rooms, and per-property revenue reports the franchisee actually reads. The advertising gets the attention, but what makes the rollout survive is the boring layer underneath: procurement specs, questionnaires, named owners and a written brand sign-off. Get those right and property five looks exactly like property one. Get them wrong and the pilot becomes a story the group tells about why screens do not work here.