You don’t need enterprise CRM to remember who you messaged when. You need a lean system you’ll actually open — and a rule for what counts as a “reply.”
What I track at minimum
- Last outbound date — so I don’t double-tap by accident.
- Reply state — none, short acknowledgment, real thread, meeting booked, or closed.
- Next follow-up date — optional, but explicit; “later” isn’t a date.
Why “tool chaos” happens
Spreadsheet plus inbox plus notes app plus a task list means nothing is authoritative. I pick one place for pipeline truth — usually a simple sheet or a single board — and let the rest be scratch.
Reply vs. noise
An auto-reply or a thumbs-up isn’t the same as a conversation. I tag “meaningful reply” loosely: they answered a question, asked one back, or accepted a small next step. That keeps my stats from lying with volume.
Weekly pass (short)
Ten minutes: update states, archive dead threads, and fix any row where “next step” is blank but I’m still mentally carrying the person. The goal isn’t perfect data — it’s not guessing in the next send.
If the system needs a manual every time you return from vacation, it’s too heavy. Trim until you’ll use it on a bad Tuesday.