# Morevy

> Morevy is recurring-revenue analysis software for finance owners and fractional CFOs. It computes monthly MRR and ARR movement from revenue data, shows the customers and records behind each change, and writes commentary only from checked figures. Its line is "Computed. Checked. Explained.": a conversational analyst that turns subscription billing data into revenue waterfalls, formula-driven models, and a written read, or tells you when it can't. Every figure is computed by a deterministic engine, checked, and carries the customers and the calculation behind it. Business context is kept as rulings and reused, and every export ends with a record of what was computed, what was withheld, and why.

**Product context**

- Category: recurring-revenue analysis software (slogan: Computed. Checked. Explained.). It sits on top of the billing system and the finance stack; it is not a system of record, a general ledger, or a BI dashboard.
- Audience: the person accountable for explaining recurring revenue to a board or to clients: in-house finance owners and fractional CFOs of subscription businesses.
- Status: private beta. Early access is opening in small cohorts.
- Product surface: web application at [app.morevy.ai](https://app.morevy.ai) with public documentation at [morevy.ai/docs](https://morevy.ai/docs/introduction). Data comes in through a Stripe connection or a file export from any billing system.
- Contact: [hello@morevy.ai](mailto:hello@morevy.ai).
- The roadmap page at [morevy.ai/roadmap](https://morevy.ai/roadmap) is the canonical status list. A feature not listed there as live is not available; entries marked in progress or planned are not dated and are not commitments.

**Vocabulary**

Inside the product, a "close" is a month whose figures have been computed, checked and signed off on the record. It is not a general-ledger close, revenue-recognition system, bookkeeping service, tax tool, or audit. "Checks" are the per-figure tests the engine runs before a figure renders (amounts, customer counts, source coverage, classification completeness, provenance); a figure that has no honest version on the reporting basis in use is withheld and named, not estimated.

**Reporting basis**

Morevy starts from customer-level billing or payment activity. The reporting basis is identified explicitly because invoices, cash collections, subscription status, and GAAP-recognized revenue are not interchangeable. Results depend on the completeness of the supplied data, the selected definitions, and the rulings you approve.

**Calculations and AI**

Recurring-revenue calculations, checks and models are deterministic under the selected reporting basis and your rulings. AI writes the read and answers questions from the computed output; it does not resolve ambiguous classifications or serve as the source of financial figures. Definitions, assumptions, exceptions, and reviewer judgment stay visible.

**Capabilities**

- Ask about any figure in plain words. Answers are computed by the engine, with the customers and the calculation behind them, or the analyst says the answer cannot be supported.
- Revenue waterfall (the ARR bridge): starting recurring revenue to ending, through who started paying, paid more, paid less, stopped paying, or came back, by segment. Named customers behind every leg, and each leg total ties to them.
- Customers, segments and cohorts: segments crossed two ways, cohort retention curves, gross and net revenue retention with the prior period beside each. Retention ratios are withheld on a cash basis when the data cannot support them.
- Checks on every figure, and rulings (plan lengths, scope, basis) kept and reused month to month.
- A written read after each month, and a client-review brief composed from the engine, printable or saved as PDF, marked draft until it is signed off.
- Exports: a close workbook, and a formula-driven financial model seeded from closed months when the history supports one.
- The record on every export: the source, the basis, the checks, what was withheld, the rulings applied and by whom, and the calculation version.

Movement legs are named for the direction of collected cash, which the computation supports, rather than for contract events it cannot observe. The legs are New, Returned, Growth, Contraction, Unchanged, and Lost, between a Starting and an Ending balance. Growth and Contraction mean a customer paid more or less than the prior period; they are not upgrades or downgrades. Lost means an absence of payment, which is not a cancellation. Where billing activity alone cannot establish commercial intent, Morevy presents the case for review rather than silently assigning a definitive label.

**Limitations**

- Morevy identifies measured revenue contributors. It does not infer why a customer expanded, contracted, or stopped paying from billing activity alone. Causal explanations require additional business context.
- Morevy does not treat cash collections as GAAP-recognized revenue or perform a general-ledger, bookkeeping, tax, or audit close.
- Morevy does not combine currencies without an explicit conversion policy and rate. Mixed-currency data is flagged for review rather than silently summed.
- Morevy does not silently resolve ambiguous classifications or conflicting records. Recorded assumptions and unresolved decisions remain explicit.
- Stripe is the only direct connector today; every other system comes in as a file export.

**Product identity**

Morevy evolved from work that began with Jetti Sheets. Jetti at [jetti.com](https://jetti.com) is separate software focused on reporting and retention for gyms and studios. Jetti pages should not be used as evidence for Morevy's features, audience, pricing, or availability.

## Product and access

- [Morevy home](https://morevy.ai/): Product overview, what is built in, and private-beta access.
- [Features](https://morevy.ai/features): How the system works: the engine computes the revenue waterfall and who drove it, five checks on every figure, the AI writes the read from checked figures, and your rulings are kept and reused.
- [Product documentation](https://morevy.ai/docs/introduction): Detailed guidance on preparing, running, and reviewing a month.
- [Roadmap](https://morevy.ai/roadmap): What is live in Morevy today, what is being built, and what comes next, grouped as Computed, Checked and Explained.
- [Join the waitlist](https://morevy.ai/get-started): Request access to a future private-beta cohort.

## Guides

- [Guides index](https://morevy.ai/guides): All Morevy guides to recurring-revenue measurement and reporting.
- [Recurring Revenue Analysis: The Complete Guide for Finance Teams](https://morevy.ai/guides/recurring-revenue-analysis): How to define the basis, calculate MRR and ARR, reconcile the movement bridge, and trace every change to the customers and source records behind it.
- [The Complete SaaS Revenue and Growth Metrics Guide](https://morevy.ai/guides/saas-revenue-metrics): Definitions and formulas for MRR, ARR, NRR, churn, customer lifetime value, and customer acquisition cost.
- [How to Automate SaaS Revenue Categorization Logic](https://morevy.ai/guides/automate-revenue-categorization): A rule-based approach to classifying recurring-revenue movements and testing whether opening revenue plus movements equals ending revenue.
- [The Recurring-Revenue Close](https://morevy.ai/guides/recurring-revenue-close): What a monthly close of recurring revenue is, its five steps, and what makes one hold up under questioning.
- [Getting your data out of Stripe](https://morevy.ai/guides/export-stripe-data): Five routes out of Stripe, three traps that quietly truncate history, and which route fits the job.

## Getting started

- [Connecting Stripe](https://morevy.ai/docs/connecting-stripe): The restricted, read-only API key that lets Morevy pull payment history directly, and what the connection cannot do.
- [Export your payments](https://morevy.ai/docs/export-your-payments): The source fields and export preparation needed before running an analysis.
- [The three questions](https://morevy.ai/docs/the-three-questions): The reporting-basis and policy decisions Morevy asks before calculating recurring-revenue movement.
- [Your first monthly review](https://morevy.ai/docs/your-first-monthly-review): How to create and review a first month from an export.

## Running a month

- [What you can ask](https://morevy.ai/docs/what-you-can-ask): Questions Morevy can answer from the supplied data and questions that require additional context.
- [Reading the revenue movement](https://morevy.ai/docs/reading-the-revenue-movement): How opening revenue, classified movements, and ending revenue relate.
- [Breaking a month down](https://morevy.ai/docs/breaking-a-month-down): How to inspect the accounts and available segments contributing to a reported movement.
- [When Morevy stops to ask](https://morevy.ai/docs/when-morevy-stops-to-ask): The exceptions and ambiguous cases that require a reviewer decision.

## How the numbers work

- [Cash vs recurring revenue](https://morevy.ai/docs/cash-vs-recurring-revenue): Why collections, billing activity, recurring revenue, and recognized revenue are different measures.
- [Where every figure comes from](https://morevy.ai/docs/where-every-figure-comes-from): How calculated movements link to source records, customer activity, and applied rules.
- [Retention and churn](https://morevy.ai/docs/retention-and-churn): How retention and churn are defined under the selected reporting basis and policy.
- [What reconciled actually means](https://morevy.ai/docs/what-reconciled-actually-means): The tie-out, coverage, and exception checks behind a checked result.

## Reference

- [Glossary](https://morevy.ai/docs/glossary): Definitions for recurring-revenue, movement, evidence, review, and policy terminology.
- [Scope and limitations](https://morevy.ai/docs/scope-and-limitations): Product boundaries, data requirements, unsupported inferences, and known limitations.
- [Troubleshooting](https://morevy.ai/docs/troubleshooting): Guidance for export, mapping, check, and review issues.
- [Data handling and privacy](https://morevy.ai/docs/data-handling-and-privacy): How Morevy handles uploaded data and protects customer information.

## Optional

- [About Morevy](https://morevy.ai/about): Company background and the principles behind source-backed recurring-revenue explanation.
- [Morevy blog](https://morevy.ai/blog): Articles about recurring-revenue measurement, reporting, review, and explanation.
- [Why Defensible Revenue Reporting Requires Human Judgment](https://morevy.ai/blog/defensible-revenue-reporting): Why source evidence, visible exceptions, and reviewer judgment matter in recurring-revenue reporting.
- [From MRR Bridges to Narrative Drivers](https://morevy.ai/blog/narrative-drivers-revenue-analysis): Why a reconciled MRR bridge explains measured movement but not necessarily its business causes.
- [Monthly Recurring Revenue (MRR): Formula, Movements, and How to Reconcile It](https://morevy.ai/blog/monthly-recurring-revenue): What MRR is, how to calculate it consistently, and how to reconcile every movement from opening to ending MRR.
- [Getting help](https://morevy.ai/docs/getting-help): Support and contact information for Morevy users.