1of 2
Startup metrics by stage, from pre-product to scale
Choose a North Star metric that reflects what your startup needs to prove at its current stage, from learning before product-market fit to measuring value delivered at scale.
Adapted by the EWOR Team from Juan Carillo’s article (opens in a new tab)2 min read
Choose the question before the number
A dashboard can fill up before the team knows what it needs to prove. Juan Carillo, a founding team member at Rebolet, investor and partner at Enzo Ventures, and Global Executive for LATAM at Sigma Squared Society, frames North Star metrics around the company's stage. Choose a signal that helps you decide what to work on now, then revisit it when the company's priorities change, not simply because another number looks better.
Define the stage’s unresolved question
Start by defining what success needs to look like next. Before there is a product, the central uncertainty may be whether a specific customer problem exists. While building an initial version, it may be whether you can put a testable workflow into users' hands. After launch, it may be whether your target customers actually use that workflow. Treat these stage-specific examples as starting points, not universal targets.
Choose a metric that tracks progress towards answering the unresolved question. Interviews completed can measure research activity, for example, but cannot establish whether interviewees need or will buy the product. Likewise, launching a feature measures delivery, not customer value. Document these limitations alongside the metric so the team doesn't mistake a convenient count for proof.
Check both customer and company value
Once customers repeatedly receive value and the business can capture it, trace the steps connecting delivery, usage and payment. A metric for a more mature company should link the value customers receive to the value the business captures.
Test your proposed metric against both sides: could it rise while customers are worse off, or while the company captures no value? If so, add a complementary measure or rethink the definition.
Record exactly what counts as an event, where the data comes from and who owns it. A spreadsheet is sufficient if it reliably captures actual activity. Keep forecasts and informal estimates separate from observed results.
Review whether your projects are likely to influence the chosen metric, but don't neglect essential work the metric cannot capture, such as fixing a serious product defect.
Set a review trigger
Define when you'll revisit the metric: a product change, evidence of repeat use, a shift in customer segment or a new revenue model. Don't change it simply to improve the numbers in a report.
Keep the metric's definition, limitations and intended use visible. A North Star metric can focus the team's attention, but it cannot prove what caused a result.





No comments yet.
Be the first to comment on this signal.