Most projects communicate brilliantly right up until the money lands.
Then the updates get sparser. The Telegram questions get slower answers. A milestone slips and nobody mentions it. Six months later the community is hostile, the fund that led the round is hard to reach, and the next raise is a much harder conversation.
The quiet period after a raise costs projects more than any single execution failure.
Why token IR is harder than equity IR
An equity company has a small, contractually-defined investor base and a quarterly reporting rhythm. A token project has thousands of holders, none of whom signed anything, all of whom can see your treasury on-chain, and many of whom will publish their conclusions publicly.
You also have a second audience with different needs: the funds that backed you, who want detail, and who talk to each other about which portfolio companies communicate well.
Running both properly is a discipline. Most teams treat it as something the founder does when there’s good news.
The programme
A predictable cadence. Pick a rhythm you can actually sustain and hold it. The specific frequency matters far less than the predictability. A community that expects an update reads silence as information, and their interpretation of that silence is always worse than the truth.
A consistent place. One canonical location where updates live. Not scattered across a Telegram announcement, an X thread and a blog post with different contents.
Honest shipped-and-slipped reporting. What you said you’d do, what you did, what moved and why. The projects that survive difficult periods are the ones that were already reporting the misses when things were going well.
Treasury transparency. Holdings, addresses, runway, and material movements. Your treasury addresses are visible on-chain regardless. The choice isn’t whether people see the movement — it’s whether you explain it or someone else does.
Unlock communications. Publish the schedule, remind holders before each cliff, and say what you know about recipient intentions. Sophisticated holders already track this. Announcing it yourself removes an information advantage from anyone planning to trade against your community.
A route for questions. Office hours, a monthly call, a dedicated channel. Something better than hoping the founder sees a message.
The moments that decide reputation
A missed milestone. Say it before someone notices. Explain what changed. Give the revised position. Communities forgive delays with remarkable consistency and never forgive discovering that a date quietly stopped being mentioned.
A security incident. Speed and specificity. What happened, what’s affected, what you’re doing, when the next update comes — and then actually deliver that next update on time. The second update landing when promised does more for trust than the first one’s content.
A price collapse. You can’t fix it and you shouldn’t pretend to. What you can do is keep reporting on the things you control. Projects that go silent during drawdowns lose the holders who would have stayed.
A team departure. Address it plainly. The rumour that fills the gap is always worse than the reality.
A pivot. Explain the reasoning and what it means for holders. Pivots handled with a full explanation land far better than ones announced as a positive development with no acknowledgement of what changed.
What funds actually want
Having sat in a lot of these conversations, the pattern is consistent. Funds want:
- Numbers that don’t change definition between updates. Redefining your key metric is the fastest way to lose credibility with a professional investor.
- Bad news early. Every experienced investor has heard bad news. What they haven’t heard, and what they hold against people, is bad news late.
- A specific ask. Introductions, hiring help, a customer conversation. Vague updates with no ask suggest you don’t know what you need.
- Consistency between what you tell them and what you tell the public. These diverge more often than teams realise, and funds compare notes.
The mistakes
Only reporting wins. A perfect record reads as selective, because it is.
Different messages to different audiences. Both will find out.
Treating the community as retail and the funds as real investors. Your community holders are a large part of your float and a larger part of your public perception.
Letting the founder be the only channel. It doesn’t scale and it stops entirely when the founder is busy, which is exactly when the community most wants to hear something.
What drives the work
- Size and dispersion of the holder base, and how many languages it spans.
- Whether you have institutional investors with their own reporting expectations.
- Reporting obligations your counsel has flagged in the markets where you operate.
- Unlock complexity, since more tranches means more communication moments.
- Whether you have anything difficult to communicate, which changes the work substantially.
- Internal reporting maturity. Teams that already track their metrics consistently have far less to build.
The summary
Communicate on a schedule. Report what slipped alongside what shipped. Publish the treasury and the unlocks before anyone asks. Answer questions in a place people can find.
None of this is complicated. It’s just unglamorous, and it only pays off in the moment when something goes wrong — which is precisely when you can no longer build it. Trust is a balance you deposit into during the good months and withdraw from during the bad ones.
Common questions
What does investor relations mean for a token project?
It means running a deliberate communication programme for the people who hold your token and the funds that backed you — regular reporting, honest updates on what shipped and what slipped, transparency on treasury and unlocks, and a predictable channel where questions get answered. Token projects have a wider investor base than equity companies and a more visible one, which makes the discipline more important rather than less.
How often should a token project report to holders?
On a predictable schedule you can sustain, published in a consistent place and format. The specific frequency matters less than the predictability, because a community learns to expect an update and reads silence as a signal. A shorter update delivered reliably beats a comprehensive one delivered when things happen to be going well.
What should a project disclose about its treasury?
Holdings, the addresses where they sit, the runway those holdings represent, and any material movements. Treasury addresses are usually visible on-chain anyway, which means the choice is between explaining movements yourself and having someone else explain them for you. Projects that publish proactively face far easier conversations than those that respond to a thread.
How should you handle a missed milestone?
Say so before someone notices, explain what changed, and give the revised position honestly. Communities forgive delays and remember concealment. The damage from a missed date is small and short. The damage from discovering a missed date the team quietly stopped mentioning is large and permanent, and it attaches to the founders rather than the project.
How do you communicate around token unlocks?
Publish the schedule in advance, remind holders before each unlock, and state clearly what recipients intend to do where you know. Unlocks are public information that sophisticated holders already track. Announcing them yourself removes the information advantage from anyone planning to trade against your community and demonstrates that you expect scrutiny rather than fear it.
