Which project details belong in a Cosmos campaign brief?
The first working artifact is a project map with 4 fields: product, chain, audience and user action. That map keeps ecosystem language tied to facts your team can confirm. It also gives each channel a consistent reference before copy is drafted.
Send a short description of what the product does, who uses it and what those users should do next. Add the chain where the product operates and identify any IBC connection that matters to the user journey. Mark each integration as live or planned. The distinction prevents campaign copy from presenting future work as an available feature.
The brief should also identify a person who can approve technical claims. We review supplied materials before turning them into campaign language. If a claim has no supporting product page, documentation or approved explanation, we flag it for review. We do not fill the gap with broad ecosystem wording.
Use this checklist to prepare the first version:
- Product summary and current status.
- Chain and relevant IBC connections.
- Up to 3 priority audiences and their questions.
- Approved links, claims and the intended next action.
For a broader view of network-specific planning, see marketing by blockchain.
What should an IBC explanation show a potential user?
A user-facing IBC explanation should show the route, the supported action and the information a person needs before acting. Those details matter more than a general claim about interoperability. We base campaign copy on the project’s current documentation and confirmed user journey.
Build the explanation in 3 parts. First, name the relevant chains or product components. Next, describe what the user can do through the connection. Finally, link to instructions that show any required steps. If an asset transfer or data exchange is involved, describe only the route and functionality the project can substantiate.
We keep separate notes for 2 statuses: available now and planned. That simple division helps reviewers check announcements and social copy. It also gives reviewers a way to check longer explainers against the same source material. This division gives your team a clear place to update when product details change.
A useful review asks whether a new reader can answer these questions from the copy: What product is involved? What does the connection let me do? Where can I verify the steps? If the answer relies on familiarity with Cosmos terminology, add a plain-language explanation before publication. For channel context beyond the technical explanation, compare this work with community growth and engagement.
When does Osmosis belong in the project’s message?
The audience map shows whether Osmosis has a concrete role in the product story. Mention it when the project’s users, use case or confirmed activity make that connection relevant. Do not add the name simply to make a campaign sound more connected to Cosmos.
We assess the proposed reference against 3 checks: Is the connection current? Can the project explain what a user can do with it? Does the audience need that detail to understand the product? If the materials do not support a clear answer, the campaign stays focused on the project’s verified use case.
This decision affects the message, not just the channel list. A developer-facing explanation may need a technical integration reference. A user-facing post may need a simple description of the benefit and a link to instructions. Partner communication may instead explain the project’s role and coordination needs.
Write each version from the same approved facts, then adjust the amount of detail for the reader. That gives the team distinct content without suggesting that Osmosis endorses the project or that every Cosmos audience shares the same priorities. If editorial coverage is part of the plan, review PR and media as a separate channel option.
What should a Cosmos campaign delivery record contain?
The delivery record should connect each published item to its audience, intended action and evidence of completion. It makes campaign activity reviewable without treating a published placement as proof of audience response.
We agree on the reporting format at kickoff and track 4 fields for each activity: content or placement, destination, target audience and delivery evidence. The record can include publication links, approved copy, placement details and questions raised during community activity. We label channel observations by source so readers can see what was directly recorded.
A typical review has 3 checkpoints: confirm the brief and source materials, review content before release, and compile the delivery record after activity. The number of review rounds and the overall schedule follow the agreed scope. Your team receives a shared readout that separates completed work from follow-up decisions.
Use the readout to identify explanations that need revision. It also shows which questions deserve a clearer answer and what the next campaign should address. If a visibility placement is included, the record should state its agreed format and provide available proof of delivery. See trending campaigns for a separate view of visibility-focused work.
Where does campaign delivery stop in the Cosmos ecosystem?
The delivery record can verify agreed messaging, coordination and placements; it cannot establish that an independent chain or audience will adopt a project. IBC availability, decisions by other ecosystem participants and third-party channel display or editorial choices remain outside the campaign team’s control.
That boundary makes accurate project materials essential. Keep descriptions of live connections, supported actions and product status aligned with documentation your team can confirm. When a feature changes, update the source materials before using the old wording in another campaign asset.
For a scoped recommendation, send GeoMarketing Experts a product overview, the chain and IBC context, approved documentation, priority audiences and any timing constraints. Include the contact who can review technical statements. Those inputs give the review a source record for checking campaign language. We will check the materials, flag open questions and return a channel plan with proposed deliverables for your team to assess.
Frequently asked questions
How can we tell whether an IBC detail is ready for campaign copy?
Use it when your team can verify the connection, the available user action and the relevant instructions. A reviewer should be able to trace the claim to approved documentation or a product resource. Mark planned integrations clearly, and keep them separate from features users can access now.
Does an Osmosis mention make sense for every Cosmos project?
No. Include Osmosis when it has a specific, verifiable role in the product or user journey. Check whether the connection is current, whether users can act on it and whether the detail helps explain the offer. If those points are unclear, keep the campaign focused on the project’s confirmed use case.
What materials should we share before a Cosmos campaign review?
Share a product summary, chain details, relevant IBC information, approved documentation and the audience you want to reach. Include the action readers should take and name one person who can approve technical claims. Those inputs give the review a source record for checking campaign language.
How do you report what was delivered for a Cosmos campaign?
We record each activity with its content or placement, destination, audience and delivery evidence. The readout separates completed work from channel observations and audience response. This gives your team a usable record for reviewing what ran and deciding which messages or materials need another pass.
Can a campaign secure adoption across IBC chains?
No. The campaign team can deliver agreed content, coordination and placements, but cannot direct decisions by independent chains or control third-party channel display choices. We document completed work and keep claims about live connections tied to approved project materials. Adoption remains an outcome to observe, not a campaign deliverable.
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…