What does an implementation manager do?

What an implementation manager owns after the contract is signed

After the contract is signed, an implementation manager owns the path to go-live: scope, plan, set-up and the moment the customer can work without help. In software that usually means configuration, data migration, user training and connecting the product to the customer's other tools.

They work as a project lead on the customer's behalf. The customer brings an internal owner, often an operations or IT lead, and the two agree a plan with milestones, dates and who does what. Slipped dates are the implementation manager's to spot early and explain.

• Run a kick-off meeting that confirms scope, success criteria and owners.
• Plan data imports, permissions and connections to the customer's systems.
• Train the first users and the person who will administer the product.
• Track risks and escalate blockers on either side before a date slips.
• Sign off go-live and hand the account to customer success.

How the handover from sales to implementation works

The handover from sales works when the account executive passes on the customer's reasons for buying, not only the paperwork. The contract says what was bought; the implementation manager also needs the problem the buyer described, who championed the deal, who doubted it and any dates the customer is working towards.

A good handover is a short written note followed by a call with the seller, before the customer kick-off. Teams that skip it make the customer repeat everything they told sales, which is a poor first week for a new account.

Why expectations set in the sales cycle land on the implementation manager

Expectations set in the sales cycle land on the implementation manager because they are the first person who has to make them true. A loose answer in a demo, such as a connection described as simple or a go-live promised for the end of the month, becomes the customer's plan.

This is why experienced implementation managers ask to see the sales notes, join late-stage calls for complex deals and write down assumptions at kick-off. When a promise cannot be kept, they say so early and offer an alternative, rather than letting the customer discover it at launch.

Implementation manager, onboarding manager or implementation specialist

An implementation manager leads the whole rollout, while an implementation specialist usually does the hands-on configuration and data work inside it. An onboarding manager is the closer neighbour: in many companies the two titles mean the same job, but onboarding often refers to lighter, faster set-ups for smaller customers.

Customer success is the next role along. A customer success manager looks after adoption, renewal and growth once the account is live, so the implementation manager's sign-off is their starting point. Implementation managers often report to a head of professional services, customer success or operations.

What it means for someone selling to an implementation manager

If you sell to an implementation manager, expect detailed questions about rollout rather than vision. On the buyer's side, the person who will run the internal rollout of your product often joins late in the deal to judge set-up effort, data migration and who on their team will carry the work.

Bring a realistic plan with dates and owners, name the effort you need from them, and say plainly what is not included. Implementation managers who sell project or onboarding tools to their own teams also care about templates, visibility for customers and less status chasing.