MOST STUDIOS FAIL ON EXECUTION, NOT ON IDEAS.
The gap between a strong pitch and a delivered game is where budgets get out of hand. I embed with teams and report on execution risk before you sign, greenlight, or fund the next milestone.
What you’ll know after this
- Whether the team can ship on the current plan
- Where execution risk is hiding (and why)
- What would have to change, in priority order
Late discovery is expensive
When a structural problem surfaces after signing, every option is bad: fund a team that can't deliver, restructure mid-production, or cancel and absorb the loss. Most late-stage cancellations represent problems that were detectable earlier. This assessment exists to move that knowledge ahead of the commitment.
Signals that execution risk is real
- Priorities shift constantly, but capacity and timeline don't adjust with them
- Milestones look fine on paper until they slip all at once
- Ownership is unclear; nobody knows who has final say
- Leadership says the team is aligned, yet they are requesting additional budget
What a Studio Assessment checks
- Team operating system: planning, execution, and accountability
- Leadership: decision quality, clarity, and trust
- Scope discipline: what’s in, what’s out, and what’s drifting
- Delivery realism: the gap between plan and capacity
- Signal triangulation: playtest results, user research, and production metrics weighed against the team's own read on progress
The 5 Failure Patterns I Detect
After 30 years shipping games, I've identified five structural issues that predict team collapse. These patterns are invisible in pitch meetings but obvious when you're embedded.
Creative Leadership Failure
The most common reason studios don't ship
Warning Signs I Look For:
- Creative and technical leads have incompatible visions for the game
- Leadership chasing personal passion projects with no market discipline
- Inability to make decisive cuts when scope exceeds budget or timeline
What this costs you:
You fund a growing scope instead of a defined product. From the outside, everything can look on track until there is no time left to recover the schedule.
Technical Dysfunction
The problem that compounds the longest before it's visible
Warning Signs I Look For:
- Tech leads building impressive systems with no gameplay application
- Inability to adapt when creative or budget realities shift
- Technical team operating independently of game vision
What this costs you:
You discover a year in that the demo can't scale to a full game, and the timeline doubles.
Structural Communication Breakdown
The miscommunication tax
Warning Signs I Look For:
- Unclear decision-making authority (“who has final say?”)
- Feature pipeline ignoring budget and team size constraints
- Critical decisions made in hallways, not in meetings
What this costs you:
Every unclear decision adds days, and the accumulated slip has no single cause you can fix.
Hiring for Loyalty Over Capability
The mistake that's hardest to correct later
Warning Signs I Look For:
- Founders hiring people who won't push back or challenge decisions
- Talent selected for personal trust over demonstrated shipping ability
- Leadership aware of performance gaps but unwilling to address them
What this costs you:
Problems stay unsurfaced until fixing them means replacing people.
Creative Rigidity
Reality denial
Warning Signs I Look For:
- Unwillingness to adapt to playtest results or user research
- “This is my vision” as the response to all pushback or concerns
- Major scope decisions made without acknowledging resource reality
What this costs you:
You fund the game the lead wants rather than the game the market will buy.
These patterns get harder to fix the longer they run. I typically identify them in a matter of days, early enough to give you a clear picture before the next capital decision.
What is a Studio Assessment?
A short, structured engagement designed to give you a clear picture of execution risk before the commitment is made. Not a full-time embed or staff role: 3-10 embedded days spread across 1-3 weeks, enough to observe how the team actually works without disrupting it. What “on track” means depends on the stage of development, the type of game, and how the studio works, so every question is calibrated to all three. Each engagement is a fixed fee agreed before kickoff, scoped to team size and the decision in front of you.
Immersion
I embed with the team to see how work actually happens: planning, handoffs, decision-making, and day-to-day execution.
Assessment
I evaluate the team's ability to deliver: leadership alignment, operating rhythm, dependency management, and scope control.
Deliverable
You get a written assessment, clear recommendation, and a prioritized roadmap of changes that will improve delivery reliability.
When publishers bring me in
The same assessment supports four different decisions. Publishers typically engage at one of these moments.
These decisions carry more than the production budget: the release slate, the brand on the box, and the partner relationship all ride on whether the team can deliver.
Before signing
An independent read on whether the team can deliver the pitch, run alongside your legal and financial diligence. The signing decision gains a source of truth that portfolios and vertical slices cannot provide.
At a greenlight gate
A second source of truth for the go decision. Build reviews show what the team prepared for you. Embedded time shows how the build got made and whether the next one will arrive.
When a funded project slips
A clear-eyed view of whether the problem is fixable, what fixing it would take, and whether continuing is justified. Useful before a continue-or-stop call, and cheaper than making that call blind.
Selecting external partners
Co-development and outsourcing decisions grounded in how a studio actually works, before the contract is signed. When the project carries your franchise or licensed IP, the studio's ability to deliver is a brand decision as much as a budget decision. A hard question asked by a third party costs no relationship capital with your partner.
Where the assessment fits
How it works
A simple, three-step process designed for speed, clarity, and minimal disruption.
Kickoff
We confirm goals, timeline, and the key risks you want answered. I review available materials (pitch deck, team roster, current build if applicable) and establish communication protocol with your team.
Duration: 1-2 days
Observation
I spend time with the team to see how decisions and delivery actually work. This includes attending standups, reviewing pipelines, having direct conversations with team members, and mapping how information moves through the organization. Teams engage with me as a fellow developer.
Duration: 3-10 embedded days across 1-3 weeks, scaled to team size
Synthesis and Recommendation
I identify risks, root causes, and what must change to raise the probability of shipping. This includes detecting which failure patterns are present and evaluating leadership capability. You receive a comprehensive written report with a decision-ready recommendation (proceed / pass / proceed with conditions), specific findings, and prioritized action items, followed by a debrief call.
Duration: 1 week
Total Timeline: 1-4 weeks from kickoff to final report
Fast enough to inform urgent decisions, thorough enough to give you confidence.
The report
- 1Executive Summary – proceed / pass / proceed with conditions
- 2Failure Pattern Analysis – which patterns are present
- 3Key Findings – specific observations from embedded time
- 4Leadership Assessment – individual capability evaluation
- 5Recommendation – framed for the decision in front of you, whether that's signing, greenlight, continue or stop, or partner selection
Case examples
Three anonymized assessments: one recommendation against signing that preserved a $2M budget, one validation that unblocked continued funding, and one conditional proceed that led to a restructure. The point is the decision logic, not the details.
The other half of the read
Studio Assessment tells you whether the team can execute. It doesn't tell you whether the game is worth executing. Title Review covers the second question.
Common questions
A clear recommendation before you commit.
Signing, greenlight, and continue-or-stop decisions all improve with ground truth about how the team works. You get a decision-ready report inside a normal deal timeline, and the team gets a workable path forward.
Confidential consultations with no obligation. All engagement details treated as confidential. NDA available upon request.