What to post during launch week

Why the quiet days matter more

Launch day has attention supplied by mechanisms. New-pair feeds surface anything new. Launchpad boards show whatever is filling. Anticipation peaks by definition at the moment of launch. None of that was earned and all of it expires within hours.

What follows is a week where the token competes with everything else and has nothing structural working for it. That is when people who heard about it come back to look, when the chart starts accumulating a shape, and when the decision about whether the project is real gets made.

Almost every launch plan allocates its effort in exactly the wrong proportion: enormous preparation for the day that carries itself, and improvisation for the week that decides the outcome. The week-one failure guide covers what that produces, which is a token that looks abandoned by day three because nobody had anything planned to say.

Before launch

Two things want to exist before the token does, and both are logistics rather than marketing.

A pinned message with the mint address, ready to go the moment the pool is live. In the first week the token is not searchable by name, duplicate tickers are the norm, and everyone arriving needs the address from a source they trust. If it is buried in a post that scrolls away, you have lost a share of the most motivated arrivals to a search box that returns somebody else's token.

The diligence links assembled. Pool address, lock transaction, mint account showing authorities. Not because anyone asked yet, but because the first person who does will ask publicly, and answering in ten seconds is a different event from answering in an hour.

Launch day

The day needs less persuasion and more logistics than people expect, because the audience is already present.

1. Confirmation the pool is live, with the address.
2. The mint address, pinned, and repeated in the profile rather than only in a post.
3. The verification links, posted proactively rather than in response to a challenge.
4. What happens next, which is the single most useful thing you can say on the day and the one most often omitted.

The fourth item is worth dwelling on. Everyone looking at a new token is trying to work out whether it will still exist next week. Saying concretely what is planned for the next fortnight answers that better than any amount of enthusiasm, and it also commits you publicly, which is the point.

Days two to seven

The goal for this stretch is not excitement. It is demonstrating presence, which is a much lower bar and one that most tokens fail.

Post most days, even when small. A question answered, a number explained, progress on something specific. The content matters less than the fact that the most recent message is not from launch day.

Attach activity to what you say. Anything you do on-chain during this period reads better when there is a post next to it explaining why, and any campaign run against a real moment is defensible in a way that the same spend on a random Tuesday is not.

Answer the checkers. People will ask about authorities, liquidity and the team. Each of those questions is an opportunity to post evidence in public, and each answer stays visible for the next person.

Do not go quiet after a bad day. This is the instinct that does the most damage, and it is covered below.

One practical scheduling note. Write the week's posts before launch day rather than during it, even in rough form. The reason is not efficiency; it is that the person deciding what to post on day four will be tired, will have been reading the chart all week, and will be in a considerably worse position to judge tone than the person planning it beforehand. Drafts written in advance can be edited or discarded, but their existence removes the situation where nothing goes out because nobody had the energy to decide what should.

What each post is actually for

The bottom row deserves the bluntness. A feed that is mostly about price trains an audience to care about price only, and that audience leaves the moment the chart stops cooperating. The people worth attracting are the ones who stay through a flat week, and they are attracted by what the project does rather than by what it costs.

What to post when it is going badly

Most teams stop posting when the chart turns, on the entirely reasonable instinct that there is nothing good to say. It is the most damaging habit in this whole area.

What it produces is a token where the last visible message from the project predates the decline. To anyone arriving afterwards, that reads as abandonment rather than as a difficult period, and the chart is then attached to a project that appears to have stopped rather than to one that is still there.

Continuing to post something factual through a bad week costs nothing and changes what a visitor concludes from identical data. It does not require optimism or a plan to fix the price; it requires being visibly present. Acknowledging that a week has been poor, and saying what is being worked on regardless, is more credible than silence and considerably more credible than forced enthusiasm.

The extreme version of this is an accusation, where the same logic applies at higher speed and the cost of silence is measured in hours rather than days. The accusation guide covers that case, and the preparation it recommends is the same preparation described here: have the links ready before you need them. If activity is part of the plan for the week, the launch checklist covers where it belongs in the order, which is after the free work rather than instead of it.