What Is Implementation?
Implementation is the technical phase of customer onboarding focused on product configuration, data migration, integrations, and environment setup.
Implementation is the technical backbone of onboarding. It covers everything required to get the product working in the customer's environment: configuring settings, migrating data from previous systems, building integrations with existing tools, setting up user permissions, and creating custom workflows or reports.
Implementation complexity varies enormously by product. A self-serve SaaS tool might require 5 minutes of setup. An enterprise CS platform might need 4-8 weeks of implementation involving data engineers, solution architects, and multiple integration partners.
Implementation Best Practices
Define scope clearly at kickoff. Implementation scope creep is one of the top causes of delayed onboarding. Document exactly what will be configured, migrated, and integrated in phase one. Additional requirements go into a phase-two backlog, not the initial timeline.
Assign clear ownership for each implementation task. Some tasks require the customer's IT team (API access, SSO configuration, data exports). Some require your team (configuration, migration scripts). Ambiguous ownership causes delays when both sides assume the other is handling a task.
Implementation and CS Alignment
CSMs should be involved in implementation planning even if a separate team handles execution. The CSM understands the customer's business goals and can ensure that configuration decisions support those goals. A product configured for efficiency without considering the customer's specific workflow needs may technically work but fail to deliver the expected value.
Post-implementation handoff to the ongoing CSM should include documentation of configuration decisions, known limitations, workarounds implemented, and open items for future phases. This context prevents the CSM from re-discovering issues the implementation team already identified.
Track implementation metrics: days to completion, scope changes, customer satisfaction with the implementation experience, and time from implementation completion to first value milestone. These metrics identify bottlenecks and improvement opportunities in the implementation process.
Frequently Asked Questions
What is included in a SaaS implementation?
SaaS implementation typically includes product configuration, data migration from existing systems, integration with other tools (CRM, email, data warehouses), user provisioning, SSO setup, and custom workflow or report creation.
How long does implementation take?
It depends on product complexity. Simple tools: days. Mid-market products: 2-4 weeks. Enterprise platforms: 4-12 weeks or more. Factors include integration count, data migration volume, configuration complexity, and customer IT resource availability.
Who manages implementation?
Some companies have dedicated implementation or solutions engineering teams. Others assign implementation to the CSM or a technical onboarding specialist. For complex enterprise products, a project manager often coordinates across vendor and customer teams.