Somewhere in your Google Drive is a spreadsheet called "Contacts 2024" with maybe thirty rows and a column for "follow up" that hasn't been touched since March. You built it during a slow week with good intentions, added a dozen names, and then never opened it again, because nothing in it ever told you to.
Learning how to build a personal CRM fixes that specific failure: not the absence of a system, but a system with no reason to be reopened. This guide covers how to go from a blank spreadsheet or Notion page to a working relationship system in about an hour.
By the end, you will have a contact table, a cadence, and a weekly review that surfaces exactly who to message on Monday morning.
Pick the tool you already have open during your workday. A personal CRM you have to remember to visit is a personal CRM you will abandon by week three.
That means the decision is less about features and more about proximity. If your day runs through Google Sheets, build it there. If your notes, meeting docs, and project pages live in Notion, build it there so a contact is two clicks from the deal note that mentions them.
A spreadsheet wins on speed. You can have columns, filters, and sorting in five minutes, and building a functional contact tracker in Excel or Sheets takes no formulas beyond a filter, as shown in this walkthrough of a basic Excel CRM setup. For a consultant tracking 60 past clients and referral sources, that is enough.
A Notion-style workspace wins on context. Each contact becomes a page, so meeting notes, a proposal draft, and their last three messages sit in one place. That pays off during a long sales cycle where you need to recall what a buyer said in February before a September call.
Say this part out loud now so it does not surprise you in month two: a spreadsheet has no memory of its own. It will never tell you that a warm lead has gone silent for 90 days. It sits there, accurate and completely passive.
That single limitation decides whether your build works. A manual personal CRM only functions if you attach a recurring human review to it from day one, because nothing inside the file will ever prompt you. Skip that step, and you get a tidy archive of people you used to talk to.
So block a 15-minute recurring calendar hold before you enter a single contact. Then build the table it will point you to.
Start with one table, one row per person, and eight columns. Resist the urge to build a second table for companies until you have used the first one for a month.
The point of the structure is to make your next message easier to write. Every field should earn its place by answering a question you will have when you are staring at a name and wondering what to say.
These are the columns that stop you from sending a generic check-in:
Leave out anything a CRM built for sales teams would include. Deal value, pipeline stage, and lead scoring add maintenance without helping you remember that a former colleague is job hunting.
The field you will wish you had added is Last Contact Note. Without it, you know you spoke in March and nothing else. With it, you open with "how did the Series B close go" and the reply rate changes.
Keep notes to one line, written like a text to yourself. "Hiring two AEs in Q4, wants intros" beats a three-paragraph meeting summary you will never reread.
Tags should describe how you will search, so build them around use cases. Tag someone "referral-source," "hiring," or "prospect-2026," and you can pull a filtered list in seconds when a role opens, or a project ends.
Cap yourself at six tags total. A tagging scheme with 30 labels turns every new contact into a small decision, and small decisions are what kill weekly habits.
Export your LinkedIn connections to CSV, paste them in, then delete anyone you wouldn't recognize in an email. You will cut 70 percent of the list, and that is the correct outcome.
Do not backfill Last Contact Date for 300 people. Fill in the 25 relationships that matter most to your next six months, leave the rest blank, and let the blanks fill themselves as you interact.
A clean 40-person table you use beats a 900-row import you avoid. With the names in place, the next question is how often each one should hear from you.
Cadence is what separates a personal CRM from an address book. You assign each person a rhythm, then let the dates tell you who is due.
Do this by tier, not by individual guesswork. Guessing per person means renegotiating the decision every week, and you will stop.
Three tiers is enough. Tier 1 gets contact every 30 days, Tier 2 every 90, Tier 3 every six months.
Size the tiers against your actual calendar. If you can send eight thoughtful messages a week, Tier 1 should hold about 15 people, not 60. A sales rep working named accounts might put every active buyer in Tier 1 and drop past champions to Tier 2 once a deal closes.
Tiers also make hard calls easy. That contact you met once at a conference belongs in Tier 3, and putting them there is what protects your attention for the five people who can open doors.
Three saved views do all the work. This Week filters Next Follow-Up Date to the next seven days. Overdue shows anything past due. Key Relationships filters to Tier 1 so you can scan for silence.
In Sheets, that is a filter view per tab. In Notion, it is three linked database views on one dashboard page. Either way, you should never open the raw table again during a normal week.
The Overdue view is the uncomfortable one, and it's why the system works. Seeing four names from six weeks ago is a prompt no reminder app matches.
Set the next date the moment you finish a conversation, while you still know what should happen next. A later date is a date you invent from nothing.
Anchor dates to real events when you can. "Two weeks after their product launch" or "early January, when budgets reset" gives you a reason to write. A repeatable sequence of low-pressure touchpoints works because it removes the pressure to convert in a single interaction.
Now the system knows who is due. The remaining risk is that updating it feels like work.
Read more: Best Follow-Up Techniques After Networking Events That Keep Doors Open
If logging a conversation takes longer than 60 seconds, you will stop logging conversations. Design for the version of you who just got off a call and has another one in four minutes.
The target is two edits per interaction: update Last Contact Date and write one line in the note field. Everything else is optional.
Capture the detail you would need to sound like you were paying attention. A promotion mentioned in passing, a hiring plan, a conference they are speaking at in November.
Write it in their words when possible. "Frustrated with their current vendor's onboarding" is a usable opening in six weeks. "Good call" is not.
For a job search, log what the person offered rather than what you asked. "Said she'd flag me if the platform role reopens" is a specific thing to reference when you follow up in October.
Your 15-minute Friday hold does four things in order: clear Overdue, scan This Week, check Key Relationships for anyone silent past their tier, and set new dates for everyone you contacted.
Attach it to something you already do. Do it right after your weekly pipeline review or your Friday inbox cleanup, so the habit borrows an existing trigger.
Protect the length. Fifteen minutes forces decisions; an open-ended session turns into reorganizing columns.
You need one nudge that reaches you outside the file. Create a recurring calendar event titled with the actual instruction: "Open CRM: clear Overdue, set 5 dates."
For time-sensitive follow-ups, add a second layer. Email yourself with a send-later date, or put a single calendar event on the day a specific follow-up is due, named after the person. Two or three of those a month, reserved for high-stakes moments like a post-interview check-in.
That is a complete working system. What it will never do is notice a pattern you missed.
Run this manual build for 60 days before you consider software. The habit is the asset, and the tool you eventually choose should inherit a habit that already works.
You will hit the ceiling in a predictable way. Your table knows what you told it, and nothing more. It cannot see that a Tier 2 contact just changed jobs, that a prospect went silent three weeks earlier than their pattern, or that two people in your list should meet.
That gap is where a copilot earns its place. Goodword watches for timing and surfaces who is worth a message this week, so your attention goes to the conversation instead of the maintenance. The judgment stays yours; the remembering does not have to.
Move when the manual review starts feeling like data entry. That is the signal you have more relationships than a passive file can hold.
Yes. Google Sheets, Excel, and Notion's free tier all handle a personal CRM for a few hundred contacts with no cost. You only pay when you want a tool that tracks timing and prompts you without a manual weekly review.
Use a spreadsheet if you want filtering and sorting today with minimal setup. Choose Notion if you write detailed notes per person and want each contact to have its own page linked to meeting docs and projects.
Eight are enough: name, company and role, how you met, last contact date, last contact note, next follow-up date, tier, and what they care about. The last contact note is the one people skip and later wish they had, because it makes your next message specific.
Update it twice: once right after any real conversation (under a minute), and once during a 15-minute weekly review. The weekly pass is non-negotiable in a manual system, since nothing in the file will prompt you.
Set the next follow-up date the moment a conversation ends, then build an Overdue view that shows anything past due. Pair it with a recurring calendar event that names the exact task, so the reminder reaches you outside the file.
Move when your weekly review starts feeling like data entry, or when you pass roughly 150 active relationships. That is also when you start missing signals a static table cannot see, like a job change or a contact going unusually silent.
You now have the full build: a single contact table with fields that preserve context, three tiers that set cadence, saved views that tell you who is due, and a Friday review that makes the whole thing run. Open a blank sheet and enter 25 names. That is a working system before lunch.
Then go find the one name you already know belongs in the Overdue column. The hiring manager, the former client, the person who offered an introduction in the spring. Send that message today, and let the system carry the next one.
When the manual review starts costing more than it returns, try Goodword for free and let it surface who you should reconnect with this week.
.svg)
.png)