Start with relationship roles, not a giant address book
Importing every contact creates the feeling of progress but rarely improves a founder's week. Begin with the 30 to 100 people whose context can change a current company priority. Include active customers, credible prospects, investors, operators, domain experts, recruiting prospects, and people who regularly make relevant introductions.
Give each person one primary relationship role and a small number of tags tied to a real decision. Tags such as investor, design partner, fintech, Singapore, or hiring are useful because they answer a future question. A tag like important is too vague unless you define what it changes.
- One primary role
- Two or three decision-useful tags
- The last meaningful interaction
- A next step only when one genuinely exists
Capture the sentence you will need six months from now
The highest-value note is usually not a transcript. It is a compact memory: why this person matters, what they care about now, what you promised, and what would make a future message relevant. Write notes so your future self can act without reopening the entire meeting history.
A reliable pattern is: context, priority, commitment, next window. For example: Met at an enterprise software dinner. Expanding into Korea this year. I promised an introduction to a local compliance operator. Revisit after their Q3 planning cycle. This is specific enough to guide a useful follow-up without storing unnecessary personal detail.
Build three review queues
A founder does not need to review the entire network every week. Use three small queues: conversations with a promised action, relationships connected to the current company objective, and valuable contacts becoming stale. Review commitments twice a week, the current-priority group weekly, and stale relationships monthly.
The key is to make every reminder earn its place. A reminder should explain why that date matters. Replace follow up in two weeks with ask whether the security review is complete after July 24. The second version gives you a reason and a message angle.
Use an agent for retrieval and preparation, not relationship judgment
A personal CRM agent is most useful when it reduces the cost of finding context. Ask for contacts connected to a market, a summary before a meeting, or a list of commitments that need attention. Then review the result. The founder still decides whether a message is appropriate, timely, and worth sending.
This boundary matters. Automated volume can damage a relationship faster than forgotten data can help it. Use the agent to surface context and draft a plan; keep introductions, sensitive notes, and outbound communication under human control.
Measure usefulness, not database size
Contact count is a weak success metric. Better signals are the percentage of important meetings prepared with context, promised actions completed on time, relevant introductions made, and dormant relationships revived for a genuine reason. Review these outcomes monthly and delete fields or tags that never change a decision.
Founder CRM weekly review
- Which promises are due in the next seven days?
- Who is relevant to the company's single most important objective?
- Which upcoming meetings need a brief?
- Which three relationships have a genuine reason for a check-in?
- What context or tag should be corrected while it is fresh?
Common questions
Should a founder personal CRM replace the company sales CRM?
Usually no. A sales CRM owns shared pipeline stages and forecasting. A founder personal CRM holds individual relationship context across customers, investors, partners, talent, and advisors.
How many contacts should I add first?
Start with the smallest group connected to current priorities—often 30 to 100 people. Expand only when a review habit is working.
What information should not go into a personal CRM?
Avoid unnecessary sensitive personal information, speculation, and notes you would not be comfortable correcting or explaining. Store only context that supports a legitimate relationship purpose.