Why Web3 Needs More Data Analysts (and Not Just Developers)

When people talk about Web3, the spotlight almost always lands on developers—smart contract engineers, protocol architects, dApp builders. Don’t get me wrong—they’re doing incredible work. But there’s a gap no one’s really talking about: data analysts. I recently made the switch from Web2 data analytics to Web3 on-chain analysis, and one thing I’ve noticed quickly is this—there’s a ton of data in Web3, but not nearly enough people turning it into insight. Developers Build, But Analysts Tell the Story Blockchains generate raw, chaotic data every second—wallet transactions, gas fees, contract calls, NFT transfers, DAO votes. It’s a goldmine, but it doesn’t mean much until someone makes sense of it. That’s where analysts come in. We help answer critical questions like: What’s driving protocol growth? Which wallets are power users, and how do they behave? Where are whales moving capital—and why? Without these insights, projects are flying blind. Why the Gap Exists There are two main reasons: Tooling is still evolving. Unlike Web2, where tools like Excel, Tableau, or Power BI are plug-and-play, on-chain data requires you to know SQL, write subgraphs, or wrestle with APIs. Narratives dominate over numbers. Many Web3 projects focus more on hype and less on measurable performance, which leaves data roles undervalued. What Needs to Change We need to start seeing data analysis as a core part of building in Web3—not just a nice-to-have. More analysts means better decision-making, stronger communities, and healthier ecosystems. As someone making this transition, I’m just getting started. But I already see the need—and the opportunity. Are you a Web3 founder, dev, or fellow analyst? I’d love to hear your thoughts. Do you think Web3 is sleeping on data? What tools or frameworks have helped you most? Let’s discuss.

Apr 21, 2025 - 12:16

Why Web3 Needs More Data Analysts (and Not Just Developers)

When people talk about Web3, the spotlight almost always lands on developers—smart contract engineers, protocol architects, dApp builders. Don’t get me wrong—they’re doing incredible work. But there’s a gap no one’s really talking about: data analysts.

I recently made the switch from Web2 data analytics to Web3 on-chain analysis, and one thing I’ve noticed quickly is this—there’s a ton of data in Web3, but not nearly enough people turning it into insight.

Developers Build, But Analysts Tell the Story

Blockchains generate raw, chaotic data every second—wallet transactions, gas fees, contract calls, NFT transfers, DAO votes. It’s a goldmine, but it doesn’t mean much until someone makes sense of it. That’s where analysts come in.

We help answer critical questions like:

What’s driving protocol growth?

Which wallets are power users, and how do they behave?

Where are whales moving capital—and why?

Without these insights, projects are flying blind.

Why the Gap Exists

There are two main reasons:

Tooling is still evolving. Unlike Web2, where tools like Excel, Tableau, or Power BI are plug-and-play, on-chain data requires you to know SQL, write subgraphs, or wrestle with APIs.
Narratives dominate over numbers. Many Web3 projects focus more on hype and less on measurable performance, which leaves data roles undervalued.

What Needs to Change

We need to start seeing data analysis as a core part of building in Web3—not just a nice-to-have. More analysts means better decision-making, stronger communities, and healthier ecosystems.

As someone making this transition, I’m just getting started. But I already see the need—and the opportunity.

Are you a Web3 founder, dev, or fellow analyst?
I’d love to hear your thoughts. Do you think Web3 is sleeping on data? What tools or frameworks have helped you most? Let’s discuss.