A private working arrangement, with circulation kept narrow
Your project details remain confidential within the working arrangement until you approve what may be shared. One named point of contact coordinates the review, keeps questions together and confirms which materials are ready for wider circulation.
At the outset, we establish what is private, what is already public and who may approve publication. Product notes, launch context and draft language stay with the people handling the work until you give written sign-off. Nothing leaves the desk as campaign material before that approval.
This makes the first conversation useful without requiring a public announcement or a finished campaign. You can share the current product description, documentation and relevant community links, then clarify which details are not for circulation. Your contact keeps those boundaries visible as the message and channel plan take shape.
The product comes before the ecosystem shorthand
A useful Cosmos message explains what a person can do with your product before describing its wider ecosystem context. IBC chains or Osmosis belong in the story where that connection changes the user experience, not as a substitute for a clear product explanation.
We organize the message around three practical points: who the product serves, what it supports today and what evidence backs each claim. The level of detail can then suit the reader: an introductory post can establish the purpose, while an explainer or documentation can address setup and use.
Before a draft is prepared, it helps to have:
- A current product description and status
- The user actions your product supports through IBC or on Osmosis, where relevant
- Documentation or other reliable material supporting public claims
For network-specific context beyond Cosmos, see marketing by blockchain. If user questions and ongoing conversation need attention, community growth and engagement can sit alongside the messaging plan.
The arrangement in three approval points
The approval sequence gives you a clear view of what is being prepared and when your decision is needed. The named contact keeps the stages together, so the public message follows the product facts you have confirmed.
| Step | Who is involved | What you approve |
|---|---|---|
| 1. Context | Your project contact and our named contact | Product status, audience and details that remain private |
| 2. Draft | Our contact prepares the proposed message and channel use | Claims, wording, links and any material for publication |
| 3. Delivery | The agreed channel owner and our contact | The completed materials and record of where they appeared |
The sequence is intentionally simple. If a proposed claim needs clarification, it returns to you before publication rather than being inferred from general ecosystem language. You may also identify a separate decision-maker for technical details, while keeping one person responsible for final sign-off. The working plan records ownership and the evidence to collect for each agreed activity.
Which channels suit the Cosmos audience you need to reach?
The appropriate channels are those your intended audience can use to understand and assess the product, and that your team can support after publication. We connect each channel to a purpose, a responsible owner and a next step for the reader.
A project website and its documentation should carry consistent product information. Community spaces can address practical questions, provided someone is responsible for replies and escalation. Editorial coverage suits a relevant, supportable announcement; a PR and media plan can give that story a considered structure. Creator activity may fit when the audience and format are appropriate, with message and disclosure expectations agreed in advance; see KOL and creator campaigns.
The channel plan notes the material required, its owner and how delivery will be verified. This gives you a composed route from discovery to reliable product information, rather than repeating one announcement everywhere. The final selection follows your audience, available materials and capacity to maintain the channels.
A measured delivery, with a clear record at the end
Delivery follows the approved plan, with agreed materials checked and recorded by channel. The timing is set after the initial review, taking account of the available documentation, decision-makers and publication sequence.
- Prepare: Your contact gathers the current product information, audience priorities, community links and launch context.
- Approve: We present proposed messaging and channel activity; you confirm claims, links and publication materials in writing.
- Record: We note published or shared materials, placement links, status and follow-up actions in a channel-by-channel report.
The report distinguishes completed work from audience response, which the team can observe but not direct. That record gives you a practical basis for deciding what to continue, revise or set aside. A launch window, the relevant chain, or the person signing off is the most useful first detail. Your named contact will place it beside the current materials and prepare the first approval draft for your consideration.
Frequently asked questions
What should we prepare for a private Cosmos marketing discussion?
A current product description, documentation, community links and a short note on the audience are a useful beginning. Include how IBC chains or Osmosis relate to the product only where that connection matters to users. Your named contact can also record which details must remain confidential until you approve their use.
How should we describe an Osmosis connection in campaign materials?
Describe the connection in terms of what users can currently access and where they can find dependable instructions. A draft should distinguish confirmed product capabilities from planned work. We present that wording for your sign-off, so you can confirm both the factual detail and whether the Osmosis reference belongs in the message.
Can you coordinate community and creator activity for an IBC project?
Yes, when those formats suit the audience and the team can support them. The plan can assign an owner for community questions and set the intended message and disclosure expectations for creator activity. Your contact keeps those items alongside the approved product explanation and records agreed delivery.
How do we know which channel activity was completed?
The channel-by-channel report records agreed materials, links, status and follow-up actions. Before work begins, the plan identifies what evidence will be collected for each activity. Your named contact can clarify the record with you, keeping completed placements distinct from audience response.
From a founder’s side, can you guarantee visibility across IBC chains or on Osmosis?
No. We can agree on specific marketing work and verify its delivery, but independent chain teams, community response and third-party publication decisions remain outside our control. IBC participation and visibility on Osmosis are not outcomes a campaign can secure. Materials describe only product capabilities you have confirmed.
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…