Write your one-paragraph vision statement

Where does the world end up if your project succeeds? Not what your product does — what changes in the world. Think 3-5 years out. A strong vision statement is specific enough to be meaningful and ambitious enough to be worth working toward.

Write your mission statement

What is your project specifically doing, for whom, and why now? This is more grounded than the vision. It's the operational north star. It should fit in two sentences and be impossible to confuse with another project.

Define the problem you're solving

Be specific. Vague problems produce vague projects. Who has this problem? How badly do they have it? How are they currently solving this problem? The answers to these questions are what make a narrative feel real rather than constructed. If you can't name the person experiencing the problem, you don't know the problem well enough yet.

Why now?

What has changed in the market, in technology, or in crypto that makes this the right moment for this project to exist? "Why now" is one of the most important questions in any launch. Projects that can't answer it feel opportunistic. Projects that can answer it feel inevitable.

Write your one-sentence hook

If a KOL had 10 seconds to describe your project to their audience, what would they say? This single sentence will be used in KOL briefs, X bio, community posts, partner outreach, and every piece of marketing you produce. It needs to be specific (no one cares about vague promises), compelling (it should make someone want to know more), and true (you have to be able to deliver on it).

Test: Can you say it out loud and have someone immediately understand what the project is and why they might care? If there's any hesitation or confusion, rewrite it.

Identify your narrative category and angle

Every project fits somewhere. Picking your primary category isn’t limiting — it’s how you get remembered. Buyers, KOLs, and community members all use categories as mental shortcuts. If you don’t give them one, they’ll assign you one, and it may not be the one you want.

Choose one primary category from the list below. You can note a secondary if relevant.

Choosing a category is only half of it. The other half is deciding how you stand in relation to it. Are you the best version of your category — competing within it and winning on execution? Or are you the alternative to it — using the incumbents as the problem and yourself as the solution?

Unpacking the two options:

Within — "We’re a [category] and we’re better than the incumbents because of X." You’re competing inside the category and winning on execution or features.

Against — "Everyone in [category] is doing it wrong, and here's why." You're positioning yourself as the alternative to what already exists — the incumbents are the problem, you're the solution. This is often more powerful because it creates instant contrast and makes you memorable. But it only works if the criticism is true and your audience feels it. Airbnb didn't say "we're a great hotel." They said "hotels are impersonal and expensive — stay with a real person instead." The worse hotels looked, the better Airbnb looked.

Write the "why this team" story

Founders are part of the narrative in crypto. People back people. What about your background, obsession, or insight makes you the right people to build this? This doesn't require impressive credentials. It requires authenticity and specificity. Why are you (and/or your team) uniquely qualified or positioned to do this?

Complete the narrative stress test

Share your one-sentence hook with at least 5 people who are not on your team and not already invested in your success.

Ask them:

• Do you understand what this is?
• Does it make you curious?
• What questions does it raise?

Write down their actual reactions. This exercise consistently reveals where founders are being too abstract, too technical, or too inside-their-own-head. It's uncomfortable but essential.

Define what you are NOT

Clarity on positioning often comes from what you're explicitly not. What comparable projects or narratives should people not conflate you with, and why? Defining your edges helps people place you correctly in their mental map, and helps KOLs position you accurately to their audiences.

Define your brand voice

Brand voice is how your project writes and communicates — not just how it looks. It should be consistent across every post, community message, and piece of content your team produces. Defining it now means it's locked in before any creative work begins. The way it looks and the way it sounds should feel like they come from the same place.

Set up and configure Telegram community

Telegram is the primary community channel for most token launches. It needs to be set up properly from day one. Get the pinned message, rules, welcome message, bot, and mod structure right before you invite anyone in.

Moderation

Moderators enforce rules, answer questions, prevent scams, clean up the chat and keep conversations on track. Without proper moderation, your community can quickly become chaotic or vulnerable to bad actors. A few things to get right:

• Choose mods you trust who understand your project and can be active daily
• Give them admin permissions and ensure they know how to use Rose Bot or equivalent
• Mods must never talk about price. It's fine for the community to discuss it, but not your team or mods
• Set clear escalation procedures: when to mute, warn, or ban
• Assign a security lead responsible for SafeGuard settings, as these will need to be adjusted on launch day to combat the fake CAs and spam that you’ll inevitably get on launch day

If you need quality moderators, line them up early. Raise it in the team Telegram.

Telegram Portal

Don't share your direct group link publicly. Instead, use a portal bot (SafeGuard is recommended) to control entry and keep bots out. This ensures only real, verified users can join from day one.

1. Add SafeGuard bot to your Telegram group

2. Set up a verification step (CAPTCHA or reaction confirmation)

3. Share the portal link instead of your direct group link

Full setup guide: https://docs.safeguard.run/group-security/creating-a-portal

Set up a waitlist or pre-launch interest capture

Don't wait until launch day to find out who's interested. A simple waitlist or interest form linked from your website, X bio, and Telegram means you're building a warm audience from day one. People who opt in before launch convert at significantly higher rates than cold traffic on launch day. Even 200 genuinely interested sign-ups is a meaningful asset.

What fields to include

• Email — your primary contact channel for pre-launch updates
• Telegram handle — so you can reach out personally before launch and invite them to join the community
• X (Twitter) profile link — lets you identify and engage with them on social before launch
• How did you hear about us? — helps you understand which channels are driving awareness

Keep the form short. The fewer fields, the higher the completion rate. These four are all you need.

Set community growth milestones

Define minimum community thresholds required before launch. Set specific targets for Telegram members and X followers. A launch with insufficient community reach will underperform regardless of how good everything else is. Set the target first, then plan how to hit it in the next item.

