Keeping consultants after go-live: why people leave when a long project ends

The system went live on a Monday. By Friday, the client's CFO has written a warm email, the founder has sent a cake and the team has a lunch. Three weeks later, the lead data consultant gives notice. She says there is no single reason. She was tired and nobody had mentioned what came next.

Anyone who runs a delivery team knows this pattern. A long project builds close bonds and heavy fatigue. When it ends, the structure that held the team together ends too. This post explains why people leave then and what a delivery head can do in the months around go-live.

• Exhaustion: the team ran hot through testing and cutover, and the first quiet days let people think.
• Uncertainty: nobody has said where they go next, and people imagine the worst.
• Lost identity: for a year they were the finance team on that client. Now they are on the bench.
• Market timing: their name is known on the client's side, and recruiters call at exactly this moment.
• Unmet promises: a talk about promotion or a pay review was put off until after go-live.
• Hypercare fatigue: the same few people stay on call while others move on.

Retention work starts in the last two months of the project, not after. Make a list of the people whose loss would hurt: those with deep client knowledge, rare skills or a role no one can fill quickly. Beside each name, write what you can honestly offer next.

That offer may be a new project, a larger role, a rotation to presales, support work on the client's next phase or a stretch on an internal practice. It should be specific, and it should be true. If you cannot offer anything yet, say so and give a date for the answer.

1. 1

   Name the key people eight weeks before go-live

   The delivery head and HR agree a short list. Include quiet performers, who often leave without warning.

2. 2

   Hold a next-step talk with each person

   Cover what comes next, what they want to learn and what worries them. Take notes. Share what you can decide yourself, and promise a date for the rest.

3. 3

   Protect rest after cutover

   Give agreed time off in a way that is visible to the whole team. Rotate hypercare so the same people are not on call every night.

4. 4

   Recognise by name and by deed

   Tell the team and the client what each person did. Add a promotion or pay review where it was already due, and do not leave it for later.

5. 5

   Run stay conversations after three to four weeks

   Ask what keeps them here, what might make them leave and what one change would help. Act on at least one item and tell them.

6. 6

   Review the pattern after each project

   Note who left and why. Use the notes to improve the next project's plan.

Many consultants leave because they cannot see their next role. A written ladder answers much of that. Our post on career paths for functional and technical consultants explains how to build one. Without it, every stay conversation turns into an argument about titles.

Staffing decisions matter too. If you want to retain people through the next project, plan the load from the start, as set out in staffing an ERP implementation without burning out the team. Burnout during the build is the first cause of a resignation after it.

Clients who have worked closely with your consultants sometimes try to hire them at the end of a project. This is common and not always hostile. Decide your stance before it happens. Check what your client contract says about non-solicitation, and have your adviser read it.

Talk to the consultant openly too. If you treat the question as betrayal, they will hide it. If you ask what they want and respond with a real next step, many will stay. Those who go can leave on good terms, which helps future work with the same client.

Open: thank them for something specific from the project.
Ask: what did you enjoy most, and what drained you most?
Ask: what would you like to do or learn in the next year?
Ask: what would make you consider leaving, and what would keep you?
Check: workload, rest taken, team relationships, recognition felt.
Share: what the firm can offer, what is undecided and when you will return with an answer.
Record: three points agreed, owner of each, review date. Keep the notes private to the delivery head and HR.

If resignations repeat after every project, the issue is in how projects are run and how people are placed afterwards. Look at exit reasons, pay against role scope, project allocation and manager behaviour. Our employee retention and attrition management service helps firms find the pattern and plan changes.

The broader picture of people practice in this sector is in the HR guide for software development companies. If you also want a process for hiring replacements well, see testing process knowledge when hiring ERP consultants.