Follow-Up.

A family friend in Kirkland was thinking about selling his one-of-a-kind home. We spent a few hours with him at the listing presentation, answering questions and talking through the whole process. It felt like a great meeting. We knew him personally, and we were excited about the chance to sell the home. He told us it would probably be about a year before he was ready.

At first, we stayed in touch. We would stop by, see how he was doing, ask if we could help, and sometimes sit down for coffee. Then, toward the end of that year, we lost the rhythm. I got a call and learned that he had signed a listing agreement with another agent. I was told she had come to his door and made a strong impression. My reaction was, “What do you mean he signed a contract with somebody else?”

I cannot say why he made that choice, and he did not owe us the listing. What I do know is that a strong presentation and a personal relationship did not replace steady follow-up. I learned to build a system that would not fade as a long timeline approached its decision point. I also learned not to mistake a promising conversation for a commitment: when the seller is ready and it is appropriate, get the listing agreement signed.

A long timeline is still a relationship

The failure in that story was not a lack of an initial conversation. It was losing continuity before the person reached the moment of decision. A good follow-up system must do more than send messages at fixed intervals. It should remember what the person needs, when their circumstances might change, and the next useful thing the agent has promised to do. It should also make a long-horizon relationship visible to someone authorized to step in when the usual agent is unavailable.

The symptoms are easy to miss: an active relationship has no next useful action, owner, or date; a question remains unanswered; a promised introduction sits in someone's memory; or a future decision point passes without a human check-in. An automation can create the appearance of activity while none of those gaps is resolved. The first question is not “How many touches went out?” It is “Which person is waiting for something useful from us?”

Build the next-step rhythm

After a meaningful conversation, record the need or question in the person's words, their timing, contact preference and permission, and the specific next useful action. Give that action an owner and a due date. If the decision is months away, record the known decision point and schedule a human review before it arrives; do not rely on a vague “someday” tag. Use reminders or content to support the relationship, but do not present an automated touch as a personal conversation or a fulfilled promise.

Once a week, open an exception view in the existing CRM. Look for active relationships with no next action, overdue actions, unanswered questions, no owner, or a stalled decision point. Resolve the oldest promises first, then decide whether each other record needs a human response, an appropriate reminder, a revised date, or closure. If the same exception keeps appearing, fix the handoff or process that produces it. The Follow-Up System Builder and Weekly Review is a configuration and review tool, not another contact database.

An agent should be able to open the CRM record for an active relationship and understand the last meaningful contact, the person's need, the next useful action, and who owns it. That is the observable standard. It does not require a particular CRM brand or a high-frequency campaign.

Know whether it is holding

Each week, count active relationships missing a next action, owner, or due date at the start and end of the review. Then check whether due promises—answers, introductions, or agreed check-ins—were actually fulfilled on time. If the gaps grow, look at ownership, capacity, notification, or an unrealistic follow-up rule before adding more messages. Conversations reveal a need; Follow-Up keeps the next step alive. Technology makes it visible, and Time gives the human work a place to happen.