Subscribers, churn and failed payments, counted the same way every month.

A subscription business lives or dies on one sum: how many people joined this month, minus how many left. Everyone agrees on that. Nobody agrees on the details. Does a paused subscriber count as churned? Does a customer who fails a payment and pays three days later count as lost and then won back? Two spreadsheets with two answers make for a long meeting.

Halvard defines each metric once, in plain words, and every dashboard reads that one definition. Churn means what you decided it means, and when someone changes the definition the change has a name and a date against it. After that the numbers stop being the topic, and what to do about them becomes the topic.

What subscription teams watch

• Failed payments, and how many come back. Card failures are the quietest churn there is. Halvard counts the retries that recover and the ones that do not, by reason code.
• Pack day, hour by hour. On dispatch day the orders dashboard shows boxes packed against boxes due, so a slow line is spotted before the courier arrives.
• Why people leave. Cancellation reasons from your shop and help desk tickets tagged “cancel” are grouped into one list, ranked by how much revenue each reason cost.

Typical setup

A box with 6,000 subscribers, weekly add-ons and a help desk sends around 300,000 events a month. On the Team plan that is £39 plus £6 of extra events, £45 in all. Most teams move to annual billing after the first quarter to get two months free.