All notes
    28 September 2026·6 min readAccounting practicesCase study

    Five apps, and no screen showed the whole client

    A bookkeeping practice with 84 clients and five good tools that didn't talk. Why we diagnosed before building, and why we didn't migrate a single record.

    Daniel Huthwaite

    Daniel Huthwaite

    Founder, 88 Automate

    A bookkeeping and tax practice in the United States, 84 clients, a team that knows its work. They run the practice on five tools, and every one of them is good at its job: a CRM for contacts and email, a proposals and billing platform, a bookkeeping delivery tool, a tax workflow system, and the clients' own accounting software. The problem wasn't any of the tools. It was that answering "where are we with this client, and what are they buying from us?" meant opening four or five of them.

    The finding that shaped everything

    Before anything was built, I spent time looking at how the practice actually ran. The finding was one sentence: each app knows part of the story, and no screen shows all of it.

    That sentence decided the architecture. The obvious fix, and the one most implementers would sell, is to migrate everything into one system. It's also the wrong fix. Each of those five tools is the right tool for its job, the team knows them, and the data in each is trustworthy precisely because that tool owns it. Migrate it and you get one system that's worse at everything, plus a year of pain.

    What we built instead

    A hub that reads from every tool and writes back through them, and owns no duplicate copy of anything. One login. One screen per client that shows: what they've signed up for and who owns it, every open item across every app worst-first, every email in and out, every ticket, every document, with a link back to the real thing. One screen per deal with the next action a click away, labelled with the app it fires through.

    Nothing moved. Every app stayed the source of truth for its own data. The hub is a window, not a replacement.

    The lesson that came from another client

    I'd built two-way sync between systems before, for a business where two apps both wanted to own the same booking. It works, and it costs you: every conflict needs a rule, every rule needs a screen, and someone has to look at that screen. That experience is why the practice hub reads and writes through, rather than syncing both ways. No conflicts, because nothing is owned twice.

    That's what I mean when I say every business I work with makes the next one better.

    What it's worth

    The practice gets a daily focus list for every person, worked out automatically from billing status, job status and how long each client has been waiting. Meeting summaries written after every client call, with the follow-up drafted. A lead form on the website that scores itself and routes to the right person. And an owner who can see revenue by service line and where the work is stuck, from the same live data, without a spreadsheet.

    None of it required abandoning a tool they liked. All of it came from looking properly before building anything, which is why I charge for the looking and credit it back against the build.

    If you run a practice on several good tools that don't talk to each other, the answer probably isn't a new tool. It's a screen that shows the whole client. I'm happy to look at yours.

    Sound like your business?

    Thirty minutes on a call with me. You tell me what's frustrating you, I tell you straight what I'd do.

    A note from Daniel, once a month

    One real lesson from a business I work with, and one thing you can fix this month. No newsletter padding. Unsubscribe any time.