You're staring at a flat MRR number and you don't know what it's hiding. Expansion could be covering churn, a few downgrades could be cancelling out strong new sales, or failed payments could be doing quiet damage. The data's sitting in your billing records. What you're missing is a better way to ask about it.
That's where well-formed natural language examples earn their keep. You're not writing SQL or rebuilding spreadsheet formulas. You're asking a complete business question and getting a chart, a breakdown, and a short explanation back. The difference between a useful answer and a misleading one usually comes down to phrasing, not the tool.
The eight question types below run from simple period comparisons to recurring monthly reviews. Each one includes the exact question shape, the metric logic behind the answer, where the answer can mislead you, and a repeatable tactic you can add to your own routine. The same discipline applies whether you're reviewing your own revenue or using a service like done-for-you SaaS appointment setting to fill the pipeline in the first place. Good questions make the numbers usable.
Table of Contents
- 1. Period-over-period revenue questions
- 2. Acquisition channel questions tied to paying customers
- 3. Revenue movement breakdown questions
- 4. Retention and cohort questions
- 5. Failed payment and billing event questions
- 6. Plan and segment comparison questions
- 7. Explanation questions for unexpected metric changes
- 8. Recurring reporting questions for monthly reviews
- Natural Language Question Types for SaaS Data at a Glance
- Turn These Questions Into Your Reporting Routine
1. Period-over-period revenue questions
Start with the question most founders ask first. Try: "What was our MRR last month compared to the month before?" You're asking the tool to compare one recurring revenue figure across two time windows and explain the gap. It turns a static dashboard number into a trend, which is what you need to make a decision.
The answer depends on how the tool defines MRR. Chartsy derives figures from issued invoices, so prorations, partial refunds, failed payments, and mid-cycle plan changes show up in the result rather than getting estimated from subscription records. That distinction matters when a month looks flat for billing reasons, not product reasons.
Say a solo founder raises prices and asks how MRR changed. The chart shows both months, but the headline alone won't tell her whether existing customers absorbed the increase or downgraded. A small B2B team checking a quarter-end dip faces the same problem. Fewer new customers and more cancellations look identical in a single total.
How to phrase it well
- Name the metric and range: Ask for "MRR, last 30 days vs previous 30 days" so the comparison stays exact.
- Ask for the breakdown next: Request new, expansion, contraction, and churned revenue separately, then dig into the driver with a guide to MRR growth rate calculations.
- Check sync status first: Confirm your billing sources are fully synchronized before you trust a recent period.
2. Acquisition channel questions tied to paying customers
Traffic reports tell you who signed up. Billing reports tell you who paid. Neither one alone tells you which channels produced customers who subscribe.
Ask: "Which channels brought the most paying customers in the last 90 days?" That question forces a join between where visitors came from and whether they later paid. Chartsy links website visits and signups to subscription records, so the answer reflects paying customers instead of raw click volume.
Practical rule: Judge a channel by retained revenue after 60 or 90 days, not by signup counts on day one.
A growth lead might compare paid search against newsletter signups by paying customers after 60 days and find the cheaper channel churns twice as fast. An agency reviewing a client's funnel might check which channels trial users came from before converting, so budget follows conversion instead of traffic.
First-touch and last-touch answer different questions
First-touch attribution credits the channel that started the journey. Last-touch attribution credits the one right before conversion. Compare both side by side and note where they disagree, because that disagreement tells you how much the journey bends your results. Ask about retained revenue alongside customer counts too, or you'll favor channels that deliver high churn. Treat the results as directional. Move budget in small steps and watch what happens, rather than shifting everything based on one answer.
3. Revenue movement breakdown questions
A single MRR total can rise while churn climbs, as long as expansion covers the loss. That's why movement questions matter. Ask: "How much MRR came from expansion versus churn this quarter?"
A standard bridge starts with beginning MRR, adds new and expansion MRR, and subtracts contraction and churn, which is the structure described in the Digital Vantage SaaS metrics guide. According to AWS guidance on SaaS growth metrics, net revenue retention incorporates expansion, contraction, and churn relative to the starting cohort, and it gets hard to interpret when those movements aren't instrumented by cohort.
Say a small B2B team sees flat total MRR. The breakdown shows churn rising while expansion from annual upgrades rises just as fast. Two problems and one success, all hiding inside one flat number. A fractional CFO reviewing several client accounts can use the same categories to explain a flat quarter to a board without guessing.
Reading the breakdown
- Ask for both views: Request absolute amounts and percentages of starting MRR.
- Segment by plan: Check whether churn concentrates in one tier.
- Separate failed payments: A retry that succeeds later can look exactly like churn.
4. Retention and cohort questions
Your total churn rate blends every customer into one average. It can't tell you whether customers who joined last quarter behave differently from the ones who joined two years ago.
Cohort questions fix that. Ask: "What is 12-month cohort retention for customers who started on the annual plan?" You're grouping customers by when or how they started, then tracking how well each group stays subscribed. Lifetime value questions work the same way, estimating revenue per customer over a defined period instead of counting accounts.
Say a bootstrapped founder adds an onboarding email sequence. She compares retention for customers who joined before the sequence against those who joined after, and now she has evidence instead of a hunch. A subscription business on Paddle Billing might check whether monthly and annual plans retain revenue at different rates before changing its pricing page.
Keeping cohort comparisons fair
Require a minimum cohort size before comparing rates, because tiny cohorts swing wildly. Compare cohorts over the same number of months, so an older group doesn't win just by having more time to churn. For a deeper method, work through SaaS cohort analysis fundamentals and apply the same structure each cycle.
Treat retention trends as guides for experiments, not fixed forecasts. A cohort tells you what happened to a specific group under specific conditions. It doesn't guarantee the next group repeats it.
5. Failed payment and billing event questions
Not every revenue dip means a customer chose to leave. Cards expire. Banks decline charges. Refunds and prorations change what you collect without anyone clicking cancel.
Ask: "How much MRR was affected by failed payments this month?" Because Chartsy calculates metrics from issued invoices, prorations, partial refunds, failed payments, and mid-cycle plan changes land directly in the figures. You're seeing money events, not subscription estimates.
Say a founder blames a product change for a soft month. The billing breakdown shows a card expiry issue caused a bigger dip than the release did. That's a dunning problem, not a product problem, and the fix is completely different. A fractional CFO can run the same question across client accounts before closing the month to catch refund and proration activity early.
Don't let involuntary churn masquerade as a retention failure. Ask for failed payments separately from cancellations every single month.
Run this question on a schedule so recurring billing problems surface as patterns, and read up on involuntary churn and dunning recovery if the numbers keep surprising you. Confirm your billing sync is current before reading the latest period, since an incomplete sync understates recovered payments.
6. Plan and segment comparison questions
Ask: "Which plans have the highest retained revenue per customer?" You're comparing subscription groups to find where revenue holds up, instead of assuming your biggest segment is your best one.
Segmentation by plan, tag, or custom field lets you test pricing, packaging, and targeting decisions against real revenue outcomes. Say a small B2B team compares its mid-tier plan against its enterprise plan by revenue retained after six months. The enterprise plan brings fewer customers, but each one retains far more revenue. That changes where sales effort goes. An agency can run the same comparison by industry tag across several client accounts and spot which verticals outperform.
What makes a comparison trustworthy
- Keep definitions stable: If segment rules change monthly, your trends mean nothing.
- Check cohort size first: A segment with nine customers can't support a packaging decision.
- Save the winners: Store frequent comparisons as dashboard templates so you stop rebuilding them.
I recommend reviewing segments quarterly rather than monthly. Most segments don't move fast enough for monthly reviews, and you'll chase noise. The exception is a segment tied to a recent pricing or packaging change, where monthly checks catch problems early.
7. Explanation questions for unexpected metric changes
A sudden MRR drop needs a cause, not just a chart. Ask: “Why did net MRR fall in March?” The period and metric make the question specific, while the answer should point to possible drivers rather than substitute for checking the underlying figures.
A useful explanation connects the movement to billing events or changes in customer activity. Research on ambiguity in natural language interfaces suggests that clarifying an ambiguous question before interpreting it can improve results. If “MRR” could mean different things in your reporting, define the metric and period before asking why it changed.
A solo founder might follow a reported drop with: “Which plan contributed most to the March decline, and was the change caused by cancellations, downgrades, or discounts?” That follow-up names the breakdown and the possible revenue movements. Check the answer against the underlying records before changing pricing. If paying customers fell, ask separately whether signups or conversions changed; those measures point to different parts of the funnel.
Treating explanations with discipline
After an explanation, ask a focused follow-up that names the plan, channel, or period. Compare the leading cause with the underlying data, and record unusual changes alongside causes you have confirmed. A short AI explanation can direct your investigation, but it is not definitive truth.
8. Recurring reporting questions for monthly reviews
One-off questions answer surprises. Recurring questions build a reporting habit you can compare over time.
Ask: "Summarize this month's MRR, churn, and new customers compared with last month." Run with identical wording each month, that question removes the repetitive work of rebuilding the same plan-level totals. Chartsy supports the routine through daily briefings, weekly email reports, and saved dashboards, so a consistent question gets reused on schedule instead of reinvented.
Say a bootstrapped founder receives a weekly email covering MRR movements and churn without opening a dashboard. She spots problems in minutes and digs deeper only when something moves. A fractional CFO sends each client a monthly summary built from the same saved questions, so every client sees consistent definitions and the CFO stops reformatting spreadsheets.
Building the habit
- Store your wording: Save exact question text so every month uses identical definitions.
- Add one question per quarter: Test a new hypothesis while keeping the core report stable.
- Verify your sources: Confirm every billing source appears in the report before sharing it externally.
What I'd do: Lock three core questions for a full quarter before adding more. Stability beats coverage when you're building a baseline.
The routine only works if definitions stay put. Change a metric definition mid-quarter and your trend line breaks, even if the new definition is better.
Natural Language Question Types for SaaS Data at a Glance
| Question focus | Primary metrics | Best for | Key tactic |
|---|---|---|---|
| Period-over-period revenue | MRR, ARR, active subscriptions | Spotting changes between time periods | Specify the metric and date ranges, then request a breakdown |
| Acquisition channels tied to paying customers | Paying customers, retained revenue by channel | Comparing which channels bring valuable customers | Compare first-touch and last-touch attribution |
| Revenue movement breakdown | New, expansion, contraction, and churned MRR | Finding what drives net revenue change | Ask for amounts and percentages, segmented by plan |
| Retention and cohorts | Cohort retention, lifetime value, subscription activity | Comparing customer retention over time | Compare cohorts over equal periods and check cohort size |
| Failed payments and billing events | Failed-payment impact on MRR, refunds, prorations | Identifying revenue at risk from billing issues | Separate failed payments from cancellations and confirm data is current |
| Plan and segment comparisons | Revenue and retention by plan, tag, or custom field | Evaluating pricing, packaging, and customer segments | Keep segment definitions stable and check sample sizes |
| Explanations for unexpected changes | Metric components, revenue movements, traffic, and signups | Investigating unexpected metric changes | Verify the suggested cause against underlying breakdowns |
| Recurring monthly reporting | MRR, churn, new customers | Standardizing regular reviews and summaries | Reuse consistent questions and periodically check data connections |
Turn These Questions Into Your Reporting Routine
The strongest results from these natural language examples don't come from clever phrasing. They come from specific wording, meaning a named metric plus an explicit time range, and from follow-up questions that drill into components instead of accepting a headline. A period comparison tells you what changed. A movement breakdown tells you which category drove it. A cohort or segment question tells you who it happened to. Each question type answers one layer, and stacking them in that order keeps you from jumping to conclusions.
Repetition does the rest. When you run the same question structures every week, your definitions stay stable and month-over-month comparisons stay honest. That's when a flat MRR number stops being a mystery, because you've already built the habit of asking what's moving underneath it.
Honesty about limits belongs in the routine too. Answer quality needs checking against semantic correctness and downstream decision usefulness, not just whether a response sounds plausible. Check the interpreted metric, the filters, and the date range before you act, and be careful with vendor claims while you're at it. The FTC advertising guidance states that advertising claims must be truthful, nondeceptive, and evidence-based, with a reasonable basis before they're made. Hold your own internal reporting to the same standard.
Tools like Chartsy are built for this workflow. Its dashboard chatbot answers plain-language questions about revenue and retention in real time, and a typed follow-up returns a chart with a one-sentence takeaway you can verify against the breakdown. Since the underlying models are general-purpose, we state plainly that output accuracy can vary and nothing returned should be taken as definitive truth. Use the explanation to aim your investigation, then confirm it.
Start small. Pick three of the eight question types, standardize their wording in writing, and run them as a weekly routine for a month. I recommend beginning with period comparisons, movement breakdowns, and failed payment questions, since those three explain most surprise dips. Add channel, cohort, and segment questions once the baseline feels solid, and keep one explanation question in reserve for the months when something moves and you don't know why.
Connect your Stripe, Paddle, or other billing source to Chartsy and ask your first three standardized revenue questions this week, using the exact wording patterns above. You'll get charts, movement breakdowns, and retention views from your issued invoices without writing SQL, plus weekly reports that keep the routine running.
Written by
Chartsy TeamAnalytics team at Chartsy
The Chartsy Team writes guides, product updates, and resources to help SaaS and eCommerce founders make sense of their metrics, without SQL or spreadsheets.
Chartsy
