Client portals for small businesses: when logins are worth building.

Somebody — maybe a client, maybe a competitor's website — put the idea in your head: "We should have a portal. Clients could just log in and see everything." And now you're picturing it: project status, invoices, documents, approvals, all in one place, and your inbox finally quiet.

Here's the uncomfortable part: most small-business client portals get built, get announced, and then get ignored. Clients keep emailing anyway, because email is where they already live. The portal becomes a second place to maintain, not a replacement for the first.

That doesn't mean portals are a bad idea. It means they're a specific idea — one that pays off in some businesses and quietly bleeds money in others. Let's figure out which one you are.

What a portal actually is (and what it costs)

A client portal is a login-protected area where your customers can serve themselves: check project status, download documents, pay invoices, approve work, upload files. The pitch is fewer "quick question" emails and a more professional front door.

The cost depends on the route:

• Off-the-shelf portal features inside tools you may already pay for. Many invoicing, project management, and CRM products (think QuickBooks, Jobber, HoneyBook, and similar) include some client-facing view. Cost: often $0 extra beyond your subscription. Limitation: it looks and works how the vendor decided, not how your business runs.
• Configurable portal platforms. Dedicated portal products typically run in the range of $50–$300 per month depending on seats and features. Faster to launch, monthly cost forever, moderate flexibility.
• Custom-built. A tailored portal built on your own stack usually starts around $15,000–$40,000 for a focused first version, plus ongoing hosting and maintenance. Full control, real ownership, real price tag.

Those are illustrative ranges, not quotes — the point is the order of magnitude. A custom portal is a five-figure decision. That's why the question isn't "would a portal be nice?" (it always would) but "will it get used enough to earn that back?"

The threshold test: three questions

A portal earns its cost when clients return repeatedly for things you currently handle by email. One-time customers don't log in twice. Run your business through these three questions:

1. Do clients come back? (Recurring relationships)

If a typical client works with you once and disappears — a one-off remodel, a single event, a one-time repair — they will never bother creating a password. Portals need repeat visits to justify their existence. Rough threshold: if fewer than half your active clients will interact with you more than five times a year, a portal is solving a problem you don't have.

2. Are jobs multi-touch? (Status checking)

Count the "where are we on this?" emails. A typical Keller custom home builder might field a dozen status questions per project per month; a typical Fort Worth bookkeeper might field two per client per quarter. The builder's clients would check a status page weekly. The bookkeeper's clients wouldn't remember the login. If a single job generates 10+ status touchpoints, self-serve status starts paying for itself in staff hours.

3. Is there real document and approval volume?

Contracts, change orders, photo approvals, proofs, compliance documents, monthly reports. If you're regularly digging through email threads to find "the version the client actually approved," a portal creates a single source of truth — and an audit trail. If you send each client three PDFs a year, email is fine.

Scoring it: if you answered a confident yes to all three, a portal is probably worth building, and the math on saved admin time will usually show it. Two yeses: try the middle path below first. One or zero: skip the portal, spend the money on something clients will actually notice.

The middle path: portal benefits without the login

Here's what most small businesses should do before building anything — because the login itself is the biggest adoption killer. Every password reset is a client who gave up and emailed you instead.

Three moves, in increasing order of effort:

1. Shared links instead of attachments. Put project documents in a client-specific cloud folder (Google Drive, Dropbox, OneDrive) and send one link at project kickoff. The client bookmarks it. Every document lives there. No login they didn't already have. Cost: an afternoon of setting up a folder template.

2. Proactive status emails on a schedule. Most "where are we?" emails exist because the client heard nothing for two weeks. A short, templated Friday update — "Here's what happened, here's what's next, here's what we need from you" — kills the majority of inbound status questions. Automate it from your project tool if you can; send it manually if you can't. Cost: 10 minutes per client per week, often less than the interruptions it replaces.

3. Single-purpose no-login pages. A private, unlisted status page per project — just a URL, no password — showing phase, next milestone, and recent photos. Same for approvals: a link where the client clicks "Approve" or "Request changes." This is a fraction of a portal build (typically a low-four-figure project rather than five) and delivers the two features clients actually use.

Run the middle path for three months and watch behavior. If clients click the links constantly and start asking for more — payment history, past documents, multiple team members needing access — congratulations, you've validated the portal with real usage data instead of a hunch. If the links go unclicked, you just saved yourself $25,000.

When to build the real thing

Build a genuine logged-in portal when the middle path starts creaking:

• Sensitive data. Financials, health information, legal documents — anything where an unlisted URL isn't acceptable protection and you need real authentication and access control.
• Multiple people per client. When three people at the client company need different views and permissions, links stop scaling.
• Payments and account history. Letting clients see every past invoice and pay online is where portals produce measurable cash-flow gains — invoices with an online payment option simply get paid faster than "check enclosed."
• You're an agency serving agencies. White-label portals — your client's clients logging into a branded space — are a legitimate differentiator and can justify custom work on their own.

Scope the first version brutally. Status, documents, invoices. Not messaging (email already exists), not a dashboard with twelve widgets. Every feature you add is a feature you maintain forever.

How West Fork approaches this

When a client asks us for a portal, our first job is to try to talk them out of it — or at least into the smallest version that could work. We'll run your actual email volume through the threshold test, often prototype the no-login middle path first, and only scope a custom build when the usage data says clients will show up. If we build it, we build it on a stack you own.