A Base plan begins with the next conversation
A useful Base plan starts with one clear audience and one next action. It then chooses a small set of channels your team can keep active. We begin with the product story, rather than assuming that every Base-connected project needs the same promotion.
A short brief can help us see what is ready and where a new visitor might need more context. We ask about the product, intended audience, next milestone, and who can respond to questions. Our first-pass review checks whether the public message explains what the project does before it describes its ecosystem connections.
| Starting point | Useful when | First thing to prepare |
|---|---|---|
| Product explanation | People need to understand the offer | A plain-language description |
| Community conversation | You want to hear or answer questions | A named responder and discussion prompt |
| Milestone communication | A release or update needs context | The announcement and its next action |
This is a working choice, not a permanent channel map. If your project is weighing more than one network, our marketing by blockchain overview can help frame the comparison. We keep the decision tied to your audience and the work your team can support.
The channel choice should fit the work you can show
Picture an NFT artist with a small following, deciding which channel to start with. They are considering Aerodrome, Zora, and Farcaster, but have limited time to explain the work. We would first ask what they want people to understand, then help them choose a useful first conversation.
The point is not to appear everywhere. It is to make the project easy to understand wherever you do show up. Aerodrome, Zora, and Farcaster should each earn a place in the plan. Each needs a clear connection to your product, audience, or next milestone.
We look at the material you already have, then agree on what needs adapting. That might mean a short introduction or a message for a specific community. It might also mean a clear route to more product information. We also make sure someone on your team can answer the questions that follow. For a broader view of network choices, see our Ethereum marketing page. It can help clarify which parts of your story belong to Base and which travel across ecosystems. The useful test is whether the proposed activity helps a real person take the next step.
What should each Base channel help a person understand?
Each channel should make one part of your project easier to understand. Agreeing on that purpose first keeps your posts from repeating the same introduction without giving people a reason to continue.
Start with the reader
Write down what someone arriving for the first time should understand. Keep it to a product, a useful distinction, or an action they can take. If the answer needs a long explanation, prepare the explanation before asking for attention.
Give each channel a reason
Consider Aerodrome, Zora, and Farcaster separately. Ask what the project can contribute to each conversation and what material would make that contribution clear. A channel is a poor fit if the team has no relevant message or no one available to reply.
Make the next action visible
A person who is interested should know what to do next. That could be visiting a project page, reading an explanation, or joining a relevant conversation. Connect each activity to one action, then check that the destination is current. Teams comparing community work across networks can also look at community growth and engagement. The useful test is whether the proposed activity helps a real person take the next step.
A small review loop keeps the plan usable
A light review loop helps your team keep the Base plan current without turning it into a reporting project. We agree on the work, name one owner for each activity, and decide what evidence to check together.
- Gather the basics. Collect the project description, current links, and next milestone in a 3-part brief.
- Choose the activity. Match a message and format to the audience and the channel’s purpose.
- Name the owner. Confirm who approves the message and who answers follow-up questions.
- Check what happened. Use 2 review points: what was published, and what response or next action can the team observe.
- Choose a next move. Keep, revise, or pause an activity based on what the team learned.
Say a team is preparing an update and has already drafted several messages. We would check that the product details agree, choose which message suits each channel, and make sure someone can respond afterward. At Brand Community, we record completed work and the observations in a clear weekly note. We can also compare the plan with trending campaigns when a visibility placement is part of the discussion.
Keep Base activity tied to what your team can verify
A sound Base plan separates the work your team can direct from the response it can only observe. Your team can approve its message, prepare public materials, set a publishing schedule, and confirm who handles replies. We can document the agreed work and share a clear record of what was completed.
Platform display and community response are not ours to decide. Farcaster visibility and attention around Aerodrome or Zora may shift with platform choices and user activity. We don't promise a particular position or level of attention. We focus on the agreed work and the evidence your team can inspect.
Before we begin, bring your project link, a short product description, the audience you have in mind, and the next milestone. Tell us who approves messages and which channels you are considering. We’ll review those materials with you, return a practical first plan, and agree on the next step together.
Frequently asked questions
Can a project use Base marketing before its product is live?
Yes. Before launch, you can prepare a clear explanation, choose who will answer questions, and decide which message belongs with the milestone. For example, a team with a draft product page can review whether a new visitor understands the offer before sharing it. The plan should match what you can show today.
Do we need to use Aerodrome, Zora, and Farcaster together?
No. Treat them as separate options, not a required bundle. We look for a clear reason to include each one, such as a relevant audience or a message your team can support. If one has no useful role in your current plan, start elsewhere and keep the choice open for later.
What should we have ready for a first Base marketing discussion?
Bring your project link, a short description, the audience you want to reach, and your next milestone. Add links to current public materials and name the person who can approve messages. If something is unfinished, say so; we can identify what to prepare before planning channel activity.
How do we tell whether a Base channel is worth continuing?
Decide what you want to learn before sharing anything. Record what was published, what relevant questions came back, and whether people took the intended next action. A message that leads to useful questions may be worth revising. A post with attention but no clear connection to your goal may need a different purpose.
Can you promise a particular level of visibility on Farcaster?
No. We can agree on the work to prepare, publish, or place and show you what was completed. Farcaster determines how its content is displayed, while user activity shapes the response. We’ll set the plan around clear tasks and review the visible response with you, rather than promising a position.
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…