How to use a personal CRM to keep in touch

Want AI to help with the maintenance?

This guide covers the habits and structure that make a personal CRM useful. If you want help building one, drafting profiles from email history, or organizing conversation notes automatically, I also wrote a detailed guide to setting up a personal CRM with AI.

Remembering people is part of caring about them.

I have 2,500+ people in my personal CRM, mostly from the last four or five years. It gets automatic updates and duplicate records are cleaned up. I’m obviously not close friends with all 2,500 people. I use it to remember our conversations and notice ways I might be able to help.

Keeping in touch is fun for me. It’s a daily habit. Someone comes to mind because of an idea, an article, or another person I think they’d enjoy meeting. Having a few notes makes it much easier to pick that conversation back up.

You can start with a notes app or a spreadsheet. Before choosing a tool, try keeping track of ten people you would like to stay in touch with. You’ll learn what is useful by having the next conversation.

Start with people you already know.

A giant contact import gives you a lot to organize before you have learned whether the system helps. Choose ten people you would actually be happy to hear from. They might include friends, former colleagues, people from a community, or someone you recently enjoyed meeting.

Add enough context that you could reopen the record in six months and understand the relationship. If you have an open promise, put it somewhere you will see it. “Send the article we discussed” is more immediately useful than another job-title field.

• Choose ten people you want to remember and stay in touch with.
• Write how you know each person.
• Add a short note about your latest real conversation.
• Record anything you promised to do.
• Choose a small daily or weekly moment to look at the list.

Bring your old notes over a little at a time.

If your notes are scattered across apps and message threads, bring over a few people you actually want to stay in touch with. Try using those records before importing everyone. You’ll find out pretty quickly which details help and which ones just give you more sorting to do.

Check identity before merging anything. Two people with the same first and last name can be different people. One person may also appear under an old company, a nickname, and a newer email address. Match against something you know, such as where you met and an existing conversation. When you are uncertain, keep the records separate until you can resolve it.

Keep the date on an old note. “Thinking about starting a company” from two years ago gives you a question to ask. It doesn’t tell you what they’re doing today. Moving that note into a new app doesn’t make it current.

Before relying on a new tool, make sure you can retrieve your own notes from it in a usable format. Try an export and open a few records. Check that names, dates, line breaks, and open promises survived. You do not need a complicated migration plan for ten people, but you should know where the information you care about will live.

A personal CRM template you can start with.

Here’s a made-up record for Maya, someone you met at a writing dinner and kept talking to over text. It only needs enough detail to help you remember the conversation. You can leave out the play-by-play of the whole evening.

Keep a person’s current situation separate from something they might do. “Thinking about starting a group” is different from “launching a group next month.” If you aren’t sure, preserve that uncertainty.

A date helps you judge whether context is still fresh. Something from years ago might be a good question to ask, rather than a fact to assume.

I’ll keep a spouse’s name, children’s names, or pets’ names if the person mentions them. Also hobbies, projects, things they’re excited about, ideas, and challenges they share. I want to remember the things that matter to them. I’m not researching their family to complete a profile.

Maya Chen

How we met: Writing dinner, September 5.
Last real exchange: Text conversation, September 6.
What we discussed: Short fiction; helping new writers feel comfortable sharing unfinished work.
Current project: Thinking about starting a neighborhood writing group.
My promise: Send the welcome-email example we discussed.
Possible next question: How is the writing group idea coming along?
Usual channel: Text.
Circle: Writing friends.

They told you they are exploring a move.

Record that they are considering it. Ask how the decision is going before assuming it happened.

You promised to send something.

Record the specific item and an action you can complete.

You notice a possible introduction.

Keep it as an idea until you ask both people. A possible match can wait.

They mention family, a pet, or another personal detail.

Save only voluntarily shared context that is useful to remember. Do not infer missing details. Keep the record private and leave unnecessary personal information out of anything you forward.

Organize by context you can recognize.

Circles help you remember why people belong in your life. “Former coworkers,” “writing friends,” and “people from that dinner” are useful because they bring back shared context.

A person can belong to more than one circle. Someone who started as an industry contact may also become a friend. Let the record reflect the relationship as it changes.

