Cold DM Weekly Metrics Template

How to use this template

Fill the rollup table each week from your tracker or CRM, then answer the prompts to produce one change for next week. Keep it short; a ten-minute review that yields a decision beats a dashboard that takes an hour and changes nothing. The discipline is the decision, not the data entry.

Weekly rollup table

Totals tell you volume; rates tell you efficiency. Always show both, because a week with double the sends will show double the replies while the rate reveals whether efficiency improved or scale did the work. Without rates, growth and improvement look identical and you cannot tell which you achieved.

Review prompts

The prompts exist to force a conclusion. A week of numbers with no question asked is a week of data with no learning. Answer them in writing so hope cannot quietly rewrite the answer, because a review done in your head gets reshaped by what you want to believe.

1. 1Which rate moved most, and why might that be?
2. 2Where did prospects drop out of the flow most?
3. 3What is the single change to test next week?

Reading the rates

Use the rates to ask questions, not to celebrate or panic over one week. A single week is noisy; the trend across four weeks is the signal worth acting on. When reply rate drifts, trace it stage by stage rather than blaming the whole campaign at once, because a blended judgment hides the specific leak.

Turning metrics into action

The output of the review is one test, not ten. Pick the highest-leverage change: usually the weakest transition or the cheapest test. Ten changes at once teach you nothing because you cannot tell which one moved the number, and a review that changes everything changes nothing you can attribute.

• Pick the weakest transition as the test target.
• Change one message or one qualification rule.
• Watch that rate next week for the effect.
• Document the result so learning accumulates.

Worked example

Week one: 300 sends, 24 replies, 8 percent rate. Week two: 320 sends, 22 replies, 6.9 percent. Volume up, rate down. The prompt reveals the new list segment converted worse, so next week's test is to revert to the prior segment or tighten its fit signal. The table exposed the trade that totals alone would have hidden.

Which metrics belong in the rollup

A rollup with too many metrics gets ignored; one with too few hides the leak. Track the handful that map to the funnel and drop vanity numbers that never change a decision. Each metric earns its place by pointing at an action, not by looking impressive on a dashboard.

Spotting trend versus noise

Small programs generate noisy weekly numbers, and reacting to noise burns effort on phantom problems. Use a simple rule to tell a real move from random variation before you change anything, so your one weekly test targets a genuine signal rather than a coin flip.

1. 1Look at the four-week trend before judging any single week.
2. 2Treat a change under roughly 1 point on small samples as noise.
3. 3Confirm a shift persists two weeks before acting on it.
4. 4When in doubt, wait one more week rather than changing two things.

Running the ten-minute review

The value of weekly metrics is the decision they produce, not the numbers they store. A tight, repeatable ritual keeps the review from ballooning into an hour that changes nothing. Time-box it, follow the same order every week, and end with exactly one written test for the coming week.

Building a simple metrics history

A single week is noise; a stored history is where the real learning lives. Keep each week's rollup in one growing sheet so you can see trends, spot seasonality, and prove whether a change actually moved the number over time. The history also protects you from re-testing something you already learned and forgot.

• Append each week's row instead of overwriting the last.
• Keep a notes column recording the test you ran that week.
• Chart reply rate over time to see trend, not just this week.
• Review the last quarter before starting any new experiment.

Sharing metrics with the team

Metrics change behavior only when the people doing the work can see them. Share the weekly rollup in a way that invites contribution rather than blame: show the rates, name the weak transition, and ask the senders what they noticed. The people sending the messages often know why a rate moved before the numbers explain it, and a shared review turns their intuition into a testable idea.

• Show rates, not just totals, so effort and efficiency are separated.
• Frame the weak transition as the team's shared target, not a fault.
• Ask senders what they observed before you interpret the numbers.
• Assign the one test to a named owner for the coming week.

Avoiding metric gaming

The moment a metric becomes a target, people optimize the metric rather than the outcome, sometimes in ways that hurt the program. If you reward raw sends, you get more sends and worse targeting; if you reward reply rate alone, senders may cherry-pick easy contacts. Watch for the gaming that each metric invites, and pair metrics so one cannot be inflated at the expense of another.

Suggested image brief

Quick checklist

• Rollup table filled from tracker or CRM weekly.
• Reply and meeting rates computed, not just totals.
• Three review prompts answered in writing.
• Weakest transition identified from the rates.
• One test change recorded for next week.
• Result of last week's test documented.
• Trend reviewed over four weeks, not one.

Frequently asked questions