Your Product Is Live—What Should You Measure in the First 90 Days?

Launch day brings relief, and then a new question: now what? In the first 90 days, real people use your product in ways you did not predict. That usage is the most valuable information you will ever have, provided you measure the right things. Too many numbers create noise. These are the ones that matter.

Before you measure: define what success looks like

Pick the one outcome your product exists to deliver. For a booking tool it may be a completed booking; for a business system, an order processed without help. Everything below is judged against how many users reach that outcome, and how easily.

Days 1 to 30: activation

Activation is the moment a new user first gets real value. It is more meaningful than sign-ups, because many people register and never return. Track:

• Activation rate: the share of new users who complete the key first action
• Time to value: how long it takes them to get there
• Drop-off points: the exact step in onboarding where people leave

If activation is low, do not spend on acquiring more users. Fix onboarding first.

Days 30 to 60: conversion

If your product has a paid step, an enquiry or a purchase, measure how many users complete it and where the others stop. Look at the funnel from visit to sign-up to activation to payment, and compare by device and source. Mobile checkout problems and unclear pricing pages are common leaks. Our guide to conversion optimisation covers how to test the fixes.

Days 60 to 90: retention

Retention shows whether the product is truly useful. Measure how many users return after one week, one month and two months. A product that keeps people coming back has found a real need. If users disappear after the first session, no marketing will rescue it. Compare groups who signed up in different weeks to see whether your changes are helping.

Throughout: support issues

Support requests are free research. Tag every ticket and message by topic, and count them. If ten users ask the same question, the product, not the users, needs to change. Also track how quickly issues are resolved and which problems reappear.

How to prioritise what to fix

You will end up with a long list of ideas. Rank them with three questions:

1. Impact: how many users are affected, and how much does it block the key outcome?
2. Evidence: do usage data and support requests point to it, or is it an opinion?
3. Effort: how long will it take to fix?

Start with high-impact, well-evidenced, low-effort fixes. Be wary of adding features before fixing the basics that block activation and retention.

Set up measurement early

None of this works if tracking is added after launch. Define events for each key action, check they fire correctly and review them weekly. Keep consent and privacy in mind for anything you track. Dashboards help here, as described in our page on analytics and dashboards.

Keep improving

The first 90 days set the direction for everything that follows. If you need a plan for what to measure and improve, explore our conversion optimisation and product growth service, or start with a Business Blueprint.