# LinkedIn outreach for enterprise deals
> Map the buying committee, find the economic buyer and technical gatekeeper, and send each role a LinkedIn message built for what they're judged on.
- HTML: https://getkinlead.com/linkedin-outreach-for-enterprise-deals
- Markdown: https://getkinlead.com/linkedin-outreach-for-enterprise-deals.md

**Short answer:** Treat an enterprise account as a group of people, not one lead. Name the economic buyer, the technical gatekeeper and the end user, then send each one a message about the thing they are judged on. Work from the end user upward so the person who signs has already heard your name.

## Map the buying committee before you send anything

In a small business you convince one person and the deal is done. In an enterprise account you sell to a group whose members want different things. Message only the VP and you have no evidence the tool works day to day. Message only the manager and the contract stalls somewhere above them.

Write down four roles for every account you care about. You won't always find all four, but the list stops you from sending the same paragraph to everyone and calling it a campaign.

| | Role | What they're judged on | What kills the deal |
| --- | --- | --- | --- |
| Economic buyer | Cost, revenue, risk of the project failing | A pilot with no number attached to it |
| Technical gatekeeper | Security, uptime, how much work the rollout adds | A demo that skips their architecture questions |
| End user | Whether their day gets easier or longer | Another tool they have to maintain |
| Champion | Looking right for bringing in something that works | Being surprised in front of their boss |

## Find the people who actually hold those roles

Job titles lie. A head of revenue operations at one company owns the budget and at another runs reports for someone else. Check what the person posts and who reports to them before you decide which role they play.

Two signals tell you someone is worth a message. They post about the problem you solve, or they started in the role recently. A new VP usually has a mandate and a budget in the first two quarters, and that window closes fast.

1. **Search the company, then the function.** Type the company name into the LinkedIn search bar, switch to People, then add title words like VP of Sales, Head of Infrastructure or Procurement Manager. Run one search per role instead of one search for the whole account.
2. **Read the company page posts.** Open the posts tab on the company page and look at who comments. Employees who comment on hiring news or product launches are active on the platform and more likely to answer a request.
3. **Walk the org chart from one profile.** When you find a manager, open their profile and look at who they report to and who reports to them. That single step usually surfaces the economic buyer and the end user without another search.
4. **Check the people also viewed panel.** Profiles of one stakeholder usually list the others. This is the fastest way to find a director of operations who controls the budget without having a title that suggests it.

## Write a different first message for each role

The same message to four people reads as a mail merge. A VP skims past anything about the interface. A technical lead skims past anything about growth. Change what the sentence is about, and change the name.

Lead with what that person is measured on and one detail you actually noticed. If you can't find a specific detail, you haven't read enough to send the message yet. Keep each one short enough to read on a phone without scrolling: two sentences of context, one of offer, one question.

**Same message to everyone**

- Hi, I'd love to show you how our platform helps enterprise teams work more efficiently.
- We partner with companies like yours to drive growth and improve productivity.
- Our solution plugs into your existing stack and grows with your team.

**One message per role**

- VP: You're hiring four account executives this quarter. We shorten ramp on new reps, which is the number your board asks about.
- Manager: Your team rebuilds the Friday pipeline report by hand. We pull it straight from the CRM so nobody touches a spreadsheet.
- Gatekeeper: Before the questionnaire lands, we run inside your cloud, support SAML single sign-on, and the rollout is one config change.

```
VP of {function}: Hi {name}, {company} is hiring {number} {role}s this quarter, which usually means {process} is under strain. We take {task} off that team without adding headcount. Open to a short call?

Hiring manager: Hi {name}, your team at {company} ships {deliverable} every {cadence}. We remove the manual steps between {tool A} and {tool B}. Want the two minute version?

Technical gatekeeper: Hi {name}, before anyone sends you a security questionnaire, we run inside {cloud}, support {sso method}, and the rollout is {one sentence}. Happy to send the docs so you can rule us in or out.
```

## Sequence the outreach so nobody gets blindsided

Do not message the whole committee on the same morning. If the VP forwards your note to a manager who has never heard of you, you look like a vendor who went over someone's head. That's a bad first impression to recover from.

Start with the end user or the champion. Get one reply that confirms the problem exists, then move up with that person's name in the first line. You're someone already discussing a solution with their team, which changes how the message reads.

- **you:** Hi Sarah, saw your team is handling the Northwind migration. Are you still building the weekly report by hand?
- **them:** Yes. It eats most of Friday morning.
- **you:** That's the part we remove. I can send a two minute clip of how it works on a setup like yours. Worth a look?
- **draft:** Hi Mark, I've been talking with Sarah about the Northwind migration. Her team loses most of Friday morning to the weekly report. I have a way to take that off them. Open to a short call?

> When you move up the chain, name the person you already spoke to and the problem they described. Going over someone's head only causes damage when you do it silently.

## Keep a record of who said what

A committee conversation falls apart when you forget which of four people told you which thing. LinkedIn won't track it for you. Keep one row per contact with what they're judged on, what they said, what they need next, and the date you last spoke.

When someone goes quiet, don't send a follow-up that says nothing. Send something new: a document, an answer to a question they asked, an introduction to someone useful. Silence usually means the project dropped down their list.

Handoffs matter too. If the technical gatekeeper asks for security docs, send them the same day and tell the champion you did. Small confirmations like that build the case inside the account while you're not in the room.

- Who you contacted and when, so you never double-message the same person from two campaigns
- The exact words they used about the problem, because their phrasing is what the VP will recognise
- What each person asked for and whether you sent it
- Which colleague referred you to whom, so the next message can open with that name

## Doing this with Kinlead

Kinlead keeps the committee in lead groups. Each contact is scored from 0 to 100 against the profile you described, leads below the fit line are dropped, and VPs, managers and gatekeepers can sit in separate groups so a campaign points at the right one.

The [Steal Customers agent](/features/steal-customers) watches competitor company pages and the founder or employee profiles you add, reads the comments on their recent posts, and turns commenters who look like buyers into leads with the post and their comment attached. That gives you a real reason to open a conversation with a role you'd otherwise cold-message.

Campaigns run from your own LinkedIn account at one action every five minutes, inside the send window you set. Queued messages can be read and edited on the Actions page before they go, and replies from every campaign land in one inbox, so a thread that starts with a manager and moves to a VP stays in one place.

## Related

- [AI sales playbook](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Lead scoring setup](https://getkinlead.com/ai-lead-scoring-fit-line-setup.md)
- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)

## Common questions

**Should I send the same message to everyone in the account?**

No. Each person is judged on something different. A VP cares about cost and risk, a manager cares about the team's workload, and a gatekeeper cares about security and rollout effort. The same paragraph to all three reads as a mail merge.

**What if the VP tells me to talk to a manager instead?**

That's a useful outcome. When you message the manager, say the VP pointed you their way. It gives you a reason to be in their inbox and tells the manager the project already has attention above them.

**How do I get past a technical gatekeeper who won't engage?**

Send the material they would ask for before they ask: architecture, security posture, rollout steps. Ask them to rule you in or out rather than to take a meeting. A short technical answer is easier to give than a calendar slot.

**How many people should I contact at one account?**

Three or four. Enough to cover the buyer, the gatekeeper and the person who uses the product daily. Past that you're guessing at names and diluting the story you're telling each of them.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
