Should You Be Afraid to Negotiate a Game Publishing Deal?

A question I see come up regularly in game dev communities: Will a publisher walk away if I try to negotiate?

The fear is real. Developers spend years building a game, the publisher represents a potential lifeline, and the last thing anyone wants to do is blow the deal by asking for too much. So they sign what’s put in front of them, tell themselves the terms are probably fine, and find out years later that they weren’t.

Here’s the reality: negotiation is expected. Publishers put favorable terms into their starting contracts precisely because they expect pushback. A developer who doesn’t negotiate is leaving money, rights, and protections on the table.

And a publisher who responds to negotiation with anger or pressure? That’s one of the biggest red flags you can encounter before signing.

The Fear of Negotiating Is Real, and Publishers Know It

Many indie and even more established developers approach publisher negotiations from a position of fear. They’ve spent years building their game, the publisher represents a potential lifeline, and the last thing they want to do is blow the deal by asking for too much.

That fear is understandable. It’s also exactly what bad actors count on.

I’ve been in publishing agreement negotiations dozens of times, representing both sides of the table. On the few occasions I’ve seen a publisher react to negotiation with frustration or pressure, it came as a genuine shock — not because it’s surprising in hindsight, but because it’s so far from how a professional business relationship should work.

The flip side is also true: legitimate publishers don’t just tolerate negotiation; some actually view it as a green flag. A developer who fails to negotiate may signal that they don’t understand what they’re signing, or that they’re desperate enough to accept any terms. Neither of those is a good sign for a long-term publishing partnership.

One lawyer quoted in a recent r/gamedev discussion put it plainly: “If they become angry, I think that’s perhaps the biggest cultural red flag that you have in publishing contracts.”

I agree completely.

What a Publisher Getting “Angry” Actually Signals

When a publisher reacts to negotiation with pressure, irritation, or veiled ultimatums, there are really only a few explanations:

• It’s a negotiation tactic. Manufactured frustration is a classic pressure technique designed to make you back down. Don’t.
• They know their contract is one-sided. The clauses you’re pushing back on exist because they benefit the publisher at your expense. Their reaction tells you those clauses matter.
• They don’t actually respect you as a partner. If they can’t treat you as a professional during the courtship phase, the relationship after signing will be worse.

As one developer in that same discussion put it: “The angrier they get, the bigger the bullet you are dodging.”

I’ll be direct about something: I draft these agreements for publishers, in addition to reviewing them for developers. When I’m on the publisher side, I’m not doing the developers any favors. I’m trying to get the best starting point for my publisher client.

Any negotiation of a potential publishing deal should be viewed through that lens. The publisher’s attorney is not your friend, and neither is the contract they present on day one. That doesn’t mean every publisher is a bad actor — it means you need to advocate for yourself, because no one else at that table will.

Other Red Flags to Watch in a Publishing Contract

Publisher attitude is just one signal. There are plenty of others lurking in the contract itself. I covered many of these in my article for GamesIndustry.biz, but the key ones to scrutinize include:

Vague or publisher-friendly revenue definitions. “Net revenue” can be defined almost any way the publisher wants. Make sure you understand exactly what costs are deducted before your share is calculated, and get a right to audit. I’ve reviewed contracts where the deductions were so broad that “net revenue” was less than half of gross sales. Our guide to video game royalties covers this in detail.

No reversion rights. If the publisher fails to release your game, or stops actively selling it, you should be able to get your rights back. A contract with no reversion clause can trap your game in limbo indefinitely — even if the publisher has gone quiet, scaled back, or effectively abandoned the title.

Overbroad IP rights. Some contracts ask for far more than they need: rights to sequels, ports, or derivative works you haven’t even conceived yet. Read the IP provisions carefully. See our post on common game development contract mistakes for more on this.

No concrete marketing commitments. A publisher promising to “promote your game” means nothing without specific, enforceable obligations. What platforms? What spend? By when? Vague marketing language is one of the most common ways developers get burned in deals that look good on paper.

Unilateral termination rights. Can the publisher walk away at any time, for any reason, while keeping rights to your game? That’s a trap, and it appears in more contracts than you’d think.

