> 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/creating-a-deal.md).

# Creating a deal

Creating a deal takes three fields in one dialog: the product type, a deal name investors will recognize, and an optional phone number. Decide the product type first, because it sets how many assets the vehicle can hold and how many times it can close.

To start, select **Create Deal** on the Deals page, beside Export.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/LthyJGqTJcLcJOi44XhC/Unknown%20image)

1. **Product Type:** Choose Standard SPV, Premium SPV, or Fund, which sets how many assets and closes the vehicle allows.
2. **Pricing and fees:** Links to the price list for each product type.
3. **Deal Name:** Sets the required name investors see on their invitation and on the Invest page.
4. **Phone** Holds an optional contact number for the deal lead, shown to investors who need to reach you.

### The three product types

Three cards sit in the Product Type group, with Standard SPV selected by default. A Standard SPV holds one asset and closes once, so if you expect a second close or a second asset, choose Premium SPV or Fund.

* **Standard SPV:** Holds one US startup investment with a single close.
* **Premium SPV:** Holds custom assets and allows multiple closes, for an asset other than a US startup or a deal that closes more than once.
* **Fund:** Holds multiple assets through one entity, for a vehicle that invests in several companies.

> **Check pricing before you choose.** The Pricing and fees link opens the current price list for each product type.


---

# 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/creating-a-deal.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.