The Renewal Date on Your Games Licence Is a Decoy. Diarise the Notice Date Before You License HTML5 Games Again.

Before you license HTML5 games for a second term, find the notice date in your renewal clause — not the expiry date. That is the day your leverage quietly ends.

Most catalogue licences get signed by someone who has been told to get games live by a date. Twelve months later that person has moved teams, the portal is running, and the contract is a PDF in a folder nobody opens. Then an invoice arrives carrying a number twelve or eighteen per cent above last year's, and the conversation that follows is not a negotiation. It is an appeal.

The renewal is the second time you buy the catalogue, and it is the only time the scope is genuinely open. First time round you had no usage data and no idea which titles would carry the portal, so you bought breadth because breadth was the safe guess. Now you know which forty titles do the work. That knowledge is worth real money — but only if you spend it before the notice window shuts.

📅 Two Dates, and the One That Matters Comes First

A term licence carries two dates. The expiry date is the one everybody diarises. The notice date is the one that decides whether the expiry date exists at all.

Two structures cover most catalogue deals. A fixed term with automatic renewal runs for, say, twelve months and then rolls into another twelve unless one side gives written notice inside a defined window. An evergreen term has no end date and simply continues until somebody cancels. In both cases the notice window is the actual decision point, and it commonly sits 30, 60 or 90 days before the term end. Thirty days is typical of standard-form agreements; sixty and ninety turn up in negotiated deals, usually at the licensor's request.

Three details decide how much that clause costs you:

• The rollover length. Missing notice on a monthly rollover costs you a month. Missing it on an annual rollover costs a year, and the price for that year is often reset at renewal rather than held.
• The delivery method. Plenty of clauses still require written notice to a named address or a specific contract contact. An email to your account manager, who has left, is not notice.
• Whether notice is all-or-nothing. Most catalogue licences let you terminate the whole agreement and nothing else. If you want to drop one territory or one platform, that is an amendment, and amendments happen when the licensor wants your signature on a renewal — not four months later.

The practical consequence: the day you want the renegotiation to start is roughly 60 days before the notice window opens, not after it closes. Everything below works backwards from that.

📈 The Price Line Is Moving, and Credible Sources Disagree About How Fast

Software pricing is the backdrop to every renewal conversation in 2026, including ones that have nothing to do with software. Vertice's SaaS Inflation Index put SaaS price inflation at 12.1% in April 2026, 14.2% in May and 16.4% in June — the highest reading it has recorded, and by its own comparison almost four times the US CPI figure of 4.2% for the same period. The index is drawn from more than $75bn of processed spend and a benchmark set of 250,000-plus contracts.

Treat that as one dataset, not the market. It is the transaction data of a single procurement platform, weighted towards the categories its customers buy. Other credible reads land lower: Gartner analyst commentary through 2025 described large-vendor SaaS increases in the 10–20% band, and several 2026 trade estimates cluster nearer 12% as an average annual increase. The honest range for enterprise software is roughly 10% to 20%, with the top of that band reserved for renewals where the buyer had no alternative.

A games catalogue licence is not indexed to any of this. But two things follow from it anyway. Your own procurement team will benchmark whatever your licensor asks for against those numbers, so a 6% increase reads as restraint and a 20% one reads as opportunism regardless of what sits underneath. And any licensor carrying hosting, ad-tech, CDN and tooling costs is absorbing some of that curve itself. Asking which line items moved, and by how much, produces a more useful conversation than asking for a discount.

🧾 A Catalogue Licence Is Not a Seat Licence, and the Playbook Doesn't Transfer

Your procurement team runs a lot of renewals. Zylo's 2026 SaaS Management Index reports that the average enterprise faces nearly 211 SaaS renewals a year across an average of 305 applications, and that large enterprises waste $80.6M annually on unused licences. The standard play is well drilled: pull usage, find the seats nobody logs into, deprovision before the renewal date, pay for fewer.

There is no seat to deprovision in a games licence. Four hundred unplayed titles cost you exactly what four hundred played ones cost, because the price was set on scope, not on consumption. Point the SaaS playbook at a content licence and it produces one move — cut the title count — which is the weakest thing you can ask for. Title count is the cheapest concession a licensor can make and the least valuable thing for you to hold.

What actually prices a catalogue licence is a different list: how many domains and properties the games may appear on, which territories, which platforms and formats (web build, APK, TV, kiosk), whether you may sublicense to clients, who hosts, how often new titles arrive, whether any of the content is branded, and what reporting and support you get. Renewal is where those get re-cut. Seats have nothing to do with it.

📊 Build the Cut List From Plays Per Title, Not From Opinions

Before any call, produce one table. Four columns per title, over the last 90 days: plays, unique players, share of site entries, and category coverage (is this the only title you hold in its genre, on its language, or at its device weight?).

If your titles run inside third-party iframes you may only have click-ins rather than in-game events, and that is enough for this job. You are ranking titles against each other on a consistent, if crude, measure — not proving a retention curve. Say so in the meeting rather than pretending to a precision you do not have.

Then be careful about what the ranking does not tell you. Five common traps:

• SEO landing titles. A title with modest plays but a high share of first-touch entries is buying you traffic. Cutting it removes the page that ranks, not just the game.
• Sole coverage. The only racing title, or the only one with Arabic UI, holds a category open. Its replacement cost is higher than its play count suggests.
• Seasonality. Ranking a Halloween or Ramadan title in the wrong quarter tells you nothing.
• Titles that never got shelf space. If a game was never surfaced on the homepage or in a rotation slot, its low play count is a merchandising result, not a content one. Do not cut it — test it.
• Device weight. The title that carries your low-end Android traffic may look mediocre on aggregate numbers and be indispensable to a third of your audience.

