How To Manage The Handover From Sales to Project Team
When you think about handovers in project management, you probably think of the handover to the customer, or for technical projects, the service desk who is going to support the software product on an ongoing basis. That handover to operations at the end of a project is something that is a focus for teams who want to successfully deliver business change.
However, there’s another handover, equally, if not more important, and it comes far earlier in the proposal. The handover from sales team to project team is essential to get the project off to a good start. Sometimes project managers are involved in the pitch and proposal; other times they have very little involvement beyond their resume being appended to a proposal to let the client know who will be managing the work.
Either way, when the sales team secures a new project, that handover to the team who will deliver it is crucial. It’s worth considering the risk of failing to manage this handover effectively.
- Projects take longer to get started
- Key information is not passed on to those who need it
- Clients receive a poor impression of your PSO from the start of the project engagement.
So how can you offset some of the risks, and ensure that the handover from sales to project team is as efficient as possible? Here are some suggestions.
Use Automation for Proposals
A clear proposal helps the project team know what has been promised to the client. Any constraints or expectations are set out before the project even starts. The project manager can have an informed and professional conversation with the client, who doesn’t feel as if they are providing the same information all over again.
This is all possible with proposal automation. Proposal automation is where your PSO has a library of curated content specifically for commonly-asked RFP questions. As proposals are received with new questions, you update the library. The end result is a constantly improving knowledge repository, with responses that can be copied and pasted to provide a proposal document. Then, depending on the nature of the project and the customer, those answers can be refined as necessary to provide exactly the information the client is asking for.
Finally, proposal automation ensures that the finished document is stepped through a workflow process to secure the necessary checks and approvals before it is issued to the client.
Automating the workflow and making all aspects of the work to date transparent are ways of making the handover from sales to project that little bit easier. The end of the proposal automation process is a decision: either to proceed with the project or to record it as an unsuccessful bid.
Once a proposal is accepted by the client, relevant information can be pre-populated into the project management system to save the project team a job. As a project manager, you have everything you need to get started at your fingertips: details of key contacts, and outline of what is expected and what needs to be delivered, within any appropriate constraints or guidelines. The decision to proceed is effectively the mandate the project manager needs to get started, so pushing a proposal through a workflow reduces the time it takes to get to work.
Ideally, the project manager should be involved with the proposal and have the opportunity to meet with the client if that is part of the process. The more the project manager knows about the project before the work “officially” starts, the easier it will be to make an efficient start. This might not be possible, given the workload of project managers and the other initiatives they may be working on. However, the more focus you can put on cross-team collaboration, the better it is. Project managers will have some good ideas about how best to deliver the work, and will probably need to provide details around the types of resources required for the project or the timelines.
You could make these “transactional” moments, where the sales team asks a question and the project manager pings back a response. But it’s more effective to try to create genuine collaboration between the sales and project teams, and a discussion that lasts beyond the moment of this particular pitch. Try to build relationships between the sales and project teams over time. It’s a long term commitment but it pays off because the handovers will be smoother, and the proposals will be more robust.
You can start the conversation going between the teams with very simple steps. For example, once a quarter invite the sales team to present to the project managers, and vice versa. Socialize as a business across teams. Create opportunities for networking – virtually or in person – across the organization so that people get to know each other. All of these little interactions will make the handover process more reliable and faster.
Start Your Project With The Information You Need
Project teams are used to working in a changing environment, often without all the information they really need to make decisions. Many client engagements evolve over time, even for fixed price contracts, and PSOs need to be flexible to deal with that.
However, it is far easier to at least get a core set of information at the start of any project. That is likely to be different for different organizations. You might need to always capture certain information about the size of the client’s company, for example, whereas another PSO carrying out different engagements may be more interested in staff engagement or organizational culture. Whatever the key points are for you, try to include capturing them in the sales process. If you already do have relevant information on hand, make sure it is included in the handover process.
Make Knowledge Management Part of the Process
The sales team should pass on everything they have captured about the client organization. It may help to prepare this in a structured way, perhaps as part of the output of the process for a successful RFP. Build up your organizational knowledge by updating your knowledge management system with your latest intelligence.
Sharing information across the organization makes it easier for project teams to pick up the work and run with it. Equally, information gleaned during the sales process might be incredibly useful for other teams preparing other proposals. Handovers are more successful when the process is automated. For more information on whether proposal automation is right for you, download our white paper on the five signs your organization needs to automate your RFP process.Request A Demo