Monday’s dashboard says activation fell. Nobody can remember whether the denominator includes accounts still setting up, whether test workspaces were removed or whether the activation event changed last week. The chart looks precise. The meeting has no decision to make.
Write the contract before the query
Name the recurring customer job first. A reporting product may ingest current data and produce a report. A reminder product may schedule a notice and preserve the state around its delivery. Your measurement cadence should follow that job and its consequence; a quarterly workflow does not produce a useful weekly retention signal merely because the meeting is weekly.
Give each metric seven fields: decision, event, eligibility, denominator, exclusions, period and owner. If one is missing, leave the number out of the dashboard until the definition is repairable.
Four metric cards, four different decisions
| Metric card | Formula or definition | Boundary to record | Decision it can inform |
|---|---|---|---|
| First useful event | Eligible new accounts completing the named event inside the local setup window ÷ eligible accounts whose window has closed | Window, test accounts, duplicates, staff and missing telemetry | Which setup state to inspect |
| Retained job | Accounts completing the core job again ÷ accounts with an eligible repeat opportunity in that cohort period | Natural recurrence, paused accounts and event completeness | Which repeat cycle needs investigation |
| Logo churn | Paying accounts ended in the period ÷ paying accounts active at the start | Period, trials, voluntary cancellation, failed payment and closure | Which cancellation evidence to open |
| Support burden | A proposed operating view of workflow-related contacts and handling time beside eligible active accounts | Bug, setup, billing, unclear state and incident consequence | Which product state or support path to examine |
The logo-churn formula above is a local operating definition compatible with common subscription analysis, not a universal provider definition. Stripe calculates subscription analytics such as MRR and churn using its own documented data and rules. If you use provider numbers, write their inclusions and exclusions into your dictionary rather than silently treating them as accounting standards.
Formula boundary: MRR is not “whatever recurs”
Document which recurring components enter MRR and keep the rule stable. Usage charges, taxes, credits, currencies and one-off services require explicit treatment. Stripe’s current analytics documentation is useful for understanding Stripe’s calculation; it does not settle every ledger or accounting decision.
Likewise, Google Analytics can collect, process and aggregate configured events, but the configuration affects what appears in reports. It cannot choose your product’s first useful event. Audit event names, filters, duplicates and missing telemetry before interpreting a movement.
Put each signal on the clock it deserves
Incident-led
Incorrect billing, failed imports, broken delivery or data-integrity states. Contain and investigate; do not wait for the dashboard meeting.
Operating review
Recent eligible starts, repeat opportunities, cancellations and support evidence. Choose one question to open, not five charts to admire.
Natural product cycle
Retention for monthly, quarterly or event-driven jobs. Review when another opportunity actually exists.
Commercial review
Package, cohort and pricing assumptions after comparable contract events—not after every account movement.
Illustrative review — fictional data, not PBT metrics
The following is a scenario, not a benchmark or expected result: a reporting product records 6 repeat jobs from 8 eligible accounts. Two other accounts are marked “telemetry unknown” and stay outside the fraction. Support shows one delivery incident and several low-consequence wording questions.
The founder does not annualise the fraction or call it healthy. The meeting first verifies the event definition, then opens the delivery trace because its consequence differs from the wording questions. The decision is to repair or instrument that state. The number merely located the evidence.
A review agenda that ends in work
- Validate the measurement. List changed definitions, delayed records and missing events.
- Locate the customer job. Before first value, during repeat use, at delivery, in billing or at cancellation?
- Open the record. Event trace, support contact, cancellation note or invoice—not the chart alone.
- Name one owner. A solo founder can hold every role; the decision still needs an owner.
- Write the next action. Instrument, investigate, repair or deliberately gather more evidence.
What to leave off the dashboard
Leave out CAC, LTV/CAC, annualised tiny-period rates and borrowed “good churn” targets until you have the definitions and evidence to use them. Do not force every metric into a weekly cadence. Do not label provider-accepted email as a completed customer job. A shorter dashboard with visible unknowns is more useful than a KPI wall with hidden denominators.
Complete this card before a metric earns dashboard space
Decision for this week: remove one undefined rate from the dashboard and replace it with a completed metric card. If the underlying evidence is support contact, continue with the ticket evidence register.
Definitions worth pinning
- Stripe subscription analytics, observed 2026-07-28. Provider definitions depend on Stripe data and configuration; the page is mutable and is not a universal accounting standard.
- Google Analytics event data, observed 2026-07-28. Describes Google Analytics collection and processing; it does not define activation or a successful product outcome. Check the current provider documentation before relying on these definitions.