> For the complete documentation index, see [llms.txt](https://wefund.gitbook.io/wefund-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wefund.gitbook.io/wefund-whitepaper/wefund/roadmap.md).

# Roadmap

**Q4 2022**

* Launch new WeFund dapp with a dashboard system
* Finish fundraising (seed)
* Smart Contract audit
* IDO
* TGE + Listing
* Launch 3 Projects 
* API prototype building
* API partner testing (3 partners)

**Q1 2023**

* Incubate 10 projects
* Launch 10 Projects
* Audit the API
* Launch the API
* Have 5 partners using the API

**Q2 2023**

* Equity crowdfunding integration
* Launch profit-sharing-based projects
* Incubate 10 new projects
* Launch 10 projects
* Having 8 Partners using the API
* NFT market place testnet

**Q3 2023**

* Incubate 3 Equity crowdfunding projects
* Incubate 10 new projects
* Launch 10 projects
* 10 Partners using the API
* Launching the NFT marketplace
* Integrate the NFT marketplace in the API solution (testnet)

**Q4 2023**

* Incubate 10 new projects
* Launch 10 projects
* 12 Partners using the API
* Release the API with NFT marketplace integration


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wefund.gitbook.io/wefund-whitepaper/wefund/roadmap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.