What survives that filter is a defensible list. It is also the first honest answer you have ever had to the question "how much of this catalogue are we actually using?" — and that answer is your opening position.

🔁 The Refresh Clause Is Worth More Than the Discount

A frozen catalogue depreciates. Returning players exhaust the front page, the same forty titles carry every session, and by month nine the portal's problem is not price but staleness. A 10% saving on a static catalogue is a worse deal than list price on one that refreshes every quarter.

So convert the cut list into a swap list. Instead of "remove 200 titles and reduce the fee", ask for "replace 200 titles at the same fee, on a schedule". Licensors agree to that far more readily, because it protects their revenue line while costing them inventory they already own. Specifically, put four things in the renewal:

• A committed number of new titles per quarter, with a floor rather than a best-effort promise.
• A swap right — N titles per period exchanged at no charge, at your discretion.
• Replacement rights when a title is withdrawn during the term, so a removal does not silently shrink what you paid for.
• A metadata lead time: thumbnails, descriptions, categories and language files delivered with the builds, not chased afterwards.

🧮 Nine Things to Renegotiate That Are Not the Price

Price is one line. These are the ones that change what the licence is worth:

1. Additional domains and properties. Most first licences name one site. Your second year usually has a second surface in it — an app, a partner white-label, a client microsite.
2. Territories. If you launched in one market and are planning two more, add them now rather than as a mid-term amendment.
3. Formats. Web-only licences age badly. Adding APK rights alongside the HTML5 builds at renewal is far cheaper than opening a second negotiation later.
4. Sublicensing. If you serve clients, the right to deploy the catalogue on their properties is the clause that decides whether you have a product or a permissions problem.
5. Hosting. Licensor-hosted embeds and self-hosted builds are different products with different failure modes. Pick deliberately at renewal.
6. A price escalation cap. The lesser of a fixed percentage or a published inflation index, so year three is not a surprise.
7. A shorter notice window. Ninety days down to thirty is a genuine concession worth asking for, and it costs the licensor nothing if they intend to keep you.
8. Reporting cadence. Monthly play and revenue reporting by title, in a format you can join to your own analytics.
9. A wind-down tail. Thirty to ninety days after term end to remove builds, flush caches and de-index pages, so a clean exit is not a breach.

🚫 Five Ways Operators Lose the Renewal

• Discovering the notice window inside it. By then your only options are sign or roll. Licensors know this, and the quote reflects it.
• Arguing about title count. It is the easiest number to move and the least valuable. You will win it and gain nothing.
• Bringing no data. Without a cut list you are negotiating against the licensor's assumptions about your usage, which are generous to the licensor.
• Treating the account manager as the counterparty. Scope changes — territories, formats, sublicensing — usually need someone else's sign-off. Ask early who that is.
• Renewing on the same scope out of caution. A second year identical to the first is the one outcome that guarantees you paid for breadth you have now proven you do not use.

🗓️ A 120-Day Renewal Calendar, Worked Backwards

Count back from the term end date, not from the invoice.

• Day −120: Pull the plays-per-title table and the licence itself. Confirm the notice window, the rollover length, the notice address and the escalation terms in writing.
• Day −105: Build the cut list and, more importantly, the swap list. Note the titles you never merchandised — those go into a test, not the cut.
• Day −95: Write the scope you want for year two: domains, territories, formats, sublicensing, hosting, refresh cadence. One page.
• Day −90: Open the conversation, before the notice window rather than inside it. Send the scope page, not a request for a discount.
• Day −60: Decide whether to serve notice. Serving notice while continuing to negotiate is normal commercial practice and keeps both options live.
• Day −30: Close on scope and price together. If the answer on refresh cadence is still vague, that is your answer about year three.

🎯 What You Get When You License HTML5 Games From a Direct Licensor

Licensing direct changes what the renewal conversation can cover. Forestry Games has operated since 2017 and licenses a catalogue of 1,049 titles spanning HTML5 games and Android APK games, with titles also published on Google Play and the Apple App Store. Because both formats sit with the same licensor, adding APK rights alongside web builds at renewal is a scope change rather than a new supplier search.

A licence scope is written around your use case: which domains and properties the games run on, which territories, which formats, whether builds are hosted for you or delivered for self-hosting, what branding is applied, and — where applicable — source access. Games are developed in-house as well as licensed, which is what makes swap rights and refresh commitments possible to agree rather than merely promise. You can browse the catalogue to see the range, or start from the HTML5 games and Android games collections if you already know which format your next term needs.

🧸 Licensing Branded Games for Campaigns, Portals and Events

Some renewals are the right moment to add branded content rather than more of the same. Forestry Games works with branded IP and has brand partnerships including Disney, Nickelodeon, Cartoon Network and Warner Bros, and businesses can license branded game content through Forestry Games for campaigns, portals, events and apps.

Branded titles carry their own approval and territory constraints, so they belong in a scope conversation early rather than as a late addition. If a branded window is something you want inside your next term, raise it with the rest of the scope at day −95, not after signature. Ask for a licence scope, request a white-label portal demo, or send the one-page scope you built above and get it priced.

🧭 Put the Notice Date in the Calendar Before You Close This Tab

Open the licence, find the renewal clause, and write two dates in a shared calendar: the term end, and the last day you can serve notice. Then set a third reminder 30 days before the notice window opens, owned by a named person rather than a team inbox. That single act converts your renewal from something that happens to you into something you run.

The rest is arithmetic you already have. You know which titles get played, which ones bring traffic, and which ones have never been given a fair chance. Turn that into a swap list and a one-page scope, and the second term you buy will look nothing like the first — which is the point. If you are approaching a renewal now, or evaluating a move to a direct licensor before the next one, browse the catalogue and ask for a licence scope written around the surfaces you actually run.