DevRel Work Group Case Study

Jupiter DAO Working Groups
1

Summary

This case study outlines how the Jupiter DevRel Work Group (DRWG) successfully:

  • Laid Groundwork Early: Operated for months before any official funding, building tools and community support.
  • Iterated to Product-Market Fit: Developed Catalytics and Jupiverse Kit, pivoting and improving these projects based on feedback until they solved real needs in the Jupiter ecosystem.
  • Evolved into a Trial Work Group: Applied for a Jupiter DAO grant after demonstrating proven value, then used the funding to scale their community impact, ultimately establishing a Work Group dedicated to assisting developers in the Jupiverse.

Problem Statement

The DRWG formed to address a clear gap in the Jupiverse:

  • Overburdened Jupiter Team: Jupiter’s team is focused on shipping features for the most part, leaving little time for community support. Documentation started to lag behind and dev support was provided by two people (one being the CTO who sent 50,000+ support messages in two years - an unsustainable stopgap).
  • Community Developers Adrift: Meanwhile, eager builders from the community struggled to get feedback or guidance, as the DAO initially prioritized content creation and social outreach over technical contributors. This led to talented devs feeling unsupported and disconnected, with no clear path to contribute.
  • Rising Need: With Jupiter’s developer community growing, it was crucial to bridge this divide. The situation called for a dedicated developer-relations effort to support builders and connect them with Jupiter’s tools and community.

Getting Started

Before applying for a grant, the future DRWG members spent months building and iterating on their solutions:

  • Minimum Viable Product: In August 2024, Konstantinos and Fiji launched Catalytics.pro – a platform for Jupiter DAO governance analytics. With time this passion project gained traction: by December nearly 30,000 unique addresses had used its features. The site drew 2,000–3,000 visits per day, indicating significant demand for Jupiter DAO data insights.
  • Validating Product-Market Fit: Crucially, the team treated their early projects as experiments to find what sticks. They were willing to iterate and pivot. Catalytics started with basic governance data, then expanded features based on user requests, including SNS support, USD values of Active Staking Rewards, and Catalytics trust index.
  • Grant Application: By the time they considered a grant, they had proven engagement: their tools addressed real pain points, and a loyal audience had formed around their efforts. With proven product-market fit, going through a Jupiter DAO Grant vote in late 2024 was a relatively trivial procedure.
Catalytics Grant Application

ASK

5,000USDC

Project Title

Catalytics (Cats in analytics)

One-Liner Description

Your hub for real-time analytics and insights in the Jupiter and Solana ecosystem

Project Details

The problem we aim to solve is the challenge users face in accessing comprehensive and relevant information within the decentralized finance space. As the landscape becomes increasingly complex, individuals often struggle to navigate multiple platforms to find the critical data necessary for informed decision-making. Catalytics addresses this challenge by aggregating data and showcasing valuable Information in the Jupiter ecosystem. By creating a centralized hub for information, we empower DAO members to explore various opportunities, enhancing their engagement and participation in the broader ecosystem while simplifying the decision-making process.

Twitter

https://x.com/solatropos

Deadline

15 March 2025

Proof of Work

https://catalytics.pro

Goals and Milestones

By March 15 2025 we will have achieved following milestones:

  • Mechanism to monitor active proposals with live data
    • % of votes for each choice
    • vote weights averages
    • likely outcomes based on data
  • Upgraded voting profile (this exists but will be refactored and more powerful)
    • general data about each proposal, asr period, all time
    • specific data by typing an address
    • downloadable pdf with many details
  • LSTs dashboard (upgrade)
    • charts comparing LSTs
    • backtest function

In general we dont want to promise many things because we already have a working platform with traffic and this also needs maintainance. we spend hours every week with refactoring and improving features

Primary Key Performance Indicator

Last time i filled out this field i was worried about social reach and that people will not see our work.

Today this has changed, our KPIS are our numbers and this is something no1 can ignore.

Our goal will be that our new X Account will reach 1500 organic followers until the 15th of March.

