# Aixbc Founder Playbook *A spiritual successor to the* [*Believe Builder Playbook*](https://believe.app/playbook) *with expanded insights from $aixbc.* *** ### Disclaimer **WHO SHOULD USE THIS GUIDE:** Committed founders who are passionate about their projects and in it for the long haul. This playbook is for builders who are willing to put their reputation on the line and are prepared to execute consistently over time. **WHO SHOULD NOT USE THIS GUIDE:** * Projects without genuine long-term vision * Founders unwilling to engage actively with their community * Those not genuinely excited about what they're building *If you are an investor or trader, you may find that this serves as a lightweight due diligence guide for Believe ecosystem projects. For comprehensive due diligence guides, aixbc has more detailed tutorials exclusively for holders of 1M+ $aixbc tokens.* *This guide focuses **solely** on helping committed founders win.* *Make sure your entire team reads this guide.* *** ### Pre-Launch: Foundation Building #### Project Validation * Ensure your project solves a **real problem** or serves a genuine need * Validate your idea with trusted **advisors** before public announcement * Several advisors should be Web 3 natives * Selection here is crucial * Seek advisors you know well, are knowledgeable, and genuinely support you * Be prepared to articulate why you are uniquely positioned to build this ("Product-Founder Fit") * Founder background is extremely important for knowledgable investors * Document clear short-term (3 months) and medium-term (6-12 months) objectives #### Brand & Identity Development * Create a distinctive, memorable brand identity if you haven't already * Design professional logo and visual assets * Prepare X banner and DEX banner in advance * Make sure your banner is 1500:500px for Dex; it refuses non 3:1 aspect ratio uploads * Create these assets in advance of launch and have them ready * Secure consistent social handles across platforms * Create clear, concise tagline that explains your value proposition in 5-7 words * Develop a professional website with clear value proposition and styling #### Social Preparation * Establish genuine X presence (don't buy followers or engagement) * Never buy X accounts for yourself or your project (easily detected and damages credibility) * *But if we really have to tell you this, reconsider launching in the first place :)* * Engage authentically with relevant communities, let them know what you're up to * Follow and interact with Believe ecosystem accounts and founders #### Network Activation * **CRITICAL**: Identify and engage with crypto Twitter influencers in your niche you already know * These folks will often invest on day one to support you * They will often share your project on X when you launch * Manage DMs in an organized way e.g. using a CRM like [TweetDM](https://tweetdm.com) * Join relevant Telegram groups and Discord servers * Connect with potential large holders and community leaders directly * Especially if you already know them personally, these relationships are gold * Seek intros to Believe team members if possible * Join the Believe Slack channel #### Technical Readiness * If building on-chain, have functional code ready to demonstrate * Smart investors will always visit your site and test your app firsthand * Prepare GitHub or equivalent to showcase development work if project is technical/open source * Test your product with a small group of trusted users * Create documentation for your project (even if minimal) #### Content Creation * Produce a clear, concise launch announcement * Bonus: Prepare a video introduction (casual Screen Studio or Loom recordings are great) * Draft 3-5 follow-up announcements for post-launch momentum * Create graphics explaining your project's value proposition * Prepare documentation of your team's background and credentials * Ensure website is ready with placeholder for contract address *** ### Launch Execution #### Timing Strategy * Launch between 10am-8pm PM ET on Monday-Thursday for optimal attention * **Deploy from the account with fewer followers and RT it from your main** * This avoids snipers that dump on your true supporters * Immediately upon launch, you can quote-tweet the launch post from your main * Be sure your main account follows the smaller one after you launch

Example of how to deploy from a smaller account

* Give Believe team a heads-up well in advance of your launch on X or Slack * If they offer support, you should 100% take them up on this if given the chance * Coordinate with supporters to ensure immediate post-launch engagement #### Launch Announcement * Clear, concise explanation of your project * Tag @launchcoin using proper formatting * Include a short video explaining your vision and background * Use simple language that non-technical supporters can understand * Show genuine enthusiasm for your project #### Immediate Post-Launch Actions * Purchase Enhanced Token Info on DEXScreener immediately after listing * Update all social profiles with contract address * Pin contract address to profile * Update website with contract address prominently displayed * Deploy Telegram community group (recommended over Discord) #### First 24 Hours Critical Tasks * Host X Space within 1 hour of launch * Assign team member to answer questions in Telegram continuously * Post first project update with next immediate steps * Engage with all substantive questions across platforms * Thank early supporters personally #### First X Space Structure

