MRR and churn tracking

ChartMogul calculates recurring revenue metrics such as MRR, ARR, and churn by combining data from a company's billing systems. A Beam agent reads these metrics on a schedule, compares them against the prior period, and updates a shared dashboard or summary once the numbers are confirmed consistent. It applies the variance rule a customer has approved, such as flagging any month where churn moves more than an agreed amount. When a metric shifts sharply or a billing source stops reporting data, the agent does not adjust the figures itself, it notifies finance so a person can investigate the cause.

Customer and plan segmentation

ChartMogul groups customers by plan, cohort, or segment so revenue can be analyzed by customer type. A Beam agent reads segment data when a new billing period closes, checks that customers are still classified under the correct plan or cohort, and updates a segment record where the classification has changed, such as an upgrade or downgrade. It follows only the segmentation rule already agreed with the customer. Where an account does not clearly fit an existing segment, or billing data looks incomplete, the agent leaves the classification open and routes the account to a person to confirm.

Revenue reconciliation across billing sources

Companies often connect more than one billing system to ChartMogul, and figures can drift apart if data does not sync cleanly. A Beam agent reads revenue totals from each connected source, compares them against the consolidated ChartMogul figure, and updates a reconciliation record once the totals match within the agreed tolerance. It flags any period where the numbers do not line up. Because a mismatch usually points to a billing error or a sync problem rather than a routine variance, the agent routes any unresolved discrepancy to finance instead of forcing the figures to agree.