Walk back how your KPIs are populated — validating every checkpoint the data passes through, from the dashboard metric all the way to the source event.
Pulls from a scheduled query or direct SFDC report. SUM(MRR) × 12 across all active subscriptions.
Is this a live query or a cached snapshot? Does the refresh cadence match decision-making timelines?
Field mapping: dashboard.arr = sfdc_report.total_mrr * 12. Check: does the report include churned accounts still marked active?
Opportunities with Stage = Closed Won, Amount field, Close Date, Subscription Start/End dates, linked to Accounts.
Is Amount the annual value or monthly? Are multi-year deals handled correctly? Is there a recurring revenue field vs. one-time?
Fields: Opportunity.Amount, Opportunity.StageName, Opportunity.CloseDate, Opportunity.Subscription_MRR__c. Filter: Stage = "Closed Won" AND Type != "One-Time".
Subscription objects with status, plan, MRR, billing cycle, next renewal date. This is the billing source of truth.
Does subscription MRR in Chargebee match what SFDC says? Are trial/free plans excluded? Are downgrades reflected?
Chargebee fields: subscription.mrr, subscription.status = active, subscription.plan_id. Compare: SUM(chargebee.mrr) vs SUM(sfdc.Subscription_MRR__c).
When a subscription is created/updated in Chargebee, a sync job pushes data to SFDC. This creates or updates the Opportunity and sets MRR fields.
What triggers the sync? Is it real-time or batched? What fields get mapped? What happens on subscription change (upgrade/downgrade/cancel)?
Sync mapping: chargebee.subscription.mrr → sfdc.Opportunity.Subscription_MRR__c. Trigger: subscription_created, subscription_changed, subscription_cancelled webhooks.
Actual charges, invoices, payment status. This is the money-truth — did the customer actually pay?
Are there subscriptions in Chargebee marked "active" but with failed payments in Stripe? Is dunning working?
Stripe fields: charge.status = succeeded, invoice.status = paid, subscription.status. Compare active subs in Chargebee vs. successfully billing subs in Stripe.
The original event — a customer signed up via the product, or a contract was executed via DocuSign, or a sales rep manually created the opp.
Is every subscription traceable to an originating event? Are there orphan subscriptions with no clear origin?
Trace: DocuSign envelope → SFDC Opp created (automation) → Chargebee subscription created (webhook) → Stripe payment initiated. Check for leaks at each handoff.
Begin with the number executives see. What does the dashboard say? Where does that value live? What object or field is it pulling from?
Walk backward through every system, sync, automation, and manual process that touches the data. Document the field mappings, triggers, and logic at each layer.
At each checkpoint, mark it validated, warning, or broken. If any layer has gaps, bad logic, or stale data — the KPI above it is unreliable. Fix the chain.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
