# Connecting with non-decision makers for internal intel
> Target end users and middle managers on LinkedIn to map the buying process and gather intel before you approach the executive who signs the deal.
- HTML: https://getkinlead.com/connection-requests-for-cross-functional-partners
- Markdown: https://getkinlead.com/connection-requests-for-cross-functional-partners.md

**Short answer:** Target the people who use the product daily instead of the person who signs the check. Connect with peers and managers in the target department to learn who actually makes decisions and what the current pain points are, then take that detail to the executive.

## Why target non-decision makers

Most sales teams go straight to the VP or the C-level. Those people have the most filters on their profiles and the least patience for cold outreach. They ignore messages from strangers unless the value is obvious in the first line.

Individual contributors and middle managers are easier to reach. They feel the daily friction of a broken process, so they admit to specific problems instead of reciting a company line. They'll tell you the internal name for the tool, the workaround the team built, and the reason the last vendor got turned down.

The other thing they give you is language. Every company has its own words for things. A team at Northwind might call their handoff process 'the queue' while a team at Acme calls the same thing 'triage'. Open with the wrong word and the executive knows you've never spoken to anyone inside.

None of this works if you treat them as a stepping stone. People can tell when a connection request is a door rather than a conversation. The ones who answer are usually the ones who like talking about how their team works, so let them talk.

**The direct executive approach**

- Messaging a VP of Sales: I have a tool that increases revenue by 20%. Do you have 15 minutes next Tuesday?
- Sending a generic pitch deck to a CEO without any internal context.

**The intel-first approach**

- Messaging a Sales Ops Manager: I saw you're scaling the team at Acme. I'm curious how you're handling lead routing right now.
- Asking a user for their opinion on a workflow trend before mentioning a product.

## Mapping the department

You need more than one role in the department to see the whole buying process. Each role shows you a different part of it. Talk to one person and you get one person's view of the problem.

Start with the people who touch the work. Then find the person who manages them. Then find whoever owns the budget line. On LinkedIn the reporting structure is usually readable from titles and from the company page. Job postings help too: a posting that says the role reports to a Director of Revenue Operations tells you where the team sits.

The goal is to know who uses the tool, who manages the tool, and who signs for it before you ever write to the executive. That keeps you from walking into a meeting blind.

Write the map down. A plain list of names, roles and what each person told you is enough. When you message the executive later you'll be pulling from it.

| | Role | Primary goal | Intel provided |
| --- | --- | --- | --- |
| Individual contributor | Find daily pain points | Specific workflow gaps and user frustration |
| Team lead or manager | Find the budget holder | Reporting structure and team priorities |
| Ops or enablement | Find the procurement process | Current tool stack and integration hurdles |

## The connection strategy

Don't sound like a salesperson. If they think you're trying to get to their boss, they stop replying. Position yourself as a peer or as someone researching how teams like theirs work.

Look for something real to open with. A shared former employer, a post they wrote, a comment they left on someone else's post, a talk they gave. One specific detail beats a paragraph about your product.

Send the request without a note if the note would only be about you. A blank request with a real reason to connect later is better than a note that reads like a template.

1. **Identify the peer.** Search for people in the target department whose title matches your existing customers, or who posted about a relevant industry problem in the last few weeks.
2. **Send a low-friction request.** Send a connection request with no pitch. Mention a specific project or a point of view they shared on LinkedIn.
3. **Ask for a perspective.** Ask how they handle a specific trend in the industry. Don't ask for a meeting in the first two messages.
4. **Listen for the gap.** Focus on learning their current workflow. Let them complain about their process before you suggest a solution.

## Extracting internal intel

Once they accept, move from a general conversation to specific internal detail. You want to know how they buy, who they trust, and what the executive actually cares about.

Ask open questions that get them describing their own environment. 'How do you handle X today?' works better than 'Do you have a problem with X?' The second invites a yes or no. The first invites a story.

Three questions cover most of it: what the workflow looks like today, what happens when it breaks, and who gets involved when the team wants to change something. The third one is where budget, procurement and the executive's name usually come out.

- **you:** Thanks for connecting. I'm curious, since you're managing the SDR team at Northwind, how are you guys currently handling the handoff to AEs?
- **them:** It's a bit of a mess honestly. We use a shared sheet and a lot of Slack pings. It's a lot of manual work.
- **you:** That sounds tedious. When you've looked at tools to fix that in the past, does the decision usually come from your VP or is it something your team trials first?
- **them:** Usually, the VP has to approve the budget, but she only cares if it saves the AEs time. If we can prove it, she's usually on board.

> Never ask for a referral to the VP in the first conversation. Build trust first so they feel like they are helping a peer rather than passing a lead to a vendor.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe and scores each lead from 0 to 100 against that profile. Leads below the fit line aren't kept. That saves you from manually checking whether a title is really the end user you want to talk to.

The [Steal Customers agent](/features/steal-customers) fits this job well. It watches competitor company pages and reads the comments on their recent posts, then turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented, so you have something real to open with.

1. **Find the users.** Use [lead search](/tools/find-leads) to find people matching your user profile and keep them in a lead group.
2. **Target active users.** Point the Steal Customers agent at competitor pages to turn commenters into leads.
3. **Automate the opening.** Run a campaign whose AI-written connection note opens with why that person became a lead.
4. **Hand off at the first reply.** Set the campaign to hand the conversation to you at the first reply so you can do the intel gathering yourself.

## The transition to the decision maker

Now approach the executive with a message built on what you heard. The details come from their own team, which is why it lands differently from the other eleven messages in their inbox that morning.

Name the pain point in the team's own words. Mention the person you spoke to only if that person agreed to it. Some people will talk to you happily and still not want their name in a message to their VP, so ask before you quote anyone.

Keep the ask small. One question, one meeting, one reply. The executive has the context now, so you don't need to sell the whole thing in the first message.

```
Subject: [Pain Point] at [Company]

Hi [VP Name],

I've been speaking with a few people on your [Department] team. They mentioned that [Specific Pain Point] is creating a lot of manual work, specifically around [Detail from User].

I've helped other [Job Titles] solve this by [Brief Result]. Would you be open to a brief conversation about how to fix this for your team?

Best,
[Your Name]
```

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Find leads](https://getkinlead.com/tools/find-leads.md)
- [Steal customers agent](https://getkinlead.com/features/steal-customers.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)

## Common questions

**What if the user is afraid to talk to me?**

Shift the focus away from your product and toward their expertise. Ask for their advice on how someone in their position handles a specific industry challenge.

**How many non-decision makers should I talk to before hitting the VP?**

Aim for two or three people. That lets you see whether the pain point is a company-wide issue or one person's frustration.

**What do I do if the user tells me they have no budget?**

You aren't selling to the user. Use that information to understand the budget cycle or to find out who actually controls the funds.

**What if the executive ignores the message anyway?**

Go back to the people who already replied. One of them can tell you whether the timing is wrong, whether someone else owns the problem now, or whether your message used the wrong words for what they call it internally.

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