Crypto KPI Framework for Web3 Teams

TL;DR: A KPI is useful only when it changes a decision. Start with the business outcome, define the entity and exclusions, then use secondary metrics to explain movement.

A KPI framework prevents the wrong celebration

At Morpho, roughly $38M of migrated liquidity initially looked like a healthy headline result. The fuller view was different: activity was concentrated, Ethereum had only 70 migration transactions, and product tracking showed near-zero interaction with the CTA. The right KPI was not migrated liquidity in isolation. It was the funnel to a meaningful migration outcome, segmented by where the opportunity remained.

That led to a visible CTA, improved prompt, communications and a redesigned flow. Ethereum migrated liquidity rose from about $6M to about $32M in January. The public case study shows why a headline metric needs diagnostic context.

Build from outcomes to drivers

Layer	Question	Example
Outcome	Is the business creating value?	Net revenue, retained liquidity, repeat core action
Behaviour	What do qualified users do?	First deposit, repeat borrow, retained LP position
Driver	Why did the outcome move?	Funnel completion, chain mix, campaign cohort
Risk	What makes the result fragile?	Concentration, incentives, counterparty dependency

Choose a small executive set, then give each team driver metrics it can influence. Five trustworthy metrics are better than twenty that restart a definitions debate every week.

Write a metric specification

Every KPI needs a plain-language purpose, formula, source, exclusions, owner, cadence and known limitations. Active wallets are not active users unless that is literally what the metric represents. TVL is not revenue. A wallet count can be true and still hide one entity controlling many addresses.

The KPI review should ask three questions: what moved, why did it move, and what changes next? If the answer ends at a chart, the framework is reporting rather than management.

For KPI design tied to operating decisions, see Unchain Data's Web3 Data Audit.

Frequently asked questions

How many KPIs should a Web3 team track?

Start with a small executive set tied to the business model, then use a second layer of diagnostic metrics. The goal is not a universal number. It is a set small enough to own and stable enough to drive action.

What makes a Web3 KPI misleading?

The common failure is confusing an observable chain event with business value. Wallets may not be people, transactions may not be intent, and TVL can be concentrated or incentive-driven. Define the entity, qualifying action and exclusions beside the metric.