
You have multiple stakeholders engaged in a deal - a VP, an IT Director, a team manager - and you need to communicate with all of them without sending the same generic message to everyone.
Each stakeholder in a buying group cares about something different. A CFO is thinking about cost and payback. An IT Director is thinking about security and integration risk. A team manager is thinking about whether their people will actually use it. If you send the same message to all of them, it lands weakly with everyone. When you speak to each person's specific concern, you give them a reason to advocate for the deal in their own language - which is what moves a committee.
Generic messaging in a multi-stakeholder deal creates silence. The CFO does not respond because you talked about features. The IT Director raises a late security concern because you never addressed it. The team manager stays passive because no one asked what they needed. Each gap is a reason for the deal to slow down or fall apart.
You can prepare a short, role-specific message or talking point for each stakeholder type in a deal, so every person you reach feels like you understand their world.
Before any multi-stakeholder meeting or outreach, write one sentence for each contact that answers: 'What does this person lose if the problem stays unsolved?' Use that as your opening.
Match your content to the role. For economic buyers, lead with cost, payback period, or risk reduction. For technical evaluators, lead with integration, security, and implementation effort. For end users and managers, lead with time saved, workflow fit, and ease of adoption.
When your champion is running an internal meeting without you, give them a one-page summary tailored to the audience in the room - not a generic deck. A single page with three bullet points per persona is more useful than a 20-slide presentation.
After each stakeholder interaction, note what they reacted to and what they pushed back on. Adjust your next message to that person based on what you learned.
The AE sends the same two-page capability overview to the VP of Operations, the IT Director, and the Finance Manager. The VP does not reply. The IT Director asks about data residency, which was not in the document. The Finance Manager asks for a cost breakdown that was also missing. Three separate follow-up threads open and the deal loses momentum.
Before the next round of outreach, the AE prepares three short emails. To the VP of Operations: 'Based on what your team shared, the main gain is roughly four hours per week per ops manager - here is how we calculated that.' To the IT Director: 'Here is a one-page summary of our security posture, data residency, and integration approach for your review.' To the Finance Manager: 'Attached is a simple cost and payback model based on your team size - happy to walk through the assumptions.' Each person gets exactly what they need.
You can prepare a short, role-specific message or talking point for each stakeholder type in a deal, so every person you reach feels like you understand their w
You have got it when different stakeholders in the same deal give you different positive signals - the CFO responds to the numbers, the IT Director confirms the technical fit, and the manager says their team is on board.
Each stakeholder in a buying group cares about something different. A CFO is thinking about cost and payback. You can prepare a short, role-specific message or talking point for each stakeholder type in a deal, so every person you reach feels like you understand their world.
Generic messaging in a multi-stakeholder deal creates silence. The CFO does not respond because you talked about features.
£7-10k flat fee. The methodology, delivered.
See Hire with Assessment