Before You Negotiate: Get to a Term Sheet First

One of the most practical pieces of advice I give developers before they enter publishing negotiations: get to a term sheet before you ever open the full contract.

A term sheet is a short, plain-language document that outlines the key deal points — revenue split, IP ownership, marketing obligations, milestones. It’s typically non-binding. But it aligns both parties on the fundamentals before lawyers start drafting, and it prevents the scenario where you’re deep in contract negotiations, running out of money, and feeling pressured to accept terms you never would have agreed to at the start.

Negotiate the term sheet first. Once both parties sign off on the key terms, the contract drafting becomes about the details, not the fundamentals.

Know your non-negotiables before you sit down. What are the one or two things you will not budge on? Be ready to say so — and be ready to walk if those lines are crossed.

What to Push Back On

These are the clauses I push back on in every publishing contract I review on the developer’s side:

• Net revenue definition. Push to limit deductions to platform fees. If the publisher wants to deduct marketing costs, cap them at a dollar amount you approve in advance.
• Reversion rights. Define a specific window. If the game isn’t released within X months, or goes off-sale for Y months, you get your IP back.
• IP scope. Strip out rights to sequels, derivative works, and other IP you haven’t created. The publisher should get rights to the game you’re making, not everything you might ever make.
• Marketing obligations. Get specific commitments in writing. Minimum spend, specific channels, defined timelines.
• Termination rights. Any termination clause that lets the publisher exit while retaining rights to your game needs to be renegotiated.

Our guide to negotiating game contracts covers the full process.

Action Steps

• Always negotiate. The contract as presented is a starting point, not a final offer.
• Know your walk-away point before you start. Desperation is visible, and it costs you leverage.
• Use a term sheet. Align on the big picture before you’re in the weeds of contract language.
• Define “net revenue” explicitly. This one clause can determine whether your royalties are meaningful or functionally zero.
• Secure reversion rights. If the game doesn’t release within a defined window, you should get your rights back.
• Have a lawyer review it. Not after you’ve already given verbal agreement to the terms. Before.

FAQ

Will a publisher walk away if I try to negotiate?

A professional publisher won’t. Negotiation is a normal and expected part of any business deal. Publishers routinely include favorable terms in their starting contracts that they expect to give up. If a publisher threatens to walk away simply because you asked questions or pushed back on specific clauses, that behavior is itself a major red flag about how they’ll treat you as a long-term partner.

What is a term sheet in a game publishing deal?

A term sheet is a short, plain-language document that summarizes the key business terms before a full contract is drafted — things like revenue split, IP ownership, marketing obligations, and milestone structure. It’s typically non-binding, but it aligns both parties on the fundamentals early and prevents the scenario where you’re under financial pressure and forced to accept terms you’d never have agreed to at the start.

What are the biggest red flags in a game publishing contract?

Vague or publisher-friendly net revenue definitions, no reversion rights if the game doesn’t release or goes dormant, overbroad IP rights covering sequels and derivative works, no specific marketing commitments, and unilateral termination rights that let the publisher exit while keeping your IP. Any one of these is worth pushing back on. Multiple together is a serious warning sign.

What does “net revenue” mean in a publishing agreement?

Net revenue is gross sales minus agreed deductions. At minimum, platform fees (typically 30%) are deducted. Some publishers also deduct marketing costs, localization, QA, and porting expenses. The broader the deductions, the smaller the pool being split. This is the single most important definition to scrutinize before signing.

What are reversion rights, and why do they matter?

Reversion rights give the developer the ability to reclaim their IP if the publisher fails to release the game within a defined timeframe, stops actively selling it, or goes out of business. Without them, your game can be trapped indefinitely with a publisher who isn’t actively exploiting it — and you have no legal mechanism to get it back.

Should I hire a lawyer before signing a publishing agreement?

Yes. A game attorney will identify unfavorable clauses around recoupment, net revenue, IP ownership, reversion rights, and termination that most developers miss on their own. The cost of a legal review is a fraction of what’s at stake over a multi-year publishing deal. Set up a consultation here.