Count replies, not sends

Activity metrics feel good. They’re also the fastest way to lie to yourself about whether outreach is working.

Sends are easy to count — they’re under your control. Replies are the messy signal that something actually happened in someone else’s head.

I still track sends for pacing and platform health, but replies are the headline metric when I ask “is this working?”

What I log weekly (five minutes)

  • Outbound messages sent (rough)
  • Meaningful replies — not auto-responses or “thanks” with no next step, unless that’s the win state
  • One sentence: what I changed that week (hypothesis)

Why sends mislead

High send volume can mask a broken message — you feel productive while training recipients to ignore you. Counting sends as success rewards motion, not learning.

Pairing metrics without becoming a spreadsheet cult

I don’t need statistical significance on day twelve. I need directional truth: did replies go up after I changed the hook? Flatlined? Crashed?

The ego trap

Reply silence bruises the ego. Sends stroke it. I pick the bruise — it’s cheaper than lying to myself with busyness.

If your dashboard only celebrates output, don’t be surprised when your pipeline celebrates you back with silence.