Subscription

Origin & evolution

The recurring-payment relationship goes back centuries, from serialised newspapers to insurance. Its reframing as a general operating model is recent and has a named advocate. Tien Tzuo, who built the original billing system at Salesforce and then founded Zuora, argued the case in *Subscribed* (2018)), written with Gabe Weisert. His thesis is that customers increasingly prefer access over ownership, and that businesses across industries are shifting from selling products once to serving subscribers continuously.

The model brought its own measurements. Monthly Recurring Revenue and Annual Recurring Revenue describe the contracted stream rather than booked sales, and they decompose into the forces that move them: new subscriptions add, expansion grows existing ones, contraction shrinks them, and churn removes them. The discipline of watching that decomposition, line by line, is what separates a healthy subscription business from one quietly bleeding.

The accounting caught up in 2014, when the FASB and IASB jointly issued ASC 606 and IFRS 15, a converged standard for revenue from contracts with customers, effective for public companies from 2018. Its five-step model forces recurring revenue to be recognised as the service is delivered over the contract, not when the cash arrives. A year of subscription paid upfront is earned across twelve months, which is why a subscription's billing schedule and its revenue schedule are two different things.

How it works in practice

A SaaS company sells a team plan at 50 pounds per seat per month, billed annually. A 20-seat customer pays 12,000 pounds in January. Cash sees 12,000 in one month; ARR sees 12,000; recognised revenue sees 1,000 each month as the service is delivered.

In June the customer adds 10 seats. ARR rises to 18,000 through expansion, with no new sale, no new lead, no new deal cycle. The following January two of the original 20 seats are not renewed. That contraction trims ARR by 1,200. Across the cohort👥CohortGrowthA group of users sharing a common characteristicView reference →, the company watches net revenue retention: if expansion outweighs churn and contraction, the customer base grows revenue even with zero new logos. That single ratio, invisible in a one-time-licence business, is the number a subscription company lives or dies by.

Subscription vs. its neighbours

• Pricing tier🥉Pricing TierPricing & PackagingA pricing tier or planView reference → is the named package and its price; the subscription is a specific customer's live instance of one. The edge subscription_subscribes_to_pricing_tierSubscriptionsubscribes toPricing Tiercross-domain links the instance to the plan, so a tier change is a property of the relationship, not a new contract.
• Invoice💳InvoiceSales & RevenueAn invoice for billingView reference → is the periodic billing document a subscription generates; the subscription is the standing agreement that keeps generating them. The edge subscription_billed_via_invoiceSubscriptionbilled viaInvoicehierarchy holds that one-to-many cadence.
• Revenue stream💵Revenue StreamBusiness ModelA source of revenueView reference → is the aggregate flow the subscription feeds, modelled through subscription_drives_revenue_streamSubscriptiondrivesRevenue Streamcross-domain. One stream is fed by many subscriptions; the subscription is the atomic source.
• One-time licence transfers a right to use in a single transaction, with revenue recognised at the point of sale. A subscription keeps the relationship open and recognises revenue across its life, which is why renewal and churn exist in one model and not the other.

In the graph

In the Unified Product Graph, a subscription is the recurring-revenue anchor of the sales and monetisation region. It is reached through product_subscribed_via_subscriptionProductsubscribed viaSubscriptionhierarchy, linked to its plan by subscription_subscribes_to_pricing_tierSubscriptionsubscribes toPricing Tiercross-domain, billed through subscription_billed_via_invoiceSubscriptionbilled viaInvoicehierarchy, and aggregated into the business through subscription_drives_revenue_streamSubscriptiondrivesRevenue Streamcross-domain. The edge pipeline_sales_converts_to_subscriptionPipeline Salesconverts toSubscriptionhierarchy marks the seam where a closed deal becomes a standing relationship. Modelling the subscription as a durable entity rather than a single sale lets a product team trace consumption, expansion, and churn back to features⭐FeatureProduct SpecificationA product capability or featureView reference → and tiers, reading retention as structured product evidence🔎EvidenceValidationData supporting or refuting a hypothesisView reference →.