You don’t need a portal. 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 portal 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 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.

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. 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.
• 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. 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 app, nothing to adopt. There are live examples on the homepage if you want to see how a finished one lands.

When you do need a portal

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 is not that. It publishes and gates pages; it does not collect client uploads, sign contracts, or take payments. If two of the three above describe your practice, buy the portal without guilt. Plenty of agencies run both: the portal for paperwork, and a private link 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 and enough to publish and gate your first client pages. Solo is $19 a month and includes a custom domain. Studio is $79 with ten custom domains and the deeper read analytics: time on page, scroll depth, attention. Firm is $249 for larger practices. Pages on Free and Solo carry a small “Made with Stacktree” footer; Studio and Firm pages carry nothing but your brand. Details on the pricing page.