# Best Practices Before Launch

Launching a token is more than just deploying a contract and going live - It’s about preparing your project to succeed from day one. 

### Follow these best practices before you go live:

* <mark style="color:orange;">**Finalize Tokenomics**</mark>
  * Clearly define supply, decimals, and liquidity percentage.
  * Avoid last-minute changes that confuse investors.
* <mark style="color:orange;">**Prepare Branding & Assets**</mark>
  * Upload a clear **logo, name, ticker, and description**.
  * Ensure consistency across website, socials, and whitepaper.
* <mark style="color:orange;">**Set Communication Channels**</mark>
  * Have official **Telegram, Twitter/X, and website** ready before launch.
  * Pin important info for investors (launch time, contract address).
* <mark style="color:orange;">**Understand Fees & Revenue Sharing**</mark>
  * Review AstraPad’s platform fees, bonding curve mechanics, and post-launch revenue model.
  * Be ready to explain them to your community.
* <mark style="color:orange;">**Gas Fee Ready**</mark>**&#x20;(Optional)**
  * Ensure your wallet is funded with enough ETH/BNB/SOL for gas.
* <mark style="color:orange;">**Plan for Marketing & Growth**</mark>
  * Coordinate with your team to leverage **Spyder Ads, Starlight credits, and other Benefits Hub tools** immediately at launch.
  * Sync marketing campaigns with your launch schedule.
* <mark style="color:orange;">**Build Trust Before or After Going Live**</mark>
  * Complete **KYC** if required.
  * Highlight your **instant audit certificate** to investors for confidence.


---

# 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://docs.chatastra.ai/ecosystem/astrapad/getting-started/best-practices-before-launch.md?ask=<question>
```

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.