Most developers I’ve talked to over the years come to me with the same question, usually after a promising early conversation with a publisher has left them more confused than before. They’ve been told the publisher will “handle the business side.” But what does that actually mean? And more importantly, what are you giving up in exchange?
Here’s what I tell people: a publisher relationship is closer to a business partnership with unequal power than it is to a service contract. Understanding exactly what lands on each side of that equation is the difference between a deal that saves your studio and one that quietly kills it.
The Money Is the Most Obvious Part (And Also the Most Misunderstood)
Publishers fund development. That part everyone knows. What people underestimate is how that funding actually flows and what strings come attached.
A typical publishing deal in the mid-tier indie space right now (current as of July 2026) looks something like this: the developer receives an advance against future royalties, usually anywhere from $200,000 to $2 million depending on scope, team size, and the publisher’s confidence in the project. That advance is recoupable, meaning the publisher takes their cut off the top of every sale until they’ve recovered their investment before you see a single royalty dollar.
Here’s the thing I got wrong when I was early in my career: I assumed “recoupable” meant something like a loan you pay back and then it’s done. The reality is more nuanced. Most deals have a royalty split (often 70/30 or 80/20 in the developer’s favor post-recoup), but that recoup threshold can include marketing spend, localization, QA, porting costs, and sometimes overhead fees that aren’t always spelled out clearly in term sheets. I’ve seen developers reach 90% of their sales targets and still be in recoup.
Read the contract. Have a lawyer who specializes in games entertainment law read the contract. Ones who know game deals specifically (not just general IP attorneys) can be found through organizations like the International Game Developers Association or through referrals at GDC.
What Publishers Actually Do Beyond the Check
| Service | Typical Cost Range | Notes |
|---|---|---|
| Console QA (full certification pass) | $30,000 - $80,000 | Platform-specific compliance requirements |
| Professional localization (10 languages) | $40,000 - $100,000 | High-quality vendor relationships |
| Marketing campaign (mid-size $500K game) | $150,000 - $300,000 | 6-12 month campaign including trailers, influencer seeding, press, paid media |
| Platform port (e.g., PC to Switch) | $100,000 - $200,000 | High-quality conversion to additional platforms |
Funding is the entry point. The operational support is where the day-to-day relationship lives.
Good publishers bring platform relationships that developers simply don’t have access to on their own. Getting featured on the PlayStation Store front page, securing a Nintendo Direct slot, landing on Xbox Game Pass (which as of this year has become a genuinely significant discovery channel for mid-size titles) – these aren’t things you email your way into as a 10-person studio. Publishers have account managers at platform holders with years of established working history. That access has real dollar value that almost never shows up on a term sheet but absolutely shows up in your launch week numbers.
QA and localization are two areas where publishers save developers enormous headaches. Running a full certification-ready QA pass for a console title costs real money ($30,000 to $80,000 is not unusual) and requires people who know platform-specific compliance requirements by heart. Localization for 10 languages at professional quality can run another $40,000 to $100,000. Publishers either do this in-house or have vetted vendor relationships at better rates than you’d get cold-calling. I’ve seen small studios try to self-publish on console for the first time and burn three months they didn’t have on cert failures that a publisher’s QA team would have caught in week one.
The scenario plays out like this pretty often: Small developer attempts first console launch solo, underestimates cert requirements, hits two rejection cycles from platform holder, delays launch by six weeks, misses holiday window they’d built their financial model around. A publisher who’s done 40 console launches would have flagged those cert issues during internal QA before submission ever happened. That six-week slip, in some cases, has meant the difference between a studio continuing and closing.
Marketing and PR: The Part Most Developers Undervalue Until It’s Too Late
This might be the area where the publisher’s contribution is most invisible until it isn’t there.
Game discovery is brutal right now. Steam alone lists tens of thousands of new titles per year. The idea that a good game finds its audience organically is genuinely outdated, and I say that with some sadness because I believed it longer than I should have. Publishers run what are often six to twelve month marketing campaigns for a mid-size release, including trailer production, influencer seeding, press outreach, review copy management, presence at PAX or Gamescom, social media coordination, and paid media buys.
A well-run publisher marketing campaign for a $500K development budget game might involve $150,000 to $300,000 in marketing spend on top of development costs. That number startles developers at first. It shouldn’t. The ratio of marketing to development spend in games has been climbing for years, and even at the indie level it’s no longer realistic to expect a 5% marketing budget to move the needle.
Where publishers get this wrong sometimes is creative control. A developer I worked with closely had their trailer re-cut by their publisher’s marketing team in a way that fundamentally misrepresented the game’s tone. The trailer performed well in testing, but it attracted an audience that wasn’t there for what the game actually was. The launch week numbers looked okay. The review scores didn’t, and the long-tail word-of-mouth never built. It’s one of those things that’s hard to prove with data but the pattern is consistent enough that I believe it’s real.
The Porting and Post-Launch Piece
Publishers often handle or fund ports to additional platforms after the initial launch. This is genuinely valuable work that’s underestimated. A high-quality Switch port of a mid-size PC game runs $100,000 to $200,000 when done properly, and doing it properly matters more than people think. A bad port tanks your review score on that platform and reflects on the whole product.
Post-launch patch support, DLC planning, and community management are also areas publishers often absorb. Some do this well. Some don’t. When I’m evaluating a publisher deal with a developer, I ask specifically what their post-launch support structure looks like and who is accountable for it. Vague answers here are a yellow flag.
Worked example: Mid-size developer signs with a publisher who commits to funding a PS5 and Switch port post-launch. PC version ships, performs solidly. Publisher deprioritizes ports due to internal resource constraints. Ports arrive 14 months late. Revenue opportunity from two platform launches compresses significantly, and the developer’s back-end royalties (which they’d been counting on to fund the next project) arrive 14 months later than their financial model assumed. Studio has to bridge the gap with an emergency credit line. Not a catastrophe, but deeply stressful and avoidable with better contractual milestones around port delivery.
What You’re Giving Up
Control, to varying degrees. This is the honest part of the conversation that doesn’t always happen early enough.
Publishers typically want approval rights over major creative decisions, marketing assets, release dates, and sometimes even team staffing. How much control they actually exercise varies enormously by publisher culture and your leverage in the negotiation. A developer who has shipped a successful previous title has more negotiating room than a first-time team. That’s just reality.
IP ownership is the other big one. Many publishers want to own the IP, especially if they’re funding a significant portion of development. I’ve seen developers sign away IP ownership for deals that seemed generous in the moment and then deeply regret it when the game performed well and they had no ability to make a sequel without the publisher’s permission. If you can negotiate to retain your IP (and grant the publisher a limited exclusive publishing license instead), do it. Not every publisher will agree, but enough will that it’s worth asking.
Revenue share terms, approval rights, IP ownership, contract length, and milestone structure are the five things you want a games-specialized lawyer examining before you sign anything. Honestly, I’d skip the pricey general entertainment lawyers and find someone who does game publishing deals specifically. The IGDA or a consultation through organizations like Makers Fund can point you toward vetted resources.
Sources
- International Game Developers Association (IGDA): Developer satisfaction surveys and publisher relationship resources, igda.org
- Game Developers Conference (GDC) Vault: Annual sessions on publishing deals, IP negotiation, and developer-publisher relationships, gdcvault.com
- Makers Fund: Industry-focused investor and resource network for game developers, makersfund.com
- Simon Carless, GameDiscoverCo Newsletter: Ongoing Steam and platform discovery data, regularly updated through 2026, gamediscovers.substack.com
- Blake J. Harris, “Console Wars” (2014): Background on platform holder dynamics and publisher leverage, still relevant for understanding structural relationships
FAQ
Do I need a publisher to ship a successful game?
No, and plenty of developers successfully self-publish on PC through Steam. Console self-publishing is harder due to cert, QA costs, and platform relationship requirements, but it’s possible. The question isn’t whether you need a publisher but whether the specific deal on the table is better than the alternative for your particular situation.
What’s the difference between a publisher and a developer-publisher like Devolver Digital?
Devolver, Raw Fury, Annapurna Interactive, and others like them operate as what the industry calls “indie publishers.” They tend to offer lighter-touch creative oversight, smaller advances, and more developer-friendly terms on average than legacy AAA publishers. They’re also more selective, so the bar to get a deal is meaningful.
Can I negotiate to keep my IP when signing with a publisher?
Yes, and you should try. Whether you succeed depends on your leverage, the publisher, and deal size. Some publishers (particularly indie-focused ones) are open to limited licensing arrangements where you retain ownership. Get a games lawyer involved before you agree to anything.
What happens if my game doesn’t recoup?
In most deals, the developer doesn’t owe the publisher the unrecouped balance back. The advance is at-risk capital for the publisher, not a literal loan. However, you won’t see royalty income until recoup is hit, and depending on your contract, the publisher may have options around sequel rights or additional content if the title underperforms.
How do I find a publisher that’s a good fit for my game?
Research who published games similar to yours in genre, budget, and platform, then look at how those developers talked about the experience post-launch (Twitter/X, GDC talks, podcasts). Warm introductions from developers who’ve worked with a publisher are worth more than a cold submission. GDC’s matchmaking and events like the Big Indie Pitch are legitimate pathways in.
Photo: AXP Photography via Pexels
Samantha Roberts





