Hosting a secure client portal for a small accounting firm

A small accounting firm wants a safe place for clients to upload tax papers. Before building anything, we check whether software it already pays for can do the job.

2 min readMade-up stories, not client work

Cloud Hosting: story 1 of 15

A made-up story

Picture a ten-person accounting firm. Every spring, clients email tax documents as attachments, and staff dig through inboxes to find them.

What's going wrong

Email is a poor place for tax papers. Files get lost, and sensitive details sit in inboxes for years. A web developer has offered to build a custom portal on its own server.

What they have today

  • Practice-management software the firm already pays for
  • A simple website on a hosting plan
  • Nobody on staff who looks after servers

What we can't ignore

  • Tax documents are sensitive and must stay private
  • Busy season leaves no time for a long project
  • Clients range from tech-savvy to not at all

The choices

  • Not for them

    A custom portal on the firm's own cloud server

    Someone would have to patch, watch and back up that server forever. That's a lot of upkeep for a small office.

  • Worth a look

    A custom portal on a managed hosting service

    Less upkeep, but still custom code to build, test and maintain.

  • Our pick

    The client portal built into the firm's existing software

    Often included in the plan already. The vendor keeps it secure and up to date.

  • Worth a look

    A secure file-sharing service

    A good fallback if the built-in portal can't do the job.

What we'd do

Switch on the portal that comes with the firm's practice software, link to it from the website, and require a second sign-in step for staff and clients. No new server, no custom code.

Why

  • The firm may already be paying for it
  • The vendor handles security updates and backups
  • Staff learn one familiar system instead of two

Where the money really goes

No prices here: this shows where the costs sit, not what they'd be for any real business.

The custom portal looks affordable to build, but the real cost is keeping it safe year after year. The built-in portal adds little or nothing to what the firm already pays.

Building it
Custom: developer time. Built-in: an afternoon of setup and a short client guide.
Keeping it running
Custom: ongoing updates and monitoring. Built-in: handled by the vendor.
Staff time
Both end the inbox hunt every spring.

Running, growing, and staying safe

If something breaks

The vendor runs the portal, so the firm doesn't depend on one developer being available during tax season.

When it grows

New clients just get an invitation. Nothing to resize.

Keeping it safe

Files go straight into the firm's system instead of sitting in email, and every sign-in needs a second step.

What the business gets

  • Client papers in one safe place
  • No new system to look after
  • Less time hunting through inboxes

These are the kinds of results the approach aims for, not measured results.

When we'd look again

If clients later need things the vendor can't offer, like custom intake forms linked to other systems, we'd look again at a small custom layer on a managed service.

If you liked this, read

About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.

Next: Choosing where to host a growing online store

A store has outgrown its first setup. We compare a bigger server, a cloud rebuild and a fully hosted store, and the real question turns out to be who keeps it safe and running.

Read the next story