In this article
"Just self-publish" is common advice and mostly good advice. It is also incomplete. A publisher is not one service; it is a bundle of about a dozen, and going without means either doing each yourself or deciding it does not matter.
What a publisher actually does
- Funding, usually recoupable against royalties.
- Certification and platform relationships — getting your build through console submission and onto storefront front pages.
- QA and localisation at a scale a small team cannot staff.
- Marketing: trailers, press outreach, influencer seeding, storefront merchandising, paid user acquisition.
- Business affairs: contracts, ratings boards, tax, regional compliance.
What you can realistically replace
Marketing is the one most solo developers underestimate and most can partly cover: a consistent devlog, a wishlist campaign, and a genuinely good trailer will do a lot. Certification is learnable but slow the first time. Localisation can be scoped down to a few key languages.
What is hard to replace
Cash flow and platform relationships. Without funding you are shipping on savings and nerve, and without a publisher's account manager you are in the same support queue as everyone else. Neither is fatal. Both are why publisher deals still exist.
Decide deliberately. Self-publishing is a set of trade-offs, not a free upgrade.
