Which parts of growth are recurring, concentrated or temporary?
A founder sees $126,000 in sample monthly revenue, then checks whether a large annual invoice explains part of the change before extrapolating it.
Explore the sample companyRevenue
Separate growth, concentration, refunds, billing timing, and collection context in normalized revenue views.
SalesSample company
Invoice INV-1042
Customer invoiceDraft
Sent
Paid
Payment recorded from external evidence
$12,000INV-1043
Needs a closer look
Which parts of growth are recurring, concentrated or temporary?
Top-line growth can hide concentration, billing timing, collection delays, refunds, and the gap between operating records and accounting evidence.
- MRR
- Monthly recurring revenue: subscription revenue expressed on a monthly basis, excluding one-time revenue under the applicable definition.
- What it works with
- Supported normalized revenue, subscription, refund and customer context; field coverage depends on the source.
- What you get
- An operating analysis that helps separate repeatable patterns from timing effects or large one-off items.
How the work progresses
Who uses it
Business owners and finance teams examining revenue, customer balances and collection context.
- Confirm the source coverage and the revenue measure being reviewed.
- Inspect customer, subscription, refund or billing context where supported.
- Separate recurring patterns from exceptional items and use a separate accounting process for recognition policy.
A concrete example
Illustrative, not customer data.
What still needs judgment
Available fields vary by source. Revenue analysis does not determine revenue-recognition policy, collect money, infer missing FX, or replace qualified accounting review.
AI can explain revenue and collection patterns or draft follow-up language. It cannot recognize revenue, approve allocations, post journals, or collect money.
Available workflows depend on your plan, permission scope, configuration and supported data. Compare plans before choosing.
Before you use revenue
Can I explore this before connecting company data?
The public demo is a fixed, read-only sample company. It illustrates supported product areas without creating an account or accessing customer data; it is not proof that every configured workflow is available in the tour.
What should I verify before relying on an output?
Confirm scope, source coverage and timing. For this capability, review supported normalized revenue, subscription, refund and customer context; field coverage depends on the source. An operating status or AI explanation does not replace the required review of accounting evidence.
Does an explanation automatically authorize a financial action?
No. AI can explain revenue and collection patterns or draft follow-up language. It cannot recognize revenue, approve allocations, post journals, or collect money.
Continue the workflow
See the work in context.
Explore a read-only sample company, or start with your own supported data.