content-plan
A crypto content plan by stage: launch, growth, scale
How to build a crypto content plan for X by project stage: five rubrics, a default mix per stage, best days to post each one, and a sample two-week calendar.
A crypto content plan should start from your project's stage, not from a list of post ideas. Pick the stage you are in (launch, growth or scale), give each of five rubrics its share of the month, place every rubric on the weekday it works best, and let real facts from your team take the slots that need them. The rest of this article is the method we use to build that plan, with our default percentages, a sample two-week crypto content calendar, and the signals that tell you when to move to the next stage.
If you want the wider picture of running an account on X first, start with the hub: crypto Twitter marketing.
Why a crypto content plan starts with the stage
Most crypto calendars fail in one of two ways. Some are a stack of ideas with dates attached, so the account posts whatever was easiest to write that morning. Others copy a mature project's feed: partner announcements, volume milestones, "we're live on another exchange", from an account nobody follows yet.
The stage fixes both problems. A project in its first two months needs people to find it and understand it, so the feed leans on education and community. A project people already know needs to show that it ships and to turn attention into users. A project with a working product and incoming attention needs social proof and needs to look after the people who got it there. Same five rubrics, very different proportions.
The later your stage, the more of your plan depends on facts only your team has: a release date, a metric, a signed integration. In the plans we have built by hand, roughly 30% of slots at launch were tied to such facts, and about 70% at growth and scale.
The five rubrics
Every post in the plan belongs to one of five rubrics. They cover everything a project account needs to publish, and keeping to them makes the mix measurable.
| Rubric | What goes in it | What it does for you |
|---|---|---|
| Community & contests | Giveaways with real mechanics, Spaces and recaps, running jokes, quizzes, AMAs | Turns followers into people who show up every day, not only at TGE |
| Product & project updates | Ship logs, releases, changelogs, dev notes written for CT | Proof that you are building, especially between big announcements |
| Educational / reach | Hook-first threads and explainers about your niche | Gets bookmarked and quoted, brings new people to the account |
| Status & traction | Volume, integrations, listings, partners, press, grants | Makes the project credible beyond the chart |
| Conversion | Deadline posts, bridge and deposit guides, points reminders, offers | Closes the loop, turns attention into action |
Two rules sit on top of the table. Updates, status and conversion posts live on facts, so if the fact is missing, the slot stays empty and goes to your team as a question. It never gets filled with something plausible. Educational posts and contest mechanics are the only rubrics you can plan freely from the brief.
Links go in the first reply under the post, not in the post body. That applies to every rubric, including conversion.
Default mix by stage
These are the defaults we start from. They get adjusted per project, but they are a good first draft for any crypto content calendar on X.
| Rubric | Launch | Growth | Scale |
|---|---|---|---|
| Community & contests | 35% | 10% | 20% |
| Product & project updates | 15% | 20% | 15% |
| Educational / reach | 35% | 20% | 10% |
| Status & traction | 5% | 15% | 30% |
| Conversion | 10% | 35% | 25% |
Launch: get found and worth following
Your first two months. Community and education carry 70% of the feed between them, with enough product proof to show there is a real team behind the account. Status is almost absent because you have little to report yet, and posting thin milestones early does more harm than posting none.
Conversion is kept low, and in our plans it is also kept out of the first 40% of the period. There is nobody to convert until there is an audience. Launch periods open with a contest on day one, because a contest gives new visitors a reason to reply and follow right away.
At this stage contests attract: a meme contest, a quiz, questions collected for an AMA. Education does the heavy lifting on reach, so the threads matter. Our guide to crypto Twitter threads covers how to write ones that travel.
Growth: prove you ship, then ask
People know your name. Conversion takes the largest share at 35%, because now there is someone to ask. Updates rise to 20%, since the fastest way to earn a conversion post is a week of visible shipping before it. Education drops to 20% but does not disappear: it keeps bringing in the audience that funds the next step.
Growth is also where a fixed weekly recap appears. In our plans for growth and scale, Friday late morning is a standing slot for the week in review: what shipped, what moved, what is next.
Scale: hold the narrative, reinvest in your people
The product works and attention is coming. Status becomes the largest rubric at 30%, because social proof now has something real behind it. Conversion stays high at 25%. Education falls to 10%, since your audience already understands the niche.
Community climbs back to 20%, and its purpose changes. At launch contests bring people in; at scale they keep people around: ambassador seasons, weekly leaderboards, content contests for your existing holders and users. Scale periods, like launch periods, open with a contest on day one.
When to post each rubric
The best day depends on the rubric, not on the stage. These are the defaults we plan against.
| Rubric | Best timing | Why |
|---|---|---|
| Community & contests | Thursday to Friday | People have weekend time to enter; winners drop Monday and carry the buzz into the new week |
| Product & project updates | Tuesday to Wednesday | Peak attention, desks at screens. Never Friday night: weekend releases vanish |
| Educational / reach | Monday morning | CT is rested and in bookmarking mode, so a Monday thread earns the longest tail of quotes |
| Status & traction | The same day it happens | Numbers are news for 24 hours and history after. Post same day, resurface in the weekly recap |
| Conversion | A reminder 48h out, last call 6h before | Timed for US evenings, when wallets are awake |
Daily volume stays modest: one or two posts a day, three at most. The plan also includes days off, four a month by default. The mix is calculated across working days only, so a month with four days off simply has fewer posts at the same proportions. A human team does not post every day at even intervals, and an account that does looks automated.
A sample two-week crypto content calendar
Here is a two-week plan for Vaultic, a fictional stablecoin yield vault in the growth stage. Over 14 days the growth mix works out to five conversion posts, three educational, three updates, two status posts and one contest. Vaultic is running a points season with a snapshot at the end of week two, so the conversion slots form a ladder: open, explain, remind, last call, what's next.
| Day | Rubric | Topic | Source |
|---|---|---|---|
| Mon, week 1 | Educational | Thread: where stablecoin vault yield actually comes from, and what to check before depositing | Topic bank |
| Tue, week 1 | Update | Ship log: what went live this week, with the fixes users asked for in replies | Team roadmap |
| Wed, week 1 | Conversion | Points season opens: how points are earned, snapshot date, guide in the first reply | Team offer |
| Thu, week 1 | Community | Reply contest: your worst yield-chasing story, winners announced Monday in the thread | Mechanics bank |
| Fri, week 1 | Status | Week in review: shipped items and the metrics the team confirmed | Team metrics |
| Sat, week 1 | Educational | Short explainer: how to read a vault's risk disclosures | Topic bank |
| Sun, week 1 | Conversion | Soft CTA: deposit walkthrough for people with weekend time to try it | Team offer |
| Mon, week 2 | Educational | Thread: what separates real yield from incentive emissions | Topic bank |
| Tue, week 2 | Update | Integration live, what it changes for depositors | Team roadmap |
| Wed, week 2 | Update | Dev notes: what the team is building next and why | Team roadmap |
| Thu, week 2 | Conversion | Reminder: 48 hours until the points snapshot | Team offer |
| Fri, week 2 | Status + Conversion | Morning: week in review. Evening: last call, 6 hours before the snapshot | Team metrics, team offer |
| Sat, week 2 | Conversion | Snapshot done: what points holders get next and when the next season is announced | Team offer |
| Sun, week 2 | Day off | - | Rhythm |
Every update, status and conversion slot points to something the Vaultic team provided. If the integration had slipped, that Tuesday would stay empty and flagged instead of carrying a vague "big things coming". Friday carries two posts because the recap and the last call both have fixed timing. Contest winners are announced inside the contest thread, which keeps Monday for education.
For a launch-stage project the same two weeks look very different: five educational threads, five community posts, two updates, one status post, one conversion post, with that conversion post held until the second week.
The posts are half the work. Each slot also needs replies: answering everyone in your own threads in the first hour, and replying early under the accounts your audience reads. That side has its own playbook in crypto Twitter reply strategy.
Where the facts come from
Before writing a single topic, collect four kinds of facts from your team:
- Dated events: releases, integrations, listings, audits, press, grants. Only future dates go in the plan; past ones are background for the writers.
- Standing offers: anything a user can do on any day, such as an open pool, a points program or a referral scheme.
- Current metrics you are comfortable repeating: TVL, users, volume, audits completed.
- Weekly features: a fixed day, rubric and format, such as a Monday market note or a Friday recap.
Facts outrank proportions. If you have three real launches in two weeks, the plan runs update-heavy that period and the mix catches up later. Check every number against its source before it goes out: DefiLlama, Dune, your docs or your own dashboard.
The educational slots are the only ones you can fill from the brief alone. Build them from your audience's pain points, your edge over alternatives, and questions people keep asking in your replies. The X algorithm guide explains why posts that spark real replies travel further than posts that only collect likes.
How to move between stages
Change the stage at the start of a new period, not in the middle of an approved plan. Switching mid-month reshuffles slots your team already signed off on.
There is no follower count that marks the switch. These signals are more reliable:
Launch to growth. You have something people can act on: a live product, an open pool, a points program. Your replies include people asking how to use it, not only what it is. Your update slots fill easily because the team ships on a schedule.
Growth to scale. Status slots stop coming back empty. If, during planning, you can fill two or three status posts a week with confirmed numbers, integrations and outside recognition, you have enough proof to make status the largest rubric. If those slots keep getting flagged for a missing fact, stay in growth.
Staying put is fine. A project can sit in growth for a long time. Moving to scale because it sounds bigger, then padding the status rubric with weak milestones, reads as insecurity.
A strategist should make this call with the team rather than having it switch automatically. At Grapevine a strategist sets the stage and the voice with you and builds the first two weeks of the plan by hand; after that, an AI agent drafts the daily volume against the plan, our team reviews every draft, and the strategist reviews the plan weekly. Prices are on the pricing section.
FAQ
How many posts a day should a crypto project publish on X?
One or two, three at most. Consistency matters more than volume. Spread them through the day, answer the replies they get, and plan a few days off each month so the account keeps a human rhythm.
What is the best day to post a thread about a crypto project?
Monday morning for educational threads, when people are in bookmarking mode. Product updates do best Tuesday to Wednesday, contests Thursday to Friday, and milestones on the day they happen.
What should I do if I don't have a milestone to post that week?
Leave the slot empty and ask your team for the fact, or move the slot to an educational post. Never fill a status or update slot with a vague teaser; the audience notices when the numbers are missing.
Should a crypto content calendar include price or token performance posts?
No. Keep price talk, price predictions and investment language out of the plan. Status posts cover usage, integrations and recognition with sources, which builds credibility without the legal and reputational risk.