Example Canva template commonly used for X spaces

Pro tips for your X space: * While not necessary, you can use Canva to create a graphic for your upcoming X space * Run your X space alongside notable accounts or projects for maximum reach * Name your space something eye-catching * It's often a good idea to include your $ticker and "Believe" in the X space title * e.g. "$ticker LAUNCH on @believeapp" for X space name * Make sure you tweet the link to the space from your main *and* project X when you start it * If you haven't run a spaces before, test it prior to launch so you know how it works * Pin your token launch tweet and CA to the top of your space Here are some suggested topics to cover during your space on X: 1. **Introduction** * Your background and credentials * Why you're qualified to build this project 2. **Project Origin** * Problem identification (personal pain point is most compelling) * Solution development process * Product vision 3. **Token Launch Rationale** * Why launch a token now * Plans for transaction fee usage * Token utility roadmap 4. **Transparency Section** * Current user metrics (if applicable) * Revenue figures (if applicable) * Development timeline * Team composition 5. **Roadmap Presentation** * Immediate next steps (7 days) * Short-term milestones (30 days) * Medium-term vision (90 days) 6. **Q\&A Session** * Prioritize questions from established accounts * Address concerns transparently * Note feature requests and suggestions * Immediately remove speakers that bring up unrelated subject matter to your project 7. **Closing** * Summarize immediate next actions * Direct to Telegram for ongoing discussion * Set expectations for next formal update *** ### Post-Launch Sustainability #### Communication Cadence * Post updates daily across personal and project accounts * Include your ticker symbol in tweets regularly, even if you're a Web 2 company * Maintain consistent voice and messaging * Balance technical updates with community engagement #### Community Building * Hire moderators for 24/7 Telegram coverage * Create separate channels for announcements and general discussion * Consider a VIP or whale channel for top holders or advisors * Host or hop on AMAs (at least 2 per week) * The way you stay relevant is by talking about your project to new audiences * This is universal for all founders in any industry * X spaces are a great place to do this * Reach out to @aix\_bc for an AMA with our members — the largest community of Believe investors * Showing you are open to questions as a Founder is a crucial signal to the market

Collaborating with other projects and creators is essential to your project's longevity

#### Development Transparency * Share development updates with visual evidence and real product updates * Celebrate important milestones publicly on X and TG * Address delays or pivots honestly and proactively * Provide regular progress reports against roadmap * Open source when possible for community validation * You can also talk about what you're planning on shipping too * You do not have to wait until things are shipped to talk about them * See below for example

Case study update: Talk about what's coming up soon

Case study tweet: How to keep holders excited

