You don’t need a portal suite. Your client needs a link.

The pitch, and the part they leave out

If you run a services business sending $5,000+ work, you have had the pitch: SuiteDash, Copilot, Moxie, or whichever portal suite is sponsoring the podcast that month. One place for the client. Files, messages, invoices, a branded login screen. It sounds like professionalism you can buy.

The part they leave out is that the whole thing hinges on your client logging in, and clients of small agencies mostly do not. The invite email goes out, the client opens the portal once during onboarding, and every later “it’s in the portal” turns into “can you just email it”. Meanwhile you have spent days configuring modules and branding the thing, you are training each new client to use it, and the subscription creeps upward as seats and add-ons stack. You bought software for your client, and your client declined to become its user.

What you were actually trying to buy

Strip the feature list away and the suite was doing four jobs:

• Private. The work is not floating on a public URL or travelling as an email attachment.
• Branded. The client sees your name, not a file-sharing tool’s.
• Current. There is one place, and it always holds the latest version.
• Readable. You know whether the client opened it before the call.

A portal suite is one way to get those four. It is not the cheapest and it is nowhere near the lightest. A private link gets all four with no adoption problem, because clicking a link is the one workflow every client already has. And where a client has more than one deliverable, one address per client covers the one-place part too, without anybody signing in.

How the link approach works

• Publish the deliverable as a page. The proposal, the audit, the monthly report. You get a private, unguessable URL straight away, never listed and never indexed.
• Gate it. From Solo, add a passcode or restrict viewing to the client’s company email domain. Set an expiry so a preview does not outlive the project, or make a sensitive one-off burn-after-read. The mechanics are on the security page.
• Put it on your domain. clients.yourstudio.com reads as your practice, not a generic host.
• File it under the client. Publish with a client name and every deliverable for that client lands in one client space instead of being five unrelated links. Give the space its own hostname, acme.youragency.com, and it serves a portal at the root: the audit, then July’s report, then the strategy doc, newest at the top, each at its own path. The client bookmarks it once and the ledger grows behind it. Filing is free on every plan; the address and the portal start on Solo, which includes one space, with ten on Studio and unlimited on Firm.
• Gate the whole client, not each page. A passcode set on the space is inherited by every page served under it. The client types it once and stays in for 30 days, on your domain, on a page carrying your name and not ours. A page can still carry its own gate, which overrides the space one, so nobody is ever asked twice.
• Keep it current at the same URL. Revisions replace the page in place. The link sitting in the client’s inbox always opens the latest version, so you never send “v2 final”.
• See who opened it. From Solo, every page reports opens and unique viewers. Studio adds time on page, scroll depth, and an attention heatmap, so you walk into the review knowing what they read and what they skipped.

Your client’s side of this is: click, read. No account, no seat, no app, nothing to adopt, at any point in the relationship. There are live examples on the homepage if you want to see how a finished one lands.

When you do need a portal suite

Honest answer: some practices should buy the suite. Three signs it is the right machinery for you:

• Files flow both directions on a schedule. The client uploads monthly financials, you return the accounts. That two-way exchange is the core portal workflow.
• You collect e-signatures inside the engagement. Contracts, approvals, and sign-offs that need to happen in the same place as the documents.
• You invoice and take payment in the flow. If billing lives next to the work, a suite consolidates it.

Stacktree does none of that. The portal it generates is a reading surface, not a workspace: finished pages, gated and grouped under a client, at an address you own. It does not collect client uploads, sign contracts, or take payments. If two of the three above describe your practice, buy the suite without guilt. Plenty of agencies run both: the suite for the paperwork, and a client space for the actual work, because the deliverable deserves better than a PDF in a filing cabinet the client avoids.

What it costs

Stacktree pricing is flat, in USD, and clients are never seats. Free is $0: three pages in total, each expiring after seven days, which is enough to see how this works and not a place to keep client work. Passcodes, email gates and viewer numbers start at Solo, $19 a month, which also includes a custom domain. Studio is $79 with ten custom domains, ten client spaces, and the deeper read analytics: time on page, scroll depth, attention. Firm is $249 with unlimited spaces, for larger practices. Filing pages under a client is free on every plan; what the paid tiers buy is the address and the portal. Free pages carry a small “Made with Stacktree” footer; every paid plan, starting at Solo, carries nothing but your brand. Details on the pricing page.