Unit economics
Price the revenue lost in the gap between signing and go-live.
- Category
- Unit economics
- Signup
- None
- Your data
- Stays in your browser
- Also in
- Claude, via MCP
What does a slow customer onboarding cost?
Each week a customer is not live is a week of contract value they are not using. Delayed value per deal = annual contract value ÷ 52 × weeks of delay, and per year = that × deals per year. An 8-week delay on 40 deals worth ₹50 lakh each puts about ₹3.1 crore of contract value a year at risk.
An 8-week gap between signing and go-live delays about $369,231 of recognized revenue a year, cash you’ve earned but can’t book. Halving onboarding time reclaims roughly $184,615 and gets customers to value (and retention) faster.
Slow onboarding delays revenue recognition and time-to-value, which also depresses early retention. Templated implementation and clear milestones are the usual fix.
About this calculator
Every week between contract signature and go-live is revenue you've earned but can't yet recognize, and a slow onboarding pipeline delays that across every deal you close, not just one. This calculator prices the gap between signing and first value, and shows what compressing that window would reclaim across your yearly deal volume.
How to use it
- Enter the average contract value (annual) per deal.
- Enter the implementation delay in weeks, from signature to go-live or first value.
- Enter deals per year.
- Read delayed revenue per deal, delayed revenue per year across all deals, and the amount recoverable if the delay were cut in half.
Methodology
Weekly value is annual contract value divided by 52. Delayed revenue per deal is that weekly value times the number of weeks in the implementation delay, the recurring revenue that's "earned" contractually but not yet realized because the customer isn't live yet.
Delayed revenue per year is delayed revenue per deal times deals per year, aggregating the effect across your entire annual deal volume rather than looking at a single contract in isolation.
Recoverable if halved is simply half of the annual delayed-revenue figure, a quick before/after comparison showing the impact of cutting onboarding time in half, without modeling any specific process change to achieve that reduction.
The tool flags delays of 8 weeks or more as a caution zone. This model assumes every deal experiences the same average delay; if your delay varies significantly by deal size or complexity (larger enterprise deals often take longer to implement), segment the calculation by deal tier for a more precise read.
Contract value delayed by implementation time
Weekly value = Annual contract value ÷ 52 Delayed value per deal = Weekly value × Weeks of delay Delayed value per year = Delayed value per deal × Deals per year Value of each week saved per year = Weekly value × Deals per year
- Annual contract value
- Yearly value of a typical new contract.
- Weeks of delay
- Time from signature to go-live beyond what the customer expects, or the full onboarding time if you want the total.
- Deals per year
- New contracts signed in a year.
What the delay costs depends on when billing starts. If billing starts at go-live, delay pushes revenue later, a real cash cost. If billing starts at signature, revenue is collected but the customer pays for weeks with no value, which raises renewal risk. Either way the figure is value at risk, not revenue lost outright.
Worked example: 40 enterprise deals a year
A B2B software company signs 40 new contracts a year at an average of ₹50,00,000. Implementations take eight weeks longer than customers are told during the sale.
- Weekly value = ₹50,00,000 ÷ 52 = ₹96,154.
- Delayed value per deal = ₹96,154 × 8 = ₹7,69,231.
- Delayed value per year = ₹7,69,231 × 40 = ₹3.08 crore.
- Halving the delay to four weeks recovers ₹1.54 crore a year.
- Each week saved is worth ₹96,154 × 40 = ₹38.5 lakh a year.
Each week saved is worth ₹38.5 lakh across the year, which is the budget case for a dedicated onboarding lead, templates or partner capacity. Start by finding where the weeks go: waiting for customer data, integrations, security reviews or training. If delays start before signature, the contract redline duration predictor covers the legal stage.
What is a good implementation time?
Good is shorter than what you promised and predictable across customers. Track:
- Median days from signature to go-live, by product and deal size.
- Share of implementations finished by the promised date.
- Time to first value: the first outcome the customer cares about, which can come before full go-live.
The tool flags 8 weeks or more as a caution; that is its own threshold. A complex enterprise rollout can rightly take longer, as long as it is planned and the customer agreed the timeline.
Implementation delays in India vs the US
Indian enterprise implementations are often delayed on the customer side by approvals, data access and IT security sign-off, especially in banks, insurers and government-linked organisations. Agree a joint plan with named customer owners at signature. Payment milestones tied to go-live are common, which makes delay a direct cash cost.
US customers more often run formal security and procurement reviews before signature, so post-signature delays are more often integrations and data migration. Subscription terms that start at signature put the renewal clock under pressure: a customer live for nine months of a twelve-month term has less proof of value at renewal. See the renewals pipeline health grader.
Common implementation delay mistakes
- Measuring from kickoff instead of from signature, which hides the scheduling gap.
- Promising timelines in the sale that delivery cannot meet.
- Treating customer-side delays as outside your control without a joint plan.
- Using one average for small and large deals with very different implementations.
- Counting go-live as success when the customer has not reached first value.
FAQ
The revenue is delayed, not necessarily lost outright, but delayed recognition has real costs: it pushes recognized revenue and cash flow later, and a long, painful onboarding also depresses early retention, customers who wait too long for value are more likely to churn before ever fully adopting the product.
No, this tool measures the operational cost of a slow go-live, revenue that's delayed by implementation friction. Deferred revenue is an accounting concept for cash already collected but not yet recognized under revenue-recognition rules, a related but distinct idea, see the Deferred Revenue Amortization Planner for that calculation.
It varies enormously by product complexity, self-serve SaaS may onboard in days, while complex enterprise integrations can take months. This tool flags 8+ weeks as worth scrutinizing, but the right benchmark is your own historical fastest-possible onboarding, not a universal number.
Common levers include templated implementation playbooks, clearer milestone-based project plans, dedicated onboarding resources for the first weeks, and reducing custom configuration in favor of standardized setup paths. This calculator shows the size of the prize, not the specific process fix, that depends on where your bottleneck actually sits.
Time to value is how long a customer takes to get the first meaningful result from your product after signing. It is often a better measure than go-live, because a product can be live without being used.
Signature is better for cash flow and simpler to administer; go-live feels fairer to customers with long implementations. Whichever you choose, keep implementation short so the customer sees value well before renewal.
Standardise onboarding into a fixed plan, collect customer data and access requirements before kickoff, use templates for common setups and assign one owner on each side.
Numbers looking off?
If the model says one thing and the pipeline says another, that gap is usually where the revenue is. A 30-minute call finds it.
It starts with a 30-minute call. Pick a time below.