Our 5-Person Bookkeeping Firm Just Went Fully Remote - Here's What Actually Worked (and What Didn't)

General
1

After 10 years running Martinez Bookkeeping Services from a shared office space in Austin, we finally took the plunge this January: we went fully remote with our 5-person team. I wanted to share what’s actually worked (and what hasn’t) for anyone else considering this transition.

Why We Did It

Three main drivers pushed us to go distributed:

  1. Talent recruitment: We couldn’t find qualified bookkeepers locally. Our last two job postings got zero qualified applicants in Austin.
  2. Overhead costs: $3,000/month for office rent that we’re now saving
  3. Team flexibility demands: Our bookkeepers are parents who need flexible schedules

Our Tech Stack

Here’s what we actually use day-to-day:

  • Beancount + Git for all client books (every single client ledger is in Git)
  • Zoom for client meetings and daily team standups
  • Slack with dedicated channels per client
  • Google Drive for non-ledger documents (engagement letters, receipts, tax forms)
  • Fava deployed on our server as the client portal

What Actually Works

The Git workflow is a game-changer. Each bookkeeper works on their own branch for client work. We open pull requests for review before merging to main. This catches errors we used to miss when everyone worked independently in the office.

Morning standups keep us aligned. Just 15 minutes on Zoom every day. We go around: what clients are you working on today, any blockers, any questions. That’s it.

Beancount’s plain text format means zero sync conflicts. One of our bookkeepers can work offline during her commute (yes, even remote workers commute to coffee shops!), commit later, and there’s never a merge conflict because transaction ordering doesn’t matter.

Client portal built on Fava is powerful. Clients log in and see real-time dashboards of their financials. No more “can you send me last month’s report” emails. It’s already there, always current.

Async communication via Slack reduces meeting overload. We create a channel per client. Questions like “where should I categorize this unusual expense?” get answered without scheduling a meeting.

Unexpected Challenges

Client onboarding is harder remotely. New clients miss the face-to-face trust building. Some prospects have explicitly said “we’re not comfortable with a bookkeeper who doesn’t have an office.” We’ve lost 2-3 potential clients over this.

Time zone coordination is real. We hired an amazing bookkeeper from Oregon (Pacific Time), but coordinating meetings when she’s 2 hours behind takes planning.

Training new team members on Git AND Beancount simultaneously is a steep learning curve. It took our last hire about 6 weeks to feel comfortable with the workflow. In the office, they could just tap someone’s shoulder for help.

Security concerns with home networks. We had to implement a mandatory VPN policy and upgrade everyone to encrypted hard drives. Our professional liability insurance premium went up 15% to cover remote work risks.

Big Wins

The Oregon hire alone justified this transition. She would never relocate to Austin, but she’s the best bookkeeper on our team. Her expertise with multi-state tax compliance is something we couldn’t find locally.

Team happiness is measurably up. Our internal survey (yes, we survey our tiny team) shows everyone loves flexible schedules and no commute. One team member saves 90 minutes per day not driving.

Client work quality improved. The PR review process catches duplicate entries, mis-categorized transactions, and balance assertion errors before clients ever see them.

My Question to the Community

How are other professional bookkeepers handling distributed workflows? What tools are absolutely essential for your remote practice? Are you using Beancount + Git, or something else entirely?

And specifically: how do you handle client education when they ask “why don’t you have an office?” I’m still working on a confident answer to that one.

2

Congratulations on the successful transition, Bob! Our CPA firm (Thompson & Associates) made a similar move to hybrid work in 2025, and I really appreciate seeing another professional practice share their real-world experience.

I want to add some critical security and compliance considerations that your post didn’t fully address but are essential for any accounting practice going remote:

Security Must-Haves

Client data security is paramount. Beyond your VPN policy, we require:

  • Encrypted hard drives on all team devices (mandatory, not optional)
  • Two-factor authentication on every account that touches client data
  • Annual security training covering phishing, secure file handling, and incident response
  • Professional liability insurance updated specifically for remote work coverage (ours went up 20%, not just 15%)

Client engagement letters matter. We updated all our templates to include explicit language about remote access, data security protocols, and where client data is stored. Some clients asked detailed questions, and we had to be ready with clear answers.

Our Hybrid Model (Not Fully Remote)

We went hybrid rather than fully remote: 3 days remote, 2 days in office. Here’s why:

In-office days are strategic:

  • New client onboarding (face-to-face trust building solves your “why don’t you have an office” problem)
  • Quarterly team planning and training sessions
  • Complex tax return reviews that benefit from whiteboard collaboration
  • Team culture building (yes, we still need this)

Remote days are for focus work:

  • Individual client bookkeeping and transaction entry
  • Routine report generation
  • Email and communication catch-up

Tool Recommendation: Karbon

