TEAMS PERFORM FOR INVESTORS. I GET THE TRUTH.
Most studios fail because they can't execute, not because of bad ideas. I embed with teams to find execution risk before you commit millions.
What you’ll know after this
- Whether the team can ship on the current plan
- Where execution risk is hiding (and why)
- What to change next—prioritized and actionable
of VC-backed game projects fail to launch
typical cost to discover team failure
to identify failure patterns before deployment
The $50M problem
The cost of a missed milestone isn’t just time, it’s burn, credibility, and optionality. These are the failure modes that show up before schedules collapse.
Signals that execution risk is real
- Priorities change weekly, but capacity doesn’t
- Milestones look “on track” until they suddenly aren’t
- Dependencies are unclear; ownership is fuzzy
- Leadership alignment exists in slides, not in decisions
What Team Due Diligence 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
The 5 Failure Patterns I Detect
After 29 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 #1 cause of studio death
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
- Feature decisions made for “cool factor” rather than game needs
What this costs you:
Teams that can't kill features can't ship games. You fund 18 months of feature creep, not a product. Average cost: $3-8M before you discover the leadership structure prevents shipping.
Technical Dysfunction
Death in slow motion
Warning Signs I Look For:
- Tech leads building impressive systems with no gameplay application
- Architecture decisions made for resume value, not product needs
- Inability to adapt when creative or budget realities shift
- Technical team operating independently of game vision
What this costs you:
You discover 12 months in that the “impressive tech demo” can't scale to an actual game. The engine rewrites, the timeline doubles, and the team rebuilds from scratch.
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
- Vision communicated differently across departments
- Critical decisions made in hallways, not in meetings
What this costs you:
Every unclear decision adds days or weeks. Death by a thousand misalignments. Milestones slip, morale drops, and you can't pinpoint why until it's too late.
Hiring for Loyalty Over Capability
Early-stage poison
Warning Signs I Look For:
- Founders hiring friends who won't challenge decisions or push back
- Talent selected for cultural fit over proven shipping ability
- Leadership unwilling to make personnel changes when gaps emerge
- “We go way back” used as justification for key hires
What this costs you:
You can't course-correct when the team structure itself prevents honest feedback. Problems compound quietly until leadership finally admits what everyone knew months earlier.
Creative Rigidity
Reality denial
Warning Signs I Look For:
- Unwillingness to adapt to market feedback or technical limitations
- “This is my vision” as the response to all pushback or concerns
- Team chasing their favorite game with no regard for market fit
- Major scope decisions made without acknowledging resource reality
What this costs you:
You fund a team building the game they want, not the game the market will buy. When reality finally hits, it's too late to pivot without starting over.
These patterns don't fix themselves. They compound over time and consume capital. I identify them in weeks 2-3 of my assessment, early enough for you to make an informed decision before deployment.
What is Team Due Diligence?
A short, structured engagement designed to surface execution risk and give you a clear recommendation. This isn’t a full-time embed or staff role, it's a light-touch presence, typically 1–2 days per week, designed to observe reality without altering team behavior.
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.
How it works
A simple, four-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 embed with the team to see how decisions and delivery actually happen. This includes attending standups, reviewing pipelines, conducting confidential one-on-ones, and mapping communication flows. Teams know me as a fellow developer, not an auditor.
Duration: 2-4 weeks (depending on team size)
Assessment
I identify risks, root causes, and what must change to raise the probability of shipping. This includes detecting which failure patterns are present, evaluating leadership capability, and determining if issues are structural or fixable.
Duration: 3-5 days (synthesis)
Recommendation
You receive a comprehensive written report with a decision-ready recommendation (go / no-go / conditional), specific findings, and prioritized action items. We schedule a debrief call to discuss the assessment and answer questions.
Duration: 1 week (report + debrief)
Total Timeline: 3-5 weeks from kickoff to final report
Fast enough to inform urgent decisions, thorough enough to give you confidence.
Simple, transparent pricing
This isn’t a full-time embed or a shadow-management role; it’s a focused presence that runs roughly 1–2 days per week, enough to surface real dynamics without disrupting how the team actually operates.
Micro Studio
< 10 people
$10,000
~2 weeks
- Embedded observation
- Team dynamic assessment
- Comprehensive written report
- Go/No-Go recommendation
Small Studio
10–25 people
$15,000
~3 weeks
- Embedded observation
- Team dynamic assessment
- Comprehensive written report
- Go/No-Go recommendation
Mid Studio
25–50 people
$20,000
~4 weeks
- Embedded observation
- Team dynamic assessment
- Comprehensive written report
- Go/No-Go recommendation
ROI Calculation
Traditional Cost of Discovery:
- $2–8M spent to learn the game can’t ship
- 12–18 months of dead capital
- LP confidence erosion
- Costly, distracting unwind
Cost of Early Detection:
- One assessment fee ($10K-$20K)
- 5 weeks before capital deployment
- Clear go/no-go decision
- Maintain LP relationships
One prevented bad investment pays for 30+ assessments.
Track record
This is built from real operating experience shipping, scaling teams, and making hard calls under pressure.
Ratchet & Clank, Resistance, Vader Immortal
Vader Immortal Series
Product leadership and delivery
Teams from 8 to 150 people
Focus
Execution risk, team dynamics, and operating systems that raise the probability of shipping. I specialize in identifying structural issues that leadership can't see or teams won't surface.
Case examples
Examples are intentionally anonymized. The point is decision logic, not private details. Full case studies available on request.
Legacy Team, Fatal Structure
Studio: Veteran-led, early-stage
Finding: Dual-role leadership, hiring for loyalty
Outcome: Follow-on avoided; capital redeployed
Key takeaway: Pedigree doesn't predict performance. Structure does.
Discipline or Death Spiral
Studio: Large-scale, high ambition
Finding: Real issues; exceptional course-correction
Outcome: Continued funding with confidence
Key takeaway: Surface chaos isn't always systemic failure. Self-awareness and discipline matter.
Nightmare Scenario
Studio: small team, pre-seed
Finding: Inexperienced team. Conflict-adverse leadership.
Outcome: Conditional, proceed with investment
Key takeaway: Sometimes the right answer isn't yes or no. It's restructure.
FAQ
Quick answers to the common questions I get from publishers, investors, and studio leaders.
You wouldn't invest $3M without legal due diligence.
Why invest without team due diligence?
3-5 weeks. Clear recommendation. Before you deploy.
Confidential consultations with no obligation. All engagement details treated as confidential. NDA available upon request.