Define your community growth strategy

Building a community before launch is one of the hardest things founders underestimate. Most default to posting on Twitter and hoping people find them. That's not a strategy — it's wishful thinking.

The tactics that actually move the needle fall into a few categories:

Founder visibility

You are the most powerful distribution channel you have. Post consistently on your personal X — takes, opinions, behind-the-scenes content, and commentary on your space. People follow people before they follow projects. A founder with 200 engaged followers is worth more than a project account with 2,000 passive ones.

Direct community outreach

Find existing Telegram groups and Discord servers where your target audience already hangs out. Don't shill — add value first. Answer questions, share insights, build a reputation. When the time is right, mention what you're building. One genuine connection in the right community is worth a hundred cold followers.

Collabs and Twitter Spaces

Partner with aligned projects for co-promotional posts or joint Twitter Spaces. You share audiences and both sides benefit. The key word is aligned — partnering with a project your audience doesn't respect does more harm than good.

Community activation

Your earliest members are your most powerful advocates — and most founders never activate them. Give your existing community a reason to spread the word. Early beta access to the product is one of the most effective tools here: it makes people feel like insiders, gives them something real to talk about, and creates genuine word-of-mouth. A community member who has used your product and believes in it will do more for growth than any paid promotion.

Content that travels

Content marketing is the single highest-leverage growth channel available to you before launch — and most founders either don't do it or do it wrong. Posting project updates and announcements is not content marketing. Nobody shares those. What spreads is content that teaches, provokes, or entertains.

Formats that consistently work in crypto:

• Educational threads — break down a complex concept in your space in a way that's genuinely useful. Don't make it about your project. Make it so good that people save and share it. Your project gets associated with the insight.
• Contrarian takes — identify a widely held belief in your space and argue the opposite, with evidence. These generate replies, quote tweets, and debate. Debate is reach.
• Behind the build — document something real about what you're building. A problem you hit, a decision you made, something that surprised you. Authenticity travels further than polish in this space.
• "I wish someone had told me" — personal lessons, mistakes, and hard-won insights. These resonate broadly and position the founder as someone worth following.
• Data and observations — if you have access to unique data or on-chain insights relevant to your space, share it. Original data gets cited and reshared.

The goal is to become known for something valuable in your space before the token exists. When you launch, people already trust you. Post at minimum 3 times per week on your personal account — consistency compounds. An account that posts daily for 8 weeks will have dramatically more reach on launch day than one that posts sporadically.

Use these content types as the foundation for your pre-launch content plan, which is a task towards the end of this phase.

Write your project description in three lengths

One sentence (for X bio and KOL briefs), one paragraph (for website header and Telegram pinned post), three paragraphs (for about page and press use). All three should be narrative-first, not feature-first. These descriptions feed into your content, your website copy, and your KOL briefs.

Build Visibility, Build Trust, Build Demand 📝

This is a quick guide to building visibility for your project and your founder profile as you lead up to launch and, just as importantly, post-launch.

Good content is not about posting more. It's about posting with intent. Clear, well-written, and engaging content builds trust, which you will need plenty of on launch day and beyond. Mix up the format, stay consistent, and keep it in your own voice or the brand voice.

This module breaks down what to create, how to use AI without sounding like AI, and where to find strong examples.

💡 Five Ideas for Content to Create

Do not rely on a single format. A healthy content strategy rotates across all five.

1. Short Product Walkthrough Videos

30 to 90-second educational videos showing the product in action. Screen recordings, voiceovers, or a more professionally produced demo video work here.

Why it works

Video builds trust faster than any other format because people can see the product actually working. It removes doubt. It's also the easiest way for a new follower to understand what you've built in under a minute, without reading a thread.

Frequency

At least 1 per week

Examples

SPECTRE AI on Twitter / X

fomo on Twitter / X

Occam on Twitter / X

Kreo on Twitter / X

Avici on Twitter / X

SPECTRE AI on Twitter / X

2. Product Education Posts

Posts that explain a feature, a use case, why people should care about your product, or break down your roadmap. Basic graphics help here.

Why it works

These posts onboard users without feeling like onboarding. They give your audience a reason to come back to your profile as a reference point, and they signal that the product actually does something useful, not just that it exists.

Frequency: 1-2 a week (Even more in the 1-2 weeks pre-launch)

Examples

Avici on Twitter / X

SPECTRE AI on Twitter / X

3. Product Build Updates

Posts on recent work/updates, bugs squashed, challenges you're working through, or just your overall vision for the project/product.

Why it works

Momentum is either visible or it is not. Quick updates show the team is actively building, even between big announcements. They also make challenges feel normal rather than hidden, which builds more trust than only ever posting good news.

For weekly or monthly protocol updates, X articles work really well.

Frequency: As and when needed. As many as you want.

(No graphic is always needed here.)

Examples

Sigma on Twitter / X

Ram on Twitter / X

SPECTRE AI on Twitter / X

liminal on Twitter / X

Avici on Twitter / X

4. Short-Form vs Long-Form Content

Use a mix of short, punchy posts and longer, more detailed posts.

The X algo generally favours long-form content, so for max reach and engagement it’s important to bake in long-form posts into your content calendar.

Why it works

If every post is the same length and format, your feed starts to feel flat, and your audience switches off. Varying the length keeps the content dynamic. Short posts are easy to consume and share. Long posts let your most engaged followers go deeper and position you as a team that actually understands what it's building.

Frequency: Try at least 1 long-form post per week

5. Founder-Led Content

