Where each launch story begins
Presale marketing explains a defined sale stage. Fair-launch marketing explains how an open release works. Neither label replaces a clear description of the token, project and actual access rules.
Picture a validator team on the morning after a listing announcement. Members may ask whether the announcement changes how they can participate. We’d first check the project’s approved distribution details. Then we’d help the team answer that question in plain language. The goal is a message that matches the plan, not a fresh claim built around attention.
A presale story needs to make its stage and participation conditions easy to find. A fair-launch story needs to explain what “open” means for this release. It should also show where people can check the instructions. In both cases, your community benefits when the website, social posts and community replies point to the same information.
Start with one source document. It should name the model, confirmed terms, official links and the person who can approve updates. The token launch marketing checklist can help your team gather those details before drafting. That small bit of preparation makes later questions easier to answer. Community members won’t need to piece together separate announcements.
What can your team explain without hedging?
The better fit is the model your team can describe accurately. It should also be one your team can support with confirmed information. A defined sale stage may call for presale communications. A release intended to open on stated terms calls for messages that explain those terms plainly.
Before settling on the public story, meet with the people responsible for token operations, product updates and community replies. Ask whether they can explain who may participate. Check when access begins and where the current instructions live. Then see whether those same answers work across your site, announcement and community channels.
Suppose your team has chosen a fair launch, but the opening instructions are still changing. We’d keep the campaign draft in preparation while the owner confirms the final wording. That pause is kinder to your community than asking members to follow an announcement that may need correction.
Use a simple test: can a new member understand the rules without a private explanation? If the answer is no, make the missing detail visible before inviting more people into the conversation. When replies and moderation need a clear owner, a community growth and engagement plan can sit beside the launch messages. Keep technical questions with the person who can answer them accurately.
How the two routes shape the work
The main difference is what your campaign must make clear. It isn’t whether one format needs communication and the other does not. Use this comparison to identify the questions your team should answer before choosing channels or drafting copy.
| Campaign question | Presale | Fair launch |
|---|---|---|
| What should the opening message explain? | The sale stage and confirmed participation conditions. | What open access means for this release. |
| What should members be able to check? | The terms and official participation information. | The release instructions and public project information. |
| What needs a named owner? | Questions about sale terms and updates. | Questions about release instructions and updates. |
| What should the team prepare? | Approved sale details and a clear source page. | Approved release mechanics and a clear source page. |
| What should reporting record? | Published messages, live links and corrections. | Published messages, live links and corrections. |
At Brand Community, our first review checks proposed messages against details your team has approved. We then help organize the copy, channel plan and record of published links. If your launch also needs wider media or creator planning, compare that work with a KOL campaign guide. Keep each channel’s role clear. Members should know where to find official terms, rather than treating every post as a separate source.
Before the first post goes live
A calm launch handoff gives your team time to check the facts. It also gives you time to prepare replies and keep a record of what went out. Use these 3 steps for a presale or an open release.
- Gather the confirmed details. Put the model, participation information, official links and approval owner in one place. Flag anything still being decided.
- Review the message together. Check that the website, announcement and community replies describe the same terms. Ask the owner of technical or token details to review those claims.
- Keep a campaign record. Save the approved copy, published links, any corrections and questions passed to another owner. A check-in after the first week can help your team notice what needs a clearer explanation.
One important boundary belongs in that review. A launchpad sets its own current terms and decisions. The project controls only the information and work it supplies. On either route, individual participation is outside the campaign’s control. Later market response is too.
If you’re ready to talk through the choice, send us your planned distribution model, available materials and target timing. At Brand Community, we’ll review what’s confirmed and point out gaps in the message. Then we’ll discuss a campaign plan that fits your community.
How can you compare the people and platforms involved?
| Dimension | Self-managed team | Launchpad options such as Polkastarter, PinkSale or DAO Maker | Brand Community |
|---|---|---|---|
| Primary role | The project team plans and carries out its own communications. | The project reviews a platform’s launch offering and requirements. | Marketing support organizes communications around the chosen model. |
| Message control | The team reviews its own copy and channel work. | The project checks the platform’s role and applicable process. | Messages and channels are planned from approved project information. |
| What to prepare | Owners for copy, channels and community questions. | Current platform terms and any requested project materials. | Distribution details, source materials, audience and launch timing. |
| Potential fit | A team with time and relevant launch communications experience. | A project exploring a platform-based launch route. | A team looking for outside planning and campaign support. |
| What to check | Public claims against the project’s distribution rules. | Current requirements and responsibilities with the platform. | Agreed work, approvals and evidence of completed campaign tasks. |
These are different routes, not promises about outcomes. Confirm platform terms directly and compare any marketing work with your own launch needs.
Frequently asked questions
Which format is easier for a new community to understand?
Neither format is automatically easier to explain. Members need a plain account of how access works. They also need to know where the official instructions are and which details are confirmed. For example, a presale announcement should make its sale stage and conditions easy to find. A fair-launch announcement should explain what open access means for that specific release.
Can we prepare presale messages while some terms are still open?
Yes, you can prepare the parts that are already confirmed. Those may include the project introduction and channel plan. Keep undecided terms out of public copy until their owner approves them. A shared document with a clear pending note helps writers avoid treating a draft condition as final.
What should a fair-launch announcement explain?
It should describe the release instructions and when access begins. It should also point to the official information. Explain what “open” means under the project’s actual rules. If there are conditions, include them plainly. Don’t rely on the label to explain the experience.
Does a fair launch mean we can skip community communication?
No. People still need to understand the project and find the release instructions. They also need to know where questions belong. Marketing can make that information easier to find without changing the distribution model. A simple reply guide and one named owner can help keep answers aligned across channels.
Can one campaign message work for both launch formats?
Some project details can stay the same, such as the product description and official links. The access explanation should change to match the model. A presale message needs to describe its sale stage and conditions. A fair-launch message needs to explain its release instructions and what open access means.
What can an agency promise when a launchpad is involved?
An agency can agree to prepare and publish specific campaign work. It can then share the approved copy and live links. A launchpad makes its own decisions under its current terms. Participation depends on each person and the project’s stated conditions. Before work begins, write down what the agency handles and what the project or platform owns.
What should we send for an initial marketing discussion?
Send your planned distribution model, confirmed token and product information, target timing, official links and current channel list. Include participation rules and the name of the person who can approve claims. That gives us enough to review what is ready. We can then identify details your community may need clarified.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…