Cold DM Message Swipe File

How to use the swipe file

Copy a snippet into your draft, then replace every bracket with a specific detail about the prospect. The file saves you from the blank page; it does not remove the need to sound like a human who looked at their profile. Keep your own winners in the same file so it grows with your results.

Openers by situation

The opener sets the tone. Pick one that matches why you are reaching out, then make the reason specific to them. Vague openers about 'great content' get ignored; openers that name a real observation get read.

Value and proof lines

After the opener, earn the right to ask by showing you can help. Proof beats adjectives; a number from a past result out-converts a string of praise words.

• Keep proof to one line so it does not become a brochure.
• Use a comparable entity so the prospect can see themselves.
• Avoid promising outcomes you cannot control.

Soft ask and booking

The ask should be small and low-pressure. A big ask from a stranger gets a no by default; a tiny one gets a maybe, which is all cold outreach needs to start.

Handling replies and non-replies

Have a line ready for each common response. A polite no deserves grace; a question deserves a direct answer; a silence deserves one respectful nudge, not a flood.

Building your own swipe file

Every message that beats your average reply rate earns a slot. Over time your file becomes a personal playbook tuned to your voice and market, which is worth more than any generic template.

1. 1Tag each snippet by situation and result.
2. 2Retire lines that fall below average over time.
3. 3Keep variants so you can A/B test quickly.

Filled example snippets

Here are the same frameworks with the brackets filled in for a real scenario: selling a booking system to boutique fitness studios. Use them as a model for completing your own file so nothing stays abstract and every line has a concrete referent.

Personalization fill-in table

Before sending, complete this table for each prospect so the observation beat is specific. A blank cell is a copied-message warning; fill every one or do not send, because a generic observation is worse than none.

When to use which snippet

Match the snippet to the moment in the conversation. Using an opener when you should be booking, or a proof line when you have not earned the right, wastes the scaffold. The table maps situation to the right block from the library.

Edge cases and caveats

Personalization gaps are the most common failure. When you cannot fill a cell, the snippet will read copied no matter how good the template is, so have a fallback plan rather than sending a half-filled line.

• If no observation, use a peer opener from shared context.
• If no comparable win, soften the proof to a method.
• If the ask feels heavy, shrink it to a question.

Do and don't quick list

• Do tag every snippet by situation and result.
• Do keep two variants of each opener.
• Don't send a snippet with a blank bracket.
• Don't reuse one opener for every prospect.

Copy-this starter snippet set

Paste these three into your own file and fill the brackets for your first campaign. They cover open, proof, and ask, which is the full skeleton of a working cold message you can personalize per prospect.

How to log a winner

When a snippet beats your average reply rate, capture why, not just the text. The reason is what lets you recreate the win in a different market or platform later, which is the point of a file.

• Note the situation the snippet won in.
• Note the exact observation that landed.
• Keep two variants so you can test quickly.

Troubleshooting the file

When a snippet stops working, the cause is usually personalization drift, not the line itself. Check the observation beat before you retire a snippet that earned its place, because the line may be fine and the filling may be lazy.

Your first 15 minutes

Build the start of your file before your first send so you are adapting, not inventing, under pressure. A file started during a live send is a file that stays empty and unused.

1. 1Copy the three starter snippets into your doc.
2. 2Fill the brackets for one real campaign.
3. 3Tag each by situation and result.
4. 4Add a second variant for your top opener.

Before you launch: final check

Before sending, confirm every snippet you plan to use has its brackets filled with a specific, true detail. A snippet with a blank bracket is a copied message, and copied messages get copied straight to the mute button by prospects.

• Every opener has a real observation.
• Every proof line names a comparable win.
• Every ask is small and relevant.
• Each snippet is tagged by situation.

Swipe file maintenance

A swipe file decays if you never retire lines. Set a simple rule: any snippet below your average reply rate for two weeks gets archived, and any winner gets a note on why it worked, so the file stays sharp instead of sentimental.

• Archive sub-average snippets after two weeks.
• Note the winning observation for each keeper.
• Keep two variants of every opener.

Swipe file vs script library

Keep the swipe file and the script library separate but linked: the file holds copyable lines, the library holds the beat structure those lines plug into. A line without a framework is a one-off; a framework without lines is empty, and the two together are what a new sender needs.

Suggested image brief

Quick checklist

• Openers copied for at least three situations.
• Value and proof line drafted and trimmed.
• Soft ask prepared that is low-pressure.
• Response-handling lines written for no, question, silence.
• Each snippet tagged by situation.
• Plan to log winners into your own file.
• Personalization step added to every draft.

Frequently asked questions