Share the journey behind the product. A bug that took three days to crack. A small win. A decision that had to be made, and why. It doesn't need to be long or polished. It needs to be honest.

Why it works

This is what actually builds community in 2026. Audiences don't connect with product updates alone; they connect with the journey behind them. Founder-led content is the difference between a project with followers and a project with a community. Post the process, not just the outcome.

Take people on the build journey with you. Show the messy middle, not just the launch moment. Followers who watch a project get built from the ground up feel invested in it long before it's finished, and that investment is what turns them into your earliest and loudest supporters.

This type of content works well for your personal X account.

Frequency: As and when needed. As many as you want.

Examples

Brwn 🔮 (@brwnpb) on X

🔆 Fifi Tsamados (@CryptoFilles) on X

🗣️ Get good at replying

Posting is only half of the strategy. Replying to comments, engaging with other builders, and showing up in other people's threads builds visibility that a broadcast-only account never will.

Why it works

The X Algorithm rewards accounts that behave like part of the conversation, not accounts that only talk at people. A thoughtful reply on someone else's post can put you in front of a new audience faster than an original post does.

Treat engagement as a scheduled part of your content routine, not an afterthought.

🤖 Using AI to create content

AI is a tool. You can use it to help draft, structure, or tighten a post. It's also fine to post off the cuff without using AI, especially for founder-led content, where a slightly rough, honest post often lands better than a polished one.

There's no single right approach. The goal is the same either way: content that sounds like a real person said it.

How to avoid AI slop

If you do use AI, the biggest risk is content that reads as generic or obviously AI-written. A few basics to keep it sounding organic:

• Never use em dashes. This is one of the clearest tells of AI-generated text.
• Avoid AI-coded words. Terms like noise, execution, hype, and signal show up constantly in AI writing and rarely in how people actually talk. If you notice one in a draft, cut it or replace it with something plainer. Or at least don’t use them in every post.
• Avoid the "this isn't X, this is Y" pattern. Formulaic contrast lines are an instant giveaway that AI wrote the post. If a line reads like it's setting up a dramatic reveal, rewrite it as a plain statement instead.
• Read it back out loud. If you wouldn't say it to a friend, don't post it.

💡 Quick test before posting: would this sentence survive being said out loud in a normal conversation? If not, simplify it.

⛔️ Common mistakes to avoid

A few Web3-specific habits that quietly damage a founder's or project's credibility, even when the content itself is well written:

• Talking about price or token performance. This is a no-no. Concentrate on the product.
• Engagement-bait tactics. Posts like "tag someone who..." or "RT if you agree" read as desperate for reach rather than confident in the content. Let good content earn engagement on its own.
• Over-promising and underdelivering. Stating specific dates or features too early, then missing them, does more damage than never mentioning them at all. It's the fastest way to lose trust with a community, and once that trust is gone, it's hard to earn back. Talk about direction and progress, not commitments you can't guarantee.
• Copying the tone of other projects. What works for one founder's voice won't necessarily work for another. Consistency in your own voice matters more than sounding like whichever account just had a viral post. It’s ok to use other content as inspiration or for ideas, but always bring it back to your tone and brand voice.

Consistency builds familiarity. Familiarity builds trust. Trust is what converts attention into users and long-term community members.

Adapt tone and content to your own project's brand and product, but keep the underlying structure.*

Define your content pillars

Content pillars are the 3–4 recurring themes your content revolves around. Every post you publish should sit under one of these. They keep your feed coherent, your narrative consistent, and your audience knowing what to expect from you.

Without pillars, content becomes random. You post a product update one day, a meme the next, a market take the day after. The audience never builds a clear picture of who you are or why they should follow you.

Some examples of pillars that work well for crypto projects:

• The problem you're solving — content that educates your audience on the pain point your project addresses. You become the go-to voice on that problem. When you launch the solution, people are already primed.
• Behind the build — documenting the process of building in public. Decisions made, lessons learned, progress updates. Builds trust and makes the team feel real.
• Your space / category — commentary, analysis, and takes on what's happening in your broader category. Positions you as a credible voice in the ecosystem, not just a project shouting about itself.
• The vision — content about where things are heading, why the current state is broken, and what the future looks like. Narrative-driven, thought leadership style.
• Community and culture — spotlighting community members, sharing milestones, building the identity of the group. Makes existing members feel seen and signals to outsiders that something real is happening here.

Most projects should pick 3 of these and stick to them. A good mix is usually: one problem/category pillar, one build/vision pillar, and one community pillar.

Write your founding story post

The narrative origin story of why this project exists and why you're the ones building it. This is one of your most important pieces of content and it should be a long-form X Article. It should make the reader feel like this project had to exist and that you had to be the ones to build it. Get a second pair of eyes on it before it's published.

Establish founder X presence

The founder's personal account should be active and building an audience independently of the project account. People back people. At minimum, 3 founder posts per week leading up to launch. These can be personal takes, market commentary, or behind-the-scenes content — whatever is authentic to you. Know where you're starting from before you build the content plan.

This is where the content strategy you defined earlier becomes a real schedule. Minimum 3 posts per week on X from now, and ramping up to daily posts when you’re a couple of weeks out from launch — use the content types from your growth strategy as the basis for your calendar. Mix of educational threads, behind-the-build posts, founder takes, and community engagement. No launch date teasing until your date is locked in.

Write a plain-English product description

What does your product do, step by step, from a user's perspective? No jargon. No technical abstractions. If someone with no crypto background couldn't follow it, rewrite it.

This exercise is more revealing than it sounds. Founders who struggle to describe their product simply are usually founders who haven't fully defined what they're building yet. The clearer the product description, the clearer the narrative, the clearer the KOL brief. Everything downstream gets easier when this is sharp.

