> 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/construction-wizard.md).

# Construction Wizard

There are 7 sections in the *Construction Wizard:*

* [General Section](/portfolio-construction/construction-wizard/general.md) is where managers define their fund start date, currencies, expected commitments
* [Sector Profiles](/portfolio-construction/construction-wizard/sector-profiles.md) section where you can define the round sizes and valuations for sectors you’re investing in
* [Allocations](/portfolio-construction/construction-wizard/allocations.md) section is where you define the types of investments (Pre-Seed, Seed, Series A) the fund will make, estimated check sizes and follow-on strategies
* [Fees and Expenses](/portfolio-construction/construction-wizard/fees-and-expenses.md) for management fees and fund expenses
* [Exit Recycling](/portfolio-construction/construction-wizard/exit-recycling.md) (optional) for optional exit proceeds recycling
* [Waterfall](/portfolio-construction/construction-wizard/waterfall.md) for hurdle rates, carried interest (%)
* [Limited Partners](/portfolio-construction/construction-wizard/limited-partners.md) (optional) is where you define the LP contributions for each individual LP


---

# 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/construction-wizard.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.