Build a Unity game for under $700 with persona playtest agents

A non-developer used Claude Code with a Unity MCP to build a full Steam game for under $700, after paying a studio about $50k for her first one, with eight persona agents playtesting the demo.

Done withClaude Code· Nov 15, 2026

What they did

The poster, who does not code and holds three jobs, had paid a studio about $50k to build her first game. For the second she worked alone with Claude Code on Opus 5.5 connected to Unity 6 through a Unity MCP, starting from a plain design doc and a CLAUDE.md. Claude Code wrote nearly all the C#. When OBS lagged on her laptop it built an in-engine replay recorder, later a scripted version that turns a shot list into a finished clip. With no playtesters, it built a local API into the built game; she wrote eight player profiles, and eight agents each played the full 60-day demo and filled in an evaluation sheet. It also added 14 languages with a test for text overflowing buttons at three screen sizes, and about 360 automated tests. Music, voice-over from her own voice and 3D renders came from Higgsfield.

How it went

In a few weeks she had a playable game with a live Steam page, for under $700, with a demo due on 2 December. Comparing the eight persona sheets turned up a soft-lock, a bug that fired for the wrong reason in 7 of 8 runs, and an economy exploit before any human played it. The play, find, describe, fix loop ran about 300 times. She kept every design and balance decision. She later fed the studio-built first game's source to Claude, which fixed some open bugs there.

Worth knowing

She calls the hour spent on the design doc and CLAUDE.md before the first prompt the most valuable of the project. The persona playtest needs a way for agents to drive the built game, which Claude Code had to build first. A commenter noted that this much regression testing is standard practice for professional developers. Sales so far are small; she joked about two.

Try it

With Claude Code· 5 parts to fill in

You are working on my Unity game in [project folder], connected through [Unity MCP server]. First build a local API into the built game so an agent can read game state and send inputs. Then, for each player profile in [profiles folder], play the full [demo length] demo as that player and fill in [evaluation sheet template]: what you tried, where you got stuck, anything that felt unfair or broken. When all runs are done, put the sheets side by side and list bugs, soft-locks and exploits that more than one profile hit, with steps to reproduce. Stop and show me the list before changing any game code.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related