Swinging Between Demos and Deals
# Swinging Between Demos and Deals
I love when an episode starts with a little chaos and ends with a clear pulse. That’s exactly how my conversation with Pedro and Craig went. We kicked things off wrestling with tech gremlins, then slid into this honest look at making an indie game while life keeps happening. Their project, Tokyo Neon Monsters, looks like a candy shop of stylized 3D creatures, but the story behind it is the chewy part. These two are balancing day jobs, chasing publishers, debating when to drop a demo, and doing it all while trying to build something fun enough to survive first contact with players. I’ve been there. It’s a cocktail of excitement, doubt, and pure momentum.
## What we talked about
Pedro is a 3D artist from the film and VFX world, the kind of person who can sculpt a monster that feels like it has a personality before it ever blinks. Craig is a designer-programmer-lecturer who spends his days teaching game methods and his nights wiring Unity scenes together until they behave. They met in the wilds of a Facebook indie group, which sounds like the plot of a cautionary tale, but in this case it worked. First they talked once a week, then they prototyped, then the project snowballed into nights and weekends, and eventually they formed a company around it.
A big thread was the eternal indie dilemma: demo before publisher, or publisher before demo. Pedro’s worked on a separate project with a production company and got the classic advice to hold back the demo because a future publisher might want to change the direction. At the same time, everyone knows a demo can catch fire and make the deal easier. There really isn’t a single right move, and they’re living in that limbo while actively pitching. They’ve got a tight 45-minute build, a clean pitch deck, gameplay video, and all the usual trimmings queued up, just in case any portal asks for the whole package.
We also dug into playtesting scar tissue. They shipped builds to friends one at a time, watched people bounce off tutorials, and rebuilt their onboarding more than once. I laughed when Craig described adding a giant arrow to teach a placement mechanic, only to watch players ignore it. Been there. You want a game with soul, not a babysitter made of pop-ups, but there’s a line between discovery and confusion. Finding that line takes more iterations than pride likes to admit.
Finally, that tutorial story is a quiet master class in game UX. If a giant arrow doesn’t work, the problem isn’t size. It’s context. Players need to understand why, not just where. In product terms, that’s moving from instruction to affordance. The UI should make the action feel inevitable. Sometimes that means smarter sequencing, better verbs, or a playful micro-challenge that teaches through doing. You can respect the player’s intelligence and still light the path.
## My closing thoughts
What I loved about this conversation is how human it felt. Two people building a weird, stylish tower defense game and choosing to keep going, even when the right move isn’t obvious. That’s indie life. You pick a direction, you ship something small, you listen, you adjust. Publishers help, but they don’t define the soul of the work. Engines matter, but only as much as they help you finish the next scene. And the audience you want is the one that sticks around while you figure it out in public.
Talking to Pedro and Craig nudged me too. I came up through IT before I decided to finish one of my own ideas and commit to this creative path. The magic isn’t in the tools. It’s in the reps, the swings, the willingness to hear that your arrow still isn’t enough and try a different way to teach the moment. Tokyo Neon Monsters has that energy, and I can’t wait to see how their demo lands. Whether they sign a partner or go it solo, the heartbeat is there. That’s what keeps players coming back and what keeps creators coming back to the desk tomorrow.
Episode Info
Tooling came up too. They’re building in Unity, though Craig knows his way around Unreal and Godot. For them, the engine question isn’t philosophical. It’s whatever lets them move fast and finish. The bigger decisions are about scope and runway. The plan is modular: more characters, more modes, maybe co-op and meta progression if funding lands. Without a publisher they’ll still finish, just more slowly and with a leaner feature set. With a publisher, they get not only money, but QA muscle, platform relationships, and the kind of marketing reach you can’t brute-force with two people and a Discord.
## What stood out / lessons learned
The first thing that hit me was how openly they treat feedback. There’s a maturity in completely rebuilding a tutorial because one honest friend sent a brutal list. That’s entrepreneurship in a nutshell. Listen hard, keep the parts with a heartbeat, and rebuild the rest. It’s easy to talk about being user centered. It’s harder to own the moments where the player says, I don’t get it, and that’s on you.
Next, their approach to scope made me grin. Indie development rewards modular thinking. Design the core loop so it’s fun on day one, then layer in the marathon features when you can afford to. Endless mode, local co-op, meta systems, cosmetics… none of that matters if the first ten minutes don’t click. Their emphasis on a 45-minute, low-bug demo says they understand the audition. Ship a small slice that sings, then earn the right to make it an album.
Another thing that stayed with me was Pedro’s career arc. Hyperreal VFX trains you to worship technical precision, but it also boxes in your creative impulse. In games, he gets to ship art that moves right away and learn from how people touch it. That immediacy is addictive. For anyone switching from IT or film or academia into software products, this is the pattern: build something people can poke, shorten the feedback loop, and let the loop teach you. The tech stack matters, sure, but the habit of finishing matters more. Pedro’s mantra of consistent personal work since 2019 is exactly the mindset that carries you through the messy middle.
We talked about the marketing treadmill too. Building and promoting at the same time is not two jobs; it’s three. You have development, you have distribution, and you have audience-building, which is its own craft. Social posts are not a side quest. They’re a product surface. But timing matters. If you’re seeking a publisher, you might hold back a public demo and still communicate with intent: short gameplay clips, dev diaries, and tight community updates. The mistake isn’t posting less or more. It’s posting without a strategy that matches your immediate goal.
