Blog · Board and management reporting · Software
A product management report connects adoption and retention changes with commercial results and accountable follow-up. Build a recurring review from customer, usage, and revenue exports, with a worked comparison and spreadsheet formulas.
A product management report connects changes in product adoption and retention with business results, then sets out who will investigate or act. Build it from customer, usage, and revenue exports for a defined period, with enough detail to rebuild the headline figures.
The report should answer whether more customers are getting value, whether those customers remain, and what happened to their recurring revenue. A list of releases cannot answer those questions on its own.
Specify the reporting period, account population, adoption action, retention definition, and commercial measure before calculating. For a B2B software company, an account is often the useful unit because a subscription can cover several users. Keep user activity available as supporting detail without mixing users into the account denominator.
In this example, a US software company reviews September 2026 against August 2026 for accounts paying at August's close. Adoption means completing the product's main workflow during the month. Retention means that an opening account still has a positive paid subscription balance at September's close.
New September customers are outside this fixed-base comparison. Report their contribution separately if the meeting needs total company growth. The management reporting guide explains how this product review fits into the wider monthly package.
Bring an opening customer list with stable account IDs and segment, usage exports for both months, and customer recurring revenue balances at each close. Aggregate usage to an account-level adopted flag for each month. Include customers with no qualifying activity and customers that canceled, rather than letting them disappear from the comparison.
Check that every usage account maps to the customer list and that revenue is not repeated across individual action rows. Record unmatched IDs and incomplete periods as exceptions for resolution. A missing export is not evidence of zero usage.
Keep behavior and subscription retention separate. Amplitude's retention guide describes retention through a starting action and a subsequent return action. This report instead labels its paid-account measure explicitly, so readers do not mistake continuing payment for continued product use.
The checked account-level file produces this segment summary. Columns A through G follow the displayed order. All accounts in the opening base were eligible for the core workflow, and all figures are illustrative.
| Segment | Opening accounts | Adopted in August | Adopted in September | Retained paid accounts | Opening MRR (USD) | Closing MRR (USD) |
|---|---|---|---|---|---|---|
| Growth | 10 | 6 | 8 | 9 | 20,000 | 22,000 |
| Business | 10 | 7 | 7 | 8 | 20,000 | 18,000 |
| Total | 20 | 13 | 15 | 17 | 40,000 | 40,000 |
If the account-level sheet is named Accounts, with segment in B, August adoption flag in C, September flag in D, paid-retention flag in E, and opening and closing MRR in F and G, calculate the summary as follows. Replace row 1000 with the actual last source row.
B2: =COUNTIF(Accounts!$B$2:$B$1000,A2)
C2: =SUMIFS(Accounts!$C$2:$C$1000,Accounts!$B$2:$B$1000,A2)
D2: =SUMIFS(Accounts!$D$2:$D$1000,Accounts!$B$2:$B$1000,A2)
E2: =SUMIFS(Accounts!$E$2:$E$1000,Accounts!$B$2:$B$1000,A2)
F2: =SUMIFS(Accounts!$F$2:$F$1000,Accounts!$B$2:$B$1000,A2)
G2: =SUMIFS(Accounts!$G$2:$G$1000,Accounts!$B$2:$B$1000,A2)
Microsoft's SUMIFS reference explains conditional sums and the matching ranges they require. Keep only eligible opening accounts on this working sheet. Then calculate the report measures from the summary:
August adoption: =C2/B2
September adoption: =D2/B2
Adoption change: =(D2-C2)/B2
Paid retention: =E2/B2
MRR change: =G2-F2
Net revenue retention: =G2/F2
For the total, divide summed numerators by summed denominators. Do not average segment percentages, even though the segments happen to be equally sized here.
| Report measure | Growth | Business | Total |
|---|---|---|---|
| August adoption | 60.0% | 70.0% | 65.0% |
| September adoption | 80.0% | 70.0% | 75.0% |
| Adoption change, percentage points | 20.0 | 0.0 | 10.0 |
| Paid account retention | 90.0% | 80.0% | 85.0% |
| MRR change (USD) | 2,000 | -2,000 | 0 |
| Net revenue retention | 110.0% | 90.0% | 100.0% |
Percentages are shown to one decimal place. The headline is precise: adoption increased from 13 / 20 = 65.0% to 15 / 20 = 75.0%, while opening-base MRR stayed at $40,000. Growth's $2,000 increase exactly offset Business's $2,000 decrease.
Paid retention is 17 / 20 = 85.0%, while revenue retention is 40,000 / 40,000 = 100.0%. Expansion can offset lost customers; Stripe's cohort definitions make this distinction between subscriber and revenue retention. The unchanged total therefore does not establish an unchanged customer base.
Prove the report by matching segment counts to the opening account list, activity flags to the deduplicated usage records, and both MRR totals to their original exports. The MRR dashboard provides the separate movement reconciliation. Keep the product health dashboard available for account-level inspection between reviews.
Product owns checking whether Growth's additional adopted accounts completed the intended workflow. Customer success owns reviewing the nonretained accounts and Business's revenue decrease. Finance owns separating expansion, contraction, and churn before the team attaches a commercial explanation to adoption.
Record each action with an owner, a due date, and the evidence expected at the next review. Use the product profitability report when the decision needs costs and margin as well as recurring revenue.
Covirage is not affiliated with Microsoft, Amplitude, or Stripe.
Bring your account list, usage exports, and customer revenue files to Covirage, which maps the columns and uses its tools to compute and check the comparisons. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, set up your business, and bring a sample of your own data.
See self-service analytics for the supporting approach to recurring business reviews.
Choose a schedule that matches the decisions and the completeness of the source files. A monthly review can connect usage with subscription outcomes once finance has finalized the period. More frequent updates work only when the observation windows and commercial records are complete enough to interpret.
A dashboard keeps measures visible for ongoing inspection. A report selects the material changes for a specific review, states their business meaning and uncertainty, and records follow-up owners. Its conclusions should still point back to the customer rows that produced the dashboard figures.
Include delivery context only when it helps explain the outcome being reviewed. Keep the report centered on customer behavior and commercial results. Completion of a feature is evidence that work shipped, but it does not establish adoption, retention, or a revenue effect.