Define your launch-day product state

What specifically exists and works on launch day? Be honest — list features, not intentions. This is one of the most common places founders damage themselves: announcing a product that isn't ready, or implying capabilities that don't exist yet. Overpromising and underdelivering destroys community trust faster than almost anything else. What you say at launch needs to match reality exactly.

Build a 90-day post-launch roadmap

Your roadmap is a public commitment. It tells the market what to expect from you and gives holders a reason to stay. The difference between a project that holds value and one that dumps immediately after launch is almost always whether holders believe something meaningful is coming next.

Concrete milestones only — no vague directions. "Further development" is not a roadmap item. "Integration with X live by end of week 2" is. Be ambitious but achievable. Missing your own public roadmap in the first 90 days is a significant community trust event.

Identify your product's "wow moment" and assess PMF

The wow moment

What is the first thing a new user experiences that makes them think "this is real"? How quickly do they get there? The faster someone reaches genuine value or delight, the more likely they are to tell someone else. Word of mouth from real product users is the most credible marketing you can have — and it's free.

If your wow moment is buried behind 10 steps of onboarding, that's a product problem worth solving before launch.

Product-market fit

PMF is the degree to which your product satisfies a strong market demand. It sounds abstract but it has a very practical definition: you have PMF when your users would be genuinely disappointed if your product disappeared. Before that point, you have a product. After it, you have a business.

Most crypto projects launch before they have PMF — and that's not always fatal, because the token can fund the development that gets you there. But you need to be honest with yourself about where you actually are on that spectrum. A project that has early signs of PMF has a fundamentally different story to tell than one that is launching a concept with no usage yet.

Early signals of PMF to look for:

• Users coming back without being prompted
• People recommending it to others unprompted
• Users expressing frustration when features break or change — they care
• Organic community growth driven by product experience, not just hype
• Retention — people who try it keep using it

The further along you are, the stronger your narrative. If you have real PMF signals, lead with them. They are worth more than any KOL post.

Create your project docs in Gitbook

Your docs are the technical home of your project. They're where serious buyers, developers, and partners go when they want to go deeper than your website or whitepaper. A project without docs signals immaturity. A project with clean, well-structured docs signals that the team knows what they're doing and has nothing to hide.

This is your responsibility to produce. Getting a second set of eyes on it early helps, but the writing, structuring, and publishing is on you. Use Gitbook — it's free, looks professional, and is the standard for crypto projects.

What good docs look like

The best crypto docs share a few qualities: they're written in plain language, they're honest about what exists and what doesn't yet, they're consistent with everything else you've published (website, whitepaper, social), and they give a reader everything they need to understand and trust the project without having to ask questions.

Look at projects you respect in your category. Read their docs. Note what's clear and what's missing. That gap is the bar you're trying to clear.

What to include — minimum required sections

Introduction

What is the project? What problem does it solve, for whom, and why does it matter? This should be your sharpest, most accessible writing. Many readers will only read this page. Make it count.

How it works

A clear, step-by-step explanation of the product mechanics from a user's perspective. No jargon. Use diagrams if the product is complex. If a non-technical reader can follow it, you've done it right.

Product features

Break down each key feature or module of the product. For each: what it does, how it works, and why it matters. If certain features are not yet live, say so clearly and give a timeline.

Getting started / User guide

How does someone actually use the product? Walk them through it step by step. Include screenshots or screen recordings where possible. The easier you make it for someone to get started, the more users you'll retain.

Token utility

What does the token actually do? Why does someone need to hold it? What does it unlock, enable, or reward? This section needs to be specific. "Governance and utility" is not an answer. If the token has multiple use cases, document each one.

Tokenomics

The public-facing allocation breakdown: liquidity pool and treasury only. Include vesting schedules and lock periods. Be consistent with everything else you've published.

Lock & vesting schedule

A clear, visual breakdown of when tokens unlock for each allocation. Tables and timelines work well here. Sophisticated buyers look at this closely — clarity and transparency are the goal.

Multisig & security

Explain the multi-sig setup — what it is and what it protects against. This is one of your strongest rug-resistance signals. Write it in a way that a buyer with no technical background can understand why it matters. Remember, a rug-resistant launch structure is a major selling point — lean into it.

Tax structure (EVM launches only)

EVM launches use a tax structure at launch to capture value from early buy pressure. Starting taxes are 20% buy / 25% sell for the first 30 minutes, then automatically reduce to 5% buy / 5% sell. Document this clearly in your docs so buyers know what to expect before they transact. No surprises. If someone finds out about the tax for the first time when they try to buy on launch day, you've already lost their trust. Solana launches do not use a tax structure (it’s a 1.25% LP fee and treated differently) and should omit this section.

Roadmap

Your 90-day post-launch milestones. For longer-term vision, a high-level direction is fine — but don't over-promise.

Team

Who you are, your backgrounds, relevant experience, and why you're building this. Include links to personal X accounts and LinkedIn where available. Anonymity is a red flag for many buyers — being public builds trust.

FAQ

Anticipate the 10–15 questions buyers and community members will ask most often. Answer them honestly. A good FAQ reduces support burden and builds confidence in the team.

Map your direct competitors

List every project doing something meaningfully similar. For each: current market cap, community size, what they do well, what they do poorly, and why someone would choose them over you.

This exercise matters for two reasons. First, it forces you to know your market — founders who haven't studied their competitors are easy to catch out in conversations with KOLs and investors. Second, it sharpens your differentiation. You can't articulate why you're better without knowing exactly what you're better than.

