Which protocol facts belong in the first campaign brief?
The first brief records your staking model, incentive details, user journey and integration status. Those inputs show where messaging can be specific and where your team needs to confirm facts before publication.
We map the information across 3 audience groups: stakers, integration partners and broader crypto audiences. Each group needs a different explanation. Stakers need a comprehensible account of the product and its incentives. Partners need confirmed integration details and agreed announcement responsibilities. Broader audiences need context that does not assume prior knowledge.
Prepare these 4 items before kickoff:
- A current description of the staking model and user journey.
- Confirmed incentive details and relevant user disclosures.
- Live and planned integrations, with partner contacts and status.
- Existing content, brand guidance and priority audiences.
This makes review more useful than starting from a broad growth objective alone. We compare the source materials with the claims you want to make. Then we flag missing details for your team or partner to verify. The result is a factual base for content and co-marketing, not a substitute for product documentation. For related project work, see DeFi marketing or browse solutions by project type.
How should staking messages connect to an integration announcement?
A partner announcement needs two verified parts: what the integration enables and how it relates to the staking product. We keep those details distinct from general incentive messaging, so each audience can understand the specific information being shared.
We review the protocol materials first. Then we shape a core explanation for stakers and a separate set of details for each partner communication. Before drafting is final, your team and the partner confirm the shared benefit, names, publication responsibilities and next action. This review gives both sides a clear approval point.
The campaign can include:
- Positioning that reflects the protocol’s staking model.
- Educational content explaining incentives and the user journey.
- Co-marketing copy and coordination with integration partners.
- Channel recommendations matched to the audience and announcement.
Use one approved source of product facts across these materials. If a planned integration changes, update that source before revising partner copy. This helps prevent an announcement from describing planned work as a live feature. Creator distribution can support partner communications through KOL and creator campaigns. For ongoing campaign execution, compare the scope with a growth marketing retainer.
What will the liquid staking team receive each week?
Each weekly report records 3 activity measures: reach, engagement and integration activity. Together, they give your team a consistent view of published campaign work and partner communications.
The report is an activity record, not a claim about staking decisions. Read it alongside the materials delivered and the status of partner announcements. That comparison helps identify whether the campaign has reached its intended audience, prompted engagement or advanced an integration communication. It also gives the team a basis for choosing what to clarify next.
The campaign deliverables are organized around the work itself:
- Messaging grounded in confirmed protocol details.
- Educational content for staker audiences.
- Co-marketing materials coordinated with integration partners.
- Weekly reporting on reach, engagement and integration activity.
For an effective review, your team should keep partner status current and share relevant publication updates. We record the agreed activity in the weekly report, so the protocol team can follow what has been delivered without combining unrelated measures. Broader announcement support may also fit with PR and media. If community education is a priority, consider community growth and engagement.
What marks each stage from protocol brief to weekly readout?
The campaign follows 5 practical stages: share context, agree on audiences and claims, prepare materials, coordinate publication, and review weekly activity. Delivery usually spans several weeks, with the sequence shaped by your priorities, review time and partner readiness.
At the start, we review your overview, incentives, user journey and integration pipeline. We identify which details need confirmation before drafting. Next, we agree on priority audiences and the claims each material can support. Your team reviews educational content; integration partners confirm their own announcement details and responsibilities.
The working sequence is:
- Context: provide protocol information, existing content and campaign goals.
- Alignment: confirm audiences, approved facts and partner communication needs.
- Preparation: develop messaging and educational materials for review.
- Coordination: confirm wording, publication responsibilities and timing.
- Review: receive the weekly activity record and assess next actions.
The time between stages depends on the campaign scope and approval flow. The team supplies factual product information and approves protocol claims. Partners confirm their integration details and publication plans. Weekly reporting gives the team a regular point to assess activity and adjust the next communication. See how we work for the wider delivery approach.
Which liquid staking outcomes sit outside the campaign record?
The campaign record covers the materials and partner activity delivered; it cannot record a platform decision as a controlled deliverable. Editorial policies and search or AI answer outcomes vary by provider. No agency can determine whether a provider will display or surface a specific protocol.
For public materials, keep the review focused on facts your team and partners can verify. Check that incentive descriptions match current protocol information. Confirm that user education explains the journey without overstating benefits. Ensure partner names, integration details and publication timing have approval. Mark planned work clearly so readers can distinguish it from a live integration.
A practical approval checklist is:
- Are incentive details current and consistent across materials?
- Does each announcement describe the confirmed integration accurately?
- Are responsibilities and publication details approved by both sides?
- Can readers tell confirmed features from planned work?
These checks improve the accuracy of what the campaign publishes. They do not change how an outside provider reviews or displays that material. Use the weekly report to review delivered activity and partner communications, then choose which approved message needs attention next.
How it works
- Share protocol contextSend the product overview, staking incentives, user journey and campaign goal. Include confirmed integrations and the status of planned partnerships.
- Align on audiences and claimsWe identify priority staker audiences, approved product facts and partner messages that need coordination.
- Prepare campaign materialsWe develop the agreed messaging and educational content. Your team and partners review details for accuracy.
- Coordinate publicationAfter responsibilities and approvals are clear, we support the agreed partner communications and campaign activity.
- Review weekly activityYou receive reports on reach, engagement and integration activity. The record supports decisions about the next campaign actions.
Frequently asked questions
What should our team send before campaign planning begins?
Send a current protocol overview, staking incentive details, the user journey and your primary campaign goal. Include live and planned integrations, partner contacts, brand guidance and existing educational materials. These 4 core information groups give us a factual starting point and show which partner details need confirmation.
How many weeks should we allow for this campaign?
Plan for a phased campaign spanning several weeks. The working timeline reflects the agreed scope, your team’s review availability and partner readiness. Integration announcements need partner confirmation, so share contact details and current status early. We map the sequence during planning rather than assume every partner follows the same approval path.
Can you help coordinate co-marketing with integration partners?
Yes. Coordination can include shared announcement copy, partner details, publication responsibilities and review points. Your team and each partner confirm their own information before materials are finalized. Send the integration pipeline and partner contacts at the start. That gives us a clear record of which announcements are live, planned or awaiting confirmation.
What information appears in the weekly report?
The report tracks reach, engagement and integration activity. It provides a weekly record of campaign work and partner communications for your team to review. Use it with the published materials and current partner status to decide what needs clarification or a follow-up. It reports activity rather than attributing staking decisions to a specific message.
Can you guarantee that search or AI providers will feature our protocol?
No. Editorial policies and search or AI answer outcomes vary by provider, and those decisions sit outside the campaign. We deliver the agreed messaging, educational materials and partner coordination, then report campaign activity. The weekly report records that work; it cannot promise a provider will display or cite your protocol.
How is this different from general DeFi marketing?
This scope centers on liquid staking incentives, education for staker audiences and coordination with integration partners. General DeFi marketing may address a wider product or ecosystem story. The campaign brief makes the distinction concrete by recording the staking model, user journey and partner status before materials are prepared.
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…