Flagship · 9 weeks · 9 seats

The Packet Ledger

For the person who owns the graph the executive team screenshots. You will write an identity key, choose a window that matches how the product is used, and learn where resurrection campaigns quietly poison the series.

Study desk with laptop, notebooks and warm lamp light

Modules

  1. Naming the leak

    Before charts: a written account of who leaves, when, and which packet would have to fire for you to notice. We mark the writing, not the screenshot.

  2. Windows that match the product

    Seven, fourteen, and thirty are calendar habits. You will defend a window against how your users actually return — including apps with weekly rituals rather than daily ones.

  3. Activation versus habit

    A first-value moment is not a habit loop. We separate them on paper so marketing cannot borrow the halo of one for the other.

  4. Resurrection without costume

    Win-back campaigns inflate returning-user counts. You will learn to isolate them so the core graph remains readable.

  5. The board-shaped paper

    A pack that survives a sceptical finance director: who is missing, what you tried, what you will not claim. No vanity cover slide.

  6. Instrumentation clinic

    Live work on the schema you brought. Faculty will not rebuild your pipeline; they will refuse to let you hide behind “the tool did that.”

What you should be able to do afterwards

Instructor

Portrait of Helena Crowe, programme lead

Helena Crowe

Helena ran measurement for a Birmingham product group before opening the Bayton rooms in 2020. She still redlines dictionaries by hand. She will not pretend to be certified in every vendor console shipped this year.

Fee

The Ledger Table seat is £1,940 per person, informational only. VAT is confirmed in writing. There is no checkout here. Travel to Bayton is yours. See fees and refunds.

A limitation we will not dress up

We do not teach Mixpanel, Amplitude, or warehouse administration. If you need a click-path through a vendor console, this is the wrong house. Nine weeks will not repair a pipeline that has no identity key and no engineer assigned to give it one. We will tell you that in week one.

Questions people actually ask

Must I bring production data?

A redacted extract is enough. A toy dataset from a blog tutorial is not — we cannot critique identity you invented for the exercise.

Is there a recording if I miss a sitting?

No. The room is small so the work can be read aloud. Miss two sittings and we will discuss whether the seat should be released. That is a real constraint, not a scarcity trick.

Will this make our DAU look better?

Often it makes the honest number look smaller. If your goal is a prettier line, do not book.

From people who sat it

“The identity week slowed our shipping calendar. I still think nine weeks is long for a growth squad. The board paper, though, finally matches the product we actually run.”

Marta K. · Manchester

★★★★☆

Helena would not look at our North Star until we defined the subject of the packet. Frustrating. Correct.

Platform note · sitting xii