Cold DM Outreach SOP Template

How to use this SOP template

Adapt the sections to your team, then train everyone against it. The SOP should be specific enough to follow on a bad day, when nobody feels like making decisions, because that is when consistency matters most.

Roles and ownership

Name who does what so nothing falls between stools. Outreach breaks down in the gaps between roles, not in the tasks anyone owns, so clarity here prevents the silent failures.

Process steps

The core loop, written so a new sender can execute without asking. Each step references the deeper resource rather than repeating it, keeping the SOP lean and the detail reachable.

1. 1Pull qualified list from the ICP worksheet.
2. 2Draft using the script framework and swipe file.
3. 3Send within safe daily volume.
4. 4Follow the cadence for non-repliers.
5. 5Log every stage in the tracker.

Quality controls

Controls are what keep volume from degrading quality. Build them into the week so they are routine, not a panic audit after replies already dropped.

• Sample-review 10 percent of messages weekly.
• Block banned claims and guarantees by default.
• Compare reply rate to the brief bar each week.

Review and improvement loop

The SOP improves through the same discipline as everything else: change one thing, watch the number, keep what works. Bake the review into the calendar so improvement is scheduled, not hoped for.

Handling exceptions

Define what senders do when something is off: a restriction warning, a angry reply, or a confusing question. Exception handling in the SOP stops small issues from becoming account-ending ones.

Worked process example

Here is the core loop filled for a real day so a new sender can execute without asking. Each step references the deeper resource, keeping the SOP lean while the detail stays reachable in the linked worksheet.

Exception scripts

Write the response to each common exception so senders do not improvise under stress. A calm, pre-agreed line protects the account and the brand when something goes wrong, and it is far cheaper than a damaged reputation.

Enforcing the SOP

An SOP only works if it is used under pressure. Tie compliance to the weekly sample audit and the onboarding path so following the procedure is the default, not a suggestion anyone can quietly skip on a busy day.

Edge cases and caveats

Non-compliance is usually a sign the SOP is wrong, not the sender. When many people skip the same step, question the step before the people, because a procedure nobody follows is a procedure that needs redesign.

Do and don't quick list

• Do audit a sample every week.
• Do update the SOP from learnings.
• Don't blame senders for a broken step.
• Don't let the SOP sit unread in a doc.

Copy-this process loop

Keep this loop as the spine of the SOP. Every sender should be able to recite it on a bad day, because that is when consistency matters most and when shortcuts quietly appear.

1. 1Pull qualified list from the ICP.
2. 2Draft via the script framework.
3. 3Send within safe daily volume.
4. 4Follow the cadence for non-repliers.
5. 5Log every stage in the tracker.

What an enforced SOP looks like

An enforced SOP shows up in the weekly audit and the onboarding path, not just in a doc. When compliance is checked, quality holds at volume; when it is hoped for, it erodes quietly until replies drop.

Troubleshooting the SOP

When quality drops at volume, the SOP is usually not being followed, not wrong. Sample the work to find which step is being skipped before you rewrite the procedure and lose the parts that worked.

Your first 15 minutes

Stand up the SOP from the playbook so the team has instructions, not just inspiration. An SOP that lives only in the founder's head does not scale past the founder's own capacity.

Before you launch: final check

Before the team runs, confirm the SOP is written, assigned, and tied to a weekly audit. An SOP that is not checked is a wish that quality holds, and quality erodes quietly once volume grows past one person.

• Roles assigned with ownership.
• Process steps written end to end.
• Quality controls scheduled weekly.
• Exception handling defined.

SOP step detail

Expand the five-step loop into the detail a new sender needs, so the SOP is executable without a senior looking over their shoulder. Reference the deeper worksheets rather than repeating them.

Quality control cadence

Controls only work when they are scheduled, not when they are hoped for. Bake these into the week so quality is checked before replies drop, not after.

1. 1Mon: set weekly cap and targets.
2. 2Wed: sample-review 10 percent of sends.
3. 3Fri: compare reply rate to the brief bar.
4. 4Fri: write one SOP improvement.

SOP drift warning signs

These signs mean the SOP is being bypassed. They usually point to a broken step rather than a broken sender, so question the procedure before the person.

SOP and compliance evidence

When a stakeholder questions quality, the SOP plus the weekly audit is your evidence. Keep the audit log dated so you can show what was checked and when, turning a complaint into a review of the record rather than a debate about trust.

Suggested image brief

Quick checklist

• Roles assigned with clear ownership.
• Core process steps written end to end.
• Quality controls scheduled weekly.
• Review loop tied to the calendar.
• Exception handling defined for warnings.
• SOP linked to onboarding and training.
• Plan to update SOP from learnings.

Frequently asked questions