By · Founder, Stacktree · Last updated
buyer's guide

Client portal software: four kinds, and which one fits.

This category is sold as one thing and is really four. All-in-one suites, practice-management tools with a portal inside, no-code builders, and delivery-first links. What each is genuinely for, where each falls down, and the one question that decides it.

Send a client deliverable free

What is client portal software?

Client portal software gives each client one private, branded place to find everything to do with their engagement, usually behind an account you create for them. It comes in four kinds: all-in-one suites that bundle file exchange, messaging, e-signatures and invoicing; vertical practice-management tools where the portal is one module inside software built for accountants, therapists or law firms; no-code builders that assemble a portal on data you already keep; and delivery-first links, which drop the account entirely and put the gate on the work instead. Which one fits comes down to a single question: does your client have to put things in, or only take things out?

What the category is actually selling

Every product here makes the same promise in slightly different words. Everything in one place. A single source of truth for the engagement. One link, always up to date. An extension of your agency. Underneath the promise the products differ mostly in what they bundle around it, and the bundle is what you are really choosing between.

It is worth knowing who else is searching alongside you. The head term "client portal" is enormous, and most of it is navigational: people typing it are logging in to their therapist, their accountant or their lawyer, not shopping for software. The buying happens on the narrower phrases, and the buyer is usually a services firm of three to thirty people deciding how to hand work over. If you are that buyer, the four categories below are your actual shortlist.

The four kinds of client portal software

1. All-in-one suites

SuiteDash, Copilot, Moxo, Clinked, Zendo, OneSuite, Taskip. These sell the whole engagement in one place: two-way file exchange, messaging, tasks and approvals, e-signatures, invoicing and payments, often a CRM and a helpdesk too, all behind a branded login you invite the client into. Pricing models differ sharply: some sell flat tiers with unlimited users, others charge per internal seat or cap how many clients a tier admits.

They are the right purchase when the engagement genuinely is two-way traffic. The cost of the choice is that you are asking a client to adopt software, and every part of the value sits behind that step.

2. Vertical practice-management tools

SimplePractice for therapy practices, TaxDome and Canopy for accounting firms, MyCase for law firms, SmartVault for document exchange. Here the portal is one module inside software built for a profession, so it already knows what an intake form, an engagement letter or a trust ledger is. This is also where the navigational search volume comes from: these products have very large numbers of end clients logging in every month.

If you work in one of those professions, the vertical tool usually beats a general suite, because the portal understands your workflow and you are paying for the rest of the product anyway. If you do not, most of these are closed to you, because the portal comes bundled with the practice software rather than sold on its own. SmartVault is the exception, being a standalone document manager and portal you can buy without a practice suite.

3. No-code portal builders

Softr, Notion, and interfaces built directly on Airtable or Google Sheets. You assemble the portal you want on top of data you already keep, which is appealing when nothing off the shelf matches your shape. Softr publishes its pricing by app user, with separate allowances for team app users and client app users on its paid plans, so the cost still tracks how many people sign in.

Notion is the most common improvised version, and it has one limit worth knowing before you commit. Per Notion's own documentation, a page published to the web can be viewed by anyone on the web, and Notion does not offer password protection for published pages. Restricting access means adding the client as a guest, which requires them to have a Notion account. So the improvised Notion portal is either open to anyone holding the link or gated behind an account, with nothing in between.

Builders suit teams who enjoy owning the build. The trade is that you have become the maintainer of an internal application, and the client still has to log in.

4. Delivery-first links

This is what Stacktree is, and it is the honest opposite of the other three. Each deliverable is published as a private page at an unguessable URL on your own domain, and the gate goes on the work rather than on the person: a passcode, or a restriction to the client's company email domain. Publish under a client name and the pages collect into a client space, which can bind its own hostname, acme.youragency.com, and serve a generated portal at the root with each deliverable at a path underneath. One gate covers the whole space, so the client types the passcode once and stays in for 30 days.

Your client's side of it is: click, read. There is no account, no invite, no password reset and no seat, ever. The corresponding limitation is real: comments can come back on the page itself, but files, signatures and payments cannot.

The complaint that no feature list answers

Read enough agency threads about portal software and one finding repeats far more often than any other. The problem is never a missing feature. It is "I set it up and the client never used it". The invite goes out, the client opens the portal once during onboarding, and every later "it's in the portal" comes back as "can you just email it".

