> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/public-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/public-docs/project-docs/starting-a-project-with-legitimate.md). # Starting a Project with Legitimate What is the timeline for starting a project with Legitimate? 1. 2 months before launch - Determine which Tag type suits your project best by taking our[ Legitimate Tag quiz](https://form.typeform.com/to/uASZMl0J) 2. 2 months before launch - Determine the number of [SKUs](/public-docs/project-docs/what-is-a-sku.md) you need for your project. 3. 1.5 months before launch - Place your order with the Legitimate Team. 4. 2 weeks before launch - Send the Legitimate Team the [required activation assets](#user-content-fn-1)[^1]: your item name, image and/or animation, and description for each SKU. 5. Add in any additional exclusive content to your product's digital experience using our [Builder.io Integration](/public-docs/project-docs/managing-your-skus-on-legitimate-dashboard-with-a-third-party-cms-integration/how-to-use-the-legitimate-builder.io-integration.md) 6. Go live! [^1]: --- # 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.legitimate.tech/public-docs/project-docs/starting-a-project-with-legitimate.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.