By Rhea Kapadia — Licensing & Merchandising, Lantern House Pictures, Ahmedabad
I lead licensing and merchandising at Lantern House Pictures in Ahmedabad. Our portfolio includes 64 active licence agreements across 11 countries, and two animated series licensed for game tie-ins.
Those figures describe a portfolio, not a list of open rights. They also explain why a game pitch needs to answer more than “Wouldn't these characters look good in our game?”
A licensing conversation connects three things: a player experience, a specific rights package, and a team capable of delivering both responsibly. A recognisable character can start that conversation. It cannot replace a product plan.
Here is a studio-side framework I recommend developers use when approaching an animation licensor. It is practical guidance, not a universal studio policy or legal advice.
Start with public games—not imagined deal terms
These four released franchise tie-ins are listed in the RAWG Video Games Database. The observations come from their catalogue descriptions; the pitch lessons are my interpretation.
| Public release | What RAWG documents | What a developer can learn for a pitch |
|---|---|---|
| Teenage Mutant Ninja Turtles: Shredder's Revenge (2022) | Pixel art invoking the Turtles' classic 1987 design, familiar locations, and classic brawling mechanics. | Identify the particular incarnation of a franchise you want to adapt, then connect its appeal to what players actually do. “TMNT” alone is not a complete creative brief. |
| SpongeBob SquarePants: The Cosmic Shake (2023) | Platforming abilities, themed Wishworlds, costumes, and SpongeBob–Patrick banter. | Explain how the game's movement, scenarios and character interactions express the property's identity—not just how you will reproduce its visuals. |
| Adventure Time: Pirates of the Enchiridion (2018) | An all-new story, exploration of Ooo, playable familiar characters, tactical combat and series-cast voices. | An adaptation can propose a new playable adventure rather than retell an episode. Make the boundaries for new stories and character behaviour explicit. |
| The LEGO Movie - Videogame (2014) | A story closely following the film, with different building capabilities for Regular Builders and Master Builders. | A closer narrative adaptation still needs a meaningful translation into systems, abilities and player decisions. |
These are illustrations, not claims of Lantern House involvement or endorsement. RAWG records do not establish the underlying royalty rate, minimum guarantee, exclusivity, approval process, rights availability, sales or profitability. A catalogue entry is not a licensing term sheet.
What makes a potential partner credible?
1. A reason this property should be a game
Start with player verbs: explore, build, cooperate, solve, race, collect. Then show why those actions belong to this world and these characters.
A useful one-page mapping is:
Audience expectation → player action → mechanic → brand boundary
For example, if a property's appeal is collaborative problem-solving, explain how players solve something together. Also explain how failure, competition and rewards preserve that appeal. This is a hypothetical design test, not a description of any of the games above.
A short prototype using your own or placeholder assets can demonstrate the loop. Do not assume an enquiry gives you permission to distribute a branded demo, reproduce protected assets or announce a partnership.
2. Evidence that you understand the audience
“Animation” is not an age rating. Specify the audience you are designing for and the evidence behind that choice.
Show the intended session length, reading and input demands, accessibility options, onboarding and target content rating. If you propose online play or user-generated content, explain moderation, reporting, escalation and ongoing staffing. If children may use the game, identify the privacy, advertising and purchasing questions that need specialist review in each target market.
The studio should not have to discover your monetisation model after approving the art direction.
3. A precise rights request
“We want worldwide game rights” is broad enough to conceal several different products.
Make your initial request legible:
- Property and version: which series, characters, visual era and story material?
- Product and platforms: what game, on which devices and distribution services?
- Territories and languages: where will it be sold, promoted and supported?
- Term and exclusivity: what duration and category of exclusivity are you proposing, if any?
- Extensions: are ports, DLC, live events, sequels or crossovers part of the request?
- Assets and promotion: what do you need for the game, trailers, store pages and marketing?
Ask separately about music, recordings, performer permissions, localisation and other third-party material. For example, The Cosmic Shake's RAWG description lists series actors and music. That is a reminder to discuss those components explicitly—not evidence that they automatically accompany any character licence.
Merchandising rights, sublicensing and AI-related uses should likewise never be assumed to follow from a game discussion. Actual permissions depend on the negotiated agreement and the rights the licensor controls.
4. Proof that the team can deliver
A beautiful deck helps. Delivery evidence helps more.
Bring relevant shipped work and explain your team's actual contribution, especially if a portfolio title involved a larger company. Name the leads responsible for production, engineering, creative direction, QA and commercial decisions.
Show a feasible scope, funding status, milestone plan and principal risks. Separate money already committed from money you hope to raise. Explain how you will pay for localisation, certification, accessibility, customer support and post-launch obligations—not just the first playable build.
For an early-stage developer, a small, honest proof of capability is more useful than borrowed credibility or an implausibly large roadmap.
5. Commercial clarity without pretend benchmarks
There is no responsible universal royalty percentage or minimum guarantee to copy from these public releases.
Instead, state your business model, indicative development budget and currency, funding position, intended pricing approach, marketing responsibility and support plan. Distinguish the development budget, licensing consideration and marketing spend.
During commercial discussions, align on revenue definitions, permitted deductions, reporting, audit rights, payment currency and timing. Model downside cases as well as the optimistic forecast. The purpose is to make assumptions visible, not to turn the first enquiry into a full contract negotiation.
6. A workable approval relationship
Approvals are production dependencies. Plan for them that way.
Propose named contacts and review points for character treatment, narrative, gameplay, monetisation, promotional materials and release readiness. Agree which decisions require approval, how feedback is consolidated, how versions are tracked and what review windows are realistic across time zones.
Do not build a schedule that depends on silence meaning approval. Do not treat a target launch date as permission to announce before approval.
The studio has responsibilities too: clear brand guidance, a reliable decision-maker, a realistic review process and prompt visibility into rights constraints. A partnership should reduce uncertainty on both sides.
How to approach an animation studio
Find the authorised licensing route. Use a verified studio contact channel or authorised representative. An animator, social-media manager or fan community may not be able to discuss rights. Ask who handles interactive licensing rather than mass-messaging the production team.
Lead with a non-confidential summary. A concise email or enquiry should make the property, player experience, requested scope, team credibility and next step easy to understand. Link to relevant work. Avoid unsolicited source code, full scripts, sensitive financial documents or large attachments. Agree any NDA and secure sharing process before confidential material changes hands.
Ask about availability before assuming it. Existing agreements may create constraints by territory, platform, product category or term. A studio's international footprint does not prove that a particular game-rights package is available.
Make the next step small. Ask whether the proposed scope is worth an initial fit discussion. You do not need to request a licence, asset library and launch announcement in the first message.
Follow up respectfully. Honour any stated process or timeframe. If none is given, one concise follow-up is more useful than repeated messages to unrelated staff. Keep decisions in a trackable business channel, not scattered across personal DMs.
A first-contact template you can adapt
The brackets below are placeholders, not real projects or contact details.
Subject: Game-licensing enquiry: [property] / [genre] / [platforms and territories]
Hello Licensing Team,
I'm [name and role] at [developer or publisher]. We have shipped [relevant title and our contribution], with examples at [portfolio link].
We are exploring a [genre] for [audience] in which players [core actions]. [Specific aspect of the property] makes this a meaningful adaptation because [brief reason].
Our initial request concerns [property/version], [platforms], [territories/languages] and [indicative term]. The project is at [stage], with [funding status], an indicative development budget of [range and currency], and a proposed [release window]. Our intended business model is [model].
Is this scope available for an initial fit discussion, and are you the right team to review it? We can share a non-confidential one-page overview and agree any NDA before sensitive materials.
Thank you,
[Name / role / company / contact details]
Make the enquiry route visible
A contact page should explain what happens after a developer clicks “send.” A practical proposed funnel is:
- Enquiry received: contact details, concept and requested rights enter the licensing team queue.
- Named triage: Licensing & Merchandising checks completeness and routes the enquiry to an accountable owner.
- Rights and creative-fit review: assess availability, audience fit, capability and delivery readiness.
- Qualified conversation: clarify scope and, where appropriate, agree an NDA and secure material sharing.
- Commercial and legal review: resolve scope, approvals and economics before an agreement, production or a public announcement.
Build in “needs more information” and “not a fit” outcomes. Collect only what is useful at the first stage, provide an appropriate privacy notice before launching a form, and do not imply that submitting an enquiry grants rights, creates confidentiality or guarantees a deal.
This is a recommended intake model, not a claim that a particular live system or response-time commitment is already in place at Lantern House.
The pitch I want to be able to understand
Not simply: “We love your IP.”
But: “We understand why this audience loves this world. Here is the game they will play, the rights we need, the team that can deliver it, and how we will work with you.”
That gives a licensing team something concrete to evaluate—and gives a developer a much better foundation for a partnership.
Source and scope note: RAWG catalogue records and descriptions linked above were consulted on 19 November 2026. Years refer to the records' release fields; dates can vary by platform and territory. Public descriptions are used for factual illustration, not as independent verification of every marketing claim or as evidence of private commercial terms. Lantern House's portfolio figures and the author biography are supplied by the author. No confidential agreement terms or unnamed series details are disclosed.
Top comments (0)