The Studio Brain

Expert knowledge, at the moment you need it.

Most risk tools give you an empty form. SRIS gives you a second voice in the room: the Studio Brain.

It suggests. You decide. Nothing becomes part of your record until a person confirms it.

Apply for the pilot →

Your note, as it comes out

“Outsourced animation for the March slice is two weeks behind and the art lead is worried.”

The Studio Brain drafts

Risk · ProgrammeDraft: not in your record yet

If outsourced animation stays two weeks behind, then the March vertical slice may miss its date.

Known pattern · outsourcing dependency

Late outside work usually shows up at integration, not on the delivery date. Advice: agree what “ready” means now, and ask for a mid-point drop two weeks before the slice.

It asks youWho owns this? When do you want to look at it again?

An illustration with a made-up note. Not a real record.

Liam's knowledge, working in the background

It sees what you might miss.

Risk patterns from the Studio Risk Foundations course and Liam's book, brought to the moment you need them. More of Liam's library is added in stages.

A known risk pattern

Hey, by the way. Changes to the build pipeline close to a certification submission are a common cause of late failures. Advice: freeze pipeline changes from two weeks before submission, and name who can approve an exception.

It matches your note to the patterns it knows, and tells you what usually helps.

A gap in your record

Before you confirm. This risk has an action but no owner, and no date to look at it again. Who should own it?

It asks before it guesses. It never fills in owners, dates or scores for you.

Several teams, one problem

Did you know? Three teams have an outsourcing risk this month. When several teams share one kind of risk, it may need handling at Programme level.

A check across your records, so the same problem in three places gets one owner.

Illustrations with made-up notes. Not real records.

It suggests. You decide.

Nothing joins your record until a person confirms it.
It never invents owners, dates, evidence or scores.
It can be wrong. You check it, every time.
It is optional, and stays off until your data terms are signed.
Your information is not used to train AI models.
It sees only your own studio's site.

I have spent more than 25 years in game production. The same problems come back in every studio: work that arrives by routes nobody can see, dependencies nobody tracks, decisions made too late. The Studio Brain puts that knowledge where it helps.
“The test is not whether the producer personally did everything. It is whether the right work can happen reliably without that producer doing everything again.”
Liam Wickham, founder, Game Production Academy · Why SRIS →

Honest about where it is today.

The Studio Brain is young. Today it carries the core of the Studio Risk Foundations course and a first set of risk patterns from Liam's book. It takes a little while to answer, and it can be wrong.

We test it on made-up studios, scored blind, before anything reaches a pilot. We will not claim it beats a good producer with a general AI tool until we have tested that properly.

Help us shape SRIS.

We are looking for a small, varied group of studios. You get a private SRIS site, Liam's support and a real say in what we build next. We ask for honest use and honest feedback.