zer0Games Studios

Hayden Duswalt — founder of zer0Games Studios, Roblox game developer (known on Roblox as zer0Cactus), and Craig Duswalt's son. His business: build great games on Roblox for players who come back every day.

Roblox profile: roblox.com/users/75676997/profile

zer0Games Studios is Hayden's solo-developer Roblox studio, scaled past solo-developer bandwidth. theAppChicks onboarded him as a client with a managed AI development team configured for Roblox — same platform that powers every other theAppChicks client, tuned for Luau and the Roblox marketplace.

This isn't a startup pitch. Hayden already has two games with millions of plays on Roblox: The Vents and The Vents Relocated. Real players, real retention, real revenue. The question was never whether the games work — it was whether a solo developer could scale them.

Hayden's problem was a capacity problem, not a creativity problem.

• Time is the scarce resource. New features, new maps, new game modes, new events — all of it waits in a queue behind whatever he's shipping this week.
• Economy balancing is a second job. In-game currency, drop rates, progression curves — one bad tuning choice and players churn. Fixing it reactively is always more expensive than tuning it intentionally.
• Content ops don't scale linearly. NPC dialogue, quest text, UI copy, localization — every new map multiplies the writing load.
• Exploit prevention never sleeps. Players will always find edges. Keeping up with that on top of shipping is how solo developers burn out.
• Setting up AI infrastructure himself is the wrong spend. A game developer shouldn't be wrangling API keys, agent orchestration, and pipeline config. That's where the work isn't.

theAppChicks doesn't set Hayden up with his own AI infrastructure — once onboarded, he gets a managed AI team through the same platform that powers Craig's app, configured for Roblox. Here's what his studio will get out of it, as business capabilities Hayden will have:

Shipping velocity past solo-dev bandwidth

A six-role team working in parallel on the parts of the game that used to queue behind each other. Features that would have waited months will ship in weeks, while Hayden's attention stays on design and direction.

Economy and balance handled intentionally

A dedicated Economy / Balance role will monitor in-game currency flow, drop rates, and progression. Changes get balance-reviewed before they ship, not debugged after players complain.

Content pipeline that keeps up with the game

NPC dialogue, UI copy, quest text, and localization all move through a content role tuned to Hayden's voice. When a new map ships, the writing lands with it — not three weeks later.

Continuous exploit and performance watch

A QA / Playtester role will test for exploits, performance regressions, and edge cases as code lands — not as a fire-drill after a popular streamer finds the bug.

A business that stays Hayden's

His Roblox user, his studio, his revenue. The agent team is a service, not a co-owner. If Hayden ever chose to go back solo, everything moves with him: the repo, the tooling, the playbook.

• Updates arriving on a cadence that feels like a real studio runs the game — because one will.
• New maps, modes, and events that don't break the economy on launch day.
• Writing that matches the tone of the games they already love.
• Exploits patched fast; performance that holds up as population grows.

• A dashboard to submit feature requests ("add a new map to The Vents").
• Visibility into what agents are working on, with PRs he reviews before they merge.
• Balance reports before economy changes go live — not after.
• Content approvals in a queue he clears in minutes, not hours.
• No Claude Code, agent configs, or heartbeat scheduling to manage. He'll see his games getting better, faster.

zer0Games is the pattern for any solo creator whose ceiling is their own bandwidth:

You've proven the product works. You have real users, real revenue, and a clear direction. The thing blocking the next level isn't taste or ambition — it's hours. A managed team that works inside your game, your repo, and your tools lets the business scale without surrendering ownership.

It's also proof the theAppChicks model isn't just an app shop. Craig gets a mobile app for coaches. Hayden gets a Roblox game studio. Sophia gets a daily-encouragement ritual. Dina gets an editorial lifestyle brand. Jen gets a Hoʻoponopono membership site. Same platform, same process, completely different tech stacks — all delivering the same ownership outcome.

Coming soon. Onboarding call with Hayden pending.

Included for the curious. This is how the outcomes above are delivered; none of it is the story.

Role	Focus	Why it serves the business
CEO	Game design, monetization, Roblox marketplace	Keeps product decisions aligned with revenue, not just feature count
CTO	Technical architecture, task breakdown	Decomposes work into agent-sized tasks
Luau Engineer	Roblox scripting, mechanics, systems	Where most of the code gets written
QA / Playtester	Testing, exploit prevention, performance	Catches issues before players do
Economy / Balance	Currency, progression, drop rates	Protects the revenue surface every change touches
Content	NPC dialogue, UI text, localization	Writing keeps pace with code

Stack: Roblox Studio + Luau + Rojo + Wally + Selene + TestEZ. Standard Roblox tooling — nothing invented, nothing exotic. Hayden keeps his workflow; the agents plug into it.

Craig and Hayden Duswalt are father and son — both theAppChicks clients. Craig builds his speaking business with the Rockstar Impact app. Hayden builds his gaming studio here. Same pattern, completely different products.

"Maybe I'll put Hayden in touch with you on a phone call because he really wants to get paid for coding now. His games are doing great." — Craig Duswalt, Xcelerator call, March 23, 2026

• Roblox profile: @zer0Cactus
• Source repo: theappchick/zer0games-studios (private)
• Father's case study: Rockstar Impact