London studio · founded 2019

App analytics, practised as a craft.

We teach product teams to name events with care, to distrust flattering funnels, and to write a weekly metric letter that a sceptical founder can actually use.

Autumn desk: Signal Architecture

71 practitioners sat the last London cycle — not a vanity crowd, a room that fits critique.

Abstract dark surface suggesting layered measurement — First-party instrumentation, not theatre

Flagship desk

Analytics charts on a laptop in low light

Signal Architecture

A twelve-week studio on event design for product teams. You leave with a taxonomy you can defend, a retention window that is honest, and a habit of writing readouts that do not flatter the last release.

12 weeks £1,840 informational fee Isla Penrose, programme director

Open the syllabus

The Event grammar module stopped us renaming the same tap three ways. We still argue about session length — that is the point — but the board packet is shorter.

I wanted Amplitude recipes. Net Mapcore refused. After Funnel forensics I could finally say why our onboarding chart was lying, which was less comforting than a template.

★★★★☆

The weekly metric letter is the only homework I still keep. The live desks run long; if you need a tool-click tour, this is the wrong house. For app analytics as judgement, it held.

How we read apps

Numbers that survive a sceptical Monday.

Most product rooms drown in charts that agree with last week’s story. We train a slower habit: name the action, bind it to identity without theatre, pick a retention window you can explain to finance, and write the exception before the average.

App analytics here is not a catalogue of platforms. It is the work of deciding what must be true for a release to have mattered. United Kingdom teams join us when the dashboard has become a performance and they want the instrument back.

The studio’s method