How to turn a sales script into a LinkedIn playbook
Turn your sales script into a LinkedIn playbook with a clear goal, tone, connection note and follow-up sequence that sounds like a person, not a pitch.
Get startedShort answer
A LinkedIn playbook is your sales script broken into goal, tone, proof and next step. You use it to write a short connection note, then follow up with one useful idea at a time instead of pasting the same pitch into every message.
Why your sales script fails on LinkedIn
A phone script assumes you can hear the pause after a question. An email script assumes a subject line and a preview. LinkedIn has neither. People read the note in a feed, often on a phone, next to a photo of someone's dog.
Pasting the same pitch into a connection request gets you ignored because the note is short and the reader has no context. The fix is to turn the script into a playbook: a short set of rules for the goal, tone, proof and next step. The words change for each person. The logic does not.
A playbook also gives you something to improve. When a note gets a reply, you can see which line did the work. When it gets nothing, you can change one part instead of rewriting everything.
The test is simple. If you removed your company name and your product, would the note still make sense for this person? If not, the note is a script with a first name in it.
The rigid script
- Hi Dana, I'm with Acme. We help sales teams book more demos. Do you have 15 minutes Tuesday?
- I noticed you are VP of Sales. Our platform helps VPs increase revenue. I'd love to show you how it works.
The playbook approach
- Hi Dana, your comment on the pricing thread stuck with me. We work with agencies testing usage-based pricing. Worth comparing notes?
- Hi Marcus, saw you joined the ops group after the Northwind reorg. I'm talking to ops leads about rebuilding a team after a hiring freeze. Open to connecting?
Turn your script into a one-page playbook
Write the playbook in a doc before you touch LinkedIn. Pull out the parts of your script that do real work and throw away the stage directions. If the script says 'pause for effect', delete it.
Put the playbook where you write messages. A doc in a folder nobody opens is not a playbook. For each step, write the job in one line so you can check a draft against it in ten seconds.
- 1
Identify the core goal
Decide what you want from the campaign: a reply, a call, a demo or a piece of feedback. Write it as one sentence. If you want all four, you have no goal.
- 2
List the proof you can use
Write down the problems you solve and the examples you can share without inventing numbers. One proof point per message is enough.
- 3
Choose a tone you can keep
Pick peer, expert or helper. Then write three sample lines in that voice. If they sound like a different person, change the tone before you write more.
- 4
Map the sequence
Set the order: connection note, first follow-up, second follow-up, close. Give each step one job. Do not ask for a demo in the connection note.
Write a connection note that gets accepted
The connection note has one job: give the person a reason to accept that is about them, not your calendar. Lead with the trigger. That is the post, comment, job change or group question that made you pick them.
Keep the note under a few lines. Use a specific noun. Ask one question if you have room. Do not explain your whole product. Do not ask for a call in the note.
If you cannot find a trigger, do not send a generic note. Wait until you have one. A comment on a competitor's post, a question in a group or a new job title all work. The note only needs to show that you looked.
Avoid opening with 'I hope this finds you well.' It tells the reader nothing and wastes the first line. Start with the trigger.
Example
- You
Hi Sarah, your comment on the pricing thread stuck with me. I work with agencies testing usage-based pricing. Open to connecting?
- Prospect
Hi, yes. We are testing it now and the billing setup is a mess.
- You
That matches what I hear. What part is breaking, the metering or the invoices?
- Prospect
Metering. We can track usage but the invoices are wrong half the time.
Paste this job
Hi {{first_name}}, I saw {{specific_post_or_comment}}. I work with {{type_of_company}} on {{problem}}. Open to connecting?Build follow-ups that add one new reason to reply
Most follow-ups fail because they repeat the first message louder. A playbook follow-up should add a new reason to reply. Use one idea per message: an observation, a worked example, or a clean close.
Pick a rhythm you can keep. Send the connection note, wait for the accept, then send the first follow-up a few days later. If there is no reply, send a second note after a week and a final note after two weeks. Stop after the final note.
Do not send three follow-ups in one day because you feel nervous. That reads as pressure, not persistence.
The final note should not guilt them. Write it as a normal person would: 'I'll stop here. If the timing changes, reply and I'll pick it up.' Then mean it.
Useful observation
- Follow-up type
- Give a reason to reply
- Objective
- Mention a shift you saw in their market and ask if it matches what they see.
Worked example
- Follow-up type
- Show how the problem looks in practice
- Objective
- Describe a similar company and what changed, without inventing numbers.
Short question
- Follow-up type
- Make replying easy
- Objective
- Ask one question they can answer in a sentence, such as what they use today.
Clean close
- Follow-up type
- Leave the door open
- Objective
- Say you will stop reaching out and wish them well. Keep it short.
Test the playbook before you send a batch
Before you send a batch, write ten notes by hand. Read them as if you were the prospect. If you cannot tell why you picked that person, the playbook is too vague.
Show the ten notes to a colleague who does not know the offer. Ask them what you want and why you picked each person. If they guess wrong, rewrite the trigger line.
When something works, copy the line into the playbook. Do not keep it in your head. The next campaign should start with what you learned from the last one.
- Change one thing at a time: the trigger, the proof or the ask. Changing all three tells you nothing.
- Keep a simple doc with the note, the reply and what happened next. Read it once a week.
- If a note sounds like it could go to anyone, delete the trigger and start again.
- Use the same playbook for one campaign, not every campaign. A founder campaign and a hiring campaign need different proof.
If a prospect cannot tell what you want from the first two lines, the playbook is too vague. Rewrite the note before you send another batch.
Handle replies without jumping to a calendar link
A reply is not a meeting. It is a person deciding whether you are worth more time. Answer the question they asked, then ask for the next small step.
If they ask to chat before a demo, say yes and keep it short. If they ask for partnership terms, send the outline and ask who owns the decision. If they ask a technical question, answer it plainly and offer a call with someone who can go deeper.
Do not send a calendar link in the first reply unless they asked for one. Ask one question that helps you decide if the call is worth it. If they answer, then offer times.
If they go quiet after a reply, send one short note with a useful link or a direct answer. Do not restart the whole pitch.
Weak reply
- Great! When are you free? Here is my calendar link.
- I can show you the platform whenever you want. Let me know.
Strong reply
- Happy to chat. Before I send a link, what is the main thing you want to fix this quarter?
- That question is fair. The short answer is it depends on your billing setup. Want to spend 15 minutes on your setup?
Doing this with Kinlead
Kinlead writes messages and follow-ups from the campaign goal, tone and an optional sales playbook, which is your own sales script. You can read and edit queued messages on the Actions page before they send, and pause any campaign.
Replies from every campaign land in one inbox, classified by intent, with interested replies first. For setup, see AI LinkedIn outreach.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to turn a sales script into a LinkedIn playbook.md