Why does a Web3 project need its own Substack publication?
Substack helps you combine a newsletter, a web archive of issues, and publication recommendations in one place. For a Web3 team, it's an opportunity to regularly explain the product, publish research, and share updates in a format that goes beyond short social media posts.
We tailor the format to the task, rather than turning every issue into an advertisement. A publication can be useful if the project needs to:
- explain the product and its changes in clear language;
- share market notes, analytics, or educational materials;
- give founders and experts a platform for their own perspective;
- maintain contact with an interested audience between key events.
Before launch, we clarify who will read the newsletter, what questions these people need answered, and what topics the team is allowed to discuss. Based on this, we propose an editorial role for Substack relative to other platforms. If you are comparing different channels, also look at promotion on platforms: the goal is to choose a combination of formats that the team can sustain.
How to choose a topic and create an editorial calendar
Positioning answers a simple question: why should a reader subscribe and return to the publication? We formulate it through the audience, the value, and the level of depth acceptable for the project, then turn it into repeatable sections and an issue plan.
At the start, it's useful to prepare:
- a brief description of the product, its audience, and current priorities;
- a list of topics the team can comment on in their own name;
- links to documents, research, and materials that can be used;
- the names of experts and authors willing to participate in preparing issues;
- topics that require separate verification or approval.
The calendar can combine market notes, project updates, research, and interviews. Each topic should have a clear reader question, an author or expert, and a next step for preparation. We align the plan so that issues support each other, rather than repeating the same announcement. If the project needs separate work on materials, this can be supplemented with crypto content creation or educational content.
What we set up in a Substack publication
Before the first issue, we make the publication ready and consistent: the reader should understand who is writing, what the newsletter is about, and what to expect after subscribing. The setup covers the name, About description, welcome email, and visual design within the project's materials.
Then we agree on editorial parameters: tone, issue structure, fact-checking process, and who approves the final text. If necessary, we set up free and paid tiers. The decision on paid access is made after discussing the value of the materials and the team's readiness to regularly support the chosen format; the mere existence of a paid tier does not replace a substantive offering.
| Element | What we agree on |
|---|---|
| Publication description | Audience, topic, and value of the subscription |
| Welcome email | Tone of the first letter and reader expectations |
| Issue | Format, authorship, sources, and approval |
| Tiers | Free format and paid access, if needed |
We ask you to designate a person responsible for final approval in advance and to provide up-to-date links to project materials. This way, the editorial work is based on the team's source data, not assumptions.
How to use Notes and recommendations for growth
Notes and recommendations help connect the main newsletter with other publications on Substack and make audience engagement part of the editorial plan. We view them as separate communication formats, not as a replacement for strong issues or clear positioning.
For Notes, we define the topics and the author's voice in advance: notes can continue an issue's idea, answer a reader's question, or introduce a project material. For recommendations, we select publications whose topic and audience match the project and prepare a clear context for interaction. This approach maintains the connection between what the newsletter description promises and what the reader sees in the publications.
We only include activities in the plan that the team can sustain. Before starting, it's worth agreeing on who is willing to write in their own name, what topics can be discussed publicly, and what materials can be recommended. We also link Substack with community channels to announce issues without copying the same text everywhere. Publications on other platforms can complement this work: for example, maintaining a blog on Medium is suitable for a separate format of materials and an external archive.
How the process, approval, and reporting work
Work begins with an introductory meeting and collection of source materials, after which we agree on positioning, design, and the calendar. Then we prepare texts on approved topics, conduct editorial and fact-checking, submit materials for approval, and publish according to the agreed plan.
To prevent the process from depending on lengthy correspondence, we fix the decision-maker from the project side, feedback deadlines, and the procedure for making edits. For expert topics, we clarify in advance who checks special terms and primary sources. The project needs to provide up-to-date data, links available for publication, expert comments, and timely confirmation of final versions.
In reporting, we collect the metrics specified in the service description: subscribers, opens, and archive visibility in search. We explain what the available data reflects and connect observations to the editorial plan: which topics to continue, what to clarify in the format, and what materials to prepare next. Such a Readout is useful not as a set of numbers in itself, but as a basis for the next cycle of decisions. The specific composition of publications and the rhythm are agreed upon before work begins.
What results Substack does not control and what to do next
Substack is suitable for consistent work with an audience, but it does not give the editorial team control over how readers react to emails or which publications they find through search or recommendations. Therefore, we do not promise a specific number of subscribers, opens, or the archive's position in search; we plan months of work and are responsible for agreed-upon materials, setup, and reporting.
Before starting, check if the team has the resources for regular expert comments and who will quickly confirm facts. Clarify what information about the product can already be published, whether ready-made visual materials are available, and whether a paid subscription is needed now. If several people are responsible for content, designate one person for the final decision — this helps maintain consistency and avoid delaying an issue.
If the newsletter needs support from other channels, we will help connect the editorial calendar with the project's overall communication. Start by sending a brief description of the product, target audience, desired topics, and available materials. MediaHype will conduct an initial assessment of the task, propose a publication structure, and agree on a plan for launching and managing the Substack.
Prices
| Service | Price | Quote |
|---|---|---|
| Medium Publications | from $500 / month |
Starting prices in USD. Custom bundles and volume discounts on request. Payment in USDT, USDC, BTC, ETH, SOL, TON or your project token.
How it works
- Gather initial informationWe clarify the audience, project goals, available sources, and publication restrictions. You appoint a person responsible for approval.
- Agree on positioningWe formulate the newsletter's topic, its value to the reader, and suitable issue formats.
- Set up the publicationWe prepare the name, About page, welcome email, and design; if necessary, we discuss free and paid tiers.
- Prepare and publish materialsWe work according to the calendar, verify agreed-upon sources, and submit issues to the team for approval.
- Analyze and adjust the planWe compile a report on subscribers, opens, and archive visibility in search, then refine the next topics.
Frequently asked questions
What exactly is included in managing a Substack for a Web3 project?
The service includes publication setup, positioning, editorial calendar, content preparation and editing, working with Notes and recommendations, and reporting on subscribers, opens, and archive visibility in search. The exact composition of issues and scope of work are agreed upon before starting.
How much does it cost to launch and manage a newsletter?
The cost starts from the scope of work the project needs: the service price starts from $500 / month. Before work begins, we clarify the tasks, composition of publications, and the format of your team's involvement, then we fix the agreed-upon scope.
When can we expect the first results?
First, the team agrees on positioning, design, and the issue plan; then regular publication begins. Substack is a channel for consistent work, so we plan development over months, rather than expecting an immediate effect.
Does the project need to launch a paid subscription right away?
No, a paid tier is not necessary for every project and not necessarily at the start. First, you should determine what materials will be available for free, what additional value a paid reader will receive, and whether the team can regularly support it.
What materials need to be prepared before launch?
Send us a description of the product and audience, current links, a list of topics and experts, and information the team allows to be published. It's useful to immediately appoint a person for fact-checking and final approval of issues.
Can you guarantee subscriber or open rate growth?
No. Audience growth on Substack is organic and gradual; reader behavior, recommendation reach, and archive visibility in search are not under the editorial team's control. We are responsible for agreed-upon settings, materials, calendar work, and reporting, but not for a specific number of subscribers or opens.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…