Flagship studio
An eight-week sequence for people who must automate SaaS usage analytics until product events, seats, and invoices describe the same calendar week.
A meter contract that names grain, late events, and freeze rights. A decay table for seats that finance can reject. A warehouse job that joins billed units to events. A dry-run invoice pack you walk through with a colleague, not a slide deck.
The studio assumes you can read SQL at the level of joins and window functions. It does not assume you own Mixpanel, Amplitude, or a particular warehouse. We work in examples you can port.
£1,240 for materials, four live clinics (75 minutes each), and written feedback on one meter contract. Payment is not taken on this site. See fees for neighbouring options.
Instructor. Former billing operations lead at a Bristol subscription firm. She spent six years reconciling product events to invoice lines and now teaches that reconciliation as a craft rather than a fire drill.
You pick one billed unit and write its grain in a sentence a new hire can defend. We introduce an alias table so a product rename does not rewrite last quarter.
You set a late-event window and a freeze owner. Clinics walk through a week that arrives three days after invoice generation — a common GB billing calendar snag.
Idle logins leave the expansion story. You build a decay window and a report that finance can refuse. Refusal is treated as a successful control, not a failure of the dashboard.
A warehouse job joins events to billed units. The last clinic is a dry-run invoice pack: three line items, one known mismatch, and a written note to the freeze owner.
No. We do not teach a specific vendor’s UI. If your stack is Mixpanel-only and you need recipe screenshots, week one will feel abstract. The studio is about contracts and jobs you can move between tools.
Yes, with a local SQLite stand-in we provide. You will still write the job as if it ran overnight. Teams with a warehouse tend to finish the join faster; they do not skip the contract work.
We send a letter confirming completion of the four clinics and the contract review. It is not a vendor badge and we do not claim it is.
“Usage Meter Studio’s freeze-owner exercise embarrassed us in a useful way. We had three people who thought they could close the week.”
“The decay table from week five is still in our repo. I wanted more vendor-specific SQL than Nia would give. We filled that in ourselves after the dry run.”