# LinkedIn messaging playbook for breaking into large accounts
> Learn how to map a large account by role, write different LinkedIn messages for users, managers and executives, and turn one reply into a referral without spamming.
- HTML: https://getkinlead.com/linkedin-messaging-playbook-for-breaking-into-large-accounts
- Markdown: https://getkinlead.com/linkedin-messaging-playbook-for-breaking-into-large-accounts.md

**Short answer:** Breaking into a large account means messaging several people in different roles, not one contact. You write a different first line for the user, the manager and the executive, then use any reply to start a real conversation inside the company. The goal is to be recognized when your name comes up in their internal channel.

## Map the account by role

In a company with thousands of employees, one contact is a single point of failure. If that person leaves, changes team or ignores you, the deal stops. You need three layers of stakeholder: the person who feels the pain, the person who manages the pain, and the person who pays to stop it.

You are not trying to blanket the company. You want your name to be familiar when it comes up in a meeting. Pick people who touch the same process, then write to each one about the part of the process they own.

Start with the process, not the title. Write down the steps that happen before the buyer gets value: who prepares the report, who checks it, who presents it. The people who touch those steps are your three contacts.

| | Role | What they care about | Message angle |
| --- | --- | --- | --- |
| The user | Daily workflow and friction | Removing a specific chore or manual task |
| The manager | Team output and KPIs | Visibility and team efficiency |
| The executive | Revenue, risk and cost | Business goals and bottom-line impact |

## Write a different first line for each role

The same script sent to three people looks like a bot. Each message should stand alone, because the user may never see the manager's message. Write a specific first line for each role and keep the problem the same.

Use the user's language for the user, the team's numbers for the manager, and the business outcome for the executive. Do not ask the user to introduce you to their boss. That puts them in an awkward position and usually kills the thread.

Keep the problem identical across all three messages. If the user hears about report cleaning, the manager should hear about report cleaning, not a different problem. The executive can hear the cost of that same problem.

```
User: Hi {first_name}, quick question about {task}. Is your team still doing it manually, or have you automated it?

Manager: Hi {first_name}, I spoke with {user_name} on your team about {task}. It sounds like it adds {time} to {process}. Is that slowing your weekly numbers?

Executive: Hi {first_name}, {user_name} mentioned {task} takes {time} each week. If that time went away, what would your team do with it?
```

## The multi-thread messaging sequence

Start with the user to check the problem is real. A reply from the user gives you a concrete detail to use with the manager. Then message the manager about the team effect, and the executive about the business effect.

Space the messages over a few days. If all three land on the same morning, it looks coordinated in a bad way. Let the first reply shape the next message.

If the user replies with a detail you did not expect, use it. The best manager message often comes from the user's own words, not from your original hypothesis.

- **you:** Hi Sarah, quick question: is your team still spending two days a week cleaning these reports before the Monday review?
- **them:** Two days is optimistic. It's usually three by the time finance sends corrections.
- **you:** That's the bottleneck I suspected. I'm going to ask Mark how the corrections affect your weekly numbers. If he says it's fine, I'll leave you alone.
- **draft:** Hi Mark, Sarah mentioned finance corrections add a day to the report cycle. Does that delay your Monday KPI review, or is the team absorbing it?

## Top-down vs bottom-up strategies

You have to decide whether to build pressure from the bottom or ask for a mandate from the top. Bottom-up is slower, but you have proof of pain when you reach the executive. Top-down is faster, but executives often delegate the research to people who are too busy to talk to you.

A bottom-up approach lets you use the user's own words when you reach the VP. You can say the team mentioned the report cycle takes three days. That gives you a concrete detail to use, not a claim about their team being slow.

A top-down message works when you have a specific reason to believe the executive already cares. A public post about cost cutting, a new hire in the team, or a product launch is a reason. A job title alone is not.

**Single-threaded**

- Messaging only the VP and waiting for a reply
- Sending a generic 'I want to help you grow' message to ten people
- Asking the user to introduce you to the boss

**Multi-threaded**

- Messaging the user for a gut check on a problem
- Telling the manager that their team is struggling with a specific task
- Using the user's exact words as the hook for the executive

## Handling the internal referral

A referral is the best outcome in enterprise sales. When a VP tells you to talk to a director, you are a recommended vendor. Sellers often ruin this by starting a brand new cold conversation with the director.

Name the person who referred you in the first sentence. That creates a social obligation for the director to respond, and it tells them you are not guessing.

If the director does not reply, go back to the person who referred you once. Say the director has not replied and ask if there is a better person. Do not go around the director to their boss.

1. **Secure the specific name.** If a VP says 'talk to my team', ask: 'Who is the best person to handle the technical evaluation for this?'
2. **Build the bridge.** Message the director the same day. Start with: 'Elena told me to reach out about the report bottleneck we discussed.'
3. **Close the loop.** Once the director agrees to a call, send a short note to the VP: 'Thanks for the intro to Daniel. We are talking on Tuesday.'

> Never ask a user to introduce you to their boss. Get the boss's permission to talk to the user instead.

## When replies stop or the account goes quiet

Two unanswered messages to the same person is a signal. Do not send a third. Either the problem is not urgent, the person is not the buyer, or your message landed at a bad time. Pick a different role or wait for a trigger.

Triggers are easy to spot on LinkedIn: a new hire in the team, a post about a project, a funding round, a product launch. Use the trigger in the first line so the message does not read like a follow-up.

Keep a simple note for each account: who replied, who ignored you, and what you learned. Without that note you will repeat the same message to the same person in six weeks.

Do not delete the account from your list. Keep it in a separate list for later. A quiet account often becomes a live account after a reorg, a new hire or a bad quarter.

> If two people at the same account ignore you, stop messaging that account for a month. A third message to a third person looks like a campaign.

## Doing this with Kinlead

Kinlead finds people who match the buyer you describe and scores each lead from 0 to 100. You can keep users, managers and executives in separate [lead groups](/features/lead-groups-and-scoring) and point a different campaign at each group.

To find new entry points, the [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles. It reads comments on recent posts and turns commenters who look like buyers into leads, with the post URL and comment kept for context.

Kinlead sends from your own LinkedIn account at a human pace, at most one action every 5 minutes. You can set a [send window](/features/campaigns-and-send-windows) for business hours in the lead's time zone, so messages land when stakeholders are at their desks.

If you already have a list of stakeholders, import a CSV of LinkedIn profile URLs and put them in the right group.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Steal customers agent](https://getkinlead.com/features/steal-customers.md)
- [Lead finders](https://getkinlead.com/features/lead-finders.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**How many people in one account should I message?**

Three to five people across different levels is enough for most mid-sized and large accounts. More than that looks like a campaign to the internal channel.

**What if the executive ignores me but the user replies?**

Use the user's reply as the reason to message the executive again. Say you are talking with the user about a specific problem and ask if the executive wants the summary.

**Should I use a connection request or a direct message first?**

Use a connection request with a short note under 200 characters. Lead with the specific problem for that role and skip the 'I'd love to connect' line.

**What do I do when someone says 'not now'?**

Ask what would need to change and when to check back. Put the date in your notes and message them after that date, not before.

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