Source intake
CRM, billing, contract, ERP, and forecast exports
Customer Cube
A segmented Excel deliverable for M&A diligence teams reviewing customer revenue.
A source-mapped workbook that organizes revenue by customer, product, period, cohort, geography, segment, and other reviewable deal-team cuts.Infrastructure
A governed stack for repeatable customer-revenue analytics.
Wysdome separates source intake, mapping, output generation, and professional review so each step can be inspected before a deal team relies on the final deliverable.Customer mapping
Account, product, period, cohort, segment, and geography
Output generation
Customer Cube schedules and Data Pack chart pages
Review controls
Definitions, caveats, exception log, and consulting escalation
Cube structure
Built around the customer-level questions buyers actually ask.
The Customer Cube is not a screenshot deck. It is a workbook structure that keeps definitions, reconciliation notes, and source exceptions visible.Customer
Account, parent account, customer ID, logo, buying group, or buyer-defined customer hierarchy with explicit matching rules.
Product
SKU, module, service line, contract line, bundle, product family, or revenue category tied to the source hierarchy where available.
Period
Monthly, quarterly, fiscal-year, and LTM views reconciled to billing, revenue, ARR/MRR, or management reporting definitions.
Cuts
Geography, vertical, cohort, segment, channel, contract type, customer tier, customer size, and renewal window.
Builder
An end-to-end workflow for financial-institution revenue evidence.
The platform route is not a generic dashboard. It is a controlled path from files to reviewable transaction outputs.source_pipeline.ts
const sourceFiles = intake.crm + intake.billing;const customerMap = reconcile(sourceFiles);return generateCube(customerMap, definitions);Monarch AI
Evidence BuilderDescribe the output, source systems, required definitions, and review constraints.Generate cube, Data Pack, and exception log...
task preview
Customer CubeData PackException LogSource-mapped
Inputs stay tied to customer records and source exceptions.
Reusable outputs
Cube and Data Pack patterns repeat across transactions.
Governed review
Definitions, caveats, and boundaries stay visible.
Scoped consulting
Commercial interpretation is separated from standard analytics.
Workbook evidence
Illustrative review exhibits stay tied to the cube structure.
These views are examples of the evidence layer the workbook supports. Actual tabs and numbers depend on agreed source files, definitions, and the diligence questions in scope.Output
XLSXSegmented Excel workbookCore use
M&AStandard customer deliverableAlso useful for
Pre-M&AClient-base analysisSource checks
VisibleDefinitions and exceptionsRequired source fields
The Excel cube is only as strong as the source hierarchy.
Wysdome is most useful when the client can provide customer-level revenue history and enough identity, product, date, and segment fields to connect revenue movements back to source records.Minimum useful inputs
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
Customer
Account, parent account, customer ID, logo, buying group, or buyer-defined customer hierarchy with explicit matching rules.
Product
SKU, module, service line, contract line, bundle, product family, or revenue category tied to the source hierarchy where available.
Period
Monthly, quarterly, fiscal-year, and LTM views reconciled to billing, revenue, ARR/MRR, or management reporting definitions.
Cuts
Geography, vertical, cohort, segment, channel, contract type, customer tier, customer size, and renewal window.
Diligence use
The questions the Customer Cube is built to answer.
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?
Definition governance
Where diligence quality usually breaks.
Customer Cube work is not a dashboard exercise. The hard part is making account matching, revenue definitions, cohort logic, source exceptions, and period cuts visible enough for a deal team to review.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.