There's a whole corner of the internet dedicated to building personal CRM systems in Obsidian. People share their templates — frontmatter for birthday, phone number, relationship type, last contacted date, how you met. They show off their graph views where person nodes orbit project nodes like little solar systems. It looks genuinely beautiful.
I tried it. Most people who try it, try it seriously. And most people who try it seriously eventually stop.
Not because Obsidian is bad. Obsidian is excellent. It just isn't built for the problem you're actually trying to solve when you want to remember people.
The key insight: Obsidian solves the storage problem beautifully. It fails at the retrieval problem — the moment you actually need it. Finding the right person when they become relevant is a fundamentally different challenge than organising notes about them, and Obsidian's design optimises for the latter.
What Actually Happens When You Build a Contact Database in Obsidian
The beginning feels great. You make a template. You create your first few person notes — name, how you know them, a couple of details you want to remember. You link them to projects and meetings. The graph view looks satisfying.
Then real life starts happening.
You meet thirty people at a conference. You're not going to fill in a template for each of them on the day. You tell yourself you'll do it that evening. You do it for five of them and get tired. The other twenty-five exist only as a pile of LinkedIn requests.
Three months later, you're looking for someone who mentioned they worked in climate tech. You know it was someone you met recently. You can't find them in Obsidian because you never created their note. You search LinkedIn and scroll for twenty minutes. You can't find them there either because you don't remember their name — only that they worked in climate tech and had an interesting take on carbon markets.
This is the moment the system fails. Not when you forgot to fill it in — that's just human. The moment it fails is when you realise that even if you had filled it in, Obsidian has no way to answer the question "who was that climate tech person I met recently?" because it can only search by the fields you explicitly populated.
![IMAGE PLACEHOLDER: IMG-3 — Screenshot of a dense Obsidian graph with dozens of person nodes and relationship links, visually impressive but hard to navigate]
The Storage-Retrieval Gap
This is the core problem, and it's worth being precise about it.
Storage is capturing information about a person. Obsidian is excellent at this. You can build a beautifully structured note with every detail you ever learned about someone. You can tag them, link them, put them in a database view, track your last interaction date.
Retrieval is finding the right person at the right moment. This is what Obsidian struggles with, because retrieval in Obsidian means you already know what you're looking for. You search for a name, a tag, a property value. But the most important moments of retrieval are the ones where you don't know the name — where you only have a vague description, a half-remembered context, a feeling that there's someone in your network who can help with this exact thing.
"Who do I know in climate tech?" is not a search query Obsidian can answer unless you tagged every relevant person with #climate-tech — which you probably didn't, consistently, across hundreds of contacts over years.
One person in the r/ObsidianMD community put it clearly: "The problem wasn't capturing the information, it was actually finding it again months later."
That's exactly it. The tool you chose optimised for the wrong half of the problem.
The Maintenance Burden Is Real Too
There's a second problem that compounds the retrieval failure, and it's the reason most Obsidian contact databases gradually go stale.
Maintaining a person note in Obsidian requires effort every time. After every conversation, you have to open Obsidian, find or create the note, update the last-contacted date, add whatever you learned, maybe update the tags. On a busy week, this doesn't happen. After a few busy weeks in a row, the system is out of date. After a few months, you stop trusting it. After a year, you've quietly abandoned it while still feeling vaguely guilty about the beautiful template you made.
This isn't a discipline failure — it's a design mismatch. The system requires you to do a task (opening Obsidian, filling in fields) that is separate from and additional to your normal flow. Every system that requires this extra step will eventually be deprioritised when life gets busy.
The systems that survive are the ones built into workflows you already have — not workflows you wish you had.
What Obsidian Is Actually For
None of this is a criticism of Obsidian. It's a genuinely extraordinary tool for thinking — for building knowledge, connecting ideas, developing a personal writing practice. For the use cases it was designed for, it's hard to beat.
It's not the right tool for relationship memory, and that's okay. The mistake is using a thinking tool to solve a memory problem.
The difference matters because thinking tools are optimised for depth and connection. Memory tools need to be optimised for low-friction capture and natural-language retrieval. Those are different design constraints, and a tool can't do both well.
![IMAGE PLACEHOLDER: IMG-4 — Side-by-side: Obsidian search requiring exact field values vs. RareFriend WhatsApp interface answering "who do I know in climate tech?"]
What Actually Works
The most durable personal network systems have two properties in common:
Capture lives in a channel you already use. If you have to open a separate app to log a contact, you won't do it consistently. The best capture mechanism is the one already in your hand — a voice note, a message to an AI in WhatsApp, a 20-second recording while you're still at the conference.
Retrieval works the way memory works. You should be able to ask "who was that person who knew someone at Stripe and was building something in payments?" and get an answer — not scroll through a database hoping you tagged them correctly.
RareFriend is designed around exactly these two constraints. You send a voice note to Hops — the AI — in WhatsApp, describing who you just met. It handles the rest. And when you need to find someone, you describe them in plain language: "the climate tech founder I met at the Delhi event last month." Hops searches across everything you've ever shared, not just the fields you filled in.
No templates. No graph view. No maintenance overhead. Just your network, searchable the way your memory actually works.
Frequently Asked Questions
Can you use Obsidian as a personal CRM?
You can — and many people do build impressive contact systems in Obsidian. The limitation shows up at retrieval: when you need to find someone based on a vague description or half-remembered detail, Obsidian can only search fields you explicitly populated. It works well if your network is small and you're disciplined about maintaining it. It breaks down at scale or when life gets busy.
What's a good Obsidian alternative for managing contacts?
For pure contact storage and structured notes, Notion or a simple spreadsheet work well and are easier to maintain than Obsidian's more complex graph system. For something that handles retrieval — finding the right person when they become relevant, based on natural language — you need a tool designed specifically for that, like RareFriend or Dex.
Why do personal CRM systems always get abandoned?
The most common failure mode is maintenance overhead. Any system that requires a separate action outside your normal workflow — opening a new app, filling in fields, updating a log — will get skipped during busy periods. Over time, the system becomes untrustworthy and gets abandoned. The systems that last are built into communication channels people already use daily.
Is Obsidian good for networking?
Obsidian is excellent for capturing detailed notes about people you know well — colleagues, long-term collaborators, mentors. It's less suited to the casual, high-volume contacts from conferences or events, where the friction of creating and maintaining individual notes is too high relative to the depth of the relationship.