Cold DM Script Library

How to use the script library

Pick the framework that matches your platform and goal, then fill the beats with the prospect's specifics. Train new senders on two frameworks first, not all of them, so they build instinct before choice becomes a burden. Review recorded replies to confirm the framework is producing the right conversations.

Framework beats

Every script here follows the same four beats. Learning the beats lets a sender improvise confidently instead of memorizing lines, which is what keeps volume sustainable without quality dropping.

Per-platform frameworks

Platform norms differ. Instagram rewards visual, casual observation; LinkedIn rewards professional relevance; Reddit rewards native, non-promotional tone. The same beat order, tuned to the room, is what works across all of them.

Goal-based frameworks

Match the script to the outcome you want: a reply, a meeting, or a referral. Asking for the wrong thing wastes the open you earned, so decide the goal before you write the ask beat.

• Reply goal: ask one easy question.
• Meeting goal: propose a short, specific slot.
• Referral goal: ask who else has the problem.

Keeping scripts on-brand

Write two or three approved variants per framework and store them where senders can find them. Brand voice lives in the small word choices, so give examples rather than rules, and let senders internalize the feel.

When to retire a script

A script that quietly falls below your average reply rate has earned retirement. Track it the same way you track snippets, and rotate in a tested replacement so the library stays sharp instead of sentimental.

Worked LinkedIn script, filled

Apply the four beats to a concrete case: a payroll tool reaching HR leads at 20-80 person companies. Watch how each beat stays one or two sentences and the ask stays tiny, which is what keeps a stranger from defaulting to no.

• Open + observe: the post reference shows you looked.
• Value: half the run time is a concrete outcome they feel.
• Ask: 'quick if I share' is a low-pressure yes.

Script mistakes to avoid

These are the failure modes that make a framework read as spam even when the structure is right. Catch them in the sample review before a sender ships them at volume, because bad habits at low volume become account-ending habits at scale.

Adapting the framework live

A framework is a skeleton you improvise within, not a teleprompter. When a reply surprises you, keep the beat order but change the words; the structure is what keeps the message effective when you are thinking on your feet.

Edge cases and caveats

Off-platform norms break a copied framework. What reads as confident on LinkedIn reads as pushy in a Reddit community, so tune the voice per room while keeping the same four beats underneath.

Do and don't quick list

• Do train senders on the beats, not lines.
• Do keep two approved variants per platform.
• Don't paste one framework everywhere verbatim.
• Don't retire a script on fondness; retire on rate.

Copy-this framework

Use this as your base framework and fill the beats for your first campaign. Keep the order; change only the words to fit the prospect and the platform, because the sequence is what keeps the message effective.

How to train a sender fast

Teach the four beats first, then have the sender shadow two approved variants before writing their own. Competence comes from the skeleton, not memorized lines, so test on the beats, not the wording.

Troubleshooting the framework

When a framework underperforms, one beat is usually missing or hollow. Score the last ten messages beat by beat to find the weak link before you rewrite the whole thing and lose what was working.

Your first 15 minutes

Stand up one framework before you brief a sender. The skeleton takes minutes; the personalization is what takes the thought, and the skeleton is what keeps every message consistent at volume.

1. 1Pick the platform and its norms.
2. 2Write the four beats in order.
3. 3Approve one tested variant.
4. 4Store it where senders can find it.

Before you launch: final check

Before a sender goes live, confirm the framework beats are present in their draft and the ask is small. A framework missing the observe beat reads as spam the moment it hits a stranger's inbox, no matter how good the value.

• All four beats present, in order.
• Observe beat is specific to the prospect.
• Value stated as an outcome they feel.
• Ask is one easy step, not a pitch.

Script performance review

Review each framework the same way you review snippets: by reply rate, not by how much you like it. A framework that tests well for one sender may read as copied for another, which is almost always a personalization gap in the observe beat, not a bad skeleton.

Where scripts fit in the stack

Scripts sit between the ICP and the send: the ICP says who, the script says how the message is built, and the cadence says when it follows up. Keep all three consistent or the program pulls against itself.

1. 1ICP sets the observe beat detail.
2. 2Script sets the four beats.
3. 3Cadence sets the follow-up timing.

Suggested image brief

Quick checklist

• Two platforms frameworks selected and drafted.
• Goal-based variant written for reply and meeting.
• Four beats documented for each framework.
• Two approved variants locked per framework.
• Sender training plan based on beats, not lines.
• Reply-rate tracking tied to each script.
• Retirement rule set at below-average rate.

Frequently asked questions