# How to find leads using a sales playbook
> Pull the problems, triggers and outcomes out of your sales script, then use them as LinkedIn searches, lead groups and message prompts for small teams.
- HTML: https://getkinlead.com/find-leads-using-sales-playbook
- Markdown: https://getkinlead.com/find-leads-using-sales-playbook.md

**Short answer:** Pull the problems, triggers and outcomes out of your sales script, then use them as LinkedIn search filters, lead group rules and message prompts. The script tells you who to look for and why they should reply today. Do not paste the script into a connection note.

## Pull the search terms out of your sales script

A sales script has three useful parts for lead search: the problem, the trigger and the outcome. The problem tells you what to search for in profiles. The trigger tells you what to look for in posts and comments. The outcome tells you what to say in the first message. Most scripts bury these in long sentences, so read it with a pen.

Take one page of your script and mark every noun that describes a customer situation. Manual reporting, a new sales manager, a migration, a compliance review, outgrowing the current CRM and hiring SDRs are all search terms. Then mark every sentence that starts with when or after. Those are triggers. When a team opens a second office or after a funding round gives you a reason to reach out now.

Keep the list small. Ten to fifteen terms are enough for a first search. If you use every phrase from a 20 minute call, the search will be too narrow and you will get no results. Pick the terms that appear in the customer's own language, not your internal product names.

| | Script part | What to pull | Where it goes on LinkedIn |
| --- | --- | --- | --- |
| Problem | The words a buyer uses for the pain | Profile keywords and job titles |
| Trigger | The event that makes the pain urgent | Posts, comments and recent job changes |
| Outcome | The result the buyer wants | First message and follow-up |
| Proof | The case or example you would mention on a call | Message prompt, not a search filter |

## Turn the script into trigger searches

A title search gives you a list of people who could have the problem. A trigger search gives you a reason to message this week. Use both, but start with triggers because they give you an opening line that does not sound like a pitch.

On LinkedIn, triggers show up in public activity: comments on competitor posts, questions in industry threads, posts about a new job, a funding announcement, a request for tool recommendations, or a complaint about a process. Search for the words from your script and read the posts. Do not rely on a single search. Run the same term through posts, people and companies.

Build a short list of trigger searches for each campaign. If your script says when a team hires its first sales ops person, search for that job title and look at people who started in the last few months. If your script says when a company moves from one CRM to another, look for posts about migrations and comments from people asking about data cleanup.

1. **Pick one trigger from the script.** Choose the event that makes the problem urgent, such as a new hire, a funding round, a tool migration or a public complaint.
2. **Write the search phrase in buyer language.** Use the words a buyer would post, not your product category. Search for cleaning up reports before revenue operations platform.
3. **Run it in posts and comments.** Search the phrase in LinkedIn posts, then read the comments. The commenters are often closer to the problem than the person who posted.
4. **Save the reason with the name.** For each lead, note the post, the comment and the trigger. That note becomes the first line of your message.
5. **Stop after 20 leads.** Work the list before you build a bigger one. Twenty leads with a real trigger are more useful than 200 names with no context.

## Use the script's logic in the first message

A script assumes a conversation where the other person has already agreed to talk. A connection note or first message has to earn that agreement. The mistake is copying the opening line of your pitch. The fix is to use the script's logic in one sentence: why this person, why now, and what you want to talk about.

The first line should mention the trigger you found. The second line should connect that trigger to the problem in your script. The third line should ask for a small next step. If you cannot write it in three short sentences, you are still writing a pitch.

Keep the note short. A connection request note has very little room, so use it to explain why you are connecting, not to describe your product. Save the product sentence for after they accept.

**Script pasted into a note**

- Hi, I saw you are a VP of Sales. We help companies grow revenue with a software platform. Do you have time for a call?
- I am reaching out because we are the leading solution for sales teams. Our playbook can fix your lead generation.

**Script logic in a note**