If you can't name at least three direct competitors, you either don't know your market well enough or you're in a category that doesn't exist yet — both require different strategies.

📖 Narrative Engineering

This module ties together everything you've been building towards in Phase 3. Read it before you sit down to write your differentiation, one-pager, and pitch deck. Get this right and those documents get much easier to write.

Two projects can build almost the same thing and land in completely different places.

One gets attention early, attracts a strong community, and builds momentum quickly. The other struggles to get noticed, even when the product is just as good, sometimes better.

The difference is rarely the product itself. It's how the market understands it.

That comes down to positioning.

Positioning isn't marketing spin or a clever slogan. It's placing your project inside a narrative people already believe in, or building a new one they want to believe in. In a market driven by attention, that decision shapes everything that follows: who notices you, who joins your community, and how much benefit of the doubt you get when things get hard.

Think about this far earlier than most teams do.

1) Compete in a narrative, or create your own niche

You might be entering an existing narrative without realising it. Positioning yourself as "another" version of something that already exists. Another Layer 1. Another DeFi protocol. Another AI x crypto project.

The problem is that once you're inside an existing narrative, you're immediately compared. And unless you're clearly better, faster, or already have distribution, that comparison rarely goes your way.

What to do

Carve out a narrative niche instead. When you claim genuinely fresh ground, you shift how people evaluate you. You're no longer asking "are we better than them?", you're asking "does this niche make sense?", which is a far easier conversation to win early. This doesn't mean inventing something artificial. It means identifying what's genuinely different about what you're building and framing it clearly. Your strongest positioning usually sits adjacent to existing narratives, not directly inside them, close enough to feel familiar, different enough to stand out.

2) Timing shapes everything

Even a strong narrative fails if the timing is wrong. Every cycle in Web3 has its narratives, DeFi, RWA, AI, Robotics, and attention moves in waves.

Position too early, in a narrative the market isn't paying attention to yet, and you'll struggle to gain traction no matter how strong your idea is. Position too late and you risk getting lost in the saturation.

What to do

Don't just ask "is this a good idea?" Ask "is this the right time for this idea to land?" Early in a cycle, the market is exploring and open to new niches. Later in a cycle, attention consolidates around clear winners and it gets much harder to break through. Your idea can succeed or fail purely based on when you introduce it.

3) Build a narrative arc, don't just make a statement

One of the biggest mistakes you can make is treating your narrative as fixed instead of something that evolves.

Build an arc. Early on, keep your narrative simple and easy to grasp, enough to create curiosity and earn attention. As you build, deepen it: more detail, more proof, more context for what you're doing and why it matters. Post-launch, shift it again, now it's about actual traction and visible progress that matches what you promised.

What to do

Think in sequence. What do people need to understand first? What comes next? What reinforces belief over time? Communicate everything at once and you'll overwhelm people. Never evolve the narrative and you'll lose momentum. Don't tell your story once. Develop it stage by stage.

4) The market doesn't see what you see

You're always closer to your product than the market is. You see the technical depth, the edge cases, the long-term vision. The market doesn't start there. It starts with a simple question: what is this, and why should I care?

If your positioning doesn't answer that clearly, nothing else matters. It's easy to get stuck here, communicating from your own perspective instead of the market's, explaining how things work instead of why they matter.

What to do

Translate what you're building into something people can quickly place within what they already understand. That's what positioning is for. Without it, even your strongest product will struggle to earn attention.

5) Narrative is what gets people to pay attention in the first place

What people believe about your project shapes how they engage with it. Position yourself as part of a strong, understandable narrative and you'll benefit from that momentum: more eyes, a stronger community, more willingness to stick around when things get bumpy. Fail to make your positioning clear, or come across as just another version of something else, and everything gets harder, from building a community to earning your first wave of genuine believers.

What to do

Treat your positioning as seriously as your product. It's what determines whether people give you a chance to prove your fundamentals in the first place. Don't just explain how things work. Explain why it matters, who it's for, and what's genuinely different about it.

The bottom line

The same pattern repeats across the industry. The projects that build lasting momentum are the ones built around a story worth telling.

Your narrative becomes the lens people use to interpret everything you do next, your progress, your delays, your new developments. Get it right early, and you're giving your project the best possible chance to succeed on everything else you've worked so hard to build.

Define your competitive differentiation

For each direct competitor, write one sentence on why someone would choose you over them. If you can't write that sentence clearly, the differentiation isn't clear enough — and that's something to fix before you brief a single KOL.

Also identify your narrative white space: what story is nobody else in your category telling? The most powerful launch narratives occupy white space — they say something true and interesting that no competitor is saying.

Write your investor one-pager

Not every buyer makes decisions from a tweet. Sophisticated investors — the ones who take larger positions and hold longer — want to read something before allocating. Your one-pager is the document you share when someone asks "can you send me more info?"

It should be one page, honest, specific, and free of hype. Cover: the problem, the solution, the narrative hook, the token structure summary, the team, and why now.

Build your pitch deck

The pitch deck is a more visual, more detailed version of the one-pager. It's used when approaching partners and investors considering a meaningful allocation. Think of it as the document that does the selling when you're not in the room.

Keep it tight — 10 slides maximum. Every slide should earn its place. A bloated deck with filler signals a team that hasn't edited their own thinking.

Required slides — nothing more, nothing less

1. Cover — project name, tagline, one-sentence hook

2. The problem — make them feel it. Specific, not abstract.

3. The solution — what you've built, in plain language

4. How it works — product mechanics, simplified

5. Market opportunity — how big is this, and why now

