[SEP 41] [OBRA] Safe Ecosystem Roundups and Highlights by FinOps3

Title: Safe Ecosystem Roundups and Highlights by FinOps3

Authors: @LuukDAO , @JashFi

Abstract This proposal builds on the foundation created with FinOps3 to produce bi-weekly Safe Ecosystem Roundups published on the FinOps3 platform and social media and shared in newsletter format. In addition, 10 highlight campaigns in blog and video format will be produced with Safe Builders and stakeholders to showcase the quality and diversity of solutions built on Safe.

Aligned Strategy: Strategy 3: Increase awareness of Safe Ecosystem

Funding Request: 25,000

This proposal will cover the remainder of Season 3 (Sprint 4) and the entirety of Season 4 (Sprint 1-4). A period of approximately five months.

Relation to Budget: 35.9% of the remaining budget (69,500 USDC) - 10% of the initial budget (250,000 USDC) as indicated in the Governance Hub.

Metrics and KPIs:
The proposed initiative will impact the following KPIs:

  • Number of reads of bi-weekly ecosystem roundups across all channels (platform, socials, newsletter).
  • Total views and relevant CTA clicks in our highlight articles and platform.
  • Contribution to the overall understanding of the Web3 audience of Safe.

Initiative Description:
During the creation of FinOps3, it became clear that many Web3 teams and users have an outdated view of Safe. Besides small branding misalignments—many still refer to Safe as “Gnosis Safe” or sometimes simply “Gnosis”—it is clear that builders and users are still unaware of the vast ecosystem Safe has created.

We want to change the builder perspective of Safe, and grow the number of users and developers who embed Safe at the center of their onchain toolkit.

It all starts with Safe.

Over the past months, we’ve created the FinOps3 platform with dozens of Safe Ecosystem projects mapped and guides created. This proposal builds on top of that foundation to further enhance the understanding and growth of the Safe ecosystem.

What we’ll produce

  • At the core are bi-weekly Safe Ecosystem Roundups which will include ecosystem stats, tech updates, feature highlights, ecosystem news, and other timely updates that are relevant for new and existing Safe stakeholders alike. We expect to produce at least 10 of these Roundups, with the positive side effect that we will produce additional content and update our platform while working on these roundups. We learned during the initial FinOps3 application that continuous cycles are better for producing and growing quality content (vs. the “sprints” approach we incorporated early on).
  • We’ll produce 10 ecosystem highlights (projects/use-cases) in different formats. With FinOps3 we tested blogs and Twitter Spaces, but we haven’t identified a winning set-up yet. With this proposal, we aim to iterate on the highlighted format, for example - creating short in-person interviews (example of what our team did with Worldcoin) or blogs with custom visuals which can be used outside of the context of the specific article (for example a simple sheet cheat of onchain banking options.

Current Status:
The Safe Ecosystem Roundups will leverage the brand and platform of FinOps3 to build from. Our existing solution database will be expanded further and leveraged to source the best teams for ecosystem highlights. Our existing contribution to SafeDAO and involvement in the wider Web3 space will be leveraged to produce timely and exciting Safe Ecosystem Roundups.

Timeline and Milestones:

Milestone Deliverables Duration: $ Budget
S3 Sprint 4 Publish at least 2 Safe Ecosystem Roundups. Produce at least 2 Ecosystem Highlights. 1 month: $5,000
S4 Sprint 1 Publish at least 2 Safe Ecosystem Roundups. Produce at least 2 Ecosystem Highlights. 1 month: $5,000
S4 Sprint 2 Publish at least 2 Safe Ecosystem Roundups. Produce at least 2 Ecosystem Highlights. Produce a mid-term report and iterate on the format. 1 month: $5,000
S4 Sprint 3 Publish at least 2 Safe Ecosystem Roundups. Produce at least 2 Ecosystem Highlights. 1 month: $5,000
S4 Sprint 4 Publish at least 2 Safe Ecosystem Roundups. Produce at least 2 Ecosystem Highlights. Produce a final report and draft a follow-up proposal based on learnings. 1 month: $5,000
Total Publish at least 10 Safe Ecosystem Roundups. Produce at least 10 Ecosystem Highlights. Produce two reports. 5 months: $25,000

Risks:
The main risk is the produced content and distribution approach not contributing positively to the overall understanding and adoption of the Safe ecosystem.
To reduce this risk, we are taking a more data-driven approach and have incorporated rhythms to ensure we continue to grow, learn and improve over time.

Initiative Lead:
Kolektivo Labs

Team:
The team working on the Safe Ecosystem Roundups and Highlights will consist of the same team that developed FinOps3: lead LuukDAO, Analyst and Content Jash, and Design, Enrique.

Additional Support/Resources:

Implementation Dependencies:
No dependencies.

2 Likes
What name and approach do you think is most effective for the roundups?
  • Call it “Safe Ecosystem Roundup” and focus on informing and educating about progress and updates.
  • Call it “Safe Onchain” and focus on more viral content, such as simple how-tos, shareable memes/infographics, and actions people could take to improve XYZ.
  • Take a different approach? Please leave comments with suggestions!
0 voters

As a delegate with sufficient voting power , we believe that this is ready to move to a vote!

1 Like

These broader highlights and roundups would help me stay abreast of Safe eco happenings!

As a delegate with sufficient voting power , I consider this proposal ready to move to a vote.

As a delegate with sufficient voting power , I believe this proposal is ready to move to a vote

1 Like

As a delegate with sufficient voting power, I believe this proposal is ready for a vote.

Your proposal has reached sufficient signal to move to Phase 2: Voting. It will be live for voting on Snapshot on Wednesday, August 21st.

Proposal is live on Snapshot. Voting starts today and runs until September 2nd.

1 Like

As of September 2nd, 2024, this proposal did not reach quorum.

1 Like