I was scrolling through a late-night forum thread when a developer’s blunt line stopped me cold: “We didn’t make the numbers.” You felt that hollow shift too—the kind of quiet that follows a promise that never grew roots. I want to walk you through why that sentence probably killed the one thing fans wanted most: Starfield 2.
I’ve followed Bethesda’s trajectory for years, and you should know I’m not here to mourn or cheer—just to map what happened and why the sequel whisper now sounds like a door closing. Kurt Kuhlmann, a systems designer who left Bethesda after launch, told FRVR that Starfield was “not anywhere near successful enough to do a Starfield 2.” That line is the hinge.

At a studio meeting: What Kurt actually said
He didn’t sugarcoat it. Kuhlmann told FRVR that Starfield simply “wasn’t anywhere near successful enough” for a sequel, and he thinks that’s a shame because the team learned things that could have made a follow-up sing. You should read that as two facts: the game didn’t meet internal targets, and there was untapped potential in the code, systems, and experience design.
The clearest cut Kuhlmann points to is coherence. Starfield piled on features—planetary freedom, ship building, base construction, modular systems and a cinematic narrative—only to discover they rarely responded to one another in meaningful ways. The result felt like a Swiss Army knife with missing blades: a tool full of promise, but none of the pieces worked well enough together to be relied on.
Will there be a Starfield 2?
Short answer: probably not. When a project fails to hit the financial marks you expect—especially under Microsoft’s ownership and Xbox’s Game Pass calculus—greenlighting a sequel becomes a hard sell. Developers and executives watch metrics: engagement, retention, revenue per user across Steam and Game Pass. Kuhlmann’s quote is effectively a public version of that internal memo.
At the storefront: Money talks louder than design notes
Walk through any digital storefront and you’ll feel the market pressure: Xbox, Steam, and Game Pass all measure the same currency—how many players stay and how much they spend. Starfield improved post-launch, but not enough to flip the board for Microsoft’s investment calculus. You don’t need a crystal ball to know that when a big-budget title misses its commercial targets, sequel plans stall.
Bethesda’s ambition to be “everything” in one game collided with a practical truth: when too many systems compete for attention, none reach satisfying depth. Base building, a headline feature, struggled to tie into the story and systems—an issue the team encountered with Fallout 4 and never fully resolved here. The game became a museum of half-built exhibits, beautiful to walk through but lacking a single, obvious reason to linger.
Why won’t Starfield 2 happen?
Because the business case isn’t there. Kuhlmann framed it as lessons learned that didn’t translate into guaranteed sales. Add in the reality that Microsoft evaluates Xbox-era Bethesda titles against a global strategy that includes Game Pass subscriptions and cross-studio priorities, and the math becomes unforgiving. The sequel would need a fresh pitch and clear path to stronger retention—neither of which are cheap.
At the design desk: The problem wasn’t ambition, it was integration
I’ve seen teams chase “more” and end up with “less.” Todd Howard once gave us Morrowind’s focused, reactive world; that sensibility was muted inside Starfield’s buffet of systems. You can be a captain, a builder, a politician, and a murderer in the same save file with almost no consequences. That design choice weakens stakes and shrinks emotional investment.
If you think a sequel could fix that, Kuhlmann agrees on principle: the team learned how to build many pieces. But learning isn’t the same as convincing a board to fund another multi-year production. Bethesda, Microsoft, and the market now ask for proof that a second entry will convert lessons into stronger revenue—proof that, right now, doesn’t exist.
Was Starfield a financial failure?
“Failure” is messy. It wasn’t a catastrophe for Bethesda, but it wasn’t the blockbuster payday the studio and Xbox expected either. Kuhlmann’s phrase—“not anywhere near successful enough”—is blunt because business decisions are blunt. When a title doesn’t hit projected KPIs across Steam, Xbox storefronts, and Game Pass engagement windows, sequel parity quickly drops from “planned” to “unlikely.”
I’ve covered studio exits and post-launch eras: a designer leaving after a big release is often a signal, not the whole story. Kurt’s departure and his candor tell you something about morale and direction inside the studio. You can sympathize with fans who feel deprived of what a Starfield 2 might have been—those same fans also have to reckon with corporate spreadsheets and platform strategies.
So where does that leave us? Starfield is better than it was at launch; Bethesda earned that. But the blend of middling commercial performance, a diffuse design identity, and Microsoft’s project prioritization means the sequel is now more a hypothetical than a plan. If the team wants another shot, the question isn’t whether they learned—it’s whether they can convince executives that a second act will turn lessons into numbers. Do you think Bethesda can make that pitch and win it?