Notion or Trello as a client portal: what works and what breaks
Two excellent tools for you, and five specific ways they break the moment a client looks at them. Including the case where you really should stay put.
Plenty of very organised freelancers run their jobs out of Notion or Trello, and it works. This is not a disorganised person's method, it is usually the opposite.
The difficulty does not show up while you are using it. It shows up the day you share the page with the client.
What these two do very well
Notion is probably the best place for your own method. Your templates, your project notes, your list of services, what you have learned about each client, your reusable copy. Nothing below says move any of that out, and a tool that asked you to would be asking something unreasonable.
Trello is the most legible way to see your own pipeline. Five columns, one card per job, one glance and you know. No dashboard does better for that exact purpose.
And a Notion page shared with a client is infinitely better than nothing at all. The ceiling is elsewhere.
One: permissions are per page, and a client is not a page
This is the most serious point, and it is not theoretical.
You have two ways to share and both cost something. A narrow page, made for this client, holding only what concerns them: it is clean, and you maintain it by hand, copying from wherever the work actually happens. A wide page, inside your own tree: it stays current for free, and a share set one level too high shows the client the parent page, so your internal notes, so sometimes another client.
The second case raises no alarm. Nothing turns red, nothing fails. You only find out if somebody tells you, and a client who has seen something they should not have rarely does.
Two: nothing is frozen, so nothing is evidence
A Notion database can take answers. But the client is not filling in a form: they are editing a database.
Which means they can change what they said last week, delete a row by accident, write in the wrong column, or break the structure by pasting a table. And when you are discussing a colour in three weeks, there is no frozen version to reread: there is the current state of the page, which is the only state it has ever had.
A brief that can be rewritten afterwards is not a brief. It is a shared note.
Three: it is maintained by hand, so it will lie
Every change of state is a gesture: you move a card, tick a box, update a status.
That gesture helps nobody at the moment it needs doing. So it is the first one skipped when the day is busy, which is to say always. Three weeks later the "waiting on client" column holds two cards, one of which was settled since, and you go back to the messages to check.
Which is exactly the subject of where every job stands, without a spreadsheet: tracking that has to be kept up to date is not tracking, it is a second job.
Four: Trello has no concept of a client
A Trello card is made for your team. To show one to somebody outside it, there are two routes and both are wrong for this purpose.
A public board is on the open web. Readable by anybody with the address, complete with your client's name, their budget if you noted it, and your internal comments.
A guest has to create an account. And creating an account is where half of all clients drop out, especially on a small job and especially for somebody not comfortable with tools.
Five: payment and delivery are elsewhere
Neither of them takes a deposit, and neither can hold a file back until it clears. That is two more tools and two more manual steps per job. On the order to ask for money in: deposit, balance, delivery.
And there is a sixth point, minor but not nothing: the page looks like your tool, not like your studio. A client on a Notion page sees Notion. That does not matter on a three-hundred-pound job; it matters rather more while they are deciding whether to trust you.
The table, with no adjectives
| Notion or Trello | One page per job | |
|---|---|---|
| Your own method and notes | Excellent | Does not do it |
| Seeing your pipeline at a glance | Excellent (Trello) | Adequate |
| Several people writing in a document | Excellent (Notion) | Does not do it |
| What the client answered, frozen | No, still editable | Yes, by construction |
| What the client sees | Whatever you remembered to wall off | Their job, and nothing else |
| Account needed by the client | Yes (guest), or a public page | None |
| The state updates | By hand | Because the job moved |
| Deposit and gated delivery | Elsewhere | On the same page |
The first three rows are not politeness. They are three things you should not change tools over.
Stay with Notion or Trello if
The client never looks at your board. Plenty of excellent freelancers work this way: the board is for them, the client gets emails. It is coherent and nothing breaks.
You have three regular clients who know your method and for whom the page is no trouble at all.
What you actually need is to document your method, not to track jobs. That is Notion's trade and there is nothing better.
Change on the day
You copy by hand, from your messages onto the client's page, something the client could have read themselves.
You hesitate before sharing a page, because you are no longer certain what sits above it.
A client changed or deleted something they had written, and you no longer know what was said.
You ask a client to create an account in order to follow a six-hundred-pound job.
Frequently asked questions
Can you use Notion as a client portal?
Yes, and many people do it well. The limit is the permission model: a shared page is either narrow and maintained by hand, or wide and current for free, and in the second case a share set one level too high exposes the parent page with no alarm anywhere.
Is Trello any good for tracking client projects?
For your own pipeline it is excellent. For showing it to a client there are only two routes: a public board on the open web, or a guest who has to create an account. Both are wrong for a client.
Why is a brief in a Notion database a problem?
Because the client edits a database rather than submitting a form. What they answered last week stays editable, so there is no frozen version to reread when a conversation goes sideways.
Should you drop Notion if you change tracking tools?
No, and it is rarely a good idea. Your method, your templates and your notes are fine where they are. What benefits from moving is the part the client looks at.
Does a client need an account to follow their job?
Access yes, an account no. That is where half of all clients drop out, especially on a small job, and it is the main reason a shared board ends up being useful only to you.
Kalepio asks these questions for you
You send one link, your client answers once, and you start with everything you need.
Read next
September 4, 2026
Keeping a client in the loop during a project
The update rhythm that stops a client from asking where things stand, without turning your day into emails.
5 minute read
September 4, 2026
Onboarding a new client after they say yes
The first week is where jobs drift, not the last. The four things to send before work starts, the one to refuse, and how to set the tone of the whole job in the first round.
9 minute read
September 4, 2026
A client comes back six months later and wants their files again
The most avoidable forty minutes in this trade, the question that costs more than the missing file, and the three things to decide before it happens.
7 minute read