Import the files
CSV and Excel exports from the agreed source systems
Customer Cube
A clean customer-revenue workbook that shows where every number came from.
It matches customer records across files, checks totals against source systems, records definitions and exceptions, and keeps management answers and adjustments with the analysis.From files to analysis
Keep every result tied to the data and the people who explained it.
Wysdome connects the original files, customer matching, reconciliations, questions, management answers, adjustments, and final outputs.Match and reconcile
Customer identities, fields, definitions, exceptions, and totals
Ask and adjust
Management answers plus a record of every accepted change
Create the outputs
Customer Cube, analysis, charts, and PowerPoint Data Packs
What it brings together
A workbook built around the questions people ask about revenue.
Customer data, definitions, reconciliation notes, source problems, and approved changes stay together so the analysis can be reviewed and updated.Customer relationships
Match customer and parent-account records across systems so the same relationship is counted consistently.
Products and revenue
Connect products and revenue categories to agreed definitions without hiding missing or inconsistent fields.
Periods and cohorts
Apply consistent dates and cohort rules so growth, retention, expansion, and churn can be compared over time.
Segments and views
Organize the data by the geographies, channels, tiers, and other views that matter to the decision.
Source files
What the source files need to contain.
The work needs customer-level revenue history plus enough customer, product, date, and segment information to trace changes back to the original records.What to provide
Customer-level revenue history by month, quarter, or year
Customer identity fields that can support parent-child matching
Product or service-line identifiers tied to revenue where available
Contract, billing, renewal, and recurring-revenue fields if retention or ARR analysis is in scope
Management reporting definitions for revenue, ARR, MRR, bookings, churn, and expansion
Segment fields such as vertical, geography, channel, tier, size, or cohort
What Wysdome checks
Customer names line up across files, totals tie back to the source reports, and unclear records become questions instead of hidden assumptions. Approved answers and changes remain visible with the analysis.
Questions
What the workbook should help people understand.
01Which customers drove growth, expansion, contraction, and churn?02Is revenue broad-based or dependent on a few accounts?03Which products create cross-sell, renewal, or concentration risk?04Do projections reconcile to customer-level history?05Where are one-time revenue, credits, refunds, or services revenue affecting the story?06Which source-data exceptions need follow-up before buyer or committee review?
Definitions and matching
Most errors begin before the charts are made.
The hard part is matching the same customer across systems, agreeing what counts as revenue, handling exceptions, and applying the same period and cohort rules throughout.Customer hierarchy
Parent-child account matching, legal-entity names, customer IDs, duplicate accounts, and acquired customer mappings are documented before metrics are trusted.
Revenue definition
Revenue, ARR, MRR, bookings, billings, services, usage, refunds, credits, FX, and one-time items must be explicitly defined.
Cohort policy
Cohorts can be based on first purchase, subscription start, contract start, first invoice, or management-defined vintage; the chosen policy is disclosed.
Period logic
Calendar months, fiscal periods, LTM cuts, partial periods, renewal windows, and stub periods are aligned before trend analysis.
Source exceptions
Unmapped customers, duplicate products, missing renewal dates, inconsistent currency, and unreconciled totals are captured for review.
Client review
Outputs are analytical support. Deal teams and their advisers should review assumptions, definitions, and exceptions before relying on the pack.