#### Token Utility Evolution * Develop meaningful utility beyond speculation * Focus on creating value for token holders (Reference $Buddy, $TweetDM, and $Aixbc for examples) * Implement utility features incrementally * Gather feedback on utility features from your top advisors or largest holders * It's important you trust who you ask * People might recommend catalysts for their own exit pumps otherwise #### Mindshare Growth * Participate in at least 2 Spaces on X weekly beyond your own * Collaborate with adjacent projects in the ecosystem * Engage with comments and mentions consistently * If you post an important update on X, post it to your Telegram and pin it so people don't miss it * Monitor mentions on X for your ticker — otherwise, you’ll miss them *** ### Strategic Resource Allocation #### Use of Proceeds What sets Believe apart is that Founders get 1% of total volume transaction fees Take time to consider how you will wisely spend this new fundraising * Not recommended: * *Buybacks & Burns*: While popular, this strategy rarely sustains long-term growth * Recommended: * *Product development, team expansion, and Marketing* * This is a much better way to use funds and reflects long-term commitment to your project * Consider allocating to liquidity (market making) if possible * Set clear, transparent fee allocation policy * Regularly report on fee usage to community over X and TG #### Team Expansion * Identify critical skills gaps and prioritize hiring * Consider community-sourced talent when appropriate * Ensure all team members have skin in the game * Publicize key hires with background and responsibilities * Balance technical and community/marketing roles * This part maps well to how you would run any other technology company #### Marketing Budget Allocation * Organic growth > paid promotion in Web 3 * Do not pay for ads * Avoid paid endorsements from influencers (community can spot these) * Smart investors discount shills from 100k follower accounts with "DM for promos" in their X bios * Invest in quality content creation * Consider allocating budget for community incentives and engagement #### Community Management Resources * Hire dedicated community managers for round-the-clock coverage * Invest in moderation tools and systems * Invite the following bots to your TG: Rose, Protectron, Safeguard * If you don't know how to set these up, ask someone you trust to do so for you * Create comprehensive community guidelines for common commands e.g. /faq in Telegram * Build escalation processes for issues * Train team on crisis communication *** ### Founder Psychology & Resilience #### Managing Emotions * Prepare for extreme volatility in token price and sentiment * **Do not** obsessively check your own chart when you launch * Build and communicate about what you're up to instead * If you're putting in the work, the market will eventually take notice * Trust the process * Develop personal strategies for staying grounded * Seek support from other founders in private channels * Maintain perspective on long-term vision * Separate personal worth from token performance #### Decision Making Framework * Establish clear criteria for prioritizing requests * Create processes for evaluating opportunities * Document decision making rationale for transparency * Learn to say no to distractions from core mission * Revisit and adapt strategy regularly, but not reactively #### Burnout Prevention * It's normal to lose *some* sleep the first week of your launch * Establish normal work rhythms afterwards * Build redundancy in critical functions * Delegate appropriate responsibilities * e.g. you should not be personally welcoming each person to your public TG * Set healthy boundaries on ultra late night availability * Maintain physical and health routines #### Handling Criticism * Distinguish between constructive feedback and noise (e.g. burn token requests) * Respond to substantive criticism professionally * Don't engage with trolls or obvious bad actors * Instruct mods to use /ban command to boot them in your TG and move on * Use criticism as market intelligence * Demonstrate adaptability when feedback is valid *** ### *The $aixbc Advantage* #### *Leverage Our Network* * *Aixbc is the largest investor community on Believe* * *Our community includes experienced investors with 8 figures of capital across our 30 top holders* * *We host AMAs for quality projects committed to long-term building* * *Gain reach to sophisticated investors who understand project valuation* #### *Strategic Advisory* * *Investment in your project using our $aixbc VC fund* * *Access to experienced founders within our network* * *Hands-on involvement in product, roadmap, and token utility design* * *Introductions to strategic partners aligned with your mission* * *Ongoing advisory support through market cycles* \ \ *Reach out to us* [*@believe\_capital*](https://twitter.com/believe_capital) *or join our Telegram* [*t.me/believecap*](https://t.me/aix_bc) *to learn more and arrange an AMA* *** ### Common Pitfalls to Avoid #### Communication Errors * Going silent for days or during difficult periods * Over-promising and under-delivering * Inconsistent messaging across channels * Reacting emotionally to market movements * Failing to acknowledge mistakes #### Technical Missteps * Launching with critical bugs or vulnerabilities * Neglecting security best practices * Prioritizing features over stability * Ignoring performance issues * Failing to test thoroughly before updates #### Community Management Failures * Allowing toxic community members to dominate * Ignoring legitimate concerns brought up by holders * Lacking clear, enforced community guidelines * Insufficient moderation coverage #### Strategic Errors * Pivoting too frequently based on market sentiment * Chasing trends rather than executing vision * Focusing on token price over product quality * Misallocating resources to non-core activities * Failing to adapt to market feedback *** ### Detailed Launch Readiness Checklist #### Have this checklist pulled up the day you launch #### T-30 Minutes * [ ] Prepare your community channels (we recommend Telegram) * [ ] Update website and social bios for your new project * [ ] Double-check your launch tweets are properly formatted [@launchcoin](https://x.com/launchcoin) $TICKER +NAME * [ ] Prepare tweets from Founder and project profiles to RT and amplify your launch * [ ] Notify advisors and fans about your upcoming launch so they can invest and amplify #### T-15 Minutes * [ ] Confirm core team and supporters are online and ready * [ ] Prepare main launch tweet in drafts on X * [ ] Have your site editor open and ready to update with your new Contract Address * [ ] Final verification of all technical components * [ ] Turn off the option for people to DM you directly on Telegram * [ ] Turn off the option for people to add you to new groups on Telegram #### Launch Moment * [ ] Deploy token on Believe * [ ] Post main launch tweet with @launchcoin tag and formatting * [ ] Pin launch tweet to project and creator X profiles * [ ] Share launch tweet and contract address in primary and partner communities * [ ] Update website with live contract address * [ ] Update your audience on X that you are updating dex immediately * [ ] Add logo, banner, site, X, and TG to Dexscreener [here](https://marketplace.dexscreener.com/product/token-info). It should look something like this:\ \ ![](/files/qpCQoQC8HNzFP4AJQqH4) * [ ] Post that you've updated Dexscreener * [ ] Tweet directing people to your public Telegram link * [ ] Announce upcoming X space for a clear time > **Pro Tip:** Get these done **as quickly as possible**. Early momentum upon token launch is crucial. This is the most important time to be active and communicative. If you need to, do a test run with a test X and a test coin and update on Dex so you see how it works. Label the coin TEST so no one buys it. #### T+15 Minutes * [ ] Post first follow-up tweet with more project details * [ ] Assign team member to monitor engagement and respond to serious queries * [ ] Expect to get DMs from a lot of scammers * [ ] Ignore and block these requests * [ ] Share first quality analysis or project deep-dive * [ ] Make sure your website is updated immediately after launch with all relevant information * [ ] Hold X space for introduction and Q\&A (following structure outlined previously) * [ ] Tweet the link to your X space across creator and project profiles * [ ] Conclude X space directing listeners to your community to engage #### T+1 Hour * [ ] Post initial traction update * [ ] Post positive metrics like new members, holders, new site visitors, user count growth * [ ] Avoid discussions around the price of your token — you are here to build * [ ] Ensure community moderation is active and working smoothly * [ ] Monitor and address any technical issues * [ ] Engage with early supporters #### T+3 Hours * [ ] Post end-of-day recap/success metrics * [ ] Schedule next day's content * [ ] Team debrief on launch performance * [ ] Assign important tasks to team members in a project manager like Asana #### Additional Important Items * [ ] Prepare response templates for common questions * [ ] Have clear policy on community standards and participation * [ ] Establish emergency communication channel with mods/team * [ ] Prepare a brief pinned welcome message for your community * [ ] Have example quality analysis posts ready to demonstrate value > **Pro Tip:** Get these done **as quickly** as possible. Do not be shy or coy. > > Err on the side of over communicating the day of your launch. *** ### Sustainability Metrics Track these metrics weekly to gauge project health: #### Community Health * Engagement rate on social posts by notable accounts * New community members * Community-initiated content and posts * Mention volume across platforms #### Development Progress * Features completed vs. roadmap * Bug fix response time * Repository activity (commits, PRs) * Test coverage and quality metrics * Technical debt assessment #### Business Fundamentals * User growth rate * Revenue growth (if applicable) * Customer acquisition cost * Customer lifetime value * Runway projections *** *Remember: Building takes time. The most successful projects focus on consistent execution rather than short-term price action. Create genuine value, and trust the market will recognize it.* *** ### Ready to Launch? If you are a committed founder preparing to launch on Believe Or already launched and are seeking a hands-on help The $aixbc team is here to support quality projects with: * Pre-launch advisory * Post-launch support * AMA opportunities with our investor community * Strategic introductions to key ecosystem players * Post-launch support and guidance * Direct investment in your project **Get in touch with our team:** * DM us on Twitter @[Believe\_Capital](https://x.com/believe_capital) * Submit your project [here](https://believecapital.vc/apply) to apply * Join our [community](https://t.me/believecap) We prioritize projects with clear vision, committed teams, and long-term building mentality. Let's build something meaningful together. *** *© 2025 aixbc. All rights reserved.* --- # 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://aixbc.gitbook.io/founder-playbook/aixbc-founder-playbook.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.