Cold DM Pipeline Template

How to use this template

Create one row per prospect at first send and update the stage as they move. At week's end, total each stage to compute conversion between steps. Logging immediately is what makes the data trustworthy; logging from memory at the end of the week invites errors that quietly ruin your math. The habit matters more than the tool.

Stage definitions

Define stages before you track, or your numbers mean different things week to week. A 'meeting' in your head must be the same event as a 'meeting' in the tracker, or your conversion math is meaningless and your decisions are built on sand. Observable events beat feelings every time.

1. 1Sent: first message delivered and confirmed in the log.
2. 2Replied: any response received, positive or clarifying.
3. 3Qualified: fits your written criteria after the reply.
4. 4Meeting: call or demo booked on the calendar.
5. 5Client: paid or signed, not merely interested.

Expected conversion table

Fill the right column with your expected rates so you can compare plan to actual each week. The gap between expected and actual is the most useful number on the page, because it tells you which stage to fix rather than guessing. An expected rate is a hypothesis; the actual rate is the test.

Stage conversion math

Conversion between stages tells you which step to fix. A low reply rate is a message problem; a low meeting rate is often a qualification problem; a low close rate is usually an offer or fit problem. Each step points to a different remedy, so naming the weak step is half the battle and guessing is the other half you want to avoid.

Worked example

You sent 200 messages, 20 replied, 6 booked, 1 became a client. Sent-to-reply is 10 percent, reply-to-meeting 30 percent, meeting-to-client about 17 percent. The weakest step is the top: only 10 percent replied, so your first lever is the message or the list, not the close. The pipeline points you at the right problem instead of the loud one.

Weekly review using the template

Spend ten minutes turning the tracker into a decision. The tracker is not the goal; the decision is. If you review and change nothing, the pipeline is just a chore that consumes time without producing improvement, and people stop updating it.

• Total each stage to see the pipeline shape.
• Find the weakest transition rate.
• Plan one fix and watch the number next week.
• Note stuck prospects over 14 days and decide their fate.

Diagnosing each leaking stage

Every stage leaks for a different reason and responds to a different fix. Matching the symptom to the remedy is what turns a pipeline from a scoreboard into a repair manual. Use the table as a first hypothesis, then confirm with the actual messages and notes before you change anything.

Managing aging and stalled prospects

Prospects that sit in a stage too long distort your rates and clog attention. Build an aging rule so stalled rows get a decision rather than lingering forever as false hope. A pipeline full of stale 'maybes' looks busy but converts nothing, and it hides how the fresh prospects are really performing.

1. 1Flag any prospect with no movement for 14 days.
2. 2Send one final value-led follow-up before closing the row.
3. 3Mark as lost with a one-line reason if still silent after 21 days.
4. 4Review lost reasons monthly to spot a pattern worth fixing.

Pipeline hygiene rules

A pipeline is only as trustworthy as the discipline behind it. A few simple rules keep the data clean enough that the conversion math means something, because a pipeline half-updated from memory produces numbers worse than no pipeline at all — they look authoritative while being wrong. Enforce the rules and the weekly review becomes reliable.

• Log a prospect at first send, never retroactively from memory.
• Move a prospect only on an observed event, not a hunch.
• Never skip a stage; a jump hides where the real transition happened.
• Record a one-line reason whenever you mark a row lost.
• Reconcile the pipeline against the sender's log weekly.

Scaling the pipeline as the team grows

A pipeline that works for one sender can break with three, because ownership blurs and double-messaging creeps in. As the team grows, add the structure that keeps the data clean: clear ownership per prospect, a shared stage definition, and a hygiene owner who audits weekly. The goal is that the pipeline still answers the same questions at five senders as it did at one.

Reporting the pipeline upward

When you report a pipeline to a client or a boss, the raw tracker is too much detail and the single headline number is too little. Summarize the shape: how many entered, where the biggest leak is, and the one fix in progress. This framing turns a status update into a decision conversation and shows you are managing the funnel, not just watching it.

1. 1Report the count entering the pipeline this period.
2. 2Name the weakest transition and its rate.
3. 3State the one fix you are testing and why.
4. 4Show the trend versus last period, not just the snapshot.

Suggested image brief

Quick checklist

• Pipeline created with the five core stages.
• Stage definitions written and shared with the team.
• One row added per prospect at first send.
• Expected conversion rates filled in the table.
• Weekly stage totals computed and compared.
• Weakest transition identified explicitly.
• One improvement planned from the data each week.

Frequently asked questions