MRR Pulse
Understand recurring revenue movement without losing the underlying evidence.
Understand recurring revenue movement without losing the underlying evidence.
What this feature is for
MRR Pulse summarizes live MRR, churn, and forecast signals from the connected revenue source. It is a decision view for trend, not a replacement for a ledger. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
A connected Stripe account, consistent customer and subscription mapping, and enough history for a useful comparison period.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Review the current period, compare movement to the previous period, inspect churn or new revenue changes, and drill into the source snapshot before acting.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
The pulse should show period, currency, observed MRR, movement, and freshness so a team can tell current data from stale data. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
If the chart jumps unexpectedly, check imports, currency, subscription status mapping, and the last successful sync before changing pricing conclusions.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use MRR Pulse with Payment Sync and Activity to connect commercial movement to operational events. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.