B2B SaaS Spreadsheet Analysis With Jolene.pro: Revenue, Retention and Product Usage
A SaaS business can finish the month with more recurring revenue and still have a retention problem. Expansion in a handful of accounts may cover losses elsewhere. Meanwhile, the product team sees activity, customer success sees support tickets and finance sees subscription charges. Each spreadsheet answers part of the question.
With the relevant Excel or CSV exports, Jolene.pro can help you examine those patterns across tables, request charts and follow a finding back to its source records. The starting point is a consistent account ID and a clear definition of the month being measured.
Assemble account-level data before asking for trends
Bring subscription records with account and subscription IDs, plan, billing interval, recurring amount, currency, effective dates and cancellation dates. For retention, include historical periods. Add account-level usage summaries, renewal dates and support records where needed. Names and email addresses are usually unnecessary for this analysis; stable IDs do the joining.
Keep the subscription, account and user levels distinct. One customer can hold several subscriptions and hundreds of user accounts. Summarize each table to the appropriate level before comparing it. Define the timezone and exclude incomplete periods or label them clearly.
1. Explain how recurring revenue changed
Ask: “Build a monthly recurring revenue movement summary using our supplied MRR policy. Separate new business, expansion, contraction, churn and reactivation. Reconcile opening MRR plus movements to closing MRR and show the supporting subscriptions.”
Provide the policy rather than asking the tool to invent it. State how annual subscriptions are normalized, when cancellations take effect and how discounts, taxes, one-time fees and foreign currency are treated. A yearly invoice is not one month of recurring revenue. Payment receipts and recognized accounting revenue are separate measures too.
Two monthly snapshots can show net account changes. They cannot reveal every upgrade, downgrade or reactivation between those dates. Include subscription-event history when you need the full movement sequence. Review unexplained differences instead of adding an “other” category and hoping it behaves.
2. Compare customer cohorts fairly
Ask Jolene.pro to group accounts by first paid month and show how many of the original accounts remain paid at each later month. Request the original cohort size, retained account count and retention percentage together. Define treatment of pauses, reactivations and accounts with multiple subscriptions.
Compare cohorts at the same age. A three-month-old cohort has no twelve-month retention result. Keep immature observations blank rather than treating them as losses. If revenue retention is required, track revenue from the original cohort separately from new customers joining later.
3. Examine adoption within paying accounts
With purchased or licensed seats, assigned seats and dated activity summaries, ask: “Compare assigned seats with distinct users meeting our active-use definition during the last complete 30 days. Break down adoption by account and plan. Flag missing activity coverage.”
Specify meaningful activity, such as completing a core workflow, rather than assuming every login represents adoption. Low recorded usage can identify accounts for a conversation. It does not establish why usage is low, whether telemetry is complete or whether the customer intends to leave.
4. Build a renewal review list
Combine renewal dates with current recurring value, recent usage and unresolved support records at account level. Ask Jolene.pro to list renewals in the next 60 days and show those attributes side by side, with source references. Summarize tickets before joining them so revenue is not repeated once per ticket.
Use explicit review rules, such as a recorded usage decline plus an approaching renewal. Describe these as review flags. They are not calibrated churn probabilities, and a spreadsheet correlation does not prove that a support issue caused a cancellation.
Bring the evidence to the account conversation
Inspect the calculations, save useful analyses and assemble charts for the monthly operating review. Re-run them against the next export after checking the reporting policy and file structure. Jolene.pro helps turn scattered account records into questions your finance, product and customer-success teams can investigate together.
Reference: ChartMogul’s MRR movements guide. The prompts describe possible analyses with suitable data; no customer results are claimed here.