Using Notion to track clients: the database that replaces a light CRM
A Notion database will run a client pipeline of twenty to thirty relationships competently, and it will do something no CRM does: put the client record next to the document you are writing for them. The failure mode is not capability, it is the absence of a forcing function — nothing in Notion tells you a client has gone quiet. This design adds one.
The three databases
- Clients — one row per organisation. Properties: Name (title), Status (select: Prospect / Active / Paused / Past), Owner (person), Website (URL), Source (select), Notes (text).
- Contacts — one row per human. Properties: Name, Client (relation → Clients), Role, Email, Last contact (date).
- Engagements — one row per piece of work. Properties: Name, Client (relation → Clients), Status, Value (number), Start (date), Next action (date), Next action detail (text).
Three databases, not one. The temptation is to put everything in a single table; the cost is that a client with three engagements becomes three rows and the relationship disappears into duplicates.
The four views that do the work
- Pipeline — Engagements grouped by Status, filtered to Prospect and Active. This is your board.
- Going quiet — Engagements filtered to Next action is before today. This is the forcing function, and it is the reason to build the database at all. Open it every Monday.
- By client — Engagements grouped by Client relation. What you open before a call.
- This month — Engagements filtered to Start within the current month, with Value summed. Answers "what is live" without arithmetic.
The one automation worth building
Notion's database automations can set a property or create a page on a trigger. The single most valuable one: when Status changes to "Proposal sent," set Next action to seven days from now. That converts a stage change into a scheduled follow-up without anyone remembering to type a date.
Free-plan note: Notion's free plan includes basic buttons but database automations are a paid capability on Plus and above. If you are on free, replace the automation with a template button that pre-fills the date.
Holding the client's work next to the client
This is the advantage that CRMs cannot match. Create a page per client inside the Clients database and treat it as the home for: the brief, meeting notes as sub-pages, links to deliverables, and a short running log. Because the page is a row in the database, it appears in your pipeline view as well as in your document tree — one object, two contexts.
Keep the log short and dated. Three lines per interaction is enough: what happened, what was decided, what is next. A log that takes five minutes is a log you stop writing.
Free-plan limits you will meet
| Limit | Free plan | Practical effect |
|---|---|---|
| File upload size | 5 MB per file | No video, no large decks. Link to Drive instead. |
| Page history | 7 days | An overwritten brief is unrecoverable after a week. The only permanent failure in this design. |
| Members | Limited for 2+ | A solo operator is fine; two people is where the free plan starts to strain. |
| Guests | 10 | Enough for a handful of clients, not for a portal. |
Where this stops working
- Around 30–40 active engagements. Sorting and filtering a database is slower than reading a board, and the views start needing maintenance.
- When two people need to work the same pipeline daily. Notion has no activity ownership model. Two people editing is fine; two people owning stages is not.
- When you need revenue reporting. Summing a property is not a forecast. If a manager or a bank needs a number, you have outgrown this design.
- When the follow-up must be automatic. The "going quiet" view only works if someone opens it. A CRM that emails you is a different category of tool.
At that point, the honest options are a real CRM — see the CRM a solo consultant actually needs — or keeping Notion for documents and moving the pipeline. Both are fine; what fails is a half-migrated state where neither is authoritative.
What this guide is, and is not
This is a design method, not a review. Notion's plan limits (5 MB per file, 7-day history, 10 guests, unlimited blocks for individuals) and prices (Plus $10, Business $20 per seat per month, annual billing as displayed) were verified from its pricing page on October 23, 2026 and are re-checked quarterly. The engagement counts at which the design strains are estimates from how these databases behave at volume, not measurements — our hands-on testing cycle will replace them with observed numbers per our How We Test process.