I work with founders, studios, publishers and IP owners who are weighing a new platform, a new format or a new audience - and need to know whether it is worth the roadmap slot before they commit a team to it.
Thirty years of doing this has mostly taught me that a proven game does not transfer to a new surface on its merits. It transfers, or fails, on how that surface finds, rewards and keeps players. That is usually the thing nobody has looked at yet.
A bounded answer to a bounded question. What does winning look like here, what is the plan, what is the score today, and what is preventing it. You end up able to commit or kill, with the reasoning written down so the decision survives the next meeting.
Shape the proposition and prove it. Something gets built, put in front of people and measured. The point is to make the bet fail cheaply and early if it is going to fail at all - which is considerably better value than finding out after a year of roadmap.
Carrying a continuing product remit alongside your team: priorities, scope, quality, the route to market. This follows a pilot rather than starting cold, because by then we both know whether it is the right arrangement.
A standing second opinion for a founder or product lead who mainly needs someone to think out loud with. Scheduled, capped, and deliberately small.
Before scope or shape, one question:
What decision is this blocking, what does it cost you to get it wrong, and what does resolving it unlock?
If that is hard to answer, the engagement is probably premature and I will say so. If it is easy to answer, we will both know what the work is worth, and the rest of the conversation is straightforward.
I'm accountable for the quality of the thinking and the rigour of the process. I won't promise an outcome that depends on execution, timing and a dozen things neither of us controls.
Email me with a line or two about the decision you're facing. No brief required - if it is still a half-formed hunch, that is usually the right time to talk.
I'm based in Dubai and work with teams remotely. You can see where I've done this before, or read what I'm currently thinking about in the notebook.