Strategy
Part of When to rewrite your subscription commerce strategy and rebuild the numbers
Before you build a subscription commerce strategy framework, settle five decisions
A subscription commerce strategy framework works only if five decisions are settled first: unit economics, churn, pricing, compliance and reporting.
What to take away
- Most teams pick a platform or a product first, then try to make the numbers work. Reverse that order.
- Five decisions must be written down before you choose a subscription platform: unit economics, churn definition, price and renewal terms, compliance, and the reporting model.
- Each decision has to survive board scrutiny on its own. If you cannot explain a number in one sentence, the framework is not finished.
- Treat the framework as a working document. Revisit it when pricing, retention or regulation shifts.
Why the product-first route fails
A framework built around features collapses when the numbers do not stack. A team launches a coffee subscription because the product is good, then finds the average customer stays four months and the margin never covers acquisition. A better app does not fix that. Deciding, in advance, what retention and margin the model needs does.
The pillar guide on subscription commerce strategy and planning for 2027 sets out the order these decisions need to be made in, which is why it is worth reading before you assemble your own version.
Decision one: unit economics first
Write down the cost to acquire a subscriber, the monthly gross margin per subscriber, and the expected lifetime in months. The framework only works if acquisition cost is recovered inside the expected lifetime, with headroom.
Unit economics example
- £45acquisition cost
- £12monthly gross margin
- 9 monthsaverage life
- 5 monthsminimum viable life
For example, a team paying £45 to acquire a subscriber on £12 monthly gross margin and a nine-month average life recovers acquisition in under four months. That leaves five months of contribution. If average life falls to five months, the model breaks, so the framework must state a minimum viable lifetime.
Decision two: define churn once
Most reporting arguments come from teams using different churn definitions. Pick one and record it. Voluntary churn, involuntary churn from failed payments, and paused subscribers need separate counts, because each needs a different response.
Churn types and responses
Voluntary churn
- Cause
- customer choice
- Cheapest fix
- product or pricing
- Count separately
- yes
Involuntary churn
- Cause
- failed payments
- Cheapest fix
- payment retries
- Count separately
- yes
Paused subscribers
- Cause
- temporary pause
- Cheapest fix
- separate count
- Count separately
- yes
Involuntary churn is often the cheapest to reduce, through payment retries and card updater services. Voluntary churn usually needs a product or pricing change. Mixing them hides which lever to pull.
Decision three: pricing and renewal terms
Set the price, the billing frequency, the renewal date and the cancellation route as one package, because changing any one of them changes the others. A monthly price rise may cut voluntary churn while pushing up payment failures.
The Bank of England's monetary policy decisions shape the interest rate and inflation environment. That backdrop informs how much you can invest in acquisition and how much price headroom subscribers will tolerate. Build a sensitivity case for both a higher and a lower rate environment.
Decision four: compliance before launch
Subscription terms sit inside consumer law, advertising rules and data protection. The framework should name who owns each area and what evidence is kept.
Advertising claims about savings or free trials fall under the ASA's non-compliant online advertisers list, and appearing there damages trust and paid acquisition.
Payment and personal data need the same discipline. The ICO's security guidance for organisations sets out expectations for protecting subscriber payment and personal data, so the framework should state how those controls are tested.
Decision five: the data model and tooling
The platform you choose must report the unit economics and churn definitions settled in decisions one and two. If it cannot separate voluntary and involuntary churn, or export cohort margin, it is the wrong tool at any price. Write the reporting requirements before you shortlist vendors.
Teams that skip the data model often migrate platforms twice in a year. The article on subscription commerce strategy mistakes in England shows how those rebuilds usually start with a reporting gap rather than a product flaw.
Worked example
A UK retailer sells a £30 monthly box at £18 gross margin. Acquisition cost is £54, expected life eight months, giving £144 contribution before acquisition, or £90 after.
The framework sets a floor of six months' life and a ceiling of £60 acquisition cost. If a test cohort falls below either, the team pauses spend and every figure is illustrative, not a benchmark.
Common questions
How long should the framework take to build?
For a small team, two or three working sessions covering the five decisions. The constraint is agreeing the churn definition and the unit economics, not writing the document.
Should the framework include tooling choices?
Only as requirements. Name what the platform must report, not which vendor to buy. Vendor selection follows once reporting needs are fixed.
How often should it be reviewed?
At least twice a year, and immediately after any pricing change, platform migration or regulatory update affecting renewal terms or data handling.
What if the numbers do not work?
Change the offer, the price or the acquisition channel before you build. A framework that exposes a broken model early has done its job.
