> For the complete documentation index, see [llms.txt](https://handbook.opencoreventures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.opencoreventures.com/ocv-employees/vc-ops/company-formation-process.md).

# Company Formation Process

Forming a company involves a lot of moving parts, and OCV's role is to handle the operational complexity so founders can stay focused on building. The following pages document each stage of that process in order, from internal approval to when the business is funded and ready to operate.

## Formation Steps

1. [Internal approvals and conflict checks](/ocv-employees/vc-ops/company-formation-process/internal-approvals-and-conflict-checks.md)
2. [Choose legal entity structure](/ocv-employees/vc-ops/company-formation-process/legal-entity-structure.md)
3. [Founder offer & equity](/ocv-employees/vc-ops/company-formation-process/founder-offer-and-equity.md)
4. [Choose company name](/ocv-employees/vc-ops/company-formation-process/company-name.md) 
5. [File incorporation documents](/ocv-employees/vc-ops/company-formation-process/incorporation-documents.md)
6. [Issue equity & establish options pool](/ocv-employees/vc-ops/company-formation-process/issue-equity-and-options-pool.md) 
7. [Fund the business](/ocv-employees/vc-ops/company-formation-process/funding.md)
8. [Set up systems](/ocv-employees/vc-ops/company-formation-process/systems.md)


---

# 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://handbook.opencoreventures.com/ocv-employees/vc-ops/company-formation-process.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.