Your launch calendar: what to do 60 days out, on the day and 30 days after

What belongs at T-60?

Quick test: Count the days to launch. If it is under 30 and your facts sheet is not done, finish that before anything else.

At T-60, establish the launch brief before drafting campaigns. The team needs a shared record of what is launching, when key decisions are due, and who can approve public statements. This reduces last-minute rewrites and gives every channel the same starting point.

Create a working document with:

• The intended launch window, chain and token identifier, once confirmed.
• A plain-language explanation of the product, audience and reason for the token.
• Named owners for product facts, legal review, community, content and launch operations.
• A list of decisions still open, each with an owner and due point.
• A single approved location for current links, logos, descriptions and answers.

Keep planned statements distinct from confirmed facts. For example, mark an exchange conversation as a discussion until an announcement is approved. If the date, token details or responsibilities change, update the source document first, then use it to refresh channel drafts. For broader launch planning, see token launch and growth and the token launch (TGE) marketing guide.

Preparing the story and launch assets

Prepare a compact, consistent story that a new reader can understand without a private briefing. The core message should explain what the project does, who it serves, what the token is for, and where readers can verify the details. Avoid making promotional copy carry facts that belong in product or token documentation.

Build an asset folder and assign an approver for each item:

• Short and extended project descriptions, with wording checked against current product facts.
• Logo files, approved brand visuals and channel-specific post formats.
• A project website, social profiles, community links and contact route.
• A token information sheet covering the confirmed network, contract address and supply details.
• A response document for predictable questions about access, utility, risks and launch timing.

Before release, ask someone outside the drafting group to compare the website, social bios and announcement copy. Names, links and token details should match everywhere. For community content, prepare useful explanations and moderation guidance rather than relying on repeated promotional posts. If your project is a memecoin, the memecoin launch guide can help shape the launch-specific checklist without replacing the core facts and approvals.

Checks before CoinGecko or CoinMarketCap submissions

Treat listing preparation as a documentation and consistency task, not as a marketing announcement. Gather the information requested by each platform, verify that public project materials agree, and keep a record of what was submitted and when. Assign one person to manage questions and update the team when there is a response.

Use this preparation list:

• Confirm the project name, ticker, network and contract address wherever they appear.
• Check that the project website and social links are live and lead to official destinations.
• Make sure the public description matches the product and the token’s stated purpose.
• Collect the supporting links and materials requested in the platform’s current application flow.
• Keep copies of submitted details so any later correction can be made consistently.

Do not announce a listing as confirmed until the platform has made that status clear and the team has approved the wording. CoinGecko and CoinMarketCap have separate listing processes, so prepare their submissions individually rather than assuming one application covers both. For the platform-specific steps, read how to get listed on CoinGecko and how to get listed on CoinMarketCap.

Coordinating community, creators and content

Rule of thumb: Freeze the links, logo and contract 7 days before launch. Changes after that need a second approval.

Coordinate channel activity around useful information and confirmed milestones. A channel plan should state what each audience needs to know, who publishes it, where questions go, and which facts must be approved before publication. The goal is a coherent experience, not identical posts copied everywhere.

Map the activity in a simple table before committing to dates:

For creators, assess audience fit, content quality, past topic relevance and how the creator handles sponsored work. Provide a brief that permits an honest explanation of the project; do not ask anyone to imply personal use or make claims the team cannot support. A launch with creators needs coordination beyond a list of accounts, so use the crypto KOL campaign guide to prepare selection and briefing. Align community updates with a realistic moderation plan using the Telegram community growth guide.

Launch day

On launch day, the team should follow one approved run sheet with an owner for every public update and operational check. Keep the run sheet accessible to people handling the website, social channels and community so everyone is working from the same confirmed information.

Include these checkpoints in order:

• Confirm the current launch status and the exact details cleared for public release.
• Check that the website, official social profiles and community links are accessible.
• Publish the approved announcement and verify that its links point to the intended destinations.
• Keep a named contact available to handle corrections, questions and internal escalation.
• Record publication times, links, approvals and any material change in a shared log.

Prepare a holding message for situations where a scheduled update must wait for confirmation. It should acknowledge that the team is checking the information and point readers to the official channel for updates. Do not improvise contract, listing or availability details in replies. The launch lead should pause queued content if a core fact changes, confirm the correction with the responsible owner, and then give channel managers the replacement text.

Your 7-point T-60 to T+30 checklist

Print this checklist and tick it as you go. Each point maps to a date range, and together they cover the 90 days around launch, so nothing important is left to the final days or to launch day itself.

• T-60: write the facts sheet and name an owner for each channel.
• T-45: prepare logo, links and a pinned message.
• T-30: prepare listing submissions and check the data.
• T-14: brief the community team and creators.
• T-7: freeze the contract, links and logo.
• T-0: follow the launch-day plan hour by hour.
• T+30: review, correct and write the closeout.

Terms in one line

T-minus (in plain words: days counted down to launch day, written T-60, T-30 and so on).

Facts sheet means one page with the contract, supply, links and team that everyone reuses.

What lies outside the team's control

Your team can control whether submissions are complete, public descriptions are consistent, official links work and launch communications accurately reflect confirmed facts; it cannot determine how CoinGecko or CoinMarketCap reviews an application, whether either platform accepts it, or when a response arrives. DEXScreener and DEXTools likewise make their own decisions about whether a token or project appears in a feature or trending area, and the team cannot set those placements, their duration, or how they are displayed to each visitor. Build the checklist around actions you can verify: save submitted materials, track platform correspondence, avoid announcing an outcome before confirmation, and keep a ready-to-publish update if a profile or placement changes.

From T+1 to T+30

After launch, keep the public information current and turn recurring questions into clear follow-up actions. The first month is a useful period to review what readers misunderstood, which channels need better explanations, and what the team should publish next. Log observations rather than treating a burst of attention as proof that the project story is clear.

At T+1, check that official links, descriptions and pinned posts still reflect the live project details. During the following weeks, review community questions, creator content and incoming feedback with the relevant owners. Correct outdated material at its source, then update channel versions so the same answer is not contradicted elsewhere. At T+30, close the checklist by noting completed tasks, open issues, approved next steps and who owns each one.

A useful closeout has four parts: a record of published communications, a list of corrections made, a summary of repeated audience questions, and a prioritized follow-up queue. If you want help turning the checklist into an execution plan, send MarketingExtra your intended launch window, confirmed token details, current channels and open decisions. We will review the materials with you and identify the next practical actions.

How it works

1. Confirm the launch briefSet the intended window, token facts, audience and decision-makers. Mark unresolved items clearly and assign an owner to each.
2. Prepare approved materialsGather project descriptions, links, visual assets and token information in one source of truth. Check that public-facing versions agree.
3. Coordinate channels and partnersMap community updates, creator content and publication responsibilities to confirmed milestones. Give every contributor approved facts and a contact for questions.
4. Run the launch from one scheduleUse an approved run sheet, verify destinations and record public updates. Pause queued content when a core fact needs confirmation.
5. Review and close outTrack corrections and recurring questions through T+30. Assign owners to follow-up work and update the source materials.