Bob, you mentioned your 5-tool stack (Beancount, Git, Zoom, Slack, Google Drive). We added Karbon for practice management and it’s been a game-changer for distributed team visibility:

  • Integrates with email, so all client communication is automatically tracked
  • Shows who’s working on what client tasks in real-time
  • Prevents duplicate work and dropped balls
  • Provides visibility without micromanaging

On the Git + Beancount Learning Curve

I completely agree this is steep, but we solved it with a structured training program:

  • Week 1: Git basics with a dummy ledger (no client data, just practice transactions)
  • Week 2: Beancount fundamentals - account structure, transaction entry, balance assertions
  • Week 3: Supervised client work with a senior accountant reviewing every commit via PR

It takes 3 weeks of dedicated onboarding, but after that, new hires are productive and the quality is better than with traditional software.

Time Zone Challenge

We share this one. We initially tried hiring across all U.S. time zones for maximum flexibility, but it became untenable. We now limit hiring to Eastern and Central time zones to keep core collaboration hours reasonable.

Question Back to You

How do you handle client data backup and disaster recovery? We use automated Git pushes to a private GitLab instance with daily backups to an encrypted offsite location. What’s your approach?

Also, have any clients explicitly asked about your business continuity plan now that you’re fully remote? We had to formalize ours in writing for two nervous clients.

3

Love this discussion! Remote work + Beancount is such a natural fit, and Bob’s real-world experience from a professional bookkeeping firm is exactly the kind of content this community needs.

My Context: Personal Finance + Rental Properties

I’m not a professional bookkeeper like Bob and Alice, but I’ve been managing my family finances plus 2 rental properties remotely with Beancount for 4+ years now. Reading Bob’s post, so many things resonated with my own experience.

What Really Resonates: The Git Workflow

Bob’s point about Git + PR review is spot on. My wife and I both work in the same Beancount repository for our household finances, and we use branches too:

  • She handles day-to-day expenses (groceries, utilities, subscriptions)
  • I handle investments and property accounting (rent collection, maintenance, mortgages)
  • We have a weekly “financial sync” meeting every Sunday morning over coffee
  • During that meeting, we review each other’s PRs and merge to main

This collaborative approach has dramatically improved our financial communication as a couple. Before Beancount, we’d have these awkward “we need to talk about money” conversations once a quarter. Now it’s just a natural part of our weekly routine.

The “Zero Sync Conflicts” Point is HUGE

Bob mentioned this casually, but I want to emphasize: this is transformative.

I came from GnuCash, which used binary database files. The sync issues were constant:

  • Couldn’t work on finances simultaneously
  • Offline work was a nightmare
  • Had to manually reconcile conflicting versions
  • Lost work more than once

With Beancount + Git:

  • I can work on property finances during my flight back from visiting rental properties
  • Commit when I land
  • My wife can simultaneously update grocery expenses from her laptop at home
  • Git handles the merge automatically 99% of the time
  • The rare conflicts are obvious text diffs, easy to resolve

PR Review Catches So Many Errors

Bob mentioned this benefit for his team catching professional bookkeeping errors. It works just as well for household finances:

  • My wife has caught duplicate transactions I entered twice
  • I’ve caught mis-categorized expenses (she labeled “Home Depot” as “Groceries” instead of “Home Maintenance”)
  • We both catch balance assertion errors before they compound

In the GnuCash days, these errors would sit for months until tax time revealed them. Now they’re caught within a week.

The Training Challenge is Real

Alice’s 3-week structured training program sounds great for professional teams. For household/personal use, the challenge is different but similar:

My wife is not technical. Learning Git command line was genuinely frustrating for her at first. Here’s what finally worked:

  1. GitKraken (GUI Git client) - visual interface made everything click
  2. Written cheat sheet - literally a printed card with the 5 commands she needs: commit, push, pull, create PR, merge
  3. Patience - took about 2 months before she felt comfortable

Now she’s confident with the commit/push/PR workflow, but it wasn’t instant.

Start Simple (Advice for Professional Bookkeepers)

For professional bookkeepers reading this and considering Bob’s approach, my advice from personal experience: don’t over-engineer your Git workflow on day 1.

Start with:

  • Basic commit/push to main branch
  • Get comfortable with version control first
  • Add PR review once the team is comfortable with Git basics

Plain text + version control is already 10x better than traditional software, even without fancy branching strategies.

Bob’s team is advanced with feature branches and PRs from the start - that’s impressive, but it’s okay to build up to that complexity gradually.

Question for Bob

Your clients - are they aware you use Git and Beancount instead of QuickBooks? How do you position that to non-technical small business owners?

I’m curious because one of my rental property partners asked to see “the books” and when I showed him Fava, he was confused at first. Took some explaining that plain text accounting is actually more trustworthy and auditable than a proprietary database.

How do you handle that education process with paying clients who might have preconceptions about what “real accounting software” looks like?