> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/why-allocations/deal-setup.md). # Deal Setup Setup is where you configure a new deal before it goes to investors. You can complete its 10 sections in any order. ![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/S4iL2ioogNuQH3C0WxNL/Unknown%20image) 1. **Tab row** Moves between the deal's tabs, where Setup holds the configuration for the vehicle. 2. **Search sections** Jumps straight to a Setup section by typing its name. 3. **Section list** Lists the 10 Setup sections, each of which opens its own form. 4. **Complete deal basics** Tracks the eight deal basics and names the ones still outstanding. 5. **Tour banner** Offers a guided tour of Setup on a new deal, and returns as Take a tour at the top right once dismissed. 6. **Product Type** Shows whether the deal is a Standard SPV, Premium SPV, or Fund, with the asset types each one covers. 7. **Deal Info** Holds the deal economics that investors read on the Invest page. 8. **Edit** Opens all nine Deal Info fields for editing at once. ### The 10 sections Product Type and Deal Info are required, as shown by the marker on their headings. 1. **Product Type:** The required choice of Standard SPV, Premium SPV, or Fund. 2. **Deal Info:** The required economics and terms that investors read before committing. 3. **Data Room:** The gated materials investors can open once admitted. 4. **Fund Manager and Advisor:** The identities for the fund manager and advisor roles, which also completes the tracker's Identity item. 5. **Account:** The account the deal sits under, created beforehand in Accounts. 6. **Entity:** The legal vehicle that will be formed for the deal or attached to it. 7. **Assets:** What the deal buys, with at least one asset recorded before the vehicle can close. 8. **Legal Documents:** The subscription and operating documents generated for the deal. 9. **Banking Setup:** The banking provider and the compliance answers behind the account. 10. **Files:** The deal's own document store, separate from the investor facing Data Room. ### Product Type Setup offers the same three product types as the Create Deal dialog, described in **Creating a deal**. It also lists the asset types Premium SPV covers: secondary, SPV, fund, crypto, public company, acquisition, and football club. ### Deal Info Select **Edit** to change the nine Deal Info fields. Investors see these terms on the Invest page. * **Target Raise Amount:** The goal for the raise, shown in Raise progress on Overview. * **Estimated Closing Date:** The target close date, which sets the days remaining on Overview. * **Management Fee Percentage:** The fee percentage, read together with the frequency. * **Management Fee Frequency:** How often the fee is charged, where a value of none means a single charge. * **Minimum Investment Amount:** The minimum per investor, shown on the Invest page. * **Carry Percentage:** The carried interest percentage the manager earns on profits. * **Financial Statements:** How often statements are produced, with a note that extra charges may apply. * **Offering Type:** The exemption the raise relies on, such as 506c. * **Investor Type:** The class of investor eligible to invest, such as Accredited. ### The completion tracker Complete deal basics sits under the section list and also appears on Overview. > **Follow the arrow on a tracker item to open the right section.** Some items are completed in a section with a different name. For example, the Identity item is completed in Fund Manager and Advisor. --- # 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.allocations.com/why-allocations/deal-setup.md?ask=&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.