Penuwch studio · app analytics as a ledger

The event stream is a document. Learn to edit it.

Most product rooms drown in charts they cannot defend in a steering meeting. We teach the grammar underneath: what a session meant, which properties belong on the event, and when a retention curve is simply noise. Mira Halston, lead tutor
Open the flagship studio
Dimly lit desk with analytical charts on a monitor
63
live product teams on the teaching roster since 2019
14
people in a typical studio room — enough to argue, not enough to hide
3.7
mean score from the March intake, out of five, collected after week twelve
2,137
event names rewritten in critique last year, most of them verbs that were pretending to be nouns

What we decline

A vendor tour is not a curriculum.

  • We do not certify you on a logo. Amplitude, Mixpanel, Firebase, and the rest are tools. The studio assumes an SDK is already in the app. You will leave able to write a taxonomy that survives a tool change.
  • Vanity metrics stay outside. Daily active users, unrestricted session counts, and “engagement scores” with no denominator are treated as decorative. We measure retained behaviour and the cost of acquiring it.
  • Dashboards are homework, not the lecture. You will spend more hours on naming, identity, and session windows than on chart cosmetics. That is the expensive part of app analytics, and the part most courses skip.
Laptop showing data work on a wooden desk

Flagship

Retention Telemetry Studio

Twelve weeks for product managers, analysts, and mobile engineers who already ship, and who are tired of arguing about charts that cannot be reproduced. You rebuild one live app’s event ledger, then read week-four retention without theatrical colour.

Informational fee for the next seat: £1,840. No checkout on this site — write to the house if you want a place.

Read the modules

From recent rooms

They named the event. Then they could defend it.

The identity lecture in week two stopped us merging anonymous and signed-in traffic as if they were cousins. Our iOS funnel had been quietly double-counting trial starts. After the studio we published a two-page identity memo and the weekly product review got shorter, which nobody expected.

Helena V., product lead, subscription audio — Cardiff

I still think week three’s homework is a bit stiff if you also ship on Fridays. The taxonomy drills were slower than I wanted; I arrived hungry for dashboards. The delay was the point, though I would tell a colleague to clear that week in the diary.

Anonymous client in grocery delivery

Longer voices and two case notes

How a seat unfolds

Read, name, sit with the ugly chart.

  1. A ledger before a picture. You arrive with a current event list, however messy. We treat it as a manuscript: redundancies, missing objects, properties that describe the developer’s mood rather than the user’s act.
  2. Sessions that match human use. Timeout defaults are rarely honest. We reconstruct sessions against how your app is actually held — commuting, bedtime, one-thumb grocery runs — and you write the window down.
  3. A readout you can take into a board pack. The last fortnight is a cohort narrative with limitations listed in plain English. If the lift is small, we say so. If the sample is thin, we say that too.

Journal

Notes from the desk

Code on a screen in a dark room

Taxonomy

Name the event before the screen ships

A release that lands without a verb is how ghost events are born. A short method for writing the name in the ticket, not after the retrospective.

Read the note
Green terminal text on a black display

Metrics

Why DAU misleads a subscription app

Daily actives flatter a product that is meant to be quiet. How we ask teams to report habit without inflating the room.

Read the note

The desk is staffed

Write if the ledger is already a mess.

We reply by the third working day. Address and telephone sit in the footer, copied as the house records them. Fees are listed without a cart.

Open the writing desk