Psephos | Data Stories for Games

The work

Ten years of game data. Mobile, console, browser.

Value and forecasting. LTV modelling, revenue forecasting, ROAS and cohort work, churn and retention.
Players and product. Segmentation and behavioural clustering, A/B testing and deep dives, progression, difficulty and economy design.
Foundations. Instrumentation and pipelines, KPI frameworks, anomaly and cheat detection, and setting up a data function from scratch.

I've done this as head of data with a team around me, and as the only person in the room. Either way, the work that starts as a one off analysis usually ends up as something the studio keeps using.

Games are the specialism, though the methods travel. I take on smaller projects outside games when the problem is interesting.

The name

A psephos was a pebble.

Athens, 5th century BC. You voted by dropping one into a jar. Someone tipped it out at the end and counted. That was the whole system.

The word never really went away.

ψῆφοςpebble

ψηφίοdigit

ψηφιακόςdigital

Nobody sat down and renamed anything. It just kept up with what people were doing. There's even a field called psephology, the study of elections. Pebble science, if you translate it flatly.

Counting people to understand what they want. The pebbles are just players now.

Get in touch

If there's something you're trying to figure out, say so.

Engagements run from a few days on a single question, to a few months embedded with a team. Happy to start with a call and no expectations.

stavros@psephos.gg

Psephos on LinkedIn Stavros on LinkedIn Instagram X GitHub