# Connection requests for non-decision makers
> Learn how to connect with employees who aren't the boss on LinkedIn, talk about the daily friction they feel without pitching, and earn a warm introduction to the decision maker.
- HTML: https://getkinlead.com/connection-request-notes-for-non-decision-makers
- Markdown: https://getkinlead.com/connection-request-notes-for-non-decision-makers.md

**Short answer:** To connect with non-decision makers, stop pitching your product. Instead, ask about the specific daily frictions they face in their role. When an employee confirms a pain point, they become your internal champion who can introduce you to the boss with a recommendation based on a real problem.

## Why the bottom-up approach works

Most sellers go straight for the VP or CEO. Those people have the budget, but their inboxes are full. They often ignore cold pitches because they don't feel the daily friction of a broken process. They care about high-level results, not the grind.

The employees in the trenches feel the pain every hour. They're the ones spending four hours on a spreadsheet that should take ten minutes. If you solve their specific headache, they'll advocate for you. A CEO might ignore a stranger, but they rarely ignore a trusted employee who says a tool will save them a full day of work every week.

This approach also gives you better information. An end user can tell you which step breaks, which workaround they use, and what they've already tried. That detail makes your later message to the decision maker specific instead of generic.

**Pitching the CEO**

- Focuses on ROI and quarterly growth
- Asks for a 30 minute demo immediately
- Uses vague language like scaling and efficiency
- Is viewed as a stranger trying to take money

**Pitching the employee**

- Focuses on manual data entry and overtime
- Asks about a specific daily frustration
- Uses role-specific language and terminology
- Is viewed as a peer solving a problem

## Identifying the end-user persona

Generic searches don't work here. You need the people who actually touch the problem your product solves. If you sell a payroll tool, don't just look for the CFO. Look for the payroll clerk or the HR coordinator.

Search for titles like Specialist, Coordinator, or Analyst. These roles usually handle the execution of the work. They know exactly where the current process breaks.

The title matters less than the task. If you sell scheduling software for clinics, the front desk coordinator feels the double-booking problem. If you sell inventory software, the warehouse lead feels the stockout problem. Write down the task first, then find the people who do it.

1. **Map the daily workflow.** Write down every step an employee takes to complete the task your product automates. Identify who owns each step.
2. **Filter for execution titles.** Search for titles that imply doing the work. Replace VP or Director with Manager, Specialist, or Lead.
3. **Scan for tool mentions.** Look at profiles for mentions of legacy tools. If they list a competitor or outdated software in their skills, they're a prime target.
4. **Build a target list.** Gather a list of 20 to 50 people who fit this exact profile before sending a single request.

## Writing the request: the pain-point bridge

The first request has one job: get a connection and acknowledge that their job is hard. If you sound like a salesperson, they'll hit ignore. If you sound like someone who understands their Tuesday afternoon struggle, they'll accept.

Avoid phrases like help companies scale or improve efficiency. Those are corporate buzzwords that mean nothing to someone doing manual data entry. Use the words they use in their internal meetings.

Keep the note short. One sentence about the work, one sentence about why you're reaching out. Leave the pitch out. The connection request is not the place to explain your product.

| | Avoid this approach | Try this approach |
| --- | --- | --- |
| The hook | I help companies like yours scale their operations. | I'm curious if updating the weekly lead report is still a headache for your team. |
| The ask | I'd love to hop on a call to show you my demo. | I'm researching how Specialists handle this specific problem and would love to follow your posts. |
| The tone | Polished and corporate. | Curious and peer-to-peer. |
| The close | Let me know if you want to see a demo. | If this is a real headache, I can share what other coordinators do. No call needed. |

## Turning a connection into a referral

Once they accept, don't pivot to a sales pitch. Confirm the pain first. You want them to admit the problem exists. This creates a commitment that makes them more likely to help you later.

When they agree the problem is annoying, offer a low-friction way to see the solution. A short clip or a screenshot is better than a meeting request. Once they see the value, they'll be happy to point you toward the person who signs the checks.

If they say they don't handle that, ask who does. Keep it simple: 'Who owns this process on your side?' That gives you a name without asking them to sell for you.

- **you:** Thanks for connecting. Do you actually find the manual reconciliation process annoying, or is it just me?
- **them:** It's a nightmare. I spend every Friday afternoon doing it.
- **you:** I've seen a way to fix that. If I send over a 30-second clip of how it works, would you mind glancing at it?
- **them:** Sure, send it over.
- **you:** Glad that looks useful. Who usually handles the budget for tools like this? I'm happy to send them the details so you don't have to do the legwork.
- **them:** That would be our ops manager, Dana.
- **you:** Thanks. I'll send a short summary you can forward. No meeting needed.

> Never ask the employee to sell the product for you. Ask them who handles the budget so you can take the work off their plate.

## When to ask for the decision maker

Ask for the decision maker after the employee confirms the pain and sees the value. If you ask too early, you're just another stranger asking for a favor. If you wait too long, you become a support person with no path to a deal.

The best moment is after they say something like 'we've tried to fix this' or 'that would save me hours.' That's when you can offer to send a short summary they can forward. The summary should name the problem, the fix, and the result. Keep it to a few lines.

Don't ask them to book a meeting on your behalf. Give them something easy to pass along, then ask for the name of the person who owns the budget. If they offer to introduce you, accept and send the summary right away.

```
Thanks for the detail on the [process]. I put together a short summary you can forward:

Problem: [one line]
What changes: [one line]
Result: [one line]

Who owns the budget for this on your side? I can send it to them directly so you don't have to chase it.
```

## Doing this with Kinlead

Kinlead helps you execute this by finding the end-user personas you describe and scoring them against your profile. You can keep these users in a dedicated lead group to keep your messaging separate from your executive outreach.

You can run a campaign using a sales playbook that focuses on pain points. Kinlead sends these requests at a human pace, inside the daily limits and send windows you set.

1. **Create end-user groups.** Use Kinlead to find people matching your end-user profile and organize them into a specific lead group.
2. **Draft targeted notes.** Set up a campaign with AI-written notes under 200 characters that explain why that person became a lead.
3. **Apply your playbook.** Use a sales playbook to guide the AI in asking about daily frictions before requesting a referral to the decision maker.
4. **Manage the hand-off.** Set the campaign to hand the conversation to you once the employee expresses interest. Learn more at [book a demo](/demo).

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Lead scoring guide](https://getkinlead.com/linkedin-lead-scoring-fit-line-guide.md)
- [Human pace guide](https://getkinlead.com/linkedin-outreach-human-pace-guide.md)

## Common questions

**What if the employee ignores my request?**

That's normal. Not every end-user is open to networking. Move on to the next person in your lead group without sending follow-up requests, as that can look desperate.

**Should I tell the employee I'm trying to reach their boss?**

No. Focus entirely on their problem first. If you mention the boss too early, they'll feel like a stepping stone rather than a partner.

**How many end-users should I contact before moving to the decision maker?**

Try to connect with three to five people in the same department. This gives you a better understanding of the internal pain and more champions to cite when you message the boss.

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