The true cost of personalized video: why per-render pricing limits enterprise QSR scale

The true cost of personalized video: why per-render pricing limits enterprise QSR scale

The sticker price of a personalized video platform is rarely the real cost. For a national QSR brand, the number that determines whether personalized video is viable at scale is the pricing model, and most legacy platforms use a model that punishes exactly the scale a fast food brand operates at. Per-render pricing charges a fee for every single video generated, which is fine for a pilot of ten thousand and a dealbreaker for a campaign to ten million. Understanding the true cost means understanding why per-render pricing caps enterprise scale, and why infrastructure pricing removes the cap.

This piece is written for the marketing and finance leaders at enterprise QSR brands who have to make personalized video pencil out. It explains the two pricing models and why the difference is decisive at scale.

What is per-render pricing, and why does it limit scale?

Per-render pricing means the platform charges a fee for each individual video file it generates, so the total cost scales linearly with the number of videos produced. Every customer, every variant, and every campaign update adds another render and another charge.

For a small campaign, this looks affordable. The problem is that QSR marketing does not run small campaigns. A national brand blasting a promotion to ten million loyalty members generates ten million renders in a single send. Run that weekly, add A/B variants, add localization per market, and the render count climbs into the billions per year. At a per-render fee, the cost becomes a number no marketing budget can absorb, which is why per-render personalized video stalls at the pilot stage for enterprise QSR.

The hidden cost is worse than the visible one. Because every render costs money, teams on per-render pricing ration personalization. They limit variants, skip updates, and cut the audience to control spend, which undermines the entire point of personalizing. The pricing model does not just cost money; it caps the ambition of the campaign.

What is infrastructure pricing?

Infrastructure pricing means the brand pays for the platform capacity rather than for each individual render, so the cost stays flat regardless of how many videos are generated. Ten thousand renders or ten million, the price does not change with volume.

This model fits how QSR marketing actually operates. A brand can send to its entire loyalty base, run weekly, add every variant, localize per market, and update as often as needed, without watching a per-render meter. The personalization can be as deep and as broad as the campaign requires, because volume is not the cost driver.

The shift matters most at the top of the scale, which is exactly where QSR brands live. For a comparison of the pricing models against a legacy per-render platform, see Blings vs Idomoo: which personalized video platform is right for your enterprise.

Why does the pricing model come down to architecture?

The pricing model is not an arbitrary business choice; it follows from how the platform renders video. A platform that pre-renders a separate file per customer on its own servers has a real per-render cost, compute, storage, delivery, and it passes that cost on as per-render pricing. The architecture forces the pricing.

On-device rendering means the personalized video assembles on the customer’s own device from a single template rather than being pre-rendered as a file on the platform’s servers. Because the platform is not spending compute and storage to generate a file per customer, it does not need to charge per render, which is what makes flat infrastructure pricing possible.

This is why the pricing conversation is really an architecture conversation. A per-render price tag is a symptom of a server-side rendering model. Flat infrastructure pricing is a symptom of on-device rendering through MP5 technology. For the architectural foundation, see the MP4 is dead and AI video personalization in 2026: why architecture matters more than the algorithm.

What does affordable scale look like in production?

McDonald’s ran localized loyalty campaigns across many markets on the on-demand model, deploying and updating offers without a per-render meter capping the volume. Habit Burger Grill lifted loyalty membership signups by 47% with personalized video that reached its full audience rather than a cost-limited subset. See the Habit Burger Grill case study. Live Nation VIP produced a 17.55% lift in unique opens and a 16.6% share rate from a single template that served its entire fan base without per-render costs constraining the reach. See the Live Nation VIP case study.

The Takeaway

The true cost of personalized video is set by the pricing model, and the pricing model is set by the architecture. Per-render pricing, a symptom of server-side rendering, scales linearly with volume and caps enterprise QSR ambition at the pilot stage. Infrastructure pricing, made possible by on-device rendering, stays flat regardless of volume and lets a national brand personalize as deeply and as broadly as the campaign demands. McDonald’s, Habit Burger Grill, and Live Nation VIP all run at scale on the flat-cost model.

For an enterprise QSR brand blasting ten million users, the pricing model is the whole decision. Per-render pricing makes massive scale unaffordable. On-device rendering with infrastructure pricing makes it routine. The architecture is the economics.

References and further reading

• Blings vs Idomoo: which personalized video platform is right for your enterprise
• Habit Burger Grill case study
• Live Nation VIP case study
• The MP4 is dead
• AI video personalization in 2026: why architecture matters more than the algorithm