Products & Services
Client Types
Company
MethodologyContact
Wysdome
Products & Services overviewMonarch AICustomer CubeData PackConsulting
Client Types overviewInvestment banksHedge fundsBoutique advisorsPrivate marketsCorporate DevelopmentLenders
Company overviewAboutSecurityCompliance
MethodologyContact
Get in touch
Get in touch

Turn customer revenue files into source-mapped, reviewable Wysdome evidence.

Get in touch

Customer-revenue analytics and diligence outputs for financial institutions.

© 2026 Wysdome LLC. All rights reserved.

Services

ServicesCustomer CubeData PackConsultingMonarch AI

Company

About UsSecurityComplianceFAQGlossaryDeal FitContact

Legal

PrivacyTerms of Service

Contact

Sales: sales@wysdome.comLegal: legal@wysdome.comSupport: support@wysdome.comPhone: +1 302 610 3055

Records

Founder profileBrokerCheck

Methodology

Reviewable metrics, not black-box diligence claims.

Wysdome outputs are built around agreed metric definitions, source mapping, and exception logs so the deal team can understand what changed, which customers drove it, and what data issues require follow-up.Request access

Metric definitions

Formulas stay explicit before the output becomes evidence.

Retention, concentration, LTV/CAC, cohort, and ARR movement views are only useful after the underlying customer, product, period, and source definitions are locked.

ARR bridge

Ending ARR = Beginning ARR + New logo ARR + Expansion ARR + Cross-sell ARR − Downsell ARR − Churned ARR. Beginning ARR plus new logo, expansion, and cross-sell ARR less downsell and churned ARR. Every movement is traced to a customer record, not estimated from aggregate ARR lines.

Gross revenue retention (GRR)

GRR = (Beg ARR − Downsell − Churn) ÷ Beg ARR. Retention views calculated from agreed customer cohorts and revenue definitions. GRR is capped at 100%; it excludes expansion to isolate base durability.

Net revenue retention (NRR)

NRR = (Beg ARR + Expansion + Cross-sell − Downsell − Churn) ÷ Beg ARR. NRR captures the full revenue movement from the existing customer base including upsell and cross-sell. Values above 100% indicate net expansion from the base.

Customer concentration

Concentration = Top N customer ARR ÷ Total ARR. Top customer contribution, account movement, and long-tail durability trends. Concentration analysis covers both revenue and logo-count exposure by tier.

LTV / CAC

LTV = ACV × Gross Margin ÷ Annual Customer Churn Rate | CAC Payback (months) = CAC ÷ (ACV × Gross Margin) × 12. Computed only where the client has reliable acquisition cost, gross margin, churn, and cohort data. Period conventions should stay consistent if monthly ARPA and monthly churn are used instead.

Cohort retention

Cohort retention(t) = Revenue(t) from cohort ÷ Revenue(0) from cohort. Tracks the revenue percentage retained from each customer cohort year over year. Output includes vintage analysis to compare cohort quality across acquisition periods.

ARR bridge — illustrative

ARR bridge visualized from customer-level movements.

Each bar represents a source-traceable ARR movement from the existing customer base or new logo acquisition. Actual figures depend on client data and agreed definitions.
01Beginning ARR02New logo ARR03Expansion ARR04Cross-sell ARR05Downsell ARR06Churned ARR07Ending ARR08Customer record trace

Source quality

The analysis is only as strong as the source hierarchy.

Source controls determine whether a metric can be trusted, qualified, or should remain an explicit follow-up item for the deal team.

Source checks

Customer identity matching across CRM, billing, ERP, GL, contract, and spreadsheet exports.

Product naming and SKU consistency before product-level revenue cuts are trusted.

Partial-period and fiscal-calendar handling for monthly, quarterly, and annual views.

Recurring versus non-recurring revenue flags when the source data supports them.

Metric definitions and source exceptions kept visible for deal-team review.

Definition governance

The controls behind a banker-grade data pack.

Before Wysdome surfaces retention, concentration, forecast support, or customer rankings, the underlying definitions need to be explicit enough for a deal team to challenge and defend.

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.

Professional boundary

Analytical support, not professional advice.

Wysdome provides analytics and diligence workflow support. Platform outputs are not investment, legal, tax, accounting, credit, valuation, or securities advice and should be reviewed by the client and its advisers.

Output role

AnalyticsDiligence workflow support built from source-mapped records.

Professional advice

NoNot investment, legal, tax, accounting, credit, valuation, or securities advice.

Review standard

RequiredOutputs should be reviewed by the client and its advisers.

Reliance basis

DefinitionsMetric assumptions and data caveats stay visible for challenge.