The category's own published advice about this is telling: put something the client cannot get anywhere else behind the login, so they are forced to go in. That is a workaround for a design problem, and the design problem is the login. The alternative fits in one line: the client gets one secure link, and no account.

That is a fair description of the fourth category, and it is also why the fourth category cannot do the things the first three can. Nothing that requires the client to be an identified, logged-in user survives the removal of the login.

A decision rule you can apply in one line

If the client has to put something in, buy a portal. If the client only has to take something out, they need a link.

Three questions make that concrete. Does the client upload documents to you on a schedule? Do you collect signatures or payments as part of the engagement? Would a regulator or a client's auditor expect the exchange to be logged in one system? Two yeses and you should buy a suite, or your profession's practice software if you have one. No to all three and you are buying nine features to get one.

The four categories, side by side

Named examples are illustrative rather than exhaustive, and pricing here describes the model each category uses. Check any figure on the vendor's own pricing page before you budget from it.

Criterion All-in-one suites Practice-management tools No-code builders Delivery-first links
Named examples SuiteDash, Copilot, Moxo, Clinked, Zendo, Taskip SimplePractice, TaxDome, Canopy, MyCase, SmartVault Softr, Notion, Airtable interfaces Stacktree
Built for Running the whole engagement in one place Running a practice in one profession, portal included Assembling the portal you want on data you already keep Getting finished work to a client privately
Client login An account per client, by invite An account per client, usually required to receive documents An app user account, or a Notion account for a guest None. A passcode typed once: 24 hours on a page, 30 days on a client space
Client sends things back Yes: uploads, forms, approvals Yes: intake forms, records, signed documents Yes, if you build it Comments only. No uploads, forms or signatures
E-signature, invoicing, payments Usually bundled Built around the profession, billing rules included A bolt-on, or a second tool None of it
Whose brand the client sees Yours, though how far the white-labelling goes varies by tier Partly yours, inside the vendor’s frame Yours, with a custom-domain add-on Your own domain, and no footer on paid plans
Before the client sees anything Days of configuration, then onboarding every client A migration, often with a specialist A build, which you then own About a minute for a page, one DNS record for an address
Cost model Tiered: some flat, some per seat or per client. Published plans run from about $12 to $600 a month Per practitioner or per seat, portal bundled in Per app user, with team and client logins counted separately on paid plans Flat per workspace: $0, $19, $79, $249. Clients are never seats
Where it falls down The client never logs in No use to you outside that profession You now maintain an app, and the login is still there Anything the client has to send back

The row that decides the purchase is "client sends things back", not the price row. If that is a yes, the fourth column is not a candidate at all and the comparison is really between the first three. If it is a no, the first three are selling you a return path you will not use.

When to buy a suite instead

Some practices should buy the suite, and a comparison page that cannot say so is not worth reading. Four signs it is the right machinery for you:

  • Files come back on a schedule. The client uploads monthly financials, receipts, brand assets or case documents and you return finished work. That two-way exchange is the core portal workflow, and nothing else does it as cleanly.
  • Signatures and payments are part of the engagement. Contracts, approvals and invoices belonging next to the documents they relate to is a genuine reason to consolidate.
  • The exchange has to be logged in one system. Some professions need a defensible record of who sent what and when, in one place, with an audit trail.
  • Your profession has its own software. If you are an accountant, a therapist or a lawyer, buy the practice tool and use the portal inside it. A general suite will be a worse fit and a second subscription.

Stacktree does none of that, and no plan adds it. There is no file collection from clients, no e-signatures, no invoicing, no payments, no CRM, no project management and no messaging. Plenty of firms run both: the suite for paperwork and compliance, and a client space for the work itself, because a finished deliverable deserves better than a PDF in a filing cabinet the client avoids.

Where a delivery-first link is the better buy

  • Your output is finished artefacts. Reports, audits, proposals, decks, dashboards, prototypes. The client's job is to read them.
  • Your clients live in email. Sending a link asks nothing of them that they are not already doing twenty times a day.
  • You want your own name on it. From Solo, work serves from a domain you own with no footer of ours on the page, and the passcode prompt is a styled page rather than the browser's grey credential box.
  • You want to know it was read before the call. From Solo you see opens, unique viewers and when it was last opened. Studio adds time on page, scroll depth and an attention heatmap.
  • You do not want to run onboarding for software your client did not ask for. There is nothing to onboard.

What it costs

