Database nurture that actually earns referrals
Past clients and sphere do not need another newsletter. They need a cadence that remembers them, reaches them for a reason, and makes asking for a referral a natural next step.
Every agent knows the math: the most profitable leads are the ones who already know you. Every agent also knows why that math rarely shows up in revenue: nurture is the work that gets dropped first when a live deal heats up. The answer is not a cleverer newsletter template. It is a cadence that does not depend on you remembering to run it.
Four sequences, not one broadcast
- Just-closed care: a 90-day sequence after close — not 'how was your experience' but 'here are the three things new owners wish they had known at this stage,' with ownership on who sends and who approves.
- Seasonal check-in: twice-yearly, tied to a real reason (tax season, anniversary, neighborhood shift), drafted from past conversations, approved before send.
- Value without pitching: local market notes that cite a source and date, not vague claims — and only when you have something worth saying.
- Referral-ready ask: review request, then referral prompt — spaced, sequenced, and skipped entirely if the relationship signal is not there.
When to ask (and when not to)
A referral request after a genuine check-in succeeds because the check-in was genuine. A referral request on top of a broadcast that no one opened fails because the relationship work did not happen. The team sequences asks behind completed value — a delivered update, a answered question, a past-client anniversary — and suppresses asks when sentiment or recent activity suggests waiting. Approval sees the context, not just the draft.
Questions we hear
Will this feel automated to past clients?
Only if you let it. Drafts are prepared from real history, reference specifics, and wait for your approval. Clients hear from you, in your voice, at a pace you set — the automation is in the remembering and drafting, not the sending.