> For the complete documentation index, see [llms.txt](https://docs.morevy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morevy.ai/readme.md).

# What's Morevy

**Close your books on recurring revenue, from a file you already have.**

Export your payment history, answer three questions about it, and receive a monthly close that reconciles: opening balance, revenue gained, revenue lost, closing balance, and the customers behind every figure.

<a href="https://docs.morevy.ai/docs/getting-started/export-your-payments" class="button primary" data-icon="rocket-launch">Get started</a> <a href="https://docs.morevy.ai/docs/how-the-numbers-work/cash-vs-recurring-revenue" class="button secondary" data-icon="scale-balanced">How the numbers work</a>

***

## Who it is for

Businesses billing customers on a repeating basis, where payment history is the most complete record available.

Fitness and wellness operators, clinics, coworking, membership clubs, subscription products. The industry matters less than the shape: revenue that repeats, a portion of it prepaid, and no dedicated finance function to reconcile it.

***

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-file-arrow-up">:file-arrow-up:</i></td><td><strong>One file in</strong></td><td>A payment export identifying who paid, when, and how much.</td><td><a href="https://docs.morevy.ai/docs/getting-started/export-your-payments">https://docs.morevy.ai/docs/getting-started/export-your-payments</a></td></tr><tr><td><i class="fa-calculator">:calculator:</i></td><td><strong>A close that reconciles</strong></td><td>Opening balance plus every movement equals closing, verified rather than asserted.</td><td><a href="https://docs.morevy.ai/docs/running-a-close/reading-the-revenue-movement">https://docs.morevy.ai/docs/running-a-close/reading-the-revenue-movement</a></td></tr><tr><td><i class="fa-users">:users:</i></td><td><strong>Traceable to customers</strong></td><td>Every figure opens to the individual accounts within it.</td><td><a href="https://docs.morevy.ai/docs/running-a-close/finding-the-members-behind-a-figure">https://docs.morevy.ai/docs/running-a-close/finding-the-members-behind-a-figure</a></td></tr><tr><td><i class="fa-fingerprint">:fingerprint:</i></td><td><strong>Nothing inferred</strong></td><td>Figures are computed from your data. Where a result cannot be verified, nothing is displayed.</td><td><a href="https://docs.morevy.ai/docs/how-the-numbers-work/where-every-figure-comes-from">https://docs.morevy.ai/docs/how-the-numbers-work/where-every-figure-comes-from</a></td></tr></tbody></table>

***

{% columns %}
{% column width="50%" %}

## The problem it addresses

A customer pays **$600 in January** for a three month plan.

Did the business earn $600 in January, or $200 per month across three months?

Both are correct, and they answer different questions. Reading only one is how a promotion-heavy month is mistaken for growth, or genuine growth is missed entirely.

|                       | January | February | March |
| --------------------- | ------- | -------- | ----- |
| **Cash collected**    | $600    |          |       |
| **Recurring revenue** | $200    | $200     | $200  |

Morevy requires you to state which question you are asking, and reports which basis every figure answers.

<a href="https://docs.morevy.ai/docs/how-the-numbers-work/cash-vs-recurring-revenue" class="button secondary" data-icon="scale-balanced">Full explanation</a>
{% endcolumn %}

{% column width="50%" %}

## How a close proceeds

```mermaid
flowchart TD
    A["Export payments"] --> B["Confirm three inputs"]
    B --> C["Request a period"]
    C --> D["Opening balance"]
    D --> E["New, returned, expanded"]
    E --> F["Contracted, lost"]
    F --> G["Closing balance"]
    G --> H{"Reconciles?"}
    H -->|yes| I["Reported"]
    H -->|no| J["Variance reported<br/>with its amount"]
```

Where the classification of your data is unconfirmed, the close does not proceed.
{% endcolumn %}
{% endcolumns %}

***

## Design principles

{% hint style="info" %}
**No figure is displayed unless it has been computed and verified.**

The assistant determines what to present and how to explain it. It does not produce the figures. Computed values are supplied by the calculation engine and verified before display; where no verified result exists, nothing is rendered in its place.
{% endhint %}

|                                     |                                                                                                                                                                     |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Declines rather than estimates**  | Where recurring revenue is undefined for a dataset, the close does not proceed. An unsubstantiated figure is less useful than none.                                 |
| **Reconciliation is graded**        | Amounts, customer counts, row coverage and classification are assessed and reported independently. An unmeasured dimension is reported as unknown, never as a pass. |
| **Ratios withheld where undefined** | Revenue retention has no valid definition on a cash basis and is reported as unavailable, with the basis that would support it named.                               |
| **Revisable inputs**                | Changing an input produces a new version and a statement of what moved. Displayed figures are not silently revised.                                                 |

***

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-book">:book:</i></td><td><strong>Documentation</strong></td><td>Getting started, running a close, and how the figures are produced.</td><td><a href="https://docs.morevy.ai/docs/">https://docs.morevy.ai/docs/</a></td></tr><tr><td><i class="fa-circle-info">:circle-info:</i></td><td><strong>Scope and limitations</strong></td><td>What Morevy covers, and what falls outside it.</td><td><a href="https://docs.morevy.ai/docs/reference/what-morevy-doesnt-do-yet">https://docs.morevy.ai/docs/reference/what-morevy-doesnt-do-yet</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.morevy.ai/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
