Average Days To Go Live

What it measures

For each customer that goes live in the period, you count the calendar days from contract signature (or the contracted start date, if that precedes first billing) to the date their first recurring revenue begins. You sum those durations and divide by the number of customers that activated, producing a simple arithmetic mean. Only successfully activated customers count — contracts still stuck in onboarding, paused, or cancelled before going live are excluded. Pre-paid trial periods and one-time setup work are not counted as "live"; the clock stops only when billable recurring revenue starts.

Why it matters

Average Days to Go Live is the operational heartbeat of your sales-to-revenue handoff. Every day between signature and first revenue is deferred cash, occupied implementation capacity, and rising buyer's remorse before the customer ever sees value. Sales and finance use it to forecast when booked deals convert to recognized revenue; customer success uses it to size implementation headcount ahead of bookings growth; investors read it as a proxy for how repeatable and scalable your onboarding really is. It is also a quiet leading indicator of retention — customers who reach value quickly tend to stay longer and expand sooner, so a shorter time to live usually shows up later as stronger net revenue retention.

How to read it

Read this as a trend, never a single snapshot, and always alongside a median — one stalled enterprise rollout can drag the mean for an entire cohort. Shorter is better, but not at any cost: a sharp drop (say 20 days to 10) can mean a genuinely faster onboarding machine, or it can mean you are cherry-picking easy self-serve deals or cutting implementation rigor that resurfaces as churn later. A slow creep upward (20 → 30 → 40) signals ops strain — check whether deal complexity rose or execution discipline slipped. Always segment by customer size, product tier, and use case: a blended 15-day average can hide a 60-day enterprise cohort masked by instant self-serve activations. Compare the trend to bookings growth to decide whether to invest in implementation capacity before, not after, the backlog forms.

What good looks like

Watch-outs

• Measuring only successful go-lives in isolation. If you average just the customers who activated, you are blind to the ones stuck in onboarding who never reached revenue. Track activation rate alongside this metric, then report Days to Go Live for the winners — otherwise a falling average can simply mean you quietly stopped onboarding the hard customers.
• Blending cohorts of different size or vertical. A 15-day average is meaningless when it lumps 2-day self-serve signups with 60-day enterprise rollouts. Report the headline number, but always investigate by customer size, product tier, and use case, and watch the median, not just the mean.
• Stopping the clock at setup instead of first revenue. Counting days to technical readiness — data imported, seats provisioned — instead of days to first billing games the metric. Revenue is the finish line; setup readiness is only a prerequisite.
• Charging customer-initiated delays to your ops team. If a customer signs but pushes their own start date out 60 days, that delay is their choice, not your execution. Track elapsed days but flag and segment customer-caused pauses so the metric stays an honest read on your implementation engine.

Worked example