Close to Subscription Days

What it measures

For each new contract signed in the period, the calendar days elapsed from contract close date to subscription start date (go-live). Those day counts are summed across all new contracts and divided by the count of new contracts. The result is a simple arithmetic mean — the average activation lag for the cohort. It measures elapsed time only; it says nothing about deal size or onboarding quality.

Why it matters

This metric bridges your sales engine to your revenue engine. A close means you won the deal; subscription start means the customer is live and paying. The gap between them is operational drag — and revenue delay, since cash and product engagement don't begin until go-live. Sales, Finance, and Ops use it to answer one question: how fast are we turning closed deals into live revenue? A long lag also signals onboarding health, often hiding complex implementations, integration friction, or a customer slow to commit resources. For high-velocity SaaS, every extra day is churn risk: the customer has the most momentum at close, and delay lets that momentum cool.

How to read it

Read this as the average wait between deal-won and go-live. A short average means new customers are live and paying almost immediately after signing; a long average means operational friction between sales and revenue. This is a timing metric, not a quality metric — it tells you how long activation takes, not whether the customer is happy. Always compare against three things: your own historical baseline (getting faster or slower?), your customer segment (self-serve activates far faster than enterprise), and your forecast. If the average is rising month to month, diagnose the cause — are you closing more complex deals, has the ops team shrunk, or is the onboarding checklist growing? Pair the mean with the median, because a single long implementation can drag the average up while most deals go live quickly.

What good looks like

Watch-outs

• Confusing scheduled start with actual start. If a customer signs but contracts to begin a month later, count to the contracted start date, not to whenever the system happened to provision them — otherwise you'll misread a customer-chosen delay as operational speed.
• Including stalled implementations in the mean. A customer who signs and then sits for 60 days waiting on their own approvals is reflecting customer delay, not your efficiency. Segment 'actively onboarding' contracts separately so a few stalled deals don't poison the average.
• Reporting only the mean. A single complex deal that takes weeks can skew the average even when most deals go live in days. Always pair the mean with the median and percentiles (p50, p75, p90).
• Averaging across cohorts. Self-serve and enterprise onboarding are fundamentally different motions. Blending a near-instant self-serve cohort with a multi-week enterprise cohort produces an average that describes neither — track each separately.

Worked example