Most Notion “CRMs” are built for coaches and consultants: endless contact properties, vanity dashboards, and zero mention of Figma. Freelance UI/UX work breaks those templates. Your “deal” is a redesign scope. Your “account” has a decision owner who comments in Figma at midnight. Your next action is not “send nurture sequence” — it is “unblock copy” or “book critique round 2.”
This article walks through a client CRM shape that fits design freelancers, the exact properties worth tracking, views you will actually open, and how the CRM connects to pipeline and projects without turning Notion into a second full-time job.
Why a designer CRM is different
A general CRM optimizes for conversations. A designer CRM must optimize for engagements:
- One company may buy an audit, then a UI redesign, then a retainer — those are separate commercial objects.
- Delivery risk shows up as missing assets, unclear decision rights, and critique chaos — not just “no reply.”
- The artifacts that matter are URLs: Figma, staging, brand drive, prototype — not a notes field that says “seemed nice.”
If your CRM cannot answer who needs a touch this week, which brands are ideal vs avoid, and what Figma file is canonical, it is decoration.
The minimum viable client record
Keep one database: Clients (company/brand grain). People can live as properties plus meeting notes. A separate Contacts database is optional later; for solo freelancers it often slows you down.
Properties that earn their column
| Property | Why it matters for UI/UX freelancers |
|---|---|
| Status — Lead Only / Active / On Hold / Alumni | Separates warm names from paying delivery |
| Primary Contact + Role | Founder vs PM vs Eng Lead changes how you run critique |
| Industry | Pattern recognition for reuse (SaaS dashboards ≠ clinic booking) |
| Source | Referral vs cold — sets how hard you chase |
| Fit — Ideal / OK / Stretch / Avoid | Protects you from repeating bad-fit projects |
| Next Touch | The only field that creates a weekly habit |
| Figma / Drive URL | Stops Slack archaeology |
| Lifetime Value | Optional; useful when pricing retainers later |
| Notes | Two lines max — long narrative belongs in Meeting Notes |
Skip: lead score formulas, NPS, “personality type,” and twenty social links.
Views you will open every week
1. Needs touch
Filter: Next Touch on or before today, Status is not Alumni.
Sort by Next Touch ascending.
This replaces the “I should message someone” guilt loop. After every call, set Next Touch before you close the laptop.
2. Active
Status = Active. Show Primary Contact, Next Touch, Fit, Figma link.
Use this when you are scheduling critiques or checking who still lacks a decision owner.
3. By industry (board)
Group by Industry. Helpful when a new inbound arrives and you want prior art from similar products — without digging through Figma recents.
4. Ideal clients (gallery or table)
Fit = Ideal. This is your referral ask list and case study priority list — not a shrine.
Relations: CRM is not the whole OS
A client row should relate to:
- Pipeline / Deals — commercial offers before kickoff
- Projects — delivery after won
- Meeting Notes — discovery, critique, stakeholder
- Assets — logos, contracts, font licenses
- Invoices checklist — readiness and unpaid status
On the Client page template, embed linked views: open projects, open deals, recent meetings. That is the difference between a spreadsheet and a client operating system.
Without relations, Notion becomes five orphan tables and you retype the client name forever.
How to run the CRM in 20 minutes a week
Monday (10 min)
Open Needs touch. For each row: send the message, book the call, or push the date with a reason in Notes. No row left with a past date and no action.
After every meeting (3 min)
Create a Meeting Notes row, link Client (and Project if active), write Decisions + Actions, set Next Touch.
When a deal is won (5 min)
Pipeline → Won. Create Project. Confirm Figma URL on both Client and Project. Deposit invoice row → Ready to send checklist.
Month end (10 min)
Mark ghosted leads Lost with reason. Move finished brands to Alumni if appropriate. Skim Fit ratings honestly — Stretch that burned you becomes Avoid.
Fit scoring without drama
Ideal: clear decision owner, realistic scope for fee, respectful feedback, assets available, problem is UI/UX-shaped.
OK: some ambiguity but payable and contained.
Stretch: political stakeholders, undefined success, or “make it pop” as the brief — only if rate and buffer compensate.
Avoid: unlimited revisions culture, chronic late payment signals, or scope that is secretly brand strategy + growth + eng.
Write the definition once in your Clientrail home page. Update Fit when reality disagrees with the sales call.
Importing what you already have
CSV import works for rows, not relations. Export names, emails, status. Map Select options carefully (exact strings). Then manually link active projects. Do not boil the ocean: import Active + recent Alumni only.
If your “CRM” is currently a Notes app, create ten clients by hand. Speed of use beats perfect history.
Common failure modes
- Tracking every LinkedIn chat as a Client — use Lead Only sparingly; archive ruthlessly.
- Writing novels in Notes — decisions go to Meeting Notes with a date.
- No Next Touch habit — the CRM dies in two weeks.
- Duplicating Pipeline fields on Client — keep money stages on Deals.
- Building dashboards before seed data — add three real clients first.
A practical schema starter
If you want the full property lists, views, and rebuild order for Clients + Pipeline + Projects + Meetings + Assets + Invoices, use a documented pack like Clientrail (Notion structure aimed at freelance UI/UX, plus prompts and proposal/SOW templates). Rebuild time is under an hour; a 15-minute path gets Clients + Pipeline + Projects running first.
Whether you buy a pack or DIY from this article, the standard is the same: open it weekly, link it to delivery, and keep Figma one click away.
Checklist: standing up your designer CRM today
- [ ] Create Clients database with Status, Fit, Next Touch, Figma URL
- [ ] Add Needs touch + Active views
- [ ] Relate to Pipeline and Projects (even if those DBs are thin)
- [ ] Seed 5–10 real brands
- [ ] Set Next Touch on every Active client before tomorrow morning
That is a CRM. Everything else is optional chrome.
Want the full Client OS?
Clientrail packs Notion structure, 50 prompts, and deal templates for freelance UI/UX — no fake testimonials, no income claims.