Why crypto projects live on X
For most crypto and web3 projects, X is where the community gathers. Launches are announced there, partnerships are revealed there, and the people who care about a project follow its account and its founders to keep up.
That makes a project's follower list the closest thing it has to a membership list. Reaching those followers directly, at the moments that matter, is one of the most useful things a small team can do on X.
Announcements that reach your community
A post on X reaches a share of your followers. A direct message reaches the inbox. For a mainnet launch, a token event, an AMA, a governance vote or a security notice, a direct message to the people who chose to follow the project makes sure the news is not buried in a busy timeline.
The Twitter/X mass DM tool in Tweeksocial sends one personalised message to each follower you choose, or to a CSV list of handles, spread through your active hours. Replies arrive in the project's inbox as normal private conversations.
Make every DM easy to trust
Crypto DMs have a trust problem. Scammers impersonate projects in direct messages all the time, which is why many people in the space ignore DMs entirely or treat them with suspicion. A project that messages its community has to be more careful than anyone else.
A few rules help people trust that a message really is from you. Send only from the project's official account. Never ask anyone to connect a wallet, share a seed phrase or send funds in a DM, and say so in your bio and in the message itself. Point people to links they can check for themselves, such as your website or a pinned post, rather than asking them to click something unfamiliar. And keep the tone consistent with everything else the project posts.
It is worth writing it out plainly in announcements: "We will never ask for your seed phrase or ask you to send funds." People remember the projects that looked after them.
Welcoming new followers
New followers are often the most curious people a project will ever meet. An automatic message that thanks them and tells them where to learn more, such as your docs, your community or your latest update, gives them somewhere to go next. New followers DM sends it the same day, personalised with their name.
Keep that first message free of anything that asks them to connect a wallet. Documentation and community links are enough.
Partner, creator and KOL outreach
Projects also message people outside their own follower base: other teams, creators and key opinion leaders. Whether those messages arrive is up to X. Anyone who follows you can be messaged directly, and everyone else depends on their settings, which often limit requests to verified accounts and people they follow.
The reliable route is to earn the follow first: reply thoughtfully to their posts, and message once they follow back. The guide to why you cannot DM some people on X explains the settings involved.
Growing the right following
A project's reach depends on who follows it. Auto follow can follow people who follow related projects, at a steady daily pace, so the people who see your posts are the ones likely to care. Auto unfollow later removes the accounts that never followed back, keeping the project's following list in proportion.
Around launches, the Twitter unfollower tool shows who unfollowed and when. A wave of unfollows after an announcement is useful feedback, and it often arrives before anyone says anything publicly.
Pacing through busy weeks
Launch weeks tempt teams to message everyone at once. Spreading messages out is better for the account and for the people receiving them. In Tweeksocial, each connected account sends up to 300 messages a day, inside X's own published limit of 500 direct messages a day.
That sets the timing. A campaign to 6,000 followers from one account takes about 20 days at 300 a day. So urgent news belongs in a post first, with the direct message following for the people who missed it.
| Followers to message | Days |
|---|---|
| 1,000 | 4 |
| 3,000 | 10 |
| 6,000 | 20 |
| 10,000 | 34 |
What to avoid
Messaging the same followers every few days. Sending a first message that is nothing but a link. Inventing urgency. Messaging people about something they never showed any interest in.
All four are quick ways to get muted, and in crypto they are also quick ways to be mistaken for a scam. One clear, honest message that people are glad to receive does more than five that they are not.
An announcement checklist
Before any announcement goes out by direct message, run through a short list. It takes two minutes and protects the project's reputation.
Is it coming from the official account? Does the first sentence say what is actually happening? Does it tell people where to confirm the news for themselves, such as your website or a pinned post? Is there nothing in it that asks anyone to connect a wallet or send anything? Does it remind people that you will never ask for a seed phrase? And is there someone on the team ready to answer the replies?
If any answer is no, fix it before you send. A message that fails that checklist can do more harm than no message at all.
Segmenting your community
Not every follower needs every announcement. Someone who followed yesterday wants different information from someone who has followed the project since its first testnet.
Useful groups include recent followers, long-standing followers, people who joined during a particular campaign, and people who have replied or asked questions before. The simplest way to work with groups is to export the project's followers, split them in a spreadsheet, and upload the group you want as a CSV list. The guide to exporting your Twitter followers explains the export.
Smaller, better-targeted announcements get more replies and fewer mutes than one message sent to everyone.
Handling replies during a launch
A launch announcement can produce hundreds of replies in a day, most of them questions. Decide in advance who on the team answers them, and prepare short answers to the questions you know are coming, with links to the relevant part of your docs.
People who reply are removed from later automated sends, so nobody who is already talking to the team receives another automated message in the middle of the conversation.
Treat anything that sounds like a security problem as urgent. A follower reporting a fake account or a suspicious link is doing the project a favour, and deserves a fast answer.
Measuring the effect
Three numbers tell you most of what you need: how many people replied, how many visited the page you pointed them to, and how many unfollowed in the days after the message.
Tag the links in your announcements so your own analytics can separate visits from DMs from everything else. And compare each announcement with the previous one, rather than with other projects. The trend in your own replies and unfollows is the most honest measure you have.