When should you use it?
- You meet many people and forget details
- Separate CRM apps never stay updated
- You already keep meeting notes digitally
Not for: Team CRMs with permissions and pipelines; Data you cannot store in a hosted database
What do you need, and what do you get?
You need
- A Supabase project
- An MCP server offering four basic read and write tools
- Workflow descriptions in Markdown
You get
- Enriched contact profiles
- Ranked answers to natural-language searches
- Suggestions for people missing from the CRM
How does it work, step by step?
- Create a simple schemaPeople, roles, companies, skills, notes and flags.
- Expose atomic toolsGive the assistant only basic read and write operations through MCP.
- Describe workflows in proseWrite Markdown files for adding, enriching and searching contacts.
- Add by linkPaste a profile URL and let it enrich and attach any meeting notes.
- Watch meetingsAfter notes sync, have it flag attendees not yet in the CRM.
The prompt
Our own prompt, inspired by Jax and written to work in Claude. Values in lime are placeholders.
Add [name] to my CRM from this profile: [URL]. Enrich role, company, history and skills, then search my meeting notes for mentions and attach them. Let me confirm the new entry first. You may read, add and edit rows; removing one needs my yes. For searches, return a ranked list with a short reason for every match.
Inspired by Jax: Uncovered Bookmarks #23: Building a Personal CRM. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A delete tool is powerful; require confirmation before removing records.
- Enrichment services can be wrong; keep the source of each field.
Our take
Jax's personal CRM is an elegant example of keeping the tools tiny and letting language define the features. Four atomic database operations through MCP, plus Markdown workflow files, are enough for Claude to become the interface: add someone from a LinkedIn link, enrich the record, attach Granola meeting notes and answer searches like design people thinking of founding. The habit that makes it survive is automatic capture from meeting notes, which removes the reason most personal CRMs die, namely that nobody updates them. Be careful with privacy. You are storing notes about other people, so keep the database private, avoid sensitive personal details you do not need, and check whether anyone you meet would be uncomfortable with this kind of record. Add a confirm step before any delete, and a soft-delete recycle bin for accidents. Export a backup monthly. When enrichment pulls public data, skim it for accuracy before trusting it in a search ranking.
Where the time goes back: Updating the system costs nothing, so it actually stays current, and searches need no filters.
FAQ
Is there any front end?
What is agent-native about it?
Source and credit
Inspired by Jax. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Uncovered Bookmarks #23: Building a Personal CRM
- Creator
- Jax
- Published on
- jax.substack.com (Substack)
- Original date
- Mar 12, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.