6. Traction — community size, waitlist, any product usage, partnerships confirmed

7. Token utility — why someone needs to hold the token

8. Token structure — model, allocations, vesting summary

9. Team — who you are and why you're the right people to build this

10. Roadmap — 90-day milestones post-launch

Design matters. A poorly designed deck signals an unprofessional team before anyone has read a word.

Prepare for due diligence questions

Sophisticated buyers ask hard questions. The founders who handle these well — calmly, honestly, specifically — build more confidence than the ones who give polished non-answers or get defensive.

Use AI, and ask them to write the 10 hardest questions someone could ask about your project. Then write honest answers to all of them. If you can't answer them, that's something to fix before launch. If the answer is uncomfortable, that's even more reason to have it prepared.

This exercise also reveals gaps in your narrative and product thinking. Better to find them now.

Build your marketing swipe file

A swipe file is a self-serve marketing kit — everything a KOL, partner, or community member needs to promote your project without having to ask the team for anything. The easier you make it to share your project, the more people will.

Host it on Google Drive with a public view link and pin it in your Telegram community so it's always one click away. Share it with any KOLs or partners who are promoting the launch.

What to include

Copy & messaging

• One-sentence hook (from Phase 1)
• Project description — one sentence, one paragraph, and three paragraphs (from Phase 2)
• Narrative angle — the interesting, non-obvious thing about the project a KOL can lead with
• Key facts — token ticker, chain, tokenomics, lock and vesting schedule, contract address (added at launch)

Visual assets

• Logo files — PNG and SVG on dark and light backgrounds
• Promo video — ready to download and share
• Product screenshots — real, high-quality screenshots of the product in use. These are one of the most credible things a KOL can share. Blurry or unfinished screenshots do more harm than good — only include polished ones.
• Demo video or screen recording — if the product is live, a short walkthrough is far more compelling than any static asset

Documents

• Pitch deck
• Investor one-pager
• Gitbook docs link

Trust signals

• Any confirmed partnerships worth mentioning

Key links

• Website
• Telegram
• Twitter/X
• Gitbook docs

Everything in the swipe file must be final and approved. No drafts. No placeholders. If something isn't ready, leave it out and add it when it is.

🧠 The Psychology of a Launch

Everything in Phase 3 was about getting the substance right. This module is about getting your head right before you go live. It's not a task. There's nothing to tick off here. Read it, sit with it, and come back to it in the days before launch.

Most launch planning focuses on marketing, tokenomics, and timing, as if it's all a puzzle to solve. Nobody talks about how it actually feels to be the founder on the other side of it.

Launch is the moment your project stops being your internal idea and becomes everyone else's interpretation of it. You go from a controlled environment, months of building and quiet decisions, into full public view. Everything is visible. Everyone is watching. Nothing feels the way you imagined.

Strategy gets you to launch. Psychology gets you through it.

Here's what to expect, and how to hold your ground.

1) Your emotions will swing fast. Expect it.

However long you've planned, once you're live, the emotions hit within hours. Relief, excitement, doubt, fear, pressure, often all at once.

Markets swing. Comments pile up. FUD starts. Someone posts "this is failing" the moment there's a dip.

If you're not expecting this, it starts influencing your decisions without you noticing.

What to do

Assume your mood will change hour by hour. Build a buffer into your mindset, not just your schedule. When you feel panic, zoom out. When you feel overconfident, slow down. This isn't weakness. It's just what a high-pressure environment does to anyone. Expecting it is what keeps you in control of it.

2) Decide now what you won't decide in the moment.

Pre-launch, you're in build mode. You have time to sleep on decisions, talk them through, revise them.

At launch, you're deciding in real time: how to respond, what to post, whether to shift messaging, how to react to price and community pressure. Every one of those costs you mental energy. The more you react on the fly, the worse your judgement gets. That's decision fatigue, and tired founders make reactive, short-term calls. They flip messaging too often. They chase the market's mood instead of their own plan.

What to do

Lock in your core message, tone, and key talking points before launch. Let those be your guardrails. When you're drained, let the structure do the work instead of your judgement. It's far easier to hold a plan than invent one mid-chaos.

3) Early price tells you nothing about whether you're good.

There's no hiding from the chart. People watch it, watch your reaction to it, then judge you on that reaction.

Early price movement is statistically meaningless. It's noise from a small pool of traders and general launch mechanics. It doesn't tell you if your project is good or bad. It tells you people are trading.

Read too much into it, and you'll do one of two things: overreact to a small dip and start changing everything, or inflate your expectations after a spike and forget you're just getting started. Both derail you.

What to do

Treat early price as a separate, low-signal channel. You can't ignore it, but you don't have to take it personally. Keep your focus on what you control: product, roadmap, and how you communicate.

4) Say one thing, and keep saying it.

In the first hours and days, your messaging gets pulled from every direction. The community wants one thing, your team wants another, random voices on X want something else entirely.

Respond to each pull individually and you end up with a message that's inconsistent and confuses more than it helps.

What to do

Have one clear, simple statement of what your project is and what it's doing. Hold that line even when people push for something more sensational. Repeat it often, in slightly different ways, so it actually lands. Consistency doesn't mean one sentence forever, it means staying aligned to your core message instead of chasing every reaction. When the market's spinning, this is what makes people trust you're still following a plan.

5) The moment you feel like you're losing control is normal. It's not a signal you've failed.

At some point, something unexpected happens. A narrative you didn't plan for takes hold. FUD starts. You see the first real sign of trouble.

That feeling is natural. It means you're live, nothing more.

