Aust studio · GB cohorts

Treat usage as a ledger, not a dashboard screenshot.

Socketvectorhub trains product ops, billing, and data people to automate SaaS Usage Analytics so a seat, a meter, and an invoice describe the same week.

Signal What we teach Owner
Active seats Decay windows that ignore idle logins Ops
Feature units Event names that survive a rename Product
Overage Warehouse jobs that match Stripe line items Finance
Open the course catalogue
Laptop showing analytics charts on a wooden desk
Clinic still from Usage Meter Studio — a live join of product events to billed units.
“The Event Contract Lab stopped our weekly argument about whether ‘session_start’ counted as usage. We still argue about packaging. That is a better argument.”
Priya N., revenue operations, Leeds
“Seat Decay Workshop made our expansion forecast quieter. The warehouse job is slower than Mixpanel’s UI, and that is the point.”
Client in workplace software, Manchester

Catalogue preview

Studios currently taking notes

Laptop with financial charts on a desk

Usage Meter Studio

Flagship eight-week sequence: contracts, decay, joins, and an invoicing dry run.

Studio outline
Team discussing work around a table

Event Contract Lab

Two-week sprint for naming events so product, warehouse, and billing share a glossary.

See listing
Wall of printed analytics reports

Seat Decay Workshop

A compact clinic on idle seats, grace windows, and what not to send to finance.

See listing

Why this exists

Most usage reports are polite fiction.

We built Socketvectorhub after watching GB SaaS teams paste Mixpanel screenshots into a board pack while billing used a different grain. SaaS Usage Analytics Automation, as we teach it, is the unglamorous work of contracts, jobs, and owners.

You will not leave with a vendor certification. You will leave with a written meter definition and a job that can fail loudly.

How the studio runs

  1. Write the contract first

    Every billed unit gets a name, a grain, a late-event rule, and a person who can freeze a week.

  2. Automate the join, not the slide

    Warehouse jobs replace weekly CSV theatre. We still keep a human checkpoint before invoice freeze.

  3. Measure decay on purpose

    Idle seats and unused feature flags are first-class signals, not footnotes in a churn slide.

Field notes

Recent writing

Person reviewing documents and a laptop

Event names that survive a rename

Why we keep a frozen alias table instead of rewriting history every sprint.

Read the note
Calculator and printed financial sheets

Seat decay is not churn

A Leeds billing team stopped treating silent seats as logo loss.

Read the note
Workshop with people around laptops

When product owned the meter

A short case on moving freeze rights out of finance-only hands.

Read the note
Operators taught since 2023
163
Recorded clinic hours
27
Learners from finance ops
41%
Live joins per cohort
2