Choosing client portal software without regretting it in six months.
Most comparisons list features. The decisions that actually bite are narrower than that: how data is separated per client, what can be hidden, and whether the portal becomes a second place you have to keep updated.
- Per-client data separation and field-level hiding are the two features that matter most.
- A portal that needs separate updating will drift from reality within weeks.
- If your delivery already runs in Notion, a Notion-based portal avoids a migration entirely.
- Shared passwords are not access control — you cannot revoke one person.
- View filters are a display convenience, not a permission boundary.
- Ask what happens to your data when you leave, before you start.
What the software has to do
The non-negotiable. Client A must never see Client B's records, and it must be enforced by the system rather than by remembering to set a filter.
You will always have data on the same record that clients should not see — cost, margin, internal status. Whole-page permissions are not enough.
Per-person accounts, not a shared password. When an engagement ends, access ends without disrupting everyone else.
A portal on someone else's domain with someone else's logo undercuts the professionalism you are buying it for.
If the portal is a second place to update things, it will drift. It should read from wherever you already work.
Three ways people solve it
| Approach | Best for | Upside | Trade-off |
|---|---|---|---|
| All-in-one suites | Firms that want CRM, billing, and portal in one system | Everything integrated; no assembly required | You migrate your process into their model, and pay per seat for parts you may not use |
| Custom build | Teams with engineering capacity and unusual requirements | Exactly what you want | Months of work, then ongoing maintenance and security ownership forever |
| Notion-based portal | Teams already running delivery in Notion | Keeps your existing process; no migration; fast to launch | Requires your data to live in Notion databases with sane relations |
We build the third option, so treat this page accordingly — but the trade-offs above are real, and an all-in-one suite is genuinely the better answer if you want billing and CRM in the same system.
Six questions for any demo
- 1.Can it show two clients different rows from the same table without duplicating the table?
- 2.Can it hide a single property from clients while your team still sees it?
- 3.Can you revoke one person's access without changing anyone else's?
- 4.Does it run on your domain with your logo?
- 5.When you update the underlying record, does the client view change without a publish step?
- 6.What happens to your data if you stop paying?
Already running delivery in Notion?
Then the migration is the part you can skip. Connect what you have and put a login in front of it.
2-week free trial · No credit card · Notion-native