> 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/portfolio-construction/faqs/setting-exit-multiples-directly.md).

# Setting exit multiples directly

GPs that are used to deterministic Excel based models where may want to just set a fixed Exit multiple, and forecast fund performance based on this number. There’s a few reasons why we don’t support this methodology.

{% hint style="info" %}
We want to emphasize there is no ***right*** or ***wrong*** way to do portfolio construction. There are only approaches that are flexible and inflexible. A flexible approach has the advantage of giving the GP multiple levers to pull to run varied construction strategies.
{% endhint %}

## **The problem with setting an exit multiple is:**

* It hides away a market dynamics i.e. what are the actual valuation step-ups in the market? By sector or by geography?
* It hides away probability of early exits at lower multiples.
* It hides away impact of follow-ons, which frequently end up reducing the exit multiple.
* The final power law curve for the fund is an input, not an output.

In Tactyc we **build up to the exit multiple** from more granular assumptions such as graduation rates, exit rates, valuations. At each round, we want you to consider what the average valuations look like (based on market data), how many companies make it to that round and how many companies exit. This is frequently informed by the performance of your past funds + market benchmarks.

<figure><img src="https://1366836623-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWOWjDH33JGp4Ay1omBCB%2Fuploads%2FXQJ6TmIe3kVYPltKi9X4%2Fimage.png?alt=media&amp;token=6145e841-73e9-4c65-b204-0a90865a8331" alt=""><figcaption></figcaption></figure>

We also take into account your follow-on investments to determine what the expected MOIC looks like. Tactyc puts it all together to calculate the expected exit MOIC in for each of your allocation.

<figure><img src="https://1366836623-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWOWjDH33JGp4Ay1omBCB%2Fuploads%2FXZMo1sUhZSheVsoBgEdY%2Fimage.png?alt=media&amp;token=6de51819-f075-49c8-86e7-cb2a856dfc0b" alt=""><figcaption></figcaption></figure>

While this approach requires a bit more thought than plugging an exit multiple, it results in a model that:

* is more defensible to LPs as its supported by actual market data and your investment strategy
* later in your fund’s life, it enables you to see ***where you are going wrong*** i.e. did you assume the wrong graduation rates, investment levels or market valuations? It enables you to better course correct your fund strategy.


---

# 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/portfolio-construction/faqs/setting-exit-multiples-directly.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.
