Balatro
A rules-light deckbuilder that carried hundreds of hours of replay from a small system set. The lesson for small teams: a tight system with clear rules scales into depth without scaling into production cost.
Reading, UK PC games since the first prototype
Build the bench first, then ship.
We help UK indie developers choose an engine, prove a vertical slice, and time a Steam launch. Not a publisher, not an agency — a second pair of eyes on a running build.
What we actually help with
Four jobs come up again and again with UK teams, and they are the four we are set up to help with. Every one of them is a decision you have to make before you can move: which engine carries the project, how far a prototype has to go before you trust it, when a Steam page goes live, and how the build behaves on a handheld.
We do not take a cut of revenue and we do not ask for equity. You keep the build, the store page, and every decision. What you get in return is a second pair of eyes that has read the same engine documentation you have and cares about whether frame time holds where it matters — mid-combat, mid-crossing, mid-save.
It also means we are fine with saying no. If your project needs something we cannot help with, we will tell you and point at what we would read in your position. That is a cheaper answer than a schedule you write around bad advice.
Engine choice is a scope decision, not a taste decision
The question “Unity or Unreal?” is usually the wrong first question. Version one is: what is the smallest thing the game can be, and which engine lets a team of two to five people build that thing without fighting the tool?
Pick wrong and you lose a quarter
Most small teams spend a quarter learning the tool instead of the game. The cost is not the licence fee — it is the four months of shipping you do not get back.
Pick right and the first playable arrives in weeks
A prototype that runs in week three tells you more about the game than six months of design documents — and it changes the pitch in front of a real build.
The trade-offs got to be said plainly
Our engine guide walks through Unreal, Unity, Godot and GameMaker with the parts engine vendors do not tend to lead with — the build times, the plugin debt, the 2D story.
Prototype, then vertical slice
A prototype answers a question. Does the grapple feel good? Is a three-card combo enough to carry a run? Is the fog-of-war readable at 1080p on a laptop screen? A vertical slice answers a different question: would this game, finished, be worth buying?
The gap between the two is where most small PC teams lose their schedule, because the slice demands art, audio, UI and a real menu, and those things take longer than anyone expects.
We treat the slice as the contract with yourself. Once it exists — one level, one run, shippable-looking — the production schedule is written against the slice and not against the pitch.
See the prototyping workflow
01 / What the prototype proved
Movement holds at 60fps on a 2018 laptop; combo loop reads at 1080p.
02 / What the slice adds
One run of content, real menu, audio pass, save behaviour.
03 / What the slice refuses
A second level, a second biome, a second character. Not yet.
04 / What the schedule is written against
The slice as built. Not the pitch as imagined.
Steam pages, demos, and the wishlist question
A Steam page is not a shop sign. It is the first build most players will ever see, and the wishlist number it produces is a lagging indicator of whether the capsule, the trailer and the first thirty seconds of gameplay agree with each other. Announce earlier than feels comfortable.
Page live
Week 0
Next fest
Month 4
Demo drop
Month 7
Launch
Month 11
Deck verified
Post-launch
A demo helps some genres more than others, and the timing matters. A demo that arrives too early spends curiosity without converting it. A demo that ships alongside Next Fest spends it in front of a crowd already looking for something new.
We do not promise wishlist outcomes. Nobody honest can. What we can do is help you sequence the store page, the demo, and the early access decision so they support each other instead of competing for the same week.
Steam Deck changes what “PC game” means. It is a desktop PC with a small screen and a controller, and that combination exposes assumptions in UI layout, text size, and default bindings that desktop testing never catches.
Plan the Steam pageModern PC references worth studying
The best way to plan a PC launch is to read what actually shipped and held up. These are not models to copy. They are calibration — a team building a metroidvania in Godot can learn as much from a deckbuilder's restraint as from any platformer, because the lesson is about system clarity, not genre.
Hades II
The Supergiant pattern of combat and narrative that rewards repeat runs. It sits in current coverage of the strongest PC indie releases because the run structure and the writing carry each other.
Baldur’s Gate 3
The reference for scope, choice and polish, with an active modding conversation that keeps it in front of players years after release. Useful to study for how a mod path designed in early keeps paying off.
Minecraft
A long-tail case study: sandbox creativity and community tooling keep audiences building and buying for a decade or more. Its economy lives on what players make, not on what the studio ships next.
The Sims 4
Life-sim customisation that keeps showing up in recommendation lists. The mechanism is not genre-specific — it is whether the game gives players something to do after the credits.
The long-tail question, asked early
Mod support, save compatibility across updates, and how readable the game is on a two-year-old machine. Moddability is a marketing line only if it is designed in from the start; bolted on later, it becomes support burden.
We raise this in the engine conversation on purpose. Retrofitting a mod path onto a closed architecture is a rewrite, not a feature — and it is the kind of decision that is cheap now and expensive in year two.
The shipped card
Steam Deck changes what “PC game” means
The Steam Deck is a desktop PC with a small screen and a controller, and that combination exposes assumptions in UI layout, text size, and default bindings that desktop testing never catches. A game that runs well on a deck often runs well on a low-end laptop, which is a real slice of the PC market.
Compatibility work is unglamorous: font legibility at 1280×800, control prompts that match the actual device, suspend and resume behaving, save systems that survive a closed lid. Decide early — retrofitting controller-first UI late in production is expensive.
Plan the Steam page
What ships with the card
- Engine The one your team can build in, not the one on the box
- Slice One level or one run, shippable-looking
- Store page Capsule, trailer and description written for the scroller
- Deck pass Text at 1280×800, real control prompts, suspend tested
- Mod path Designed in early, or explicitly not promised
Who this is for, and who it is not for
This site is for indie developers and small studios in the UK, typically one to ten people, building PC games they intend to sell, usually on Steam. It is also useful for solo developers weighing whether to leave a day job, and for small teams between projects planning the next one.
It is not for large studios with an existing production pipeline, and it is not a service for outsourcing code, art or porting. If you want someone to build the game, we are not that. If you want your own plan stress-tested before you commit a year to it, we are set up for that.
We are based at 44 Park Road, Tilehurst, Reading, and we work with teams across the UK by email. You can send a project note any time through the contact page.
Before you send a note
Send a project note
You do not need a pitch deck. You need a short paragraph on the game, the engine you are leaning toward, how many people are on the team, what platforms matter, and where the project is stuck.
Screenshots or a build link help but are optional, and we will not share anything you send without asking. Expect a reply within a few working days.
Monday to Friday, 9:00 AM – 6:00 PM
Reading the site
Pages here are meant to be read in whatever order matches the decision in front of you. Engine first if you have not committed. Prototyping workflow if you have a build but no slice. Steam and Deck if launch is inside a year. Case studies if you want calibration before you decide anything. The legal pages are linked in the footer and they say what they need to say without decoration.
We update pages as engines release and storefront rules change, and we note meaningful edits rather than quietly rewriting. If something on the site looks out of date to you, say so through the contact form and it goes on the list.
Not yet committed
Engine Guide
Unreal, Unity, Godot and GameMaker, with the trade-offs named plainly.
Build, no slice
Prototyping Workflow
Question-driven prototype, then a slice that proves the core loop.
Want calibration first
Case Studies
Shipped PC games read for what holds up, not for what trended.
Replies before you write
Questions a small team asks first
Straight answers to the ones that come up most. If your question is not here, put it in the note — it will get a real reply, not a link.
Which game engine is best for a small PC indie team in 2026?
There is no single best answer, and any site that gives you one is guessing. Unity suits teams who need breadth across 2D and 3D with a deep plugin ecosystem. Unreal Engine suits teams who need high-end 3D and want design work moving through Blueprints. Godot suits lightweight, open-source workflows and smaller scope. GameMaker suits fast 2D iteration. The right pick is the one that lets your specific team build the smallest version of your specific game without fighting the tool.
How long should a prototype take?
Long enough to answer the question it exists to answer, and no longer. If the prototype is testing whether a movement system feels good, that is a matter of days or a couple of weeks, not months. The prototype is disposable. The vertical slice is the thing you keep.
Do we need a Steam page before the game is playable?
Earlier than most teams expect, once you have something honest to show. A store page with a capsule, a short trailer and a clear description starts the wishlist clock and gives you a place to point people. Put it live when the trailer shows the real game, not a target render.
Is Steam Deck support worth the work?
For many desktop-first PC games, yes, because the compatibility work tends to improve the game on low-end laptops too. Text legibility, controller prompts and suspend behaviour are the usual problem areas. Decide early, because retrofitting controller-first UI late in production is expensive.
How important are mods for PC game longevity?
It depends on the audience, but mod support consistently extends how long players stay with a game. Baldur’s Gate 3’s active modding conversation is the clearest current example. If you want mods, design the architecture for them from the start.
What should we include in a first contact note?
The game in a paragraph, the engine you are considering, team size, target platforms, and the specific decision you are stuck on. That is enough for us to reply with something useful.
How the guidance is written
Nothing here is a template
We are not a publisher, not an agency, and not a consultancy with a slide deck. We write the guidance ourselves, mostly from published postmortems, storefront documentation, engine release notes and the day-to-day reality of small teams who pay their own bills.
If a claim cannot be traced to a document or a build we have looked at, it does not go on the page. That is the whole editorial method, and it is worth stating because the PC shelf in 2026 is crowded with advice that skips the boring part.
Our sources, in order
- Postmortems What shipped teams wrote down after the fact, with the schedule they actually ran.
- Storefront docs What the store page rules require now, not what they required three years ago.
- Engine notes Release notes and migration guides, read for what changes the build time or the pipeline.
- Builds we read Projects we have sat with. If the debug overlay does not match the plan, the plan moves.
Your plan, stress-tested before you commit a year
Send a short note on the game, the engine you are leaning toward, how many people are on the team and where the project is stuck. We will reply with something useful — or with the honest answer that we are not the right fit.
At the bench
- Address
- 44 Park Road, Tilehurst, Reading, England
- [email protected]
- Hours
- Monday to Friday, 9:00 AM – 6:00 PM
Note sent through the contact page