> For the complete documentation index, see [llms.txt](https://docs.reserve.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reserve.org/core-components/yield-dtfs/deployment-guide/post-launch-playbook.md). # Post-launch playbook Once a new DTF is live, several key actions can help to encourage adoption. This guide outlines some suggested activities to maximize visibility, utility, and transparency after launch. ## Marketing & awareness Ensure the wider community hears about the new Yield DTF and understands its value proposition. * Publish a launch thread on popular social media channels (e.g., X/Twitter, Discord, and Telegram) * Create a simple explainer graphic (e.g., basket composition & headline yield) for social sharing * Reach out to newsletters or podcasts for a “new-product” segment or guest appearance * Announce any liquidity-mining, minting rewards, or other incentives with clear timelines ## Onchain integrations Listing the DTF where users already trade and borrow maximizes utility and stickiness. * Seed a primary liquidity pool on a leading AMM (e.g., Curve, Uniswap, Aerodrome) * Submit listing proposals to at least one onchain money market (e.g., Morpho, Aave, Compound) * Co-incentivize early liquidity with integration platforms and partners * Monitor pool depth and spreads; consider strategies to remedy liquidity issues ## Data & analytics Reliable, transparent data builds trust and helps investors track performance. * Apply for listings on CoinGecko and CoinMarketCap—prepare ticker, logo, & a short description * If applicable, publish data to Dune Analytics, The Graph, and/or DefiLlama * Set up automated alerts (e.g., on Discord or X/Twitter) for governance proposals or status changes --- # 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://docs.reserve.org/core-components/yield-dtfs/deployment-guide/post-launch-playbook.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.