# Connecting with different functions for a single deal
> How to run a multi-department B2B deal on LinkedIn: map the user, IT and finance roles, write a hook for each, and keep the whole thread moving.
- HTML: https://getkinlead.com/connection-requests-for-cross-functional-teams
- Markdown: https://getkinlead.com/connection-requests-for-cross-functional-teams.md

**Short answer:** To close a deal that touches several departments, change the reason for each person you contact. The user cares about hours saved, IT cares about a clean rollout, and finance cares about payback. Map those three roles first, then write a connection note that only fits one of them.

## Map your stakeholders

Most B2B deals stall because the seller treats the company as one person. A purchase that size needs sign-off from people whose goals conflict. Send the same pitch to an operations manager and a CFO and both will ignore it, for different reasons.

Before you write a connection note, list the roles in the decision. Three matter most: the person who lives with the problem daily, the person who can block the purchase on technical grounds, and the person who signs the contract. Write down what each one is measured on this quarter. That list is your map, and you'll reuse it for every message in the account.

Finding those people takes about ten minutes. Search the company on LinkedIn, then read the titles on the operations, IT and finance teams. Job posts on their careers page tell you what each team is being pushed to fix this year, which is usually the same thing you're selling against.

Multi-threading means running those conversations at the same time. It also protects the deal. If your only contact takes another job or goes quiet for a month, the account doesn't die with their inbox.

| | Role | What they're measured on | What earns a reply |
| --- | --- | --- | --- |
| User (operations, support, marketing) | Hours saved, error rates, backlog | A task you can name from their own job ad |
| Gatekeeper (IT, security, legal) | Uptime, audit findings, clean rollout | Proof you've integrated with their stack before |
| Economic buyer (finance, founder, VP) | Cost per transaction, payback period | A number tied to their own reporting |

## Write function-specific hooks

A connection note has one job: give the person a reason to accept. The reason has to match the title on the profile you're looking at, or it reads like a mail merge.

Skip the compliment about their profile. Name the work they do and the outcome they're responsible for. If you can't name a specific outcome for that role, you don't know enough to send the note yet.

Steal their language. Read two or three of their posts, the team's job ads, or a talk they gave at a conference. Whatever words they use for the problem are the words that belong in your note.

Keep it under 200 characters so nothing gets cut off, and put the role-specific reason in the first line. The reader decides in about a second whether this is about them.

**Works for any title**

- Hi James, I came across your profile and was impressed by your background. I'd love to connect and share how we help companies like yours do more with less.
- Hi James, I'm reaching out because we work with businesses in your space to improve efficiency and drive growth. Open to a quick chat?

**Fits one role**

- Hi James, your ops team is hiring two analysts for the same reporting work. I'm connecting because we take that report off spreadsheets entirely.
- Hi James, you're hiring a security engineer alongside a cloud migration. I'm connecting to ask what review process a new tool has to pass first.
- Hi James, your last update mentioned margin pressure from manual billing. I'm connecting because that's the exact line item we fix.

> If your note would work for any title at the company, it isn't specific yet. Rewrite until it only fits one role.

## The multi-thread sequence

Order matters. Going to the CFO first, with no internal support, makes you a vendor asking for budget. Going to the user first gives you a reason to exist before money comes up.

The aim is internal demand. When the economic buyer sees your name, it should be because someone on their team already said it. That turns a cold message into a referral.

Leave a few days between each role. You want the user's answer in hand before you write to IT, and IT's reaction before you write to finance. A week per step is enough for most teams.

If the user says the problem isn't real, stop. You've saved yourself a quarter of pitching to a company that won't buy. Ask who else in the business has the same problem and move to that team instead.

