# How to connect with end users to reach the decision maker
> Learn how to use bottom-up prospecting on LinkedIn to build relationships with end users and secure warm introductions to the managers who hold the budget.
- HTML: https://getkinlead.com/connection-requests-for-non-decision-makers
- Markdown: https://getkinlead.com/connection-requests-for-non-decision-makers.md

**Short answer:** To reach a decision maker via end users, you connect with the people who actually use the software or process you improve. You build a relationship by asking for their expertise on a specific problem, then ask them to introduce you to their manager once they agree that your solution solves a pain point they feel daily.

## Identify the end user

VPs and Directors manage budgets, but they don't feel the daily friction of a broken process. If you target them first, you're just another salesperson in a crowded inbox. The end user is the person whose day is actually made harder by the problem you solve.

Look for titles that imply execution. Specialists, Analysts, Coordinators, and Engineers usually do the manual work. They respond to requests for their expertise because they live with the pain.

Target people who have been in their role for 6 to 18 months. They've been there long enough to see the gaps, but they aren't so settled that they've accepted the inefficiency as a permanent part of the job.

| | Signal | End user | Decision maker |
| --- | --- | --- | --- |
| Job title | Specialist, Analyst, Coordinator | VP, Director, Head of |
| What they post about | Daily workflow fixes, tool complaints | Team strategy, budget, hiring |
| Response to your question | Shares specific friction | Asks about cost and timeline |

**Wrong targets**

- VP of Operations
- Head of Growth
- Chief Revenue Officer

**Right targets**

- Operations Coordinator
- Growth Analyst
- Sales Development Rep

## The first connection request

Your goal is an acceptance. Meetings come later. If you pitch your product in the connection request, the end user will see you as a vendor and ignore you. Position yourself as a researcher or someone seeking a peer's perspective on a specific workflow.

Once they accept, don't rush into a demo. Ask a question that lets them complain about their day. People like talking about why their current process is frustrating, especially if they feel it's an overlooked problem.

- **you:** Hi Sarah, I'm researching how Demand Gen Managers handle lead routing. I saw your profile and wanted to ask a quick question about your workflow.
- **them:** Sure, happy to help. What's up?
- **you:** Thanks for connecting. Do you find that manually assigning leads takes up most of your Tuesday, or is it something else that's the biggest bottleneck?

## Extracting the internal map

Now that you have a conversation, map out the internal power structure. You need to know what tools they use, why those tools fail, and who has the power to change the software stack.

Don't ask 'Who is the decision maker?' because it sounds too corporate. Ask how things get fixed. This tells you the path to a purchase without making the user feel like they're giving away a secret.

1. **Question the current tool.** Ask if their current software actually solves the problem or if it's just a corporate requirement. Example: 'Is [Competitor] actually fixing the routing issue, or is it just a checkbox for the company?'
2. **Validate the pain.** Confirm the friction is a recurring nightmare. Example: 'Most people I talk to say that manual data entry is a total slog. Is that true for you?'
3. **Identify the path to change.** Find out who needs to be convinced. Example: 'If you could fix this tomorrow, who would you have to convince to make it happen?'

| | What you need to learn | Question to ask | Why it works |
| --- | --- | --- | --- |
| Current tool | Is [tool] actually fixing the routing issue, or is it a checkbox? | Reveals if the tool is loved or tolerated |
| Pain level | How often does this manual step break your week? | Separates a nuisance from a budget-worthy problem |
| Path to change | If you could fix this tomorrow, who would you have to convince? | Names the approver without asking for an org chart |

## Asking for the introduction

Only ask for the intro after the user admits the problem is real and frustrating. If you ask too early, you're a stranger asking for a favor. If you ask after validating the pain, you're a potential savior for their workday.

Make the user look good. When they introduce you to their manager, they are bringing a solution to their boss that makes the whole team more efficient.

> Offer to ghost-write the introduction message. Most people want to help but are too busy to word the email. Providing a template removes the last bit of friction.

```
Hi [Manager Name], I've been chatting with [User Name] about the issues we're having with [Pain Point]. They found a tool that seems to solve this specifically for [Job Title]s. I think it could save us a lot of time, so I'm introducing you to [Your Name] to see if it's a fit.
```

## When the end user cannot introduce you

Some end users will love your solution but have no standing to introduce you. They may be new, remote, or on a team where the manager is protective of vendor conversations. Do not push. Ask for a different kind of help.

Ask them to forward your one-page summary to the manager, or to mention your name in their next one-on-one. A forwarded message from an end user carries weight because it comes from someone the manager trusts.

Another option is to ask for a peer in a different team who has the same problem and a clearer path to the budget. One warm introduction from a different team is better than a forced introduction from the wrong person.

- Ask for a forward, not an introduction.
- Ask who else on the team feels the pain.
- Offer to write the message they can send.

## Doing this with Kinlead

Managing this bottom-up approach manually for hundreds of leads is slow. Use [Kinlead](/signup) to find people who match your end-user profile and score them from 0 to 100 to ensure they fit the persona you're targeting.

Automate the initial outreach while keeping a human touch. Set up a campaign with a connection note under 200 characters that explains why that person was selected as a lead.

1. **Automate the discovery.** Use lead search to find end-user titles and group them. Use the Steal Customers agent to find people commenting on competitor posts who are likely feeling the pain.
2. **Run the conversation.** Use AI-written follow-ups based on your own sales playbook to ask about workflow and pain points at a human pace.
3. **Switch to manual for the intro.** Set your campaign to hand-off mode. Once a user admits they have a problem, you can personally step in to manage the introduction to the manager.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**What if the end user ignores my request?**

If they don't accept the invite, move on. Don't send multiple requests to the same person. Find more end users who fit the profile.

**Should I message the manager at the same time as the end user?**

No. If the manager sees you're hitting their staff and them at once, it looks like a spam attack. Wait until you have the end user's buy-in.

**How do I handle a user who wants a demo instead of an intro?**

Give them the demo. If they love it, they become your internal champion. You can then ask them to help you present it to the manager together.

**How long should I wait before asking for the introduction?**

Wait until you have had two or three exchanges and the user has described the problem in their own words. That usually takes a week or two of light conversation. Asking after the first reply feels rushed.

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