Entry offers · Entry conversation
Product Health Check
The entry conversation. A surface look at your game, wherever it is, so the work ahead is clear: what looks healthy, what looks obviously at risk, and which longer offer, if any, fits.
For games in development, in soft launch, or live
- A play of the game
- The core loop, at a glance
- The headline numbers
- Who owns the work
- What looks healthy on the surface, said in plain language
- What looks obviously at risk, separated from the noise
- A clear next step: stop here, or go on to the performance review, a workshop, or the custom work on Services
How the check runs
To start
A short call
What you are worried about, and access to what you already have. A build to play helps.
The pass
The surface
Paul plays the game and reads the headline numbers. The conversation is about what the work should be.
To close
Findings
What is on the surface, and which longer offer fits, if any. Many studios stop here.
With your teamPaul working on it
What you receive
- A short written note, not a long audit
- The findings conversation
- A recommendation of what, if anything, to do next
What it is not
- Not the Product Performance Review. That is six weeks, or twelve that include those six.
- Not the workshop.
- Not a request for player-level personal data.
Questions studios ask
- We already know we need the long work. Why start here?
- Then open the Product Performance Review and choose six or twelve weeks. The health check is the entry conversation, for when you want the work named first.
- What do you need from us?
- A build to play, and whatever headline dashboard you already look at. No new tracking.
- What happens after?
- You decide. There is no obligation to take another offer.
The other ways in
Partnership and Custom AI Transformation are on Services.