Metrics for 0 → 1 products: what to measure before you have numbers
Early-stage founders obsess over dashboards they don't have enough data to trust. Metrics do matter at 0 → 1 - but they play three very different roles. Confuse them, and you'll optimise the wrong thing with false confidence.
At 0 → 1, metrics are both seductive and dangerous. You don't have the traffic for statistical significance, yet you desperately need signal about whether any of this is working. The way out isn't “ignore metrics until you scale.” It's knowing which job a metric is doing at any given moment. In my experience taking products from zero to one, metrics show up in three roles across two contexts: discovery and strategy.
In discovery: metrics as a smoke alarm
The first job of a metric is to tell you where to look. A dip in activation, a spike in drop-off - these flag that something is wrong. But here's the trap founders fall into: a metric exposes the problem and never explains the why. It's a smoke alarm, not a diagnosis.
So when a number moves, you don't jump to a solution - you go find the cause with qualitative research: customer interviews, session reviews, actual conversations. At elyps, analytics flagged a brutal drop-off in onboarding. The number told us where. Talking to customers told us why - and that's what let us fix it.
In discovery: metrics to validate your bets
The second job: every product idea is a bet, and metrics track how the bet paid off. Before you build, you name the assumption, design the smallest experiment that tests it, and decide up front which metric would prove or disprove it - a Test Card. Then you run it and read the result honestly.
At FOUND, we validated the riskiest assumptions with concierge and Wizard-of-Oz experiments - simulating the product by hand before building it - and let the metrics tell us whether to keep going. Cheap tests, real numbers, no wasted engineering.
In strategy: metrics to align the team
The third job is different. Once you're moving from discovery to scale, you need one metric that pulls everyone in the same direction. Find the key product metric that, when optimised, most moves your business metric - the North Star Metric. A good North Star is a genuine proxy for customer value, not vanity.
Then break it into 3–5 input metrics - each one a product outcome a specific team can actually influence. Spotify's North Star is “time spent listening to music,” which directly drives its business goal of monthly premium subscriptions. The teams don't chase “subscriptions” - they chase the listening behaviour that produces them.
The 0 → 1 caveat
All of this comes with an asterisk at the earliest stage: you usually won't have statistical significance, so don't pretend you do. Lean on directional signal, qualitative depth, and small experiments - not big-data confidence you haven't earned. A metric at 0 → 1 is a compass, not a verdict. Use it to decide where to point, then go talk to the humans who'll tell you if you're right.
.svg)
.svg)
