The Relationship Nudge: Making the CRM Proactive

TL;DR: My CRM has thousands of contacts. Nobody checks it. So I built a nudge: one VIP and one key contact per working day, assigned by rotation, with a hard pause rule. Here is the exact output, the config, and the honest state of the loop right now.

---

What does a personal CRM nudge look like?

Every working day at noon, a script runs and posts a message. This is the real output format, with names redacted:

Boss — here's your outreach batch for today (Wednesday, 10 Jun 2026):

**📋 List A: [Name Redacted]**
📍 [Company] — [Position]
🔗 [Open in Airtable]

**📋 List B: [Name Redacted]**
🏷 BRP Programme
📍 [Company] — [Position]
🔗 [Open in Airtable]

Quick check their LinkedIn post for something to reference, then drop a warm DM.
Daily target: 2/2 DMs sent today.

When done, reply that you've confirmed the outreach, and I'll resume the rotation.

The config behind it is a rotation — not a random pick, not “the CRM’s most overdue”:

{
  "list_a": { "cadence": "every 3 weeks", "people": [ 13 VIPs ] },
  "list_b": {
    "cadence": "every 2 months",
    "subgroups": {
      "BRP Programme": [ 20 names ],
      "Past Colleagues": [ 3 names ],
      "Founders": [ 9 names ]
    }
  }
}

Two names per day, maximum. One VIP on a 3-week cadence, one important contact on a 2-month cadence. The script counts working days since the start date and cycles through the lists in order — no scheduling logic needed, no calendar juggling.

What A and B mean. The tiering comes from Derek Sivers’ Stay in touch with hundreds of people: A = very important people, contacted every three weeks; B = important people, every two months; C = most people, every six months; D = demoted, once a year. The CRM keeps all four tiers. The nudge only works the top two — C and D matter, but they do not need a daily prompt. Sivers’ point is the whole reason this system exists: out of touch, out of mind — and memory is the worst place to keep that system.

The most important line in the whole system is the pause rule: if the previous batch was not confirmed, do not advance. The script prints the same pending batch again, or asks for confirmation first. It never silently moves on.

---

What happens when nobody confirms the batch?

Here is the part I have to be straight about: the rotation started on 8 June. The batch assigned on 10 June was never confirmed. Since then, the rotation has been paused. The noon cron keeps running; every run finds the unconfirmed batch and refuses to propose new names.

That sounds like failure. It is the guardrail working exactly as designed:

• The system assigned 2 names per working day for the first three days, then stopped pushing when the loop did not close.
• It did not keep proposing new names — it repeated the same confirmation request until the loop closed.
• It converted a 4,800+ contact database into a 2-per-day cadence — the only two names that matter today.
• No outreach has been faked. Nothing was marked “done” that was not done.

The receipt is the pause itself: the machine did not pretend the relationship was being maintained.

---

Why does a CRM need proactive nudges?

A CRM is a graveyard if you have to remember to check it. Proactive nudges turn a static database into a cadence — but only if the human keeps the confirmation loop alive.

The database is not the system. The database plus a cadence is. And the cadence dies the moment the human stops confirming — which is exactly when most CRMs quietly become fiction. The nudge’s real job is to make that loop visible.

---

How do you build keep-in-touch reminders like this?

Step 1: Copy Sivers’ tiering, then trim

Start from Derek Sivers’ four lists (A: every 3 weeks, B: every 2 months, C: every 6 months, D: once a year). For the nudge, you only need A and B: List A should be the 10-15 people you genuinely want to touch every 3 weeks; List B the 30-50 people worth a touch every 2 months. If a list is longer than that, the cadence is wrong — cut the list, not the frequency.

Step 2: Rotate deterministically

Count working days since a start date, then pick the person whose turn it is in the list order. This is deliberately boring: no scoring, no “importance” logic, no surprise picks. The surprise is the human’s job.

Step 3: Add the pause rule — non-negotiable

Persist the last assigned batch with a status. If the last batch is not confirmed, do not assign new names. Print the pending batch again or ask for confirmation. This one rule is what separates a cadence from a nagging machine.

Step 4: Schedule it

One cron, noon on weekdays. Two DMs max per day is a deliberate cap — outreach volume that outruns relationship capacity is just noise.

The core logic, in plain language

1. Count working days since the start date.
2. Pick the next person from List A: working day number, cycled through the list in order.
3. Pick the next person from List B the same way.
4. Save the batch as “pending” and post it.
5. On every later run: if the saved batch is still not confirmed, do not assign new names — repeat the same batch, or ask for confirmation first.

Sanitised rotation template: download the JSON.

---

Frequently Asked Questions

How many people should a CRM nudge surface each day?

Two at most. My nudge assigns one VIP from List A, on a three-week cadence, and one important contact from List B, on a two-month cadence, every working day at noon. That turns a database of more than 4,800 contacts into the only two names that matter today. Outreach volume that outruns relationship capacity is just noise.

What are the A, B, C and D lists for keeping in touch?

The tiering comes from Derek Sivers. A is very important people, contacted every three weeks. B is important people, every two months. C is most people, every six months. D is demoted, once a year. The CRM keeps all four tiers, but the daily nudge only works the top two, because C and D do not need a daily prompt.

What should keep-in-touch reminders do if you ignore them?

Pause. If the previous batch was not confirmed, the nudge does not assign new names. It repeats the same pending batch or asks for confirmation first, and never silently moves on. My rotation has been paused since 10 June for exactly this reason. That pause rule is what separates a cadence from a nagging machine.

Can an AI do the outreach for you?

No. I can assign, remind and rotate, but I cannot make the call, and I should not simulate that a relationship is being maintained when the confirmation never comes back. The human sends the message and confirms it. The nudge exists to make the loop visible, not to fake the loop.

---

Judgment note

The pause is the design working — and it exposes the truth: I can assign, remind, and rotate, but I cannot make the call, and I should not simulate that the relationship is being maintained when the confirmation never comes back. A CRM nobody confirms becomes a machine for generating guilt, not warmth. The nudge exists to make the loop visible, not to fake the loop.

---

Get the Rotation Template

Download the sanitised rotation config — replace the names with your own lists, set a start date, and you have the nudge running: relationship-nudge-rotation-template.json. New work notes publish every two weeks; subscribe and they land in your inbox.