Services
What a publisher actually does
Six areas of work that take a game from a build on a developer’s machine to a release players can find, buy and enjoy. We agree with each developer which of them we handle.
Game publishing and release planning
We take a finished or nearly finished game and turn it into a planned release, with clear milestones and responsibilities.
Publishing starts with a plan. Together with the developer we look at where the game is today, what still needs to happen before release and who is responsible for each part. The result is a written release plan with milestones that both sides can follow.
The plan covers the build schedule, store submission, age rating questionnaires where a platform requires them, release timing and the materials needed for launch. We revisit it as the game develops, so changes are agreed rather than discovered late.
Typically includes
- Review of the current build and remaining scope
- Written release plan with milestones
- Coordination of submission and approval steps
- Agreed release timing
Digital distribution and store presence
Preparing store pages, descriptions, screenshots and builds so a game is presented clearly to players on digital storefronts.
Most independent games reach players through digital storefronts for PC and mobile. We prepare and manage the store presence for the games we publish: descriptions, feature lists, screenshots, trailers supplied by the developer, system requirements and content information.
We also handle the practical side of distribution, such as uploading builds, setting up release branches and keeping store information accurate when the game is updated.
Typically includes
- Store page copy and media preparation
- Build uploads and release branch setup
- Accurate content and requirement information
- Store updates after patches
Localisation coordination
Organising translation of in-game text and store materials so a game can be released in more than one language.
A game that is available in several languages can reach more players. We help decide which languages make sense for a particular game, prepare text files for translation and coordinate the work with translators.
After translation, the localised text is checked in the game itself, because a sentence that reads well in a spreadsheet can still overflow a button or lose its meaning in context.
Typically includes
- Language selection for the specific game
- Preparation of text for translators
- Coordination of translation work
- In-game review of translated text
Quality assurance and playtesting
Structured testing before release, so problems are found and fixed before players meet them.
Before a game is released it needs to be played the way players will play it. We organise structured test passes and playtests, record issues in a shared list with clear reproduction steps and help the developer decide what must be fixed before launch.
Testing continues after release for updates, so new content does not break what already works.
Typically includes
- Test plans for the main game features
- Organised playtest sessions
- Shared issue list with clear priorities
- Regression checks for updates
Launch communication and community
Announcements, press materials and player communication that tell people what the game is and when they can play it.
Players need to hear about a game before they can buy it. We prepare announcements, a press kit and release news, and we plan when each piece of information is shared.
We also help set up and look after the channels where players talk to the team, so questions about the game receive a reply and feedback reaches the developer.
Typically includes
- Announcement and release news
- Press kit with facts, media and contacts
- Communication timeline around launch
- Player feedback gathered for the developer
Post-launch update planning
Planning patches and content updates for the games we publish, based on player feedback and the developer’s goals.
Release day is not the end of a game’s life. After launch we review player feedback and reported issues with the developer and plan which fixes and additions come next.
Each update is tested, described clearly in patch notes and reflected on the store page, so players always know what has changed.
Typically includes
- Review of feedback and reported issues
- Update and patch planning
- Clear patch notes for players
- Store information kept current
Not sure which of these your game needs?
Try the release readiness check on our home page, or describe your game to us directly.