Players,understood.In seconds.

Studios were burning real money to understand their own players. They'd commission playtests, then assign people to watch the recordings to find the moments that mattered. The cost was paid twice — once to run the playtest, again to extract value from it manually.

An AI auto-tagged every video in our corpus across player-behaviour signatures. Devs filtered by those tags to surface the exact sessions they wanted, instead of trawling through every session. Limited dev resources, narrow scope.

Devs liked it — already faster than the playtest-then-watch loop. Feedback was consistent: “go further. We don’t want to watch better videos. We want the answer, with the videos as proof.”

Expand scope. Move from filtered playback to generated insights, with video as evidence underneath.

Filters surfaced sessions; they didn’t answer questions. Devs across roles asked very different things, and a static filter UI couldn’t cover that surface area.

A natural-language input field, two agents behind it. Radiologist built on top of the filter piece — adds AI session summaries, a timeline of key events, and session metadata (region, platform, device, length). Oracle, experimental — answers focused dev queries across many sessions: “where did players lose the most HP and what caused it?”, “summarise rotation, drop spot, key moves, final-zone path.”

Both agents worked technically. But devs hit a learning curve we hadn’t fully predicted — even with suggested queries and hints, devs didn’t know what to ask a system this powerful. The capability was there; the access wasn’t.

The next move had to solve query authoring, not agent quality.

Devs didn’t need more agents. They needed an entry point that knew which question to ask, for which role, on which signal — without making the dev the query writer.

Barista — a personal assistant that proactively suggests analyses based on the dev’s role on the team (PM, game designer, LiveOps, marketer) and the data flowing in. Sits above Radiologist and Oracle: Barista decides which agent to invoke and frames the result in language the role understands.

Most users now land in Barista first. Radiologist and Oracle stay accessible as the depth — but the on-ramp is what unlocked them.

Barista is the default surface; the other agents are reachable through it or directly.