What matters is what you do next. Panic and you over-communicate: explaining everything, reacting to every comment, over-promising. Shut down and you go quiet exactly when you should be present, letting others define what's happening.

What to do

Sit in the middle. Calmly work out what's actually happening versus background noise. Decide what you're willing to change and what you're holding firm on. Then say that once, clearly. You're not trying to win an argument or satisfy everyone. You're trying to keep the project moving.

The bottom line

Launch is a psychological test as much as a tactical one. How you handle emotional volatility, decision fatigue, and early price noise shapes how your project is perceived in its first weeks, and how long you're able to keep going.

The strongest founders aren't the ones who avoid the stress. They're the ones who expect it, plan for it, and build controls around their own behaviour before they need them.

Identify & close strategic partnerships

A well-timed partnership announcement on launch day can meaningfully amplify your reach and credibility. The key word is strategic — a partnership with a project your audience already respects is worth far more than a logo swap with a random team.

What makes a partnership valuable:

• Genuine audience overlap — their community would care about your project
• Mutual benefit — both sides get something real, not just an announcement
• Both teams willing to post publicly — one-sided announcements are weak

A partnership where only you announce it and the partner says nothing is not a partnership. It's a post.

When approaching potential partners, lead with what you're offering them — not what you want. The fastest way to get ignored is a message that reads like a list of asks.

Build your week 1 post-launch content plan

The 7 days after launch are as important as launch day itself. Day 2 silence after a strong launch day is one of the most common and most damaging mistakes — it signals to holders that the team has gone quiet, and quiet breeds doubt.

Your post-launch content should sustain the narrative momentum from launch day. Product updates, community milestones, partnership news, behind-the-build content. Use the same content pillars you defined in Phase 2.

🔍 Transparency as a Competitive Edge

This one's about how you communicate while you build, not just what you're building. Like the psychology module, there's nothing to tick off here. Read it before you start shaping your holder communication strategy in Phase 4.

Trust in Web3 is fragile. It doesn't take much to lose it, and once it's gone, it's nearly impossible to win back fully.

That's the part most people underestimate.

You can have a strong product, a solid roadmap, and a genuinely capable team. But if your communication is unclear, inconsistent, or reactive, people start questioning everything else too.

What separates you from the projects that struggle isn't just what you're building, it's how you communicate while you build it.

Done properly, transparency isn't a performance. It's just how you operate day-to-day. It reduces confusion, builds confidence, and gives people a reason to stick around even when things aren't perfect.

Here are the five areas where it matters most.

1) Clarity builds confidence

The fastest way to lose someone's attention is to make them work too hard to understand what you're doing.

It's an easy trap to fall into. Reaching for technical language where it's not needed, staying intentionally vague, or trying to sound more advanced than you are. It usually comes from wanting to look credible. The effect is the opposite. Confusion creates distance. If someone reads your content or your posts and still can't explain what your project does, they won't stick around.

This matters most pre-launch, when people are deciding whether to pay attention at all.

What to do

Be able to explain your project in simple terms without losing meaning. Keep your message consistent across your content, community, and product updates. Say the same thing clearly enough that people actually remember it. Don't try to impress with complexity. Focus on being understood.

2) Consistency signals maturity

Transparency isn't only about what you say, it's about how consistently you show up.

Communicating in bursts, active for a few days, then silent, then back with a big update, might feel normal from the inside. From the outside, it reads as unpredictable, and unpredictability creates doubt. Even when nothing's wrong, people start asking whether you're still building, still on track, still there.

What to do

Give people a rhythm. Not every update needs to be major news, in fact most shouldn't be. Share progress, small wins, lessons learned, even challenges. That's what turns your project from something distant into something people actually follow. Over time, consistency builds familiarity, and familiarity builds trust.

3) Handle delays early, not perfectly

No roadmap survives contact with reality exactly as planned. Delays happen. Priorities shift. That's normal for any startup, and Web3 is no different.

What's different is that in Web3 it all happens in public, in real time.

It's tempting to go quiet when a delay hits, waiting until you have a complete update or a fix in place. The intention is to avoid concern. The result is the opposite: silence creates uncertainty, and people fill that uncertainty with their own explanations, usually the negative ones.

What to do

You don't need to over-explain or share every internal detail. Just be honest and timely. If something changes, say it. Explain what happened straightforwardly, and what it means going forward. People are more understanding than you'd expect. What they don't tolerate is feeling kept in the dark. Handled well, even delays can strengthen trust rather than damage it.

4) Address FUD without feeding it

FUD is part of the industry. It'll show up eventually, whether from misunderstanding, frustration, or bad actors. No project is immune.

The mistake isn't that it exists. It's how you respond to it. Ignoring it entirely rarely makes it go away. Reacting emotionally usually makes it worse.

What to do

Work out what actually matters. Not every comment needs a response, but when misinformation spreads, or a genuine concern comes up, address it. Stay calm, stick to facts, be direct. You're not trying to win an argument; you're showing people you're in control and won't overreact under pressure. That composure is what builds confidence when it counts.

5) Transparency compounds

There's a misconception that transparency slows you down or exposes too much. In reality, it simplifies your communication, reduces unnecessary speculation, and strengthens the relationship between you and your community.

Most importantly, it compounds. Each clear update, each honest explanation, each well-handled situation adds to your track record. People start to trust not just what you say, but how you operate. That kind of trust is genuinely hard to replicate, and it's one of the few real advantages you can build early and carry with you.

The bottom line

Web3 is maturing. People are more selective about where they put their time and money, and they pay attention to how you behave, not just what you promise.

That shift rewards you for being clear, consistent, and open. Building lasting momentum isn't about trying to say the most. It's about communicating the clearest, especially when it's hardest to.

