Most SaaS companies call an implementation finished when the product is configured, the data is loaded and the customer can log in. That is a delivery milestone, and it matters. The customer measures something else: whether the process they wanted to change has changed, and whether they can keep it that way.
When those two milestones are treated as one, a project can hit every internal checkpoint and still leave the customer without the result they paid for. The problem rarely shows up during the project. It shows up months later, as low usage, an unhappy sponsor or a difficult renewal.
The causes are usually operational, not technical. Readiness is assumed instead of confirmed. Ownership is shared instead of assigned. Each department is measured on its own stage of the lifecycle, so nobody is measured on the outcome. The sections below cover where this breaks and what to change.
A signed contract is not implementation readiness
A signature confirms that the customer agreed to commercial terms. Implementation needs different things: a named customer owner, accessible data, technical access, someone with authority to approve decisions and time on the customer's calendar. A contract guarantees none of them.
Treat readiness as a formal checkpoint between signature and kickoff. Before work begins, confirm in writing:
- 01Who owns the project on the customer side, and how much of their time is committed
- 02Which systems and data sources are in scope, and who controls access to each
- 03Who approves configuration and process decisions
- 04Which internal date or event the customer is working toward, and why
If any of these is unknown, the project has not started. It is waiting, and the wait should be visible on the plan rather than absorbed into the timeline.
Disconnected incentives create unowned gaps
Most implementation delays happen at the boundaries between teams, not inside a single task. Those boundaries are shaped by how each team is measured.
Sales is typically measured on bookings and close dates. Implementation is measured on time to go-live and project margin. Customer Success is measured on retention and expansion. Each goal is reasonable. Together, they leave the customer's outcome without a clear owner. Sales has an incentive to close before readiness is confirmed. Implementation has an incentive to reach go-live, even if adoption is not yet secure. Customer Success inherits the result without having shaped it.
Inside the project, the same pattern repeats. When the owner of a decision is unclear, the decision waits, and the customer experiences that as slowness even while every team believes it is doing its part. The practical response:
- 01Assign one accountable owner to every workstream on both sides: data, integrations, configuration, training and sign-off
- 02Record those owners in a shared plan the customer can see and edit
- 03Give each owner a named escalation path when a decision is blocked for more than an agreed number of days
Shared accountability sounds collaborative. In practice, it means a decision has no owner.
Success criteria must describe the outcome, not the configuration
“Go live” describes a technical state. It says nothing about whether the customer can now do what they bought the product to do. If success criteria only cover configuration, a project can succeed on paper and fail with the customer.
Define two or three outcome criteria during the sale or no later than kickoff, written in the customer's own terms. Useful criteria name:
- 01The process or tool the product replaces
- 02The team that must use it, and how often
- 03The report, decision or result leadership expects to see
Then connect every milestone in the plan to at least one of those criteria. A milestone that does not move the customer toward an outcome should be questioned, deferred or removed.
Designing accountability across Sales, Implementation and Customer Success
Each handoff loses context. Sales knows why the customer bought. Implementation knows what was configured and what was deferred. Customer Success inherits the relationship, often without either.
Better handoff documents help, but they do not fix the underlying issue. Leaders have to design accountability so that each team carries part of the responsibility for the outcome, not only for its own stage.
- 01Shared definitions. Sales, Implementation and Customer Success use the same written definition of a successful customer, based on the outcome criteria agreed at kickoff, not three separate definitions of a completed stage.
- 02Overlapping measures. Each team carries at least one measure outside its own stage. Sales can be reviewed on readiness at kickoff, Implementation on early adoption and Customer Success on participation in the final implementation milestones.
- 03Sales to Implementation. A written record of the buying reason, commitments made, known risks and stated success criteria, reviewed live with both teams before kickoff.
- 04Implementation to Customer Success. A closeout record of scope delivered, open items, adoption status and the stakeholder map, followed by a joint transition meeting with the customer.
- 05Commitments. Anything promised during the sale is either in the plan or explicitly declined before kickoff.
- 06A single executive owner of time to value. Someone at the leadership level owns the full path from signature to realized outcome, with authority to resolve conflicts between teams. Without that owner, cross-team problems are discussed rather than decided.
Deployment completion is not value realization
Deployment completion and value realization are separate milestones. Both contribute to customer success. Deployment completion means the product is configured, available and accepted against the go-live criteria. Value realization means the intended people use it to run the intended work, and the customer's sponsor can see the result.
This does not mean an implementation project should stay open until every business benefit has arrived. Some value takes months or longer to appear. The project should close against defined exit criteria, while responsibility for value realization moves to Customer Success with the same outcome criteria still in view.
A practical close for the implementation includes a short, bounded adoption window after go-live. During that window, confirm:
- 01The intended users are active, measured against the number planned
- 02The target workflow is running in the product, not alongside it
- 03A plan and date exist for retiring the old process or tool
- 04The sponsor agrees how progress toward the outcome criteria will be reviewed after handoff
Teams that measure only go-live are often surprised at renewal. Teams that measure value realization as a separate, owned milestone see problems while there is still time to act.
Building a repeatable, accountable delivery process
Repeatability does not mean rigidity. It means every customer moves through the same checkpoints, even when the work inside each stage varies.
A workable structure:
- 01Readiness review. Before kickoff, covering owners, scope, access and the customer's target date.
- 02Kickoff. Confirming outcome criteria and the shared plan.
- 03Milestone reviews. Where risks are named and assigned, not only reported.
- 04Go-live criteria. Agreed in advance, not negotiated at the end.
- 05Adoption window. Time-bound, with defined usage and workflow checks.
- 06Formal transition. To Customer Success, with a closeout record, a joint customer meeting and the outcome criteria carried forward.
Each stage needs an owner, an exit condition and a defined place to escalate exceptions. When a project moves forward without meeting an exit condition, record the decision and the reason. Over time, those records show where the process needs to change.
What senior leaders should measure
Churn and renewal rates show problems after the customer has already decided. Leading indicators show problems while there is still time to act:
- 01Time from contract signature to kickoff
- 02Readiness items still open at kickoff
- 03Missed milestones, and whether the cause was customer, internal or scope
- 04Projects without a named customer owner
- 05Unplanned scope changes after kickoff
- 06Time from go-live to first meaningful use
- 07Active users compared with intended users during the adoption window
- 08Handoff records completed on time
- 09Customers with outcome criteria reviewed after handoff, compared with customers tracked only to go-live
None of these needs new software to start. They need a consistent definition, a named owner and a regular leadership review.
Closing
Implementations rarely fail because of the product alone. They fail when readiness, ownership, incentives and handoffs are treated as assumptions instead of managed work, and when go-live is treated as the only measure of success. Go-live and value realization are separate milestones with separate owners. Measuring both, and making each team accountable for part of the outcome, is ordinary operational discipline. It is also where much of a customer's long-term value is decided.
Back to Insights