Flagship studio · 11 weeks · 38 seats
Retention Signal Architecture
An App Analytics room for teams who already ship. You will leave with a grammar, a window, a curve you can defend, and a one-page Friday readout. You will not leave as a certified vendor operator.
Who it is for
Bring an app, or sit beside the person who ships one.
Product leads, staff ICs, and founders who still touch the event list. Engineering partners are welcome; the homework assumes someone can change production instrumentation during the eleven weeks. If that is impossible, wait a cohort rather than collecting unread notes.
Informational fee: £1,840 per Studio Seat, plus VAT where it applies. The Reading Desk (£420) is the self-paced alternative. There is no payment form on this page.
Modules
What the eleven weeks contain
Event grammar both sides will sign
We read your live dictionary aloud. Names that cannot be mimed as verbs are marked. Android and iOS drift is treated as a defect, not a cultural difference.
Activation clocks that match opening hours
You interview five users or five support tickets, then set a first-value window in hours that exist in the United Kingdom — not in a template called Day 1.
Retention without the week-0 costume
We rebuild one curve after removing the install spike and the people who never completed first value. The smaller number is the one you are allowed to show.
Flags as experiments, not as confetti
A feature flag is allowed into the readout only if it has a named hypothesis, a kill date, and an event that already exists in the Atlas.
Revenue events versus the stores
Receipts reverse. Family plans duplicate. We design paid_or_renewed so a later refund can sit beside it without rewriting history.
The Friday page
One sheet: what moved, what we distrust, what ships next. Visiting critics are unkind on purpose. Kindness is for the pub afterwards.
Outcomes
What you should be able to do by week eleven
- Defend every event in the core set in a single sentence a designer will accept.
- State activation as a verb plus a clock, and show the clock’s evidence.
- Produce a retention curve with the costume removed, and name the costume.
- Hand a founder a one-page readout that survives a hostile question about sample size.
Instructor
Amira Holt
Amira opened the first Dev Pulsebase room in 2019 after a decade inside consumer subscription apps, where she watched DAU slides win arguments they had not earned. She still marks every taxonomy in the 38-seat cohort. Visiting critics rotate; the red pen does not.
She teaches from the United Kingdom and keeps Thursday evenings in GMT even when a guest joins from further west.
From people who sat this room
I wanted a Mixpanel tour. Amira made us spend week two deleting events instead. Our Android HomeViewed and iOS home_opened are now one verb. The tour never happened. Fine.
The Friday page from module six is pinned in our Notion. I still think the revenue week assumes more store-kit fluency than a pure product hire may have — pair with an engineer or you will stall.
Questions we are tired of dodging
Will this teach me to implement Mixpanel from a blank project?
No. That is a real limitation, not a humble brag. If you have never written an event into production, this studio will frustrate you. Sit next to someone who has, or take the Reading Desk first and wait until you can change the dictionary.
Do you take idea-stage apps with no users?
Rarely. Without a live stream the homework becomes fiction, and we already have enough fiction in analytics. Ship something small, then write to us.
Is the £1,840 taken on this website?
No. Pricing here is informational. Enrolment is invoiced after we accept an enquiry. See pricing and refunds.
What if I miss a Thursday?
Recordings exist. The marked homework does not pause. Two missed live hours in a row and we will suggest converting the remaining weeks to Reading Desk access rather than pretending you are still in the room.