- Saw your comment on the Acme post about report cleanup. I work with sales ops teams on that exact handoff. Happy to connect.
- You started the new sales ops role at Northwind last month. I have been talking to other new hires about CRM cleanup. Worth comparing notes?

## Group leads by what the script says they need

Not every lead needs the same first message. A person who commented on a competitor's post has a different reason to reply than a person who simply matches the job title. Group leads by the trigger and the part of the script you plan to use.

A simple set of groups is enough: one for people who match the profile but have no trigger, one for people who showed a trigger in public, and one for people who asked a question you can answer. Add a group for referrals or past conversations if you have them. The group name should tell you which opening line to use.

When you write a campaign, point it at one group. That way the message can mention the trigger without pretending every lead has the same story. If a lead moves from cold to warm, move them to the warm group and stop the cold follow-up.

| | Group | How the lead got there | Opening line to use |
| --- | --- | --- | --- |
| Profile match | Title, industry and company size fit the script | Mention the problem in the script and ask if it is on their list |
| Public trigger | Commented on a competitor post or asked a question in a thread | Mention the post and the specific comment |
| New role | Started a job that matches the trigger in your script | Mention the new role and the first 90 days |
| Referral | Someone else introduced you or suggested you talk | Use the referrer's name and the reason they gave |

## Test the playbook on a small batch

Before you run a large campaign, test the script on a small batch of leads from one group. You are checking three things: whether the search finds the right people, whether the first line gets replies, and whether the reply moves toward a conversation. Do not change all three at once.

Start with ten to twenty leads. Send the connection requests or messages yourself, or use a tool that sends from your account. Read every reply. If people ask what you mean, your first line is too vague. If they ignore you, the trigger may be weak or the ask may be too big.

Keep a note of the exact phrases people use in replies. Those phrases are better search terms than the ones you invented. Add them to the script and to the next search. The playbook should get sharper after each batch.

- **you:** Saw your comment on the Acme post about report cleanup. I work with sales ops teams on that handoff. Happy to connect.
- **them:** Thanks. We are actually cleaning up our CRM right now. What do you do?
- **draft:** I help teams map the handoff between sales and ops so reports stop breaking after a migration. You mentioned duplicate accounts. Is that the main issue, or is it the reporting layer?

```
Trigger: [post or comment]
Problem from script: [problem]
First line: [mention the trigger]
Second line: [connect to problem]
Ask: [small next step]
Follow-up: [one useful resource or question]
```

## Doing this with Kinlead

Kinlead can use your sales script as the playbook for a campaign. You describe the customer you want, or point Kinlead at your website, and it scores leads from 0 to 100 against that profile. Leads below the fit line are not kept. That gives you a lead group you can point a campaign at.

The [Steal Customers](/features/steal-customers) agent watches competitor company pages and optional founder or employee profiles, reads comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented, so your first line can use the real trigger.

You can add your own sales script as the campaign playbook. Messages and follow-ups are written from the campaign goal, tone and that playbook. Queued messages can be read and edited on the Actions page before they send, and you can pause a campaign at any time. Replies from every campaign land in one inbox, classified by intent, with interested replies first.

> Use hand-off mode if you want to read every reply yourself before the conversation continues. In the AI reply modes, replies send without a per-message approval step.

## Related

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

## Common questions

**Can I use the same script for every lead?**

Use the same logic but change the opening line. A lead with a public trigger should hear about that trigger. A profile match should hear about the problem in the script.

**What if my script is written for a demo call?**

Pull out the problem and the outcome, then write a short note that asks for a conversation. Do not paste the demo opening into a connection request.

**How many leads should I test first?**

Ten to twenty from one group is enough to see whether the search and the first line work. Read every reply before you add more.

**What do I do when a reply does not fit the script?**

Answer the actual question and leave the script for a moment. If the reply reveals a new trigger or problem, add it to the playbook for the next batch.

**Do I need a paid LinkedIn search tool?**

No. Start with the search you already have and use the phrases from your script. Add filters later if the basic search gives you too many results.

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