How to build a personal CRM with Claude

Set up a personal CRM for me in databasedmcp, in one go.

1. Create a database called crm, described as "Personal CRM: people, conversations and follow-ups".
2. Create three tables:
   - people: id, name (required), company, role, email, how_we_met, created_at (defaults to now).
   - conversations: id, person_id (references people), happened_on (date, defaults to today), channel (call, meeting, email or chat), summary (required, two or three sentences in my words).
   - followups: id, person_id (references people), what (required), due (date, required), done_at (NULL until I say it's done).
3. Write the database a guide that says what each table is for, to look people up by name before adding them so there are no duplicates, and the queries for "who do I owe something this week" and "who haven't I talked to in 60 days".

From then on: when I mention a call, meeting or email, log a conversation with the person (adding them if they're new). When I promise something, add a follow-up with a due date. When I say it's done, set done_at. Show me the tables when you're finished.

CREATE TABLE people (
  id INTEGER PRIMARY KEY,
  name TEXT NOT NULL,
  company TEXT,
  role TEXT,
  email TEXT,
  how_we_met TEXT,
  created_at TEXT NOT NULL DEFAULT CURRENT_TIMESTAMP
);

CREATE TABLE conversations (
  id INTEGER PRIMARY KEY,
  person_id INTEGER NOT NULL REFERENCES people(id),
  happened_on TEXT NOT NULL DEFAULT (date('now')),
  channel TEXT CHECK (channel IN ('call', 'meeting', 'email', 'chat')),
  summary TEXT NOT NULL
);

CREATE TABLE followups (
  id INTEGER PRIMARY KEY,
  person_id INTEGER NOT NULL REFERENCES people(id),
  what TEXT NOT NULL,
  due TEXT NOT NULL,
  done_at TEXT
);

# crm: people, conversations, follow-ups

- **people**: one row per person. Look them up by name (LIKE) before adding, to avoid duplicates.
- **conversations**: one row per call, meeting or email thread I tell you about. `summary` is two or three sentences in my words.
- **followups**: what I promised and when. `done_at` stays NULL until I say it's done.

Due this week: `SELECT f.id, p.name, f.what, f.due FROM followups f JOIN people p ON p.id = f.person_id WHERE f.done_at IS NULL AND f.due <= date('now', '+7 days') ORDER BY f.due`

Gone quiet (no conversation in 60 days): `SELECT p.name, p.company, max(c.happened_on) AS last FROM people p LEFT JOIN conversations c ON c.person_id = p.id GROUP BY p.id HAVING last IS NULL OR last < date('now', '-60 days') ORDER BY last`

INSERT INTO people (name, company, role, how_we_met) VALUES (?, ?, ?, ?) RETURNING id
-- params: ["Maria Lindqvist","Nordwave","Head of operations","Logistics meetup, Helsinki"]

INSERT INTO conversations (person_id, channel, summary) VALUES (?, ?, ?)
-- params: [1,"call","Nordwave moves route planning off spreadsheets in Q1. Maria wants a proposal."]

INSERT INTO followups (person_id, what, due) VALUES (?, ?, date('now', 'weekday 5'))
-- params: [1,"Send Nordwave the route-planning proposal"]

UPDATE followups SET done_at = datetime('now') WHERE person_id = ? AND done_at IS NULL AND what LIKE ?
-- params: [1,"%proposal%"]

SELECT f.id, p.name, f.what, f.due FROM followups f JOIN people p ON p.id = f.person_id WHERE f.done_at IS NULL AND f.due <= date('now', '+7 days') ORDER BY f.due

SELECT p.name, p.company, max(c.happened_on) AS last FROM people p LEFT JOIN conversations c ON c.person_id = p.id GROUP BY p.id HAVING last IS NULL OR last < date('now', '-60 days') ORDER BY last

SELECT c.happened_on, c.channel, c.summary FROM conversations c JOIN people p ON p.id = c.person_id WHERE p.name LIKE ? ORDER BY c.happened_on DESC LIMIT 3
-- params: ["%Maria%"]