Remote Work, Sensitive Data

The team

A small CPA firm: a managing partner, a couple of associates, and a bookkeeper. They handle tax, payroll, and routine accounting for a mix of small businesses, contractors, and individuals. Their work runs on a shared store of client records (returns, scans, supporting documents). Tax-season deadlines run January through April. The rest of the year covers planning, filings, and audits.

The challenge

The firm wanted to operate remotely. The existing options each had a deal-breaker.

• Cloud storage. Putting client tax records on a third-party cloud raised compliance concerns and trust questions with clients.
• Emailing files. Attachments leaked into personal inboxes, file versions diverged across devices, the audit trail collapsed.
• Office VPN. It works enough that nobody has replaced it. When it doesn't, the firm calls the IT contractor and waits.

The firm needed centralized data access without putting the data outside their control, and without a per-user enterprise stack.

What they built

The firm already had a NAS in the office and a few PCs on the LAN. They installed Netrinos on one of the existing PCs, which now does double duty: regular workstation, and a bridge that puts the NAS on the mesh. The NAS itself runs no new software.

Each accountant installed Netrinos on their laptop and joined the same mesh. The office NAS now appears on the laptop as if it were on the local network, regardless of where the laptop is. No VPN client, no port forwarding, no router changes. Encrypted end-to-end, the firm's devices form a software-defined private network on top of whatever internet connection is available.

Setup. About an hour. Install Netrinos on the office PC, install on each accountant's laptop, sign in with the same firm account. Existing tax and bookkeeping software (QuickBooks Desktop, Lacerte, document scanning) was untouched.

Cost. Netrinos costs $10 per month flat for ten users and a hundred devices. For a four-person firm with twenty-some endpoints, that is less than a fancy coffee.

If a bridge PC fails. The data is still on the NAS. For redundancy, the NAS can be shared from more than one PC, with either able to provide mesh access. Adding a second bridge PC takes about five minutes.

What about hosted QuickBooks? The obvious alternative is paying a service like Right Networks to host QuickBooks Desktop in the cloud, at roughly $63 to $84 per user per month, with client data sitting on a third-party server. The mesh approach trades that recurring per-user cost for keeping the data on firm-controlled hardware. The cloud is just someone else's computer; for firms that want certainty about who can reach their data, keeping it on their own equipment removes the third-party trust dependency.

Compliance and liability

The firm's WISP and FTC Safeguards Rule responsibilities did not get harder. The answers to "where does client data live" and "who can reach it" are the same as before: on firm-controlled hardware, accessible only to authenticated mesh users. Existing E&O coverage applies as before.

The same logic applies under HIPAA, GLBA, and equivalent rules in other regulated industries. Netrinos does not store data; it provides encrypted transport (WireGuard) between authorized devices. Storage compliance does not change because the data does not move. Transmission encryption is satisfied for most frameworks; environments that mandate FIPS 140-2 validated cryptography should evaluate algorithm choice with their compliance officer.

The result

• Tax-season velocity. Files open at LAN speed regardless of where the accountant is sitting. The bottleneck stopped being the network.
• Compliance posture. Client records never left infrastructure the firm controls. The audit story is one line: the data is on firm hardware, in the firm's office.
• Reduced office footprint. The firm kept its office for client meetings, but downsized once the team stopped needing a desk apiece.
• Optional remote work. Staff can work from home when it makes sense, without committing the firm to a remote-first model.

Beyond the firm

The same architecture extends to the firm's clients. The clearest application is part-time bookkeeping: the firm installs Netrinos on the client's existing back-office PC, scoped to that one client, and reaches the bookkeeping software through a private mesh. No port forwards, no exposed RDP, no consumer remote-control software like AnyDesk on the client's PC. The number of clients one bookkeeper can serve stops being capped by the drive across town. We will cover that pattern in a separate brief.

Why this generalizes

The pattern fits any small professional services team where keeping client data under firm control is part of the value proposition. The specific software changes (legal practice management, healthcare admin, financial planning), but the architecture does not.

What we can provide

• Founder available for interview
• Walkthrough of the architecture (server, mesh, access control)
• Composite scenarios from other professional services segments
• Pricing for a five-to-twenty-person team
• Screenshots, network diagrams, and high-resolution logo files