Week six forced us to delete three charts that looked intelligent and said nothing about the account. I now open QBRs with occupancy, not DAU.
Flagship programme
Account Signal Studio
An eight-week studio for analysts and PMs who need App Analytics for B2B Platforms that survive a QBR. You leave with a revised event dictionary, an account metric tree, and a critique of one live dashboard.
What you will be able to do
- Draw an account–workspace–seat graph that matches how your product actually bills.
- Replace session-first activation with tenant-first activation, including nested orgs.
- Write metric definitions that sales operations can paste into a forecast narrative.
- Deprecate noisy events without orphaning historical reports.
- Spot when a “healthy” user count is one over-permissioned admin looping through the UI.
Modules
1. Tenant as subject
Why person-level funnels lie in multi-tenant products. Mapping legal entities, workspaces, and billed modules.
2. Event grammar under constraint
A working dictionary of no more than forty production events. Versioning rules and a written deprecation notice.
3. Seat occupancy and permission depth
Who is invited, who authenticates, who holds admin. Occupancy as a leading expansion signal.
4. Revenue join without a second warehouse
Joining invoices to tenants with the fields finance already trusts. Known failure modes with mid-cycle upgrades.
5. Quiet churn in nested orgs
Detecting unused seats, collapsing folders, and support volume that never becomes a product ticket.
6. The QBR pack
A twelve-slide limit. Every chart must name the account, the time window, and the decision it supports.
7. Critique week
You present a live dashboard from your company (sanitised). The room argues with the definitions, not the colours.
8. Handover
A one-page operating note for the person who will maintain the dictionary after you.
Instructor
Priya Langford taught herself warehouse modelling while running analytics for a UK collaboration platform with nested workspaces. She now spends most weeks reviewing other people’s event names and refusing to add “page_view” back in.
Fee (informational)
Account Signal Studio is listed at £1,840 per person, including critique week. The fee is published so teams can budget; there is no checkout on this site. Invoices are arranged after a short fit call. Employer-funded seats are common in GB product orgs.
Questions we actually get
Do I need a warehouse already?
You need access to some event stream and a way to list tenants. A mature warehouse helps, but several students work from exported CSVs and a CRM. The limitation is honesty about grain, not the brand of the stack.
Can I join if my product is still single-tenant?
You can, but the studio will feel early. The exercises assume nested accounts. We would rather you wait a quarter than force metaphors that do not exist yet.
Is there a real limitation we should know?
Yes. We do not teach mobile session replay, attribution windows, or consumer growth loops. If your “B2B platform” is mostly a consumer app with a company logo field, this syllabus will frustrate you — and we will say so on the fit call.
How much time outside class?
Plan three to five hours a week. People who also own the Monday exec pack find week four (revenue join) the heaviest.
From previous cohorts
★★★★☆ · Took Account Signal Studio while migrating warehouses. The dictionary work transferred; the revenue-join patterns needed local finance rules we had to invent ourselves.