EVERY GREENLIGHT RESTS ON TWO QUESTIONS.
Whether the studio can execute, and whether the title is worth executing. Milestone review is built to answer the first. I answer both, calibrated to the stage of development, the kind of game, and the way the studio works.
Two reads, two blind spots
Team diligence and title diligence fail in opposite directions. Run one without the other and a whole quadrant of risk stays invisible.
| Team condition | Title sound | Title broken |
|---|---|---|
| Team healthy | Team healthy / Title sound Fund. Normal risk. | Team healthy / Title broken Blind spot: the game Reviews pass, milestones hold, and the game fails at market. The most expensive failures of the last five years sit in this box. |
| Team broken | Team broken / Title sound Blind spot: the evidence Reviews dazzle or exhaust, milestone criteria move, and gameplay is under-represented. A sound idea, and no evidence the team can realize it. | Team broken / Title broken Pass. Rarely ambiguous afterward, though rarely obvious at the time. |
Studio Assessment finds the bottom-left: the review looks fine and isn't telling you anything. Title Review finds the top-right: the review is accurate and the game is still wrong. Neither one sees the other's box.
Why a green milestone isn't an answer
The build is prepared
A milestone build shows what the team chose to show you, finished to the standard they could reach by that date. How it got made is not in the build.
Gates measure the plan
A gate checks the project against its plan. When the plan itself is wrong, a project can pass every gate on the way to a game nobody wants.
One review has no baseline
Some problems only appear as change between reviews: scope that grew, a production rate that never improved, a reference title that shifted without anyone noticing. A single review has nothing to compare against.
Studios rarely misrepresent their situation on purpose. They are too close to it. Builds get curated, reviews get rehearsed, and status reports carry what leadership believes rather than what the team is living. By the time the gap is visible from the publishing side, the project has usually moved past the point where the fix was cheap. Two questions are worth asking before that happens. Whether the way this team works can produce the game on the plan you are funding, and whether that game is still worth funding.
HOW I GET TO GROUND TRUTH, NOT EXECUTIVE SUMMARY
Embed as a Peer
I join as a fellow developer, not as a representative of the money. That context changes what people say. Teams talk to me about what is actually happening in production, not the version that gets packaged for a board. Typically 3 to 10 days on site or remote, across 1 to 3 weeks.
Read Both Sides
Ten patterns, calibrated to stage, genre, and the way the studio works. Five are structural and predict that a team will not deliver. Five sit on the title side and predict that the game fails at market even when the team does deliver. Which set carries the weight depends on the decision in front of you. Often it is both.
Deliver a Decision-Ready Recommendation
A written report with one of three answers: proceed, pass, or proceed with conditions, framed for the decision you are making. Where problems are fixable, they come back in priority order, with what it costs to correct them at this stage.
This is pattern recognition built from thirty years of shipping games and running teams of eight to a hundred and fifty people. I have been inside most of these situations, which is why they usually take days to spot rather than months.
RECENT ASSESSMENTS
Three anonymized assessments: one recommendation against signing, one validation that unblocked continued funding, and one conditional proceed that led to a restructure.
WHAT YOU GET
A written assessment with a clear recommendation: proceed, pass, or proceed with conditions, framed for the decision in front of you. Studio Assessment runs one to four weeks end to end. Title Review runs one to three. Either one works on its own. Run against the same project, they answer both questions in a single engagement.
THIS IS FOR YOU IF:
You’re close to signing or funding a studio and want an independent read on the team, the title, or both.
A greenlight gate is coming and you want the game itself weighed alongside the build review.
A funded title keeps revising its milestone plan and you need to know whether that is iteration or structure.
You’re comparing several projects across a slate and want them assessed against one framework, so the comparison between them means something.
The cheapest place to catch either problem is before you commit
Signing, greenlight, portfolio, and continue-or-stop decisions all improve with an independent read. Both reviews are sized to fit inside a normal deal or review cycle. The first step is a conversation.
Confidential, no obligation. Engagements with publishers, platform holders, and investors. NDA available.