Add structure for searches you might actually make: Who would enjoy this writing event? Who has relevant experience? Who lives near the place I’m visiting?

Keep reminder frequency separate from these circles.

A reminder means “think about this person.”

A reminder brings someone back to mind. You still choose whether contacting them makes sense.

Consider a close friend regularly, an old colleague every few months, or check back after an event they mentioned. Choose a rhythm you can maintain.

Something you promised deserves a follow-up. An old friend coming to mind might deserve a quick hello. And sometimes you’ll look at the record and realize you already caught up yesterday. That’s fine too.

Before writing, read the latest exchange in the channel you normally use. If you already texted yesterday, the CRM may simply need updating.

What my own system adds.

My reminders use 14, 30, 90, and 365-day intervals. They bring someone back to mind. I still decide whether there’s a reason to message them.

Automations help me offer more value to people in my network. They can bring together recent conversation context, open follow-ups, and upcoming milestones. The useful result might be a question I can answer, a promise I can keep, or two people who might enjoy meeting. Before acting on a suggestion, check the latest exchange: is this still something the person wants help with? A reminder by itself does not answer that.

I want the system to remember what actually happened. An intro suggestion still needs two yeses, and a drafted message still needs to be sent. Otherwise I could think I’ve followed up when I haven’t.

One example I’m really happy about is finding investor matches for other people raising money. The tools suggest people in my network, then I make the final call on who fits and whom to contact. That has led to people getting investment. This is the part of automation I get excited about: it helps me offer more value to people I know.

Check whether an automated suggestion still fits.

Imagine a fictional system notices that two people have discussed running workshops. One is actively organizing a first event; the other mentioned it years ago and may have moved on. A keyword match alone would miss that difference. Read the recent context before proposing anything, and ask about the interest if you are unsure. The system can suggest the match; both people still choose whether to connect.

The same applies to a resource. A link about fundraising may fit someone’s old job title while having nothing to do with what they need today. A better suggestion includes the specific question the person asked and why this resource might answer it. If you cannot explain the relevance in a sentence, save the link rather than sending it to a list of people.

Keep an important distinction in your records: a generated draft is not a sent message, and a proposed introduction is not a completed introduction. Otherwise, your reminder system can decide you have followed through when you have not. Automation should make real follow-through easier to see.

What a small CRM review can look like.

The three people and messages in this walkthrough are fictional illustrations.

Suppose you open your list and see three people. Maya is waiting for something you promised. Ben is an old friend you haven’t spoken to in a while. Priya received a note from you a few days ago and has not replied.

Those are three different situations. Giving all three the same “just checking in” message would ignore the context you took time to save.

Try a small review. Finish open promises, read the latest exchange, and choose your next action. Stop after a few people.

In the exchange below, Maya tells you the plan changed. Great, now you know! Send what you promised, update the note, and follow the thing she’s actually working on. Asking about a live welcome session doesn’t mean you’ve volunteered to organize it.

The generic check-in makes Maya remind you about the item you already promised. In the complete exchange, you send it, read the changed context, and ask a relevant question. Mark the original promise complete, note that the group is trying live welcome sessions, and leave the new question as an unanswered conversation. Do not turn it into a promise to organize the session. When Maya answers, update the context again; until then, there is nothing else to send.

Hey Maya! Here’s the welcome-email example we talked about. The opening question is the part I thought might work for your group. Hope it helps!

Hey Maya! Just checking in. Let me know if there’s anything I can help with.

Maya: Thanks! We’ve changed direction a little. Instead of sending a longer welcome email, we’re trying a short live welcome session.

That makes sense! Is the tricky part getting people to attend, or helping them start talking once they’re there?

Maya: you promised a welcome-email example.

Find the example, send it with a sentence of context, then mark the promise complete.

Ben: an old friend came to mind and there is no unanswered message.

Send a small, honest hello if you would like to reconnect. You do not need a business reason.

Priya: you reached out recently and have not heard back.

Give her room. Correct the record if the recent message is missing; do not send again just to clear a reminder.

When everyone looks overdue, choose one useful action.

A backlog can make a relationship tool feel like a list of people you have disappointed. Before sending anything, check what the reminder actually means. It may be based on an old interval, an incomplete record, or a conversation that happened in another channel. None of those is a reason to send an apology to everyone.

