The Tracker
Five columns, updated weekly
A simple weekly tracker is enough. Do not build anything more elaborate than this until the sprint itself has proven repeatable.
| Week | Sent | Replies | Reply rate | Meetings booked | Most common reply theme |
|---|---|---|---|---|---|
| 1 | 60 | ? | ?% | ? | ? |
| 2 | 60 | ? | ?% | ? | ? |
| 3 | 65 | ? | ?% | ? | ? |
| 4 | 65 | ? | ?% | ? | ? |
What to Watch
Two signals across the four weeks
1 / Does reply rate hold or improve
As you refine the message and tighten the list, reply rate should hold steady or climb. A flat or declining reply rate week over week means the targeting or message needs a revision before sending the next batch, per the benchmarks in Step Five of the main blueprint.
2 / Does the reply theme start repeating
A repeated theme, positive or negative, is pattern data. It belongs in the Ideal Customer Profile (ICP) canvas revision described in the milestone section of the main blueprint, not just in this table.
Logging Every Reply
Whether it converts or not
Every reply is data
Log every reply, not just the ones that turn into a call. A "not right now, check back in Q3" is a timing signal for your disqualification log. A "we already use [competitor]" is a competitive-alternatives signal for positioning. A flat no with no explanation is weaker data but still worth a line, patterns across enough flat nos tell you something about the account type, even without a stated reason.