Flagship course

Dormancy Window Studio

An eight-week desk for product analysts, lifecycle marketers, and the engineer who owns the event dictionary. You will leave able to defend a dormant definition in a meeting that currently treats “no open in seven days” as science.

Person working through charts on a desk

What you will be able to do

Write a last-meaningful-action contract that product and data both sign. Build dormant cohorts that survive a seasonal dip. Separate people who paused from people who abandoned. Report return motion without a vanity reactivation rate. Explain, in plain English, why a discount test is not proof of demand.

This studio will not resurrect a product people left because billing failed or the core loop broke. Analytics for user reactivation cannot substitute for a working week of the actual service.

Portrait of instructor Harriet Keene
Harriet Keene

Instructor. Former lifecycle analyst at a Leeds B2B SaaS firm; now teaches from Northlands with visiting hours on Thursdays.

Informational fee: £1,240 per seat, or £2,080 for a product-and-data pair. No checkout on this site.

Ask about the October cohort

Modules

01

Silence that is not churn

Billing cycles, school holidays, sports seasons, and the difference between a paused account and a forgotten one.

02

Last meaningful action

Replacing session_start with the event that meant the person used the thing they paid for.

03

Window design

How to propose 11, 23, or 46 days without looking arbitrary, and how to document the argument.

04

Channel inventory

Who can still be reached, who opted out, and which vendor is already shouting.

05

False returns

Cancel flows, password resets, and support tickets that look like reactivation in a naive join.

06

Experiments that do not bribe

Copy, timing, and in-product prompts versus coupons that buy a week of chart movement.

07

The sceptical pack

A board-ready narrative that shows volume, quality of return, and what you still cannot see.

08

Handover

Event dictionary diffs, a named owner, and a 90-day review date so the window does not fossilise.

From previous seats

Module 05 caught our “reactivated” support-ticket join. We had been celebrating people who came back to complain about a failed renewal.

Owen T., product analyst, Cardiff

The pair format helped. I still think eight weeks is long if your warehouse is a mess; we spent the first fortnight just renaming events. Worth knowing before you book.

Lina, Bristol · growth

Questions we actually get

Do you teach paid acquisition for lapsed users?

No. Lookalike audiences built from dormant IDs are outside this studio. We will say so in week one so you do not sit through seven more weeks waiting for media buying.

What if our product is genuinely dying?

That is the real limitation. If retention collapsed because the core loop is broken, the studio will help you stop misreporting, not invent a comeback. Several teams have used week seven to recommend shutting a win-back programme.

Is the Lincolnshire day required?

No. It is an optional working session near Northlands for pairs who want to sit with paper printouts. Remote seats are first-class.