> For the complete documentation index, see [llms.txt](https://sply-1.gitbook.io/sply/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sply-1.gitbook.io/sply/project-owner-guide.md). # Project Owner Guide ## Project Owner Guide This page explains what project owners need to prepare before launching through Daoi and how to think about the create flow. ### Decide the launch structure first Before opening the create page, a team should already know: * which template it wants to use * how total supply and presale price relate * how soft cap and hard cap are set * what the participation limits should be * when the launch should end * what public project information should be shown ### Key create fields ### Identity and presentation * token name * symbol * total supply * description * logo * links These affect the public project surface and token page quality. ### Fundraising configuration * presale price * hard cap * soft cap * max per transaction * max per wallet * end time These define the presale boundary conditions rather than the token mechanism itself. ### Template parameters When a built-in or approved developer template is selected, the create page shows template-specific parameter inputs. These are defined by the selected template and are not universal across all templates. ### What happens after creation After a project is created, the platform exposes a project page with: * fundraising progress * configured limits * project profile data * participation access ### What owners should expect after finalize Project owners should understand that finalize is where the platform transitions the project into a standardized market state. LP creation, trading enablement, parameter closure, and verification are part of that path. ### Best practices * choose the template before entering values * verify the math between supply, price, and caps * make the mechanism understandable in the description * prepare brand assets in advance * separate test launches from production launches *** ## Agent Instructions: 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: ``` GET https://sply.fun/daoi-docs-import/project-owner-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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. --- # 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://sply-1.gitbook.io/sply/project-owner-guide.md?ask=&goal= ``` `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.