The house

A studio that treats telemetry as a craft, not a costume.

Route Maphub grew out of tracking plans that could not be handed to the next person. We teach from Cornwall, with live rooms across the United Kingdom and a few quieter seats abroad.

A calm office with glass and timber, used here as a stand-in for the studio’s working rooms

Mission

We want product teams to inherit numbers they can defend. That sounds modest until you watch a quarterly review collapse into a debate about whether “session” included background audio. App analytics, as we practise it, is the discipline of making those debates shorter and more honest.

The studio refuses two habits that dominate the market: the vendor tour that confuses a UI with a method, and the bootcamp that promises fluency in a weekend. Cartography takes longer. So do we.

Pedagogy

Every programme starts with an artefact you already own: a schema, a board, a sad retention PNG. Tutors annotate in public. Learners rewrite. We do not grade. We do stop a session if the room is performing insight instead of inspecting a join.

Reading is assigned, but it is short: a tracking spec, a paper on ecological inference, a badly named event from a previous cohort (anonymised). Writing is heavier. If you cannot describe a cohort in a paragraph, you do not yet have one.

Colleagues talking over a table, the shape of a critique hour Students with notebooks in a bright working room A small group in discussion around a table

Community

Alumni keep a private list for schema questions that are too awkward for Slack. It is not a “network”. It is a handful of people who have sat through Event Grammar and still remember how it felt to delete a sacred event. Once a quarter we hold a Cornwall afternoon for whoever can travel; most people join by video and nobody pretends that is the same.

A student’s path through the house

Most people arrive after an enquiry, not a catalogue browse. We ask for a sample of events and a question you cannot currently answer. If the fit is wrong — paid attribution, for example — we say so. If it is right, you might start with Field Notes, sit Retention Cartography, then take the Studio when you have a term you can protect.

After the Studio, some teams commission a Quiet Dashboard Audit. Others disappear into their own work, which we consider a success. We would rather be a brief, exacting chapter than a platform you cannot leave.