Topics
Email knows that you wrote to someone. It does not know who they are. The gap is the whole reason a personal CRM exists.

Search finds the message. It does not find the person. Once you notice the difference, the inbox stops feeling like a system and starts feeling like a haystack you keep dropping needles into.
Email is great at exactly three things: threads (conversations grouped by reply chain), timestamps (when each message was sent), and search (substring across the corpus). Those primitives carry an enormous amount of work - they're why the inbox feels load-bearing in the first place. The trap is mistaking them for what a relationship system actually needs.
Identity. Email tracks addresses, not people. "sarah@oldcompany.com" and "sarah.k@gmail.com" and "sarah-k@newcompany.io" are three rows for the same Sarah; the inbox doesn't know that. Worse, when she changes jobs you lose the thread entirely. State. Email knows you wrote to Sarah; it doesn't know what's currently going on with Sarah - the wedding, the move, the recovery. Cadence. Email knows when you last replied; it doesn't know when you last should have reached out. The reply timestamp is reactive; cadence is proactive. The whole gap between "I have years of email with this person" and "I haven't talked to them in eighteen months" lives here.
When you start, the inbox really is enough. With under fifty active relationships, the messages you sent and received cover ninety percent of the texture. You can recover "what did Sarah and I last talk about" by typing her name. The illusion holds because the time-cost of the search is low and the data is fresh. It breaks somewhere between fifty and a hundred and fifty active people, and once it breaks the cost is invisible: you don't notice the relationships you stopped maintaining; you only notice when you bump into Sarah at a wedding and she's been engaged for eight months.
The 5-minute test
Open your inbox. Search for someone you haven't talked to in over a year. Can you reconstruct in under thirty seconds: their current job, their current city, what's going on in their life right now? If yes, the inbox is enough for you. If no, the gap you just felt is what a personal CRM closes.
Three costs accumulate quietly. Address rot: every job change halves your historic thread on a person; over a decade most weak ties end up split across three or four addresses with no through-line. Search ambiguity: "Anna" returns 4,000 messages from six different Annas; the search becomes useless at scale. No proactive surface: the inbox shows you what just landed, never what's overdue, so the people who don't email back drift out of your attention even when you'd want to know what's going on with them. The three compound. Eight years in, your inbox feels heavier than it is useful.
You don't need a heavy CRM to fix this. Contact Book sits as a thin layer next to your inbox: one row per person (with all their email addresses + name aliases collapsing onto that row), a one-line conversation log per touch, life events with reminders, a cadence that surfaces overdues. The inbox keeps doing what it's good at - threading, search, attachments - while the personal CRM holds the parts the inbox can't: identity, state, cadence. You're not migrating, you're stacking.
FAQ
Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.
Read next
Personal CRM vs sales CRM: a clarification
Why a HubSpot doesn't work for friendships and a Personal CRM doesn't work for deal flow.
Read
What is a personal CRM, really?
Definition + the test that tells you if you need one.
Read
Contact Book vs Google Contacts: which one keeps relationships warm?
A directory vs a relationship log: where each one shines and where they don't.
Read