1. **Start with the person who does the work.** Find the operator. Ask how they handle the task today and what breaks when it gets busy. Their answer is the raw material for every other message you'll send in this account.
2. **Ask what they already tried.** Most teams have a tool nobody uses or a spreadsheet that half works. Knowing that tells you what the gatekeeper will defend and what the buyer has already paid for.
3. **Approach the gatekeeper with the user's words.** Reference the conversation without oversharing. Saying that Sarah's team does this by hand gives IT something concrete to evaluate and shows you're not selling into a vacuum.
4. **Reach the buyer with two names.** By the time you write to finance, you should be able to say who has the problem and who is reviewing the fix. That's a warmer intro than any pitch you could write.

## When they say they already have a tool

IT says this often, and it's usually true. They bought something. What's often false is that the team uses it. The gap between the licence and the daily work is where your deal lives.

Don't argue about features. You'll lose, because they chose the current tool and defending it means defending themselves. Ask about usage instead and let them draw the conclusion.

- **them:** We already have a tool for this.
- **you:** That makes sense, most teams we talk to do. Is your ops team actually using it, or is some of the work still manual?
- **them:** I'd have to ask. I think there's a spreadsheet for the exceptions.
- **you:** That matches what Sarah described. I'm talking to her about the exceptions this week. Want me to send you what we find?
- **them:** Sure, send it over.

> Never tell a gatekeeper their tool is bad. Ask whether the team is getting the value they paid for.

## What to send after they accept

The first message after a connection is where most sequences fall apart. People send a calendar link and a paragraph about the company. Write one line about their function, one question they can answer in a sentence, and stop.

Match the ask to the role. A user will tell you about their week. A gatekeeper wants to know what integration looks like. A buyer wants a range before they'll take a call. Give each one the smallest next step you can.

Send the buyer message last, and name the people you've already spoken to. That's the whole point of running the account in order.

Then wait. If nobody replies in four or five days, send one follow-up with something new in it: a screenshot, a short answer to the question they asked, or a note that you spoke to their colleague. Repeating the first message gets you ignored twice.

```
User:
Hi {first}, thanks for connecting. You said {task} still runs on {tool or spreadsheet}. How many people touch it in a normal week?

Gatekeeper:
Hi {first}, before I ask for time: this sits alongside {current system} rather than replacing it. What would your team need to see before reviewing it?

Buyer:
Hi {first}, {champion} in {team} is looking at this. Typical deals land between {low} and {high} depending on seats. Is a 15 minute call worth it to check the budget fit?
```

## Doing this with Kinlead

Running three conversations at one account by hand is where multi-threading usually collapses. Kinlead keeps the roles apart so each one gets its own message and its own reason.

Outreach runs from your own LinkedIn account through Unipile, at most one action every 5 minutes, inside the invite and message limits you set and a send window in the lead's time zone. If LinkedIn pushes back on the account, invites pause and you get an email.

If you want to see it on your own account, [book a demo](/demo).

1. **Find the roles.** Use [lead search](/tools/find-leads) to find people at the target company, then keep them in separate [lead groups](/features/lead-groups-and-scoring) for operations, IT and finance. Each lead is scored 0 to 100 against the customer profile you describe, and anything below the fit line isn't kept.
2. **Give each group its own campaign.** Any [campaign](/features/campaigns-and-send-windows) can point at any group. Each one carries its own goal, tone and optional sales playbook, which is your own script for that function.
3. **Write the note.** Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead, so the reason differs by group.
4. **Choose the hand-off.** Set the campaign to hand the conversation to you at the first reply so you coordinate the account yourself. Replies from every campaign land in one inbox, classified by intent, with interested replies first.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**Should I tell the finance lead I'm already talking to the user?**

Yes, name them. A specific person shows the need is already recognized inside the company, and it gives the buyer someone to check with before taking the call.

**What if IT blocks the deal before I reach the buyer?**

Go back to your champion in operations and ask them to show their manager what the workaround costs each week. A user making that case carries more weight than a vendor making it.

**How do I find the right people when titles don't name a department?**

Read the title for the work rather than the label. Controller and VP of procurement sit in finance, while systems administrator and director of infrastructure sit in IT.

**How long should I wait between contacting each role?**

A few days. You want the user's answer before you write to IT, and IT's reaction before you write to finance. A week per step is enough for most teams.

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