The meeting with PlayForge was three days away, and Leo had work to do.
He pulled up his developer dashboard and checked the numbers.
Getting Over It had crossed 300,000 copies sold and was still climbing toward 400,000, with no sign of slowing down.
At five dollars a copy minus PlayForge’s 30% commission, the math came out clean: his net earnings from that single game had already crossed one million dollars.
A million dollars wouldn’t make him rich by Seattle standards.
This was a city where a decent condo cost twice that.
But a million in cash, sitting liquid in a bank account, was a different kind of power entirely.
It was breathing room.
It was options.
He’d already done the math on his debts.
The original Leo Sinclair had owed a little over $300,000 to a scattered network of family members, friends, and lending institutions: the accumulated wreckage of a failed startup.
Paying all of it off in one sweep would leave him with roughly $700,000 in working capital.
That was enough to move.
Enough to set up a real workspace.
And, most importantly, enough to start building the infrastructure he was going to need going forward.
Because Leo had been thinking about his long game, and he’d identified a problem that wouldn’t solve itself.
Right now, the games he’d released were small enough to be plausibly solo-developed.
A physics climber and a pixel platformer might be unusual in design, but they were well within the production scope of a single talented developer.
Nobody was going to look at Getting Over It and ask, “How did one person make this?” The answer was obvious: one person could make this, without any special explanation required.
But Leo’s ambitions went far beyond five-dollar indie titles.
The System Store contained games that, in his previous life, had required teams of dozens, sometimes hundreds, of developers, artists, sound designers, and QA testers working for months or years.
Games with fully realized 3D worlds, cinematic narratives, orchestral soundtracks, and multiplayer infrastructure.
If he ever wanted to release something on that scale, he couldn’t just upload it under “The Nameless Rogue” and hope nobody asked questions.
A AAA-quality title appearing overnight from a solo developer with no visible studio, no team, and no production timeline would set off alarm bells across the entire industry.
He needed a company.
A real, registered, staffed game development studio that could serve as the visible pipeline for whatever the System helped him create behind the scenes.
It didn’t have to be huge, not yet, but it had to exist, and it had to look legitimate.
Employees who showed up to an office.
A production process that could be pointed to.
A paper trail that made sense.
In his previous life, Leo had spent four years at a mid-size studio before going independent.
He understood how game companies functioned from the inside: the pipeline stages, the milestone reviews, the way a game moved from concept document to vertical slice to alpha to gold.
He knew what a plausible development timeline looked like.
He could build a company that looked right because he’d lived inside one.
But companies cost money.
Rent, equipment, salaries, insurance, software licenses: it added up fast, even for a small operation.
Which meant that every dollar of leverage he could squeeze out of the PlayForge negotiation mattered.
And the best leverage in the gaming industry was always the same thing: a great game.
Leo opened the System Store and started browsing.
He had a specific target in mind.
He needed a game polished enough to impress PlayForge’s business team, something that would demonstrate range, not just another rage-inducing torture device.
He needed to show that The Nameless Rogue could make games people loved, not just games people loved to hate.
His exchange point balance sat at just over 30,000, which was more than enough for most small-to-mid-tier titles.
He also still had the optimization token he’d earned from the hidden task, meaning he could push whatever he selected up a full tier in quality.
The strategy was clear: find the right game, buy it, optimize it, and walk into the PlayForge meeting with a product so good it shifted the entire negotiation in his favor.
He started scrolling.
Potato Quest — 450 points.
Leo grimaced and kept moving.
The novelty-to-quality ratio was all wrong.
Moving on.
Where’s My Water?
— 860 points.
A physics puzzle game about guiding water through underground pipes to a cartoon alligator’s shower.
Cute, but far too simple to serve as a negotiation centerpiece.
Age of Conquest — 1,800 points.
A medieval strategy title with heavy historical detail.
Too niche and menu-heavy for a broad market.
Leo needed something universal.
Urban Enforcer — 6,840 points.
A arcade rail shooter with limited replay value.
Decent production cost, but the gameplay loop would burn out fast.
Not the kind of game that demonstrated real depth.
He kept scrolling.
The further down the list he went, the more expensive the titles became and the pickier he got.
This decision mattered.
Whatever he chose would represent him in a room with people who evaluated games for a living.
It had to be something that, the moment they put their hands on it, made them forget they were in a business meeting and just play.
Then he saw it, and the scrolling stopped.
Plants vs.
Zombies — 21,400 points.
Leo stared at the listing for a long moment, a slow, genuine smile spreading across his face.
It wasn’t the calculating grin of a man spotting a profitable angle.
Instead, it showed pure warmth and recognition.
He loved this game.
In his previous life, Plants vs.
Zombies had been one of those rare titles that transcended every demographic barrier the industry had ever erected.
Kids played it.
Grandparents played it.
Hardcore FPS veterans played it during loading screens and pretended they didn’t.
It was a tower-defense game wrapped in a garden-warfare metaphor: plant sunflowers to generate resources, place different species of weaponized flora in strategic positions, and use them to fend off waves of increasingly absurd zombies shambling across your lawn.
The genius of it wasn’t complexity, but accessibility layered over depth.
The first few levels were practically tutorials, gentle enough that a child could clear them without thinking.
Yet the difficulty scaled with a patience and precision that, by the mid-game, had even experienced players sweating over every sunflower placement.
Each new zombie type forced a strategic rethink.
Each new plant opened up tactical possibilities that hadn’t existed a level ago.
And it was addictive.
Not in the shallow, slot-machine way that mobile games manufactured engagement, but in the satisfying, “just one more level” way that came from genuinely well-crafted difficulty curves.
You struggled, you adapted, you broke through, and the breakthrough felt earned.
Then the next tier of difficulty arrived and the cycle started again.
In his old life, Leo remembered studying PvZ during his studio years, pulling it apart to understand its retention mechanics, its onboarding flow, and the way it used humor and personality to soften what was, mechanically, a surprisingly demanding strategy game.
The team at his old studio had used it as a reference case for how to make difficulty feel inviting rather than punishing.
More importantly for his current purposes, Plants vs.
Zombies was genuinely different from anything in this world’s gaming landscape.
The tower-defense genre existed here in rudimentary forms, but nothing with this level of character, polish, and gameplay depth.
Because the game was suitable for literally all ages, the potential player base was enormous, reaching far beyond the core gaming demographic to include parents, younger siblings, and non-gamer friends.
Everyone was a potential customer.
Leo ran the numbers quickly.
At 21,400 exchange points, it would burn through most of his balance, but the optimization token would elevate the final product well beyond its base quality.
He’d walk into the PlayForge meeting with something that wasn’t just good, but undeniably good.
The kind of game that made business people stop calculating margins and start playing.
That was the kind of leverage no amount of negotiating skill could replace.
He selected the game, confirmed the purchase, and watched 21,400 points drain from his balance.
What appeared in his System inventory wasn’t a finished game.
It was a development kit: the complete mechanical blueprint for Plants vs.
Zombies, broken down into its core components.
Plant behavior modules.
Zombie patterns.
Level layout schematics.
A raw asset library of character sprites, background tiles, and UI elements.
Sound files sorted by category.
Everything was there, but none of it was assembled.
It was like receiving every piece of a car engine, perfectly machined, laid out on a workbench with no instructions.
Leo looked at the clock.
Three days until the meeting.
He looked at the mountain of unassembled components spread across his System inventory.
There was a lot of work to do.
Drop a comment and let me know what you enjoyed!