> For the complete documentation index, see [llms.txt](https://docs.tactyc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tactyc.io/insights/optimal-reserves-ranking.md).

# Optimal Reserves Ranking

Tactyc helps fund managers optimize follow-on reserves by ranking each portfolio company based on the opportunity cost of investment.

## Expected MOIC on Planned Reserves

By default Tactyc automatically calculates **Exit MOIC on Planned Reserves** - this is the expected return on the next $1 into each company. Tactyc determines this multiple based on the deal-level forecasts for exits, future financing rounds and performance cases. 

[Learn more here](https://blog.tactyc.io/leveling-up-on-moic-analysis) for the various MOIC analysis in Tactyc.

## Optimal Reserves

Under **Insights > Optimal Reserves Ranking,** Tactyc will then automatically rank each portfolio company based on this **"follow-on multiple".** This chart will also show the current planned and deployed reserves for each portfolio company.

<figure><img src="https://1366836623-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWOWjDH33JGp4Ay1omBCB%2Fuploads%2Fa5ijuxKC7EvBPb54tsKs%2FScreenshot%202024-03-27%20at%202.15.33%20PM.png?alt=media&amp;token=19875a28-deda-487d-a8fc-6420b7c6f20d" alt=""><figcaption></figcaption></figure>

##


---

# 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://docs.tactyc.io/insights/optimal-reserves-ranking.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.