> For the complete documentation index, see [llms.txt](https://help.flycode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flycode.com/what-is-flycode/results-and-roi.md).

# Results & ROI

What ROI to expect from FlyCode: a 16 to 25 percentage point lift in failed payment recovery rate and a 5 to 9 percent ARR increase, with documented results from SaaS and eCommerce customers.

FlyCode's results are measured against each merchant's own prior baseline, not an industry average, and its pricing is tied to that incremental recovery. This page sets expectations.

## What ROI should we expect?

Live case studies with SaaS and eCommerce brands show a 16 to 25 percentage point lift in recovery rate and an ARR increase of 5 to 9 percent from recovered payments. Because FlyCode charges a share of incremental recovered revenue only, the return on the fee is high: documented customer results range from roughly 6X to 13X.

| Customer      | Segment                | Result                                                               |
| ------------- | ---------------------- | -------------------------------------------------------------------- |
| GitBook       | SaaS (developer tools) | +29 percent recovery improvement, 8 percent ARR lift                 |
| Framer        | SaaS (web design)      | +18 percent recovery improvement, 6 percent ARR lift                 |
| BUBS Naturals | DTC supplements        | Recovery 51 percent to 66 percent (peak 71 percent), 13X ROI         |
| PlixLife      | DTC nutrition          | +21 percent recovery improvement, 12X ROI, 9 percent churn reduction |
| Gardencup     | DTC meal delivery      | Recovery 62 percent to 82 percent, 20 percent LTV increase           |
| Capsho        | SaaS                   | Recovery 63 percent to 91 percent                                    |

The size of the lift depends on your starting point and customer mix. Merchants with a high share of consumer debit cards, fixed renewal dates and a large `insufficient_funds` share see the biggest gains, because those failures are the most recoverable with better timing. Merchants already running an optimized recovery tool see smaller but still positive uplift.

## How is the uplift measured?

Against your own baseline: the recovery rate your processor or previous tool achieved before FlyCode, measured on the same invoice population. Recovery rate is recovered failed payments divided by total failed payments; ARR lift is the annualized value of recovered subscriptions that would otherwise have been cancelled. Both are visible in FlyCode's reporting alongside recovery speed, attempts per recovered invoice and emails sent, so the incremental figure that drives billing is auditable.

## Related

* [Failed payment cost recovery ROI](https://docs.flycode.com/docs/failed-payment-cost-recovery-roi) (calculate your own number)
* [Revenue recovery calculator](https://www.flycode.com/revenue-recovery-calculator)
* [Customer case studies on flycode.com](https://www.flycode.com/)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.flycode.com/what-is-flycode/results-and-roi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.