Start with something you explicitly promised. Then look for a timely reason you would be glad to reach out even without the reminder: a shared event coming up, a question you can now answer, or an old friend who came to mind. If you have no useful context, an honest hello can still be appropriate. You do not need to manufacture a professional hook.

For the rest, change the review date or loosen the cadence if it no longer fits. A friend with whom you naturally exchange messages does not need the same system as someone you enjoy seeing once a year. An acquaintance who has not answered your last note may need space. Treat those as different relationships instead of trying to empty a queue.

When you finish, note what you actually did. Maybe you sent something. Maybe you fixed a note or decided to wait. I wouldn’t judge the system only by the number of messages you send. The point is to make staying in touch easier.

Write from the relationship, not from the reminder.

An old conversation gives you a place to begin. A shared memory, a project they were excited about, or the honest fact that they came to mind can all work.

Keep the first note easy to answer. For a no-agenda reconnection, one small life question is enough. If they reply, follow what they say. You can find out what is current before offering advice or asking for something.

A resource or an introduction can be lovely when it fits. You do not have to attach one to every hello.

When I’m busy, staying in touch might be as simple as sending an article with a quick thought because it reminded me of someone. It does not have to become a calendar invitation. A link that fits something they actually care about can give us a small, natural conversation.

hey Ben! walked past that ramen place we used to go to and thought of you. how’ve you been?

Hey Maya! How’s the writing group idea coming along? Still thinking about the part you mentioned about people sharing unfinished work.

hey, random but you came to mind today. how are you!

Text can make room for ordinary conversation.

In my experience, some of the best relationships happen over text. You can share a passing thought, ask a small question, or continue a conversation without turning it into an event.

Email is useful too, especially for an introduction, a longer update, or something with several links. Use the channel that is normal for the relationship. If a new connection is developing over email and you would like to text, ask.

A walk, dinner, call, or text can be the latest real interaction. Your system should let you record it easily.

You can reach back out after years.

Sometimes I scroll down through old text threads and see who comes to mind. A name brings back a memory, something we used to talk about, or a question I’m curious to ask now. That can be enough of a reason to say hello. I have seen conversations restart even after decades.

You don’t need to turn the gap into a long apology. Acknowledge it lightly, mention why you thought of them, and ask a question that belongs to your shared history. Leave room for the fact that life may have changed. A job, city, or interest from years ago is a place to start asking, not something to assume is still true.

If I’m reaching out because I want help with something, I should say so. There is no need to disguise a request as a reunion. When I just want to hear how someone is doing, I can let that be the whole point. Whether a conversation continues depends on both people.

Hey! I saw a tiny neighborhood chess tournament and thought of our games after school. It’s been ages. Are you still playing at all?

Capture a little, then get back to your day.

After a conversation, write a few sentences while it is fresh. What did they care about? What did you promise? Is there a date or next step worth remembering? Those questions keep the note useful.

If you use automated notes, read them before relying on them. Names get mixed up. A tentative plan can sound definite in a summary. Check the part that would change what you say or do.

When you send a message, record the actual contact. A draft is still something you are considering. When you complete a promise, close it. That keeps the next review from surfacing work you have already done.

Occasionally merge duplicate records and remove context that has become misleading. Keep the records private. People should be able to tell you something without finding it in a shared contact list.

When a note gets the story wrong.

Here is a fictional example. A summary says, “Casey is moving to Seattle in June and wants founder introductions.” The original message said, “We might spend a month in Seattle this summer. Still figuring it out.” There was no request for introductions. Sending a welcome-to-Seattle message and offering founder connections would turn two guesses into a confident story.

Repair the note first: Casey mentioned a possible summer stay; timing and plans are unconfirmed. Remove the invented request. If you were going to write anyway, a fitting question might be, “Did anything come of that possible Seattle trip?” That lets Casey supply the current facts.

If you already sent the mistaken message, correct it plainly. “I misremembered that as a definite move. Sorry about that. Are you still considering the trip?” Then update the record from the answer. A CRM is useful because you can improve it. You do not need to defend an old note when the person tells you what is actually happening.

Common questions