About the author:
‍
Outset Legal Lens is led by Alice Frei, Outset PR’s head of security & compliance. In this series, she draws on years of experience in legal, compliance, and due diligence work across Web3 projects to show where teams most often get it wrong, and how to build communication that supports growth without quietly creating liabilities.

‍

In a standard tech context, future developments point to product direction: what the company wants to test, improve, or release next. They can affect user trust, media interest and business reputation.

Web3 adds another important aspect: plans exist alongside an asset whose value may move with public discussions. 

That is why the legal issue starts earlier than many projects expect. The confidence built before the final rollout is also scrutinized because the market may treat a roadmap point as a signal about anticipated demand, liquidity, usage, or scarcity before anything is  live.

If communication leads people to connect potential upside with plans, the message becomes part of a broader market-facing narrative. 

‍

It’s not just the roadmap: Expectations come in many forms

There are plenty of channels where a Web3 team might talk about “what follows”, and each format affects expectations in its own way:

• Roadmaps and milestone pages can make next steps look more fixed than they are. A clean timeline, exact dates, confident numbers, and no visible dependencies turn a working direction into a commitment.‍
• Product announcements and utility updates like a planned integration, AI feature, infrastructure launch, or added utility may imply future usage, adoption, or demand. The closer the update sits to token mechanics, the easier it is for the market to translate product progress into economic expectations.‍
• Teasers create assumptions without substance. “Something huge is coming,” “big news soon,” or “you’ll understand why we stayed silent” leave the audience to fill in the blanks. In crypto, that blank can quickly become a risk.‍
• Founder posts, interviews, and AMAs carry extra weight as high-signal sources. Even a casual answer is meaningful when it comes from someone presumed to know what is happening behind the scenes.‍
• Community channels on Telegram and Discord may feel informal, but a hint in a private chat, a like on an inflated interpretation, or silence around a rumor support speculation that ultimately grows into expectation-setting.

‍

Where expectations meet legal evidence

A few crypto cases already show how forward-looking narratives enter the legal picture.

Telegram is a strong example. The SEC focused not on Grams themselves, but on the broader story around the TON launch, secondary market liquidity, and expected resale dynamics. Even without explicit profit promises, communication created economic expectations around the token ecosystem. Telegram later agreed to return more than $1.2 billion to investors and pay an $18.5 million penalty.

The Terraform Labs case illustrates similar logic from another angle. The SEC argued that the company and its former CEO, Do Kwon, misled investors about TerraUSD’s stability and real-world adoption through the Chai payment app. In 2024, Terraform and Kwon were found liable for securities fraud.

‍

The line between planning and expectation-setting is blurry – but visible

A healthy communication strategy gives the audience a sense of direction while keeping uncertainty visible: which parts are still exploratory, and what depends on execution.

The tension arises when the audience is no longer reading “plans” neutrally:

• A feature in the pipeline feels close to release.
• A possible integration sounds like a near-confirmed partnership.
• A long-term ecosystem goal looks like adoption already in motion.

The same message can also change meaning depending on context. “We’re in talks with partners” reads one way in a quiet product update and another way:

• after a teaser campaign,
• during token speculation,
• near a listing, unlock, or fundraising round,
• or during a rally.

‍

Timing, channel, speaker, and previous hints can turn a cautious statement into a market catalyst.

‍

Missing context causes similar problems. For example, a roadmap may describe anticipated milestones while leaving out the conditions behind them: governance approval, regulation, technical execution, liquidity, or security review. When the upside is visible but the constraints are not, the future starts looking more certain than it actually is.

Community behavior can push the message even further. Hype becomes more sensitive when teams:

• appreciate speculation with likes;
• answer with hints;
• leave obvious rumors uncorrected;
• or let moderators speak more confidently than official materials allow.

A disclaimer sits at the end of that chain. It can clarify a careful message, but it can’t neutralize what was assertive by default. 

‍

Teams need a shared system for talking about what comes next

Before anything shows up in public, everyone involved should agree on the actual status of what is being announced. Is it already live, in development, in beta testing, planned, or only a hypothesis? These categories should stay consistent across all decision-makers and communication channels.

The same discipline applies to dependencies. If a roadmap point relies on something else, that uncertainty should remain visible. This doesn’t mean every update has to read like a legal memo. The audience should understand what is confirmed, what is conditional, and what may change along the way.

Some expectation-setting topics also require stricter internal validation before publication. Anticipated utility, listings, partnerships, economics, user growth, revenue, adoption, AI integrations, and infrastructure launches stop being ordinary content themes once they sit close to a token. This is why PR, marketing, community, founders, and legal need to work from the same risk framework.

Delays and pivots are just as important. If expectations were created publicly, any changes should be explained clearly: what shifted, why, and what users should care about now. Replacing a missed milestone with another teaser only takes the risk further down the line.

‍

What matters is the impression the market walks away with

The final review should happen at the level of the entire message. A roadmap update can be technically accurate sentence by sentence and still leave the audience with a stronger conclusion than the team can support.

The headline, timing, channel, teaser history, founder comments, missing limitations, community reaction, and disclaimer all work together. Regulators may evaluate them the same way. That’s why product communication in Web3 needs a broader reality check before publication. 

Key questions to ask:

• What expectations does this update create?
• Does it make adoption, liquidity, or token value feel more certain than they actually are?
• Does it encourage people to associate potential upside with upcoming developments?
• Is the disclaimer clarifying the message – or trying to soften what has already gone too far?

None of this makes roadmap communication sterile. Projects can show direction, build confidence, and keep users engaged. The point is that they should prevent speculation from filling in the gaps on its own.

‍

This article is part of Outset Legal Lens. In this series, we’ll keep unpacking the legal side of Web3 communication, with a focus on helping teams speak clearly, responsibly, and in a way that supports the long-term growth of the industry.