chivvy. Start a conversation
What we doPractice PortalWorkHow we workGuidesArticlesAboutFree toolContactStart a conversation
For accountancy practices

Reporting for the firm,
not just for clients

Client packs produced without a partner rebuilding a spreadsheet, and — the one most firms never get to — a proper read on how the practice itself is doing.

The problem

Two reporting problems sit in every practice and only one of them gets solved.

The first is client management accounts: useful, chargeable, and usually rebuilt by hand every month in a spreadsheet somebody keeps on their own machine.

The second is the firm's own numbers. Recovery by job, work in progress, lock-up, which clients are actually profitable, which service lines are quietly subsidising the others. Most owners can tell you the fee income and very little else, because the answers live in three systems that have never been joined.

What we build
01

Client management packs

Produced on a schedule from the ledger, in your own template and branding, ready for the partner to review and write the commentary rather than rebuild the numbers.

02

Recovery by job and by client

Time recorded against what was billed, so the jobs you are losing money on stop being a feeling and start being a list.

03

Work in progress and lock-up

Unbilled time and unpaid invoices tracked together, because separately neither one tells you what the practice is owed.

04

Fee mix over time

What share of income is compliance, advisory, payroll and one-off, and which way each is moving. The number that decides what the firm is worth when you come to sell it.

05

Client profitability

Fees against the hours actually spent, including the client who rings four times a week.

06

A partner dashboard that gets looked at

One page, updated overnight, with the six numbers that matter. Anything longer stops getting opened.

Proof

The reporting a practice owner actually wanted

Buzz OS was built because the numbers that run a practice were spread across four systems and a spreadsheet. The reporting in it is the reporting Andy needed to run his own firm.

os.buzzaccounting.co.uk — job planner
The reporting a practice owner actually wanted
Case study

The practice operating system

Twenty-plus modules, 487 live clients, six AI agents and full HMRC Making Tax Digital filing. Replaced every piece of third-party practice software.

Read the case study →
Straight answers

The things people ask.

Which systems can you read?

Practice management, time recording, the ledgers your clients are on, and your own accounts. The technical audit establishes what each will actually give up — an API, a scheduled export, or nothing — before anybody commits to a build.

We do not record time properly. Is this pointless?

Partly. Recovery and profitability need time data to mean anything. Fee mix, lock-up and debtors do not, and those alone are usually worth having.

Is this a Power BI project?

It can be, and often it does not need to be. What matters is that the data is joined and owned by you; the front end is whatever you will actually open.

Who owns the data?

You do, along with the code. That is the whole point of building it rather than renting it.

Read more

Written on this, at length.

Get started

Tell us what's eating your week.

Tell us the job that keeps not getting done. We'll tell you if software can take it off you, and what it costs.

Straight to Andy, who'd be the one building it. No obligation, no follow-up sequence.