LinkedIn messaging for account based marketing

Coordinate messages across multiple roles in one company to create a surround-sound effect that drives internal conversations and bookings, without repeating one script to every contact.

Get started

Short answer

ABM on LinkedIn means targeting several stakeholders at one company with coordinated messages. You send different angles to the executive, the manager, and the end user so they discuss your solution internally before you ask for a meeting.

Map your account roles

You cannot send the same message to a VP and a manager. A VP cares about the quarterly board report, while a manager cares about weekly team output. A feature-heavy pitch to an executive gets ignored. A high-level ROI pitch to a user sounds out of touch. The role changes the pressure, the vocabulary, and the reason someone agrees to a call.

Before you send an invite, list the three roles that influence the buying decision. Each role needs a different hook. Your goal is to create a cohesive narrative across the company. Each role hears a version of the same story that fits their daily work. Write the role map on one page. Put the person's name, their daily pressure, and the one sentence you want them to repeat to a colleague. If you cannot fill that sentence, you do not know the account well enough to start.

A simple map is enough. For a 40-person agency, the owner worries about margin, the account director worries about client churn, and the coordinator worries about status updates. Those are three different conversations about the same broken reporting process. Your messages should connect them without sounding like a copy-paste job.

The executive

Role
Business outcomes
Primary goal
Revenue growth or cost reduction

The manager

Role
Team efficiency
Primary goal
KPIs and reporting

The user

Role
Daily friction
Primary goal
Saving time on manual tasks

The surround-sound sequence

The order of your outreach matters. If you start with the VP, they might delegate you down to a manager who has no context. If you start with the user, you gather language and proof that makes your message to the VP stronger. The user also gives you a reason to mention their team without guessing.

Move from the ground up. This builds a foundation of evidence. When you reach the executive, you have proof from their own team. That makes your message specific and credible. You can say you spoke with someone in the department. That sounds different from quoting a blog post about their industry.

Keep the timing loose. You do not need a military operation. Send the user note, wait for a reply or a profile view, then move to the manager. The gap gives the first conversation time to travel. If nobody replies, wait a few days and try a different angle with the same person before you move up.

  1. 1

    Engage the user first

    Send a connection request to the person doing the work. Ask a specific question about their workflow to confirm a pain point.

  2. 2

    Message the manager

    Reach out to the director or head of the department. Mention you are talking to people in their department about the pain point you just confirmed.

  3. 3

    Message the executive

    Share a high-level result you achieved for a similar company in their industry. Keep it brief and focus on the business impact.

Writing the internal trigger message

The goal of ABM is getting prospects to talk about you to each other. You want the manager to ask the user, 'Do you know this person?' or the VP to ask the manager, 'Is this something we need?' That conversation is the real win. The meeting is a side effect.

Avoid sounding like you are stalking the organization. Do not list every person you have messaged. Use phrases that imply a general conversation is happening within their department or industry. 'A few people on your team' is enough. 'I saw that Sarah, Mike, and Priya all work there' is too much.

The strongest trigger is a specific detail from one role that matters to another. A user says manual data entry eats Friday afternoons. The manager hears that as a reporting delay. The VP hears it as a cost line. Use the same fact at each level with a different consequence. The user gets a question about their week. The manager gets an observation about team output. The executive gets a result from a similar company and a request for 15 minutes.

Too aggressive

  • I am messaging your VP and your team to get your attention.
  • I have already sent requests to Sarah and Mike, so I am reaching out to you now.

Subtle and professional

  • I am chatting with a few folks on your team about how they handle process X. I thought it made sense to share this result with you as well.
  • I have been hearing from a few people in your department that reporting takes four hours a week. I wanted to see if that is a priority for you to fix.

Handling the first response

In a multi-threaded approach, the first person to reply is often the user who is most frustrated. That reply is useful. It tells you where the pain sits and gives you language to use with the manager. Do not rush to book a demo. The user cannot usually approve the purchase, and a demo with the wrong person wastes the account's attention.

When a user confirms a problem, tell them you are already in touch with their boss. This makes you look like a serious partner and puts a flag in the manager's mind. Keep it light. Let them know the conversation is moving without asking them to lobby for you.

If the executive replies first, pivot. Acknowledge their goal and mention you are also reaching out to their team to understand the current friction. Ask for a short call after you have spoken to the team. That call is easier to book because you are not asking the executive to explain the details.

Example

  1. Prospect

    Yeah, the manual data entry is a huge problem for us. It takes half my Friday every week.

  2. You

    I am glad it resonates. I am actually reaching out to Jane Doe to see if she has a vision for fixing this. I will keep you posted.

  3. Prospect

    Fair enough. She is probably wondering why we still do it this way.

Never tell a user to introduce you to their boss in the first message. It creates work for them and makes you look like you cannot find the right person yourself.

Keeping the account from feeling stalked

Multi-threading goes wrong when every message sounds like it came from the same script. People compare notes. If your note to the manager repeats the note to the user word for word, the account notices. The fix is variation. More volume makes the problem worse.

Change the proof, the ask, and the length. The user gets a question about their week. The manager gets a short observation about team output. The executive gets a result from a similar company and a request for 15 minutes. The user message can be two lines. The executive message can be four. The manager message can sit in between.

Leave gaps. Do not message three people on the same day. Do not view every profile in the account in one sitting. A natural sequence looks like one person doing research over a week. A machine sweeping a list looks different. If you use automation, set a send window and a pace that matches how you already work.

Track who has replied and who has gone quiet. If one person asks you to stop, stop for the whole account. If one person says they are not the right contact, ask who is. That answer is better than a meeting with the wrong person. If two people point to the same colleague, that colleague becomes your next message.

Doing this with Kinlead

You can coordinate these multi-threaded campaigns using lead groups. The Steal Customers agent can find people commenting on competitor posts, and you can group them by company to keep account targets organized. Each lead keeps the post URL, what the post was about, and what they commented.

Create separate campaigns for each role. Use a sales playbook to keep a different tone for executives and users. Kinlead sends at a human pace, with each LinkedIn account limited to one action every 5 minutes inside the daily invite and message limits you set and inside a send window in the lead's time zone.

To manage the timing of the surround-sound effect, set your campaigns to hand the conversation to you at the first reply. This lets you coordinate when to push the manager or VP based on what the user says. You can review queued messages on the Actions page before they send, and you can pause any campaign.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? LinkedIn messaging for account based marketing.md