Implementation Planning Basics
A defensible implementation plan covers configuration, integration, security, enablement, and go-live — co-owned with the customer, anchored to the business case.
The is the bridge between the deal you sold and the value you will be measured on at renewal. It must be co-authored by vendor and customer, anchored to the (not the product), and reviewed weekly with named owners on both sides. Plans built by the vendor alone do not survive contact with customer reality.
Deep practical explanation
Every covers six workstreams: technical configuration, integration, security and , data migration, and change communication, and pilot/. Each workstream has an owner on both sides and a written acceptance criterion.
Anchor every workstream to the . If a phase does not move a tracked outcome forward, it does not belong in the plan. This discipline keeps from creeping and keeps the customer focused on outcomes, not features.
Review the plan weekly during implementation. Slips compound; a 1-week slip caught in week 2 is fixable, the same slip caught in week 8 is a .
Real-world example
A platform vendor signed a $600k deal and handed off to a who used the standard 90-day template — same template for every account. The customer's environment had two custom integrations that were not in the template. By week 6, the integrations were not built, the pilot was delayed, and the customer's exec sponsor began to question the choice.
The rebuild: a co-authored 1-page plan, signed by both sides at kickoff, that explicitly named the two custom integrations as Phase 2 with a separate owner and date. The pilot launched on time on the in- workflows; the integrations followed in week 14 as planned. The customer stayed bought-in throughout.
Tactical steps
- Co-author the plan with the customer in the kickoff meeting; never deliver it pre-built.
- Anchor every phase to a measurable outcome from the .
- Name owners on both sides for every workstream.
- Review the plan weekly; surface slips early and replan publicly.
- Cut before slipping dates — the most damaging signal is a date that keeps moving.
- Capture the lessons at ; feed them into the next implementation. The CS team that learns fastest wins .