In 1993, two guys named John shipped Doom. No publisher. No focus groups. No retention metrics. Just a vision, a deadline, a shareware distribution model, and what would become one of the most influential games ever made.
In 1994, a team of about 20 people at Blizzard shipped Warcraft. Before that, it was a tiny studio with a borrowed office and games nobody had heard of yet.
Those are the stories that got us into this. Not the stories of 500-person dev teams with 12-figure budgets and quarterly earnings calls. The stories where a small group of people who really, really cared about making something good sat in a room and made it happen.
THE SIZE OF THE TEAM CHANGES THE SOUL OF THE GAME
This isn't nostalgia talking — it's a design principle. When a game is made by a small team, every decision is personal. There's no product manager two org levels removed from the actual design. There's no committee sign-off on whether a mechanic is fun enough. The person who thinks of the idea is usually the person who builds it, and then plays it until it's right.
The distance between inspiration and implementation is measured in hours, not sprints. That speed — and the tight creative feedback loop it creates — produces something you can actually feel in the finished product. The game feels like it was made by someone who cared, because it was.
Large teams produce large games. Sometimes those are great. But they also produce games designed by consensus, tested to death by focus groups, and tuned by data until every rough edge — including the interesting ones — has been sanded away.
The best games have a point of view. They feel like they came from somewhere specific and were made by someone with opinions. You can't committee-design a point of view.
CONSTRAINT IS A FEATURE
When you're a small team, you can't do everything. You have to choose. And choosing — really choosing, with limited resources and hard deadlines — is what forces creative problem-solving.
The original Mega Man had a limited color palette and a small sprite size. Those constraints led to some of the most recognizable character and level design in gaming history. The designers couldn't throw hardware at the problem. They had to be inventive.
Constraints don't just limit what you can do — they force clarity about what you're actually trying to do. What is this game about? What does it feel like to play? What should a player remember about it? When you can't paper over weak design with production value, you have to answer those questions correctly.
We operate with deliberate constraints. Small team. Focused scope. One game that does its thing well, not a platform trying to be everything to everyone. That's not a limitation. That's the whole point.
WHAT "RETRO" ACTUALLY MEANS TO US
We don't use retro as an aesthetic band-aid. The pixel art and chip-tune music aren't there to hack your nostalgia. They're there because they express something true about how we think about games — clean, readable, mechanical, and designed to be understood and mastered rather than experienced passively.
Retro, to us, means making games where the design is the point. Where the mechanics are tight enough that getting good at them feels genuinely satisfying. Where there's a high score because the score means something — your skill, your session, your improvement over time.
It means making games that work completely on first contact, with no tutorial that plays the first 20 minutes for you, and no narrative scaffolding designed to keep you engaged long enough to hit the monetization window. You pick it up, you figure it out, you get better. That feedback loop is the oldest and most durable thing in gaming, and we think it still works.
THE PLAN
We're not trying to build a studio empire. We're trying to build great games. One at a time. Made with care. Sold for a fair price to people who want to play them.
If that sounds old-fashioned, it's because it is. We're fine with that. The games that got us here — the ones that are still running on emulators and getting fan remakes and discussed reverently in communities 30 years later — those were made the same way.
Some things don't need to be disrupted. Sometimes the old way is the right way. 1994 didn't need an engagement team. Neither do we.