A business plan becomes more useful when its assumptions are compared with what the business is actually doing. A Stripe connection can provide a snapshot of subscription activity alongside the plan. It is a starting point for investigation, not a substitute for accounting or a complete picture of customers.

The current Stripe integration calculates an estimated monthly recurring revenue figure from active subscriptions in a selected currency. It also reports active subscriptions, recent cancellations, estimated lost recurring revenue and a 30-day churn estimate when a denominator is available. It can mark a snapshot as truncated, so check that indicator before drawing conclusions.

These are implementation-specific estimates, not necessarily the same definitions used in your Stripe dashboard, your financial statements or your investor reporting. Currency, subscription status, billing intervals and limits on retrieved records can affect the result. Review the source data and the calculation before relying on it.

The most important of these fields is the truncation flag. A snapshot that stopped early still looks like a snapshot, and an MRR figure computed from half a customer list is not a smaller truth — it is a different claim.

  • Active subscriptions

    Counted from the selected currency

    Filtered by status.

  • Estimated MRR

    From active subscriptions

    An estimate, not a Stripe report.

  • Recent cancellations

    Over a recent window

    Amounts included.

  • 30-day churn

    Estimated, when a denominator exists

    Otherwise, no figure.

First, compare the snapshot date with the period you are investigating. Then put the observed number next to the plan's target and ask what changed.

If a fictional company expected $10,000 in monthly recurring revenue and its snapshot estimates $8,000, the $2,000 gap is an observation about two numbers — not an explanation of why the gap exists. That distinction is the whole game. A tool that produces a number next to a number is useful; a tool that produces a narrative about the gap is dangerous, because you will remember the narrative and forget to check it.

Break the difference into parts before you explain it. New sales, cancellations, downgrades, annual plans moving onto a monthly cadence and currency effects all show up in the same place and have different meanings. Write down the evidence for each explanation and the next test for each.

Some explanations are cheap to check and worth checking first: a single large cancellation explains a surprising share of many small gaps, and a pricing change in the same window explains the rest. Others are expensive: cohort retention is worth measuring, and it is worth measuring on a schedule rather than in the week you need the answer.

One thing not to do is to present an estimate as an observation. A forecast belongs in the plan as a forecast. The moment a modelled figure is quoted as a fact, every downstream number inherits an error that nobody will go looking for.

Use the integration screen to provide the requested Stripe credential and follow Stripe's guidance on restricted keys and permissions. Grant the least access needed, protect the credential and review it periodically. If synchronisation fails, check the credential and access before retrying. Never paste secrets into an article or support conversation.

A snapshot is a read of a moment. The plan is a claim about a period. Keeping the two in separate columns — what happened, and what we think will happen — is the practice that stops a tool from quietly becoming an authority.

Continue with SaaS unit economics to understand what revenue does — and does not — say about the economics of acquiring a customer.