1. Home
  2. Founder Academy
  3. Metrics & Analytics
  4. What to measure, and what to ignore

What to measure, and what to ignore

Different stages need different numbers. Measuring everything is the same as measuring nothing.

12 min read · Level 2

The point

A dashboard with forty numbers changes no behaviour, and the ones that survive are usually the ones that go up regardless of whether the business is working. The test for any metric is brutally simple: if this doubled, would I do anything differently? If not, it is decoration that costs attention. Cumulative totals are the worst offenders — total signups ever rises steadily while a company dies.

What is it?

What matters changes with stage.

Early (pre-PMF): users, activation, retention, and the number of customer conversations you had. Growth (post-PMF): MRR, CAC, LTV, churn, NRR, gross margin, burn, runway.

Everything else is context, not a dial you steer by.

Why does a founder care?

Because a dashboard with forty numbers on it changes no behaviour. Nobody looks at it after the second week, and the ones that do get looked at are usually the ones that go up reliably regardless of whether the business is working.

The test for any metric: if this number doubled, would I do anything differently? If not, stop reporting it.

Example

A pre-PMF company measuring badly: cumulative signups, page views, social followers, app downloads, press mentions. All rising. All meaningless — every one can be increased without a single person getting value.

The same company measuring well:

  • Weekly active users: 34
  • Activation rate (published a rota): 8%
  • Week-8 retention: 11%
  • Customer conversations this week: 4
  • These numbers are worse-looking and far more useful. The 8% activation says exactly what to work on, and the 4 conversations says the founder is not talking to enough people.

    One of these dashboards makes you feel good. The other tells you what to do on Monday.

    The common mistake

    First-time founders often track cumulative totals — total signups, total users ever — which only go up and therefore contain no information. Use active, current and rate-based numbers instead.

    The second mistake: adding metrics without removing any. A metric added is a metric someone must maintain and read. Five that drive decisions beat forty that decorate a screen.

    The third: measuring before there is anything to measure. With twelve users, talk to all twelve.

    How it works

    Step 1: Apply the doubling test

    If this number doubled, would I act differently? If no, remove it.

    Step 2: Prefer rates and current states over totals

    Weekly active, not cumulative signups. Retention rate, not total registered.

    Step 3: Pick five, at most

    Five numbers you check weekly and can recite from memory. More than that and none of them get real attention.

    Step 4: Match them to your stage

    Pre-PMF: activation, retention, conversations. Post-PMF: the growth and money numbers.

    Step 5: Write down what each would make you do

    'If activation falls below 20%, we stop building features and fix onboarding.' A metric with no attached decision is decoration.

    When to use this

    From your first users, reviewed whenever your stage changes.

    When not to use it

    Do not build analytics infrastructure with under about thirty users. A spreadsheet updated weekly is genuinely enough and far faster.

    How founders actually did it

    Vanity metrics survive because they are pleasant

    Registered users, page views, social followers and press mentions share two properties: they only go up, and they can be increased without anyone getting value. They persist in reporting because they are the numbers that make a bad month feel survivable.

    Replace every cumulative total with an active or rate-based equivalent. The discomfort of that change is the point of making it.

    Attach a decision to each metric

    The practice that separates a useful dashboard from a decorative one is writing, next to each number, what you would do if it moved. "If activation falls below 20% we stop building features and fix onboarding" turns a metric into a trigger.

    Five metrics, each with a written decision attached. Any number without one comes off the list.

    Do this now

    • List everything you currently track
    • Apply the doubling test to each
    • Cut to five, each with a decision attached

    Create a free account to read the rest and apply it to your own startup.

    Next: Activation and retention