Stacktree is priced flat per workspace, in USD, and clients are never seats. Free is $0: three pages in total for the lifetime of the account, each expiring after seven days, no passcodes or email gates, no viewer numbers, and a small "Made with Stacktree" footer on the page. It is enough to see how a deliverable lands, not a place to keep client work.

Solo is $19 a month: 25 pages live at a time, no expiry, passcodes and company-email gates, one custom domain, one activated client space, opens and unique viewers, and no footer. Studio is $79: unlimited pages, ten custom domains, the engagement analytics, and ten activated client spaces. Firm is $249: 25 domains, up to 1 GB a page, uncapped publishing and unlimited spaces. A space counts as activated once it has a hostname bound or its portal switched on, archiving one gives the slot back, and space hostnames do not consume your custom-domain slots. Filing pages under a client is free on every plan, including Free, because grouping your own work should not be a paid feature. Full detail on the pricing page.

Two things portal buyers ask about are not built yet, and are worth saying plainly rather than burying. Applying your logo, typeface and colours across every page you publish is coming soon; today the portal is a clean neutral layout under your domain. Team members and roles inside a workspace are coming soon too; plans are flat per workspace in the meantime, which is why adding people does not change the price.

FAQ

Frequent questions

What is the best client portal software? +
There is no single best one, because the category contains four different products. If your engagement is two-way, meaning the client uploads things, signs things and pays through the same place, an all-in-one suite such as SuiteDash, Copilot or Moxo is the right machinery. If you are an accountant, a therapist or a lawyer, the portal inside your practice-management software will beat a general suite because it already understands intake, engagement letters and billing rules. If you want a bespoke shape on data you already keep, a no-code builder such as Softr fits. If the work only travels one way, from you to the client, none of that is needed and a gated link on your own domain does the job with nothing for the client to adopt.
What is the difference between client portal software and customer portal software? +
The words are used loosely, but the useful split is how many people are on the other side. Customer portal software is normally self-service at scale: hundreds or thousands of customers checking orders, tickets, invoices or account settings, so the login pays for itself. Client portal software is for a smaller number of high-value engagements, where each client sees only their own work. The smaller the client list and the more the relationship runs on email and calls, the harder it is to justify making each client hold an account.
How much does client portal software cost? +
Published pricing varies more than the feature lists do. Lighter tools start near $19 a month, all-in-one suites pitched at small firms commonly land between $50 and $300 a month once seats and modules are counted, and no-code builders such as Softr price by app user, with separate team and client allowances. Vertical practice tools are usually per practitioner, with the portal bundled in rather than sold separately. Stacktree is flat per workspace: Free at $0, Solo $19, Studio $79, Firm $249, and clients are never seats. Check any figure against the vendor’s own pricing page before you budget from it.
Do clients actually use client portals? +
Often not, and this is the most common complaint in the category by a wide margin. The failure is rarely a missing feature. It is that the agency configures the portal, sends the invite, and the client opens it once during onboarding and then goes back to email. The standard advice in the category is to put something the client cannot get any other way behind the login so they are forced in, which is a workaround for a design problem rather than a fix. Before you buy, ask honestly whether your clients will log in, because everything else depends on that.
Is there a client portal with no login for the client? +
Yes, if the work only needs to go one way. Publish each deliverable as a private page on your own domain and put the gate on the work rather than on the person: a passcode the client types once, or a restriction to their company email domain. A client space then gives that client one permanent address, such as acme.youragency.com, with everything you have delivered behind it. There is no account, no invite and no password reset at any point. What you give up is the return path: they cannot upload, sign or pay through it.
Can you use Notion as a client portal? +
You can, with a specific limit worth knowing first. Per Notion’s own documentation, a page published to the web can be viewed by anyone on the web, and Notion does not offer password protection for published pages. Restricting access means inviting the client as a guest, which requires them to have a Notion account. So the improvised Notion portal is either open to anyone holding the link or gated behind an account, and the middle option, a private page the client opens without signing up, is the one it does not have.
Do I need client portal software if I only send finished work? +
Probably not. If the deliverable is a report, an audit, a proposal, a deck or a dashboard, and the client’s job is to read it, the portal is being bought for one job it does well and several you will never use. A private link on your own domain covers privacy, branding, staying current at the same URL, and knowing whether it was opened. Buy the suite when files come back the other way. See the buyer guide for the longer version of that argument.
Keep reading

Related guides

References

Sources and further reading

Send the next deliverable as a link.

Publish one free and see how it lands. From $19 you add the passcode, your own domain, and who opened it. Nothing for your client to log in to.

Sign up free →