Source intake
CRM, billing, contract, ERP, and forecast exports

Monarch AI
Infrastructure
CRM, billing, contract, ERP, and forecast exports
Account, product, period, cohort, segment, and geography
Customer Cube schedules and Data Pack chart pages
Definitions, caveats, exception log, and consulting escalation
Builder
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.Customer CubeData PackException LogInputs stay tied to customer records and source exceptions.
Cube and Data Pack patterns repeat across transactions.
Definitions, caveats, and boundaries stay visible.
Commercial interpretation is separated from standard analytics.
Operational view
Access model
AutomatedRepeatable Wysdome analyticsSource systems
6+CRM, billing, ERP, GL, contractsCore outputs
Cube + PackExcel and PPTX deliverablesConsulting
SeparateCommercial guidance when scopedWorkflow
CRM, billing, ERP, GL, contract, forecast, and spreadsheet extracts are reviewed for fields, grain, date logic, and source conflicts.
Customer, product, period, geography, vertical, channel, and cohort dimensions are mapped into one reviewable model.
Upsell, downsell, churn, cross-sell, retention, LTV/CAC, concentration, forecast, and anomaly signals are ranked for review.
IC-ready exhibits, buyer Q&A schedules, trend tables, customer cuts, and source exception logs are exported.
Data readiness
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
Salesforce, HubSpot, opportunity/account exports, customer owner files, pipeline snapshots, and segment fields.
Stripe, Zuora, Chargebee, invoice exports, ARR/MRR schedules, renewal tables, and usage billing files.
NetSuite, SAP, GL exports, revenue reports, customer revenue by period, product revenue, and management reporting files.
Excel, CSV, TSV, and structured spreadsheet exports with stable customer IDs, dates, product fields, and amounts.
Contract metadata tables, renewal schedules, commercial-term tables, budget files, and forecast workbooks.
Scanned PDFs, screenshots, unstructured email threads, images of tables, payment card data, tax IDs, SSNs, and files without customer-level grain.
Diligence signals
Whitespace, attach rate, product adjacency, customer tier, and segment-level expansion signals.
Customer-level contraction, logo churn, revenue churn, cohort decay, renewal exposure, and churn watchlists.
Gross retention, net retention, cohort quality, CAC payback, and lifetime value diagnostics where inputs support the calculations.
Monthly, quarterly, and yearly forecast support by customer, product, cohort, segment, and scenario.
Geography, vertical, channel, product, customer tier, cohort, renewal window, and customer-size slices.
Concentration, contribution, trend direction, volatility, anomaly ranking, and follow-up question generation.
Outputs
QA and boundaries
Confirm file inventory, date ranges, customer IDs, product fields, currency fields, and required metric definitions.
Compare cube totals to source exports and management reporting. Reconciled means totals tie within agreed tolerance or exceptions are documented.
Surface unmapped customers, duplicates, missing dates, unsupported recurring flags, inconsistent product names, and currency issues.
Before final delivery, the client reviews definitions, major exceptions, period logic, and source hierarchy assumptions.
Check file names, version numbers, formulas, PDF exhibits, tab order, source references, and revision history.
AI may assist with anomaly flagging, draft buyer questions, field classification, and documentation where permitted.
AI does not make investment, credit, valuation, legal, tax, accounting, or securities recommendations.
Human review is required before output delivery.
Source data and formulas remain reviewable; AI output is not treated as authoritative.
Wysdome's default policy is not to use client data or transaction outputs for model training; engagement-specific AI/API terms may be reviewed and approved in writing.
Monarch AI is the automated route into Wysdome outputs; consulting and custom commercial guidance are scoped separately.
Wysdome provides analytics and diligence workflow support, not investment, legal, tax, accounting, credit, valuation, or securities advice.
Metrics are source-mapped where client data supports them; incomplete or conflicting data is documented through exceptions.
Public email is for non-confidential qualification only. Sensitive files require an agreed intake process.