Short answer: If your portal is mainly for showing clients where their work stands, approvals and hours, use a CRM with a portal built in: the portal shows the same records your team updates, so nothing is copied or synced. If the portal is mainly for files, invoices, payments and contracts, separate client portal software does more. In Teamo, every client can get a portal built from their records, on every plan, with no client logins and no fee per client.
Disclosure: I co-founded Teamo, and Opsters, the agency Teamo was built out of.
What's the difference?
Both give each client a page of their own. What changes is where the data on that page comes from.
- A portal built into your CRM reads the records your team already works in: the client's projects, tasks, statuses and hours. When someone moves a task to Done, the client sees it.
- Separate portal software has its own projects, files and messages. Either your team works in it as well as in the CRM, or someone keeps the two in step, by hand or with a tool like Zapier or Make.
When is a portal built into the CRM the better choice?
- The client mostly asks "where are we?" A built-in portal answers it from the statuses your team sets anyway.
- Approvals happen on the work. The client approves a task on the same record your team works from, so nobody passes the answer on.
- Requests should land as work. A form on the portal creates a record in your own module, ready to assign.
- You don't want a second tool. One subscription, one place to set up, and no sync to break.
When is separate portal software the better choice?
- Clients pay invoices in the portal, or sign contracts and proposals there.
- The portal is mainly for files: proofing designs, approving documents, keeping versions.
- You need your own domain or no vendor branding at all.
- Clients should sign in with their own account.
For tools built for that, see best client portal software for small agencies, which compares Assembly, SuiteDash, ManyRequests, HoneyBook, Dubsado and others.
How does a client portal work in Teamo?
Build the page from widgets
A portal is a page of widgets, each showing data from your modules: a table of the client's open tasks, a KPI with hours logged this month, a chart of work done, or a request form. Each widget is filtered to that client, so every client sees only their own records, and only the columns you chose.
Share it by a private link
Each client opens their portal from a private link. They don't create an account, they don't take a seat, and you don't pay per client.
The link is a long random address that can't be guessed, but like a shared Google Docs link, anyone who has it can open the portal. So put on a portal only what that client may see: you choose its widgets, the filter on each one and the columns it shows. If a link gets forwarded or you stop working with a client, pause the portal or replace its link, and the old address stops working. For data that needs a sign-in, invite the client as a guest instead: guests are free, 1, 2 or 4 per paid seat on Starter, Pro and Max.
Let clients approve and comment
In a table widget, you can make a status column editable, so the client changes it to Approved or Changes needed themselves. Their comments land in the record's comments, and your team's replies show up on the portal.
Take requests through a form
A form on the portal turns each answer into a new record in the module you choose, for example a request in your Tasks module, or a new item under the client's record, with any files the client uploads. An automation can then assign it and tell the right person.
Put your brand on it
Your logo and colors are on every portal, on every plan. Portals stay on Teamo's address; there is no custom domain, and no payments in the portal.
For a step-by-step guide to what a portal should show, see how to give clients a portal where they see project status.
What does Teamo cost with portals?
Portals are on every plan, and clients never take a seat. Starter is from €10 / $12 a seat a month billed yearly, for a solo owner or a very small team. Pro is €18 / $20 a seat a month billed yearly (€22 / $25 monthly), with a 3-seat minimum. The trial runs 10 days on Max, with no card. See pricing.
Which CRMs have a client portal built in?
From each vendor's own pages on 17 November 2026:
| CRM | Portal from | How clients get in | Pay per client? | Your own domain |
|---|---|---|---|---|
| Teamo | Every plan; Pro €18 / $20 a seat | Private link, no account | No | No, Teamo's address |
| HubSpot Service Hub | Professional, $90 a seat plus $1,500 onboarding | Login | We couldn't confirm | A connected domain is required |
| Zoho CRM | Professional and up | Login, invited by email | Free up to 1,000 portal users | We couldn't confirm |
| SuiteDash | $15 a month flat on Start ($180 a year) | Login or magic link | No, unlimited | We couldn't confirm which plan |
| Bonsai | $19 a seat on Essentials | Private link | No | Not available yet |
Prices are billed yearly, before tax. Zoho shows prices by region. "We couldn't confirm" means the vendor's own pages didn't say, not that the tool lacks it.
HubSpot's and Zoho's portals are mostly for support tickets and records, behind a login. SuiteDash and Bonsai lean toward files, invoices and contracts. Teamo's portal shows the live work itself, from the client record where your deals, projects, hours and messages already are.
FAQ
Do I need separate portal software if my CRM has a portal? Not if the portal is for status, approvals, hours and requests: a portal built into the CRM shows them live. You need separate software when clients should pay invoices, sign contracts or approve files in the portal, or when it must sit on your own domain.
Do clients need an account to use a portal? Not in Teamo: each client opens their portal from a private link. HubSpot and Zoho ask clients to log in, and SuiteDash offers a login or a magic link.
Do I pay for each client on the portal? Not in Teamo, SuiteDash or Bonsai. Zoho charges past 1,000 portal users.
Is a portal shared by a link secure? The link is long and random, so it can't be guessed, but anyone who has it can open the portal. Show only what that client may see, pause the portal or replace its link if it's forwarded, and invite the client as a guest when they should sign in.
Can clients approve work in the portal? In Teamo, yes: make a status column editable in a table widget, and the client changes it themselves, for example to Approved. Their comments land on the record.