Don't disappear when things get difficult. Don't overcomplicate your message. Don't let others control your narrative.

Show up, explain what's happening, and keep moving forward.

Plan your first post-launch milestone announcement

What is the first tangible thing you can announce in the days after launch to reinject momentum? Product update, partnership going live, integration confirmed, new feature shipped. Have it ready before you launch so it can be deployed the moment you need it.

The best projects plan their second act before their first act is finished.

Define your holder communication strategy

Holders who feel informed and heard hold longer. Holders who feel ignored sell. This is not complicated — it just requires consistency and honesty. Define how you'll communicate with your token holders on an ongoing basis before launch, so it becomes a habit from day one rather than something you figure out reactively.

Prepare for launch day AMA

A launch day AMA — typically 3-4 hours after trading opens — is one of the best tools for sustaining momentum after the initial wave. It gives the community a reason to stay engaged, gives holders confidence in the team, and gives undecided buyers a final push.

Launch day is the culmination of everything you've built over the past 8 weeks. The 2-hour window before trading goes live moves fast, and there are a lot of moving parts that need to happen in the right order. A spam attack happens on virtually every launch — it's not a matter of if, it's when. Your mod team needs to be briefed, prepped, and ready before the day starts.

Read through this entire section carefully before launch day. Sort out any questions in advance. There is no time to figure things out in the moment.

Write the play-by-play launch day timeline

The launch day timeline is the single document your entire team executes from on launch day. It takes the launch day checklist and turns it into a named, timed, assigned action plan. Every person on the team should know their role before the day starts — not figure it out in the moment.

Use the pre-filled structure below as your starting point. Fill in the owner for each action and add any project-specific tasks. The checklist in the task prior covers what needs to happen — this timeline covers when and who.

Apply for CoinGecko and CoinMarketCap listings

CoinGecko and CoinMarketCap are the two most visited crypto data aggregators in the world. Being listed means your token shows up when people search for it, gives it a legitimacy signal, and makes it discoverable to buyers who would never have found it otherwise.

Apply soon after trading is live — both platforms have a review process that takes time, so the earlier you submit the better.

Keep executing on your roadmap and content strategy

You planned your roadmap and content strategy in earlier phases. Now you execute. This sounds obvious but it's where most projects fail — the energy of launch day fades, the team gets distracted, and the community notices.

Holders don't just hold tokens. They hold belief. And belief needs to be continuously earned through consistent action, honest communication, and visible progress.

On your roadmap

Ship what you said you'd ship. If something is delayed, say so early and honestly — don't wait until the deadline passes to acknowledge it. Holders can accept delays when they're communicated well. What they can't accept is silence followed by a missed deadline they didn't know was at risk. One honest "we're running a week behind on XYZ, here's why and here's the new timeline" post builds more trust than ten hype posts.

On content

Keep posting. Use the content pillars and calendar you built in Phase 2. The founder's personal presence matters as much post-launch as it did pre-launch — people back people. If the founder goes quiet after launch, the community reads it as a red flag.

A few things that work well post-launch:

• Behind-the-build updates — what you're working on, what you shipped, what surprised you
• Community spotlights — reposting holders, celebrating milestones, making people feel seen
• Upcoming catalyst teases — building anticipation for the next milestone before it arrives

On Telegram presence

Be visible in your own community. Post updates personally. Answer questions. Show up. The community can tell the difference between a founder who cares and one who has checked out. People hold longer when they believe in the founder behind the project.

Monitor chart health and holder sentiment

Price action and community sentiment are lagging indicators of what's happening with your project. By the time the chart is in trouble, the community trust is usually already eroding. Monitoring both proactively — rather than reactively — means you can act before problems escalate.

What to watch:

• Holder count — is it growing, stable, or declining?
• Average daily volume — is there consistent trading activity or are things going quiet?
• Community activity — are people posting, asking questions, engaging? Or is the chat mostly price talk and silence?
• Wallet activity — are large holders accumulating or distributing?

When to seek outside input:

If you see a significant holder count drop, a large wallet selling, or community sentiment turning sharply negative — flag it in the team Telegram immediately. Don't try to manage it alone. An experienced launch partner will have seen these patterns before and can advise.

What not to do:

Don't ignore warning signs. Don't respond to FUD emotionally or defensively in public. Don't make promises to prop up the chart that you can't keep. Address concerns calmly, honestly, and with specifics.

Execute your holder retention strategy

Acquiring holders on launch day is the easy part. Keeping them is where the real work happens. A holder who stays for 30 days is worth significantly more than one who sells within 48 hours — both for the chart and for your community credibility.

Retention comes from one thing: belief. Holders who believe in the project, the team, and the roadmap hold. Holders who feel uncertain, ignored, or uninformed sell.

Tactics that build retention:

Regular AMAs — even a 30-minute voice AMA in Telegram or X Spaces every two weeks gives holders a direct line to the team and builds the personal connection that makes people hold through volatility.

Product drops and demos — if the product is live, show it being used. Nothing builds conviction faster than seeing something real. Short screen recordings, feature highlights, or user testimonials posted to X and shared in Telegram.

Community competitions and incentives — competitions, content challenges, community ambassador programs. Give holders a reason to be active and to bring others in.

Milestone celebrations — acknowledge and celebrate every meaningful milestone publicly. New holders, trading volume, roadmap completions. Make the community feel like they're part of something growing.

Honest holder updates — a regular written update (weekly or bi-weekly) from the founder summarising progress, what's coming, and the current state of the project. Treat your holders like investors. They are.