A lot of people at this moment follow me for information about catalytics but we want to swift this audience to our official upcoming X account with our brand new upcoming design.

What are you currently working on in the Jupiverse?

Check out our actual work and roadmap for the Jupiter and Solana ecosystem here: https://catalytics.pro/about-us

Our ToDos and ongoing work:

  • Jupiter governance statistics
  • Live data of votes happening
  • Enhancing the jupiter voting profile we have already build
  • Enhancing our LST dashboard with graphs and backtests
  • JUP POAP Statistics and insights
  • Designer onboarding (our bounty ends soon)
  • X Account (For platform) we already got a big audience but we want to switch this audience to a new x account and not on my personal
  • Dashboard of Jupiter actions (swaps/dcas/vas/perps) this is something WTP from the community told me that would be very helpful because many people as for that

What does your grant aim to achieve in the DAO, and how does it intend to scale over time once it reaches the WG stage?

Our grants aims to achieve that jupiter and solana users find a one stop platform for as many informations as possible at catalytics.

At this moment:

  • Solana LSTs
  • Jupiter voting profile
  • POAPs
  • Solana Mobile airdrops
  • Bitcoin ETFs (because everyone cares about that)

In the future:

  • when the Solana ETF starts trading we will be the number one platform from day 1. We are ultimately prepared for that

How will these funds help you scale up what you’ve been working on and the Jupiverse?

Our project started around 4 months ago and since then our platform has grown a lot and has gained a lot of traction. On active days (with votes) between 2000 and 3000 visits (not unique) and our voting profile has almost 3000 unique wallets visited.

We can provide all this data if asked.

For this reasons we had to implement strong security and backups for our application so our users are navigating in our platform with good performance and safety. (We had some DDOS attacks in the past from attackers who tried to stop traffic to our application)

Each month costs: around 400-450 USD to maintain our services

AWS Servers

AWS Backup

Database

Hosting Services

RPC Service (will be new soon)

Some Subscriptions including (Typefully + Midjourney to enhance our reach)

The rest of the funds will be distributed to the total 4 members (not equal)

  • Konstantinos (Co-Founder)
  • Fiji (Co-Founder)
  • POAP_FREAK (POAP Contributor)
  • Designer (This position will be filled in the next 10 days)

Work Group Phase

After successfully completing the grant’s course, the team applied for a 3-month Trial Work Group budget - effectively formalizing DRWG as a full-time team. Since early April, they were able to accelerate in several areas:

  • Taking Over Developer Support: A top priority was to relieve the Jupiter team of frontline developer support. DRWG members became the go-to responders in Jupiter’s Discord #dev-support channel, helping developers troubleshoot and answering technical questions promptly.
  • Improving Communication Hubs: The team worked to make the Jupiter DAO Discord more welcoming for builders. They proposed and implemented dedicated developer channels – for announcements, resource links, general dev chat, and a dev voice room for live discussions.
  • Expanded Content & Education: With official status, DRWG ramped up educational content. They began drafting multi-tiered developer guides (from “Easy” quick starts to “Hard” deep dives) to make Jupiter’s tech more accessible. The team has also started doing weekly “Vibe Code with DevRel” sessions, making them the place for developer-related announcements and idea sharing.

Outcomes

In a short time, DRWG’s impact has been felt across the Jupiter ecosystem:

  • Stronger Developer Engagement: By bridging the gap, DRWG made developers feel heard and supported. Jupiter’s dev community becomes more active and self-sustaining.
  • Jupiter Team Relief: The Jupiter team could redirect focus back to core product development, confident that community devs were in good hands. This division of labor improved overall productivity and morale.
  • Growth of Tools & Initiatives: Catalytics and Jupiverse Kit continue to grow under DRWG stewardship. Catalytics continues being the place where DAO members regularly check governance-related data, and Jupiverse Kit’s components drive even more integrations.

Advice for Future Applicants

For those looking to follow in footsteps of DevRel Work Group and secure a Jupiter DAO grant or Work Group status, here are some best practices:

1. Build First, Propose Later: Rather than pitching a raw idea, start by doing. Identify a gap in the ecosystem and begin filling it however you can. DRWG didn’t wait for permission or funding to solve problems - they just started building.
2. Gather Feedback & Cultivate Community Support: Engage with the community early and often. Spend time rallying support for your idea before the application. Share updates, answer questions, and incorporate community suggestions. When the time comes, active supporters will advocate for you. Remember, in Jupiuter DAO your future “boss” is the community, capturing its support is crucial.
3. Demonstrate Product-Market Fit: Before applying for a grant, try to validate that your project has traction or value. This could mean user metrics, testimonials, or even just a functional demo solving a real problem. In Catalytics’ case, thousands of daily users and real adoption metrics spoke volumes about the importance of their work. Proof of work speaks louder than promises.
4. Be Prepared to Pivot: Your initial idea might not be the ultimate solution - and that’s okay. Treat your project as an iteration. If feedback or data suggests a change in direction, embrace it. The best contributors are adaptable.
5. Assemble a Capable, Committed Team: Successful initiatives often have a team with complementary skills and a track record of working together. If you can, team up with others who are as passionate as you are. Make sure your proposal highlights who is involved and why they’re the right people for the job.
6. Align with the DAO’s Processes: Map out your path to fit the Jupiter DAO’s framework. Typically, projects start with smaller grants (short-term, <$10K) and progress to Trial Work Groups and then full Work Groups as they prove themselves.
7. Leverage Available Resources: Finally, use the tools and mentors at your disposal. Jupiter DAO has guides, case studies (like this one), and veteran members willing to help newcomers. Don’t hesitate to reach out, ask for feedback on your draft proposal, or seek advice from those who’ve done it. DRWG’s success was built on not just hard work, but also the use of the Jupiter community’s collective knowledge.

By following these principles, future applicants can increase their chances of success. The story of the DevRel Work Group shows that preparation, perseverance, and community-focus can turn a grassroots idea into a funded, impactful reality in the Jupiter DAO. Feel free to use this outline as a blueprint - and good luck on your journey to build the next Jupiverse success story!

10 Likes
2

Love this, great post AG and thank you very much :slight_smile:

4 Likes
3

Thank you, Konstantinos, for being one of the three reasons this post exists! :slight_smile:

4 Likes
4

Now that’s a good read. DevRel stands true to its name, can’t wait to see where the dev community for Jupiter is headed under the direction of these absolute chads!

3 Likes
5

Congratulations to @Konstantinos and @fiji for launching Catalytics.pro, an outstanding MVP that’s already proven market demand and set a high bar for DAO‐driven governance analytics.

@AG42

Jupiter DAO: Free Time Isn’t for Everyone

In Jupiter DAO, two paths are often celebrated:

  1. Build First
    Those with spare hours put in unpaid work to prove a concept before seeking a grant.
  2. Market Operators
    Teams already shipping products and earning revenue, who won’t drop a sure thing for the mere possibility of DAO funding.

— but is this model fair — or even effective?

The “Build First” Model Favors Those with Spare Time

  • Exhausting Volunteering
    Spending months building an MVP, like Catalytics.pro, without pay is a luxury few can afford. Full-time workers, parents, or anyone juggling other commitments simply don’t have that margin.
  • Availability Bias
    “Do it first, ask later” privileges students, freelancers between gigs, and hobbyists, but shuts out experienced professionals who can’t just clear their schedules on a whim. The DAO risks amplifying inequality of access rather than attracting the best ideas.

Operators Won’t Abandon the Certain for the Uncertain

  • Why Give Up Guaranteed Revenue?
    Teams with live products, steady partnerships, and paying customers aren’t going to pause their roadmaps for a “maybe” grant. Abandoning what already works is too great a gamble.
  • Opportunity Cost Is Real
    Diverting engineering effort from a revenue-generating line to build a DAO prototype risks missing deadlines, upsetting users, and harming the bottom line.
  • Slow, Unpredictable Process
    Even with a polished MVP, the DAO’s proposal and voting cycle can stretch for months—long enough that market conditions shift and the initiative loses relevance. No established operator will cripple their cash flow and risk hard-won traction on such terms.

Key Takeaways

  • Time Equity
    The “build-first” ethos favors those with flexible schedules, potentially excluding valuable contributors.
  • Risk Profile
    Established teams won’t sacrifice existing revenue streams for uncertain DAO grants.
  • Process Improvement
    To unlock broader participation, Jupiter DAO should consider mechanisms that reduce time barriers and speed up validation.

Conclusion

  • Jupiter DAO’s “build for free, prove it later” model rewards those with the luxury of time but alienates professionals who already invest capital and effort in solid businesses. To harness the best talent, the DAO must find ways to support early-stage initiatives more equitably, so contributors aren’t forced to choose uncertainty over certainty.
  • A Little Inside Scoop?
    Seems like the DAO already handpicks a few standout contributors to fast-track their proposals… or maybe I’m just imagining things?

@Rodrigues770471

2 Likes
6

Thank you for the comment! Not 100% sure what you’re trying to say, but if the main idea is that proof of work should not be a requirement - then I’m afraid this is not going to change any time soon. The past few months show that measurable contributions before applying for a grant are crucial.

2 Likes
7

I love this. With this a lot of grant would have a proven outcomes.

2 Likes
8

Hello, @AG42

Thank you for the comment! But seriously, what do we actually consider “proof of work”?

To me, it’s rolling up your sleeves, writing code, and launching applications, whether in the Jupiverse or elsewhere, with solid expertise and tangible results: PRs merged, bugs squashed, users actually using your product. I don’t believe the Jupiter team only gets paid “at the end of a grant”, hey work in sprints, hit milestones, and have clients waiting on production features.

What you’re telling me, if I’ve got it right, is “do the work first and maybe you’ll get rewarded later.” Smooth… almost as smooth as that freelancer who only sees their invoice paid after reminding the client for the hundredth time. :wink:

And the biggest irony? If you do really good work and survive the voting gauntlet, you might go from the community’s “invisible ninja” to the DAO’s “DevRel Hero”— or end up as the “eternal grant hopeful.” Only time (and a few merges) will tell!

@Rodrigues770471

9

Just to be clear, there are quite a few differences between a contractor work and grants. I think there is some unnecessary confusion between the two.

2 Likes
10

All the best!
Building community tools that will help to move jupiverse community forward, looking forward to yours plans and executional models.

2 Likes
11

So, just to make sure we’re on the same page: we’re talking about the Jupiter DAO grant model, where funding is only released after a vote and upon meeting the milestones, right?

:smirking_face: I know full well the differences between grants and contractor work, I’m simply using analogies to highlight how they’re fundamentally different. Did I get that across clearly?

@Rodrigues770471

12

Can’t say that you did tbh. At least I am not quite sure what your suggestion is about. Can you please state it in one sentence?

13

Hello @AG42,

So, just to make sure we’re on the same page: we’re talking about the Jupiter DAO grant model, where funding is only released after a vote and upon meeting the milestones, right? :smirking_face:

I’m simply pointing out that, in this grant model, requiring proof of work before any payment is like shooting in the dark:

  • There are no objective acceptance criteria.
  • You have no guarantee your work will be approved.
  • You may end up putting in hours without any compensation.

Requiring proof of work should build trust, not become a gamble on whether you’ll ever get paid.

Cheers,
@Rodrigues770471

14

Correct. Grants != employment contracts

It is not really a gamble if the value provided is apparent. Doing something just for the sake of doing something should not be incentivized in my opinion.

The underlying idea is to fund the doers, who are already working on improving different aspects of Jupiter DAO, and help them scale or dedicate more time to their projects. Jupiter DAO is not a company and it is not looking for employees.

15

Who decides ? :waving_hand:

@Rodrigues770471

1 Like
16

Here are the details on the Grants Council composition: https://discuss.jup.ag/t/jupiter-dao-microgrants-initiative

1 Like