How I Build A Personal & Professional CRM In Notion

A Notion-based CRM can be built as a connected system of three “funnels”: contact records, scheduled meetings, and meeting-driven to-dos—then topped with an automated follow-up queue. The payoff is a single workflow where choosing a person leads to scheduling time with them, capturing action items from that meeting, and surfacing who needs attention next.

The setup starts with two contact databases—personal and professional—managed through a shared “contact” structure. Each contact card includes core fields like name and email, plus optional personal details such as gender and date of birth. For personal contacts, the builder adds formula and utility properties: a “birthday month” check using the month of date of birth, a last-name extraction formula (by removing everything before the first space), and an age calculation using date-difference logic. Visual cleanliness is handled with filters and “hide when empty” settings so only relevant properties appear.

Professional contacts add business-specific tracking. A proposal pipeline is represented with a proposal status property and a board-style view that shows where each contact sits (for example, “proposal stage”). The CRM also links contacts to company records via a relation property, then uses rollups to pull organization attributes like city and state into the contact view. This connection lets meeting pages and follow-up views inherit context about where a person’s organization is located and which company they came from.

Scheduling becomes the third funnel. A schedule database (shown as a board view with proposal-status-like sorting) is linked back to contacts through templates. A “contact template” is created so that when a meeting is scheduled for a specific person, the meeting record is automatically associated with that contact. Meeting pages then use rollups to pull meeting context—such as the organization and whether the contact is personal or professional—directly onto the meeting record.

To turn meetings into execution, the builder adds “meeting notes” templates inside the schedule system. A self-referential linked database creates a to-do list that lives under each meeting. Filters ensure only the right items appear: meeting notes are typed as “meeting,” while child tasks are typed as “to do,” and each to-do is connected back to its parent meeting via a parent-child relation. Tasks move through a pipeline (not started → in progress → completed → archived), and archiving removes them from the active pipeline while keeping an archive view.

Finally, a follow-up queue automates prioritization. A rollup called “last contacted” looks back at the most recent meeting date associated with each contact. The follow-up list is filtered to show only contacts whose last contacted date is before today, then sorted so the longest-overdue person rises to the top. When a new meeting is scheduled in the future, that contact drops out of the follow-up queue automatically—because the “last contacted” rollup updates.

The result is a “skeletal CRM” that’s customizable: proposal stages can be removed if irrelevant, birthdays can be enabled or ignored, and the same scheduling and follow-up logic works for both personal hangs and professional meetings.