Why Is Your Team Still the Conveyor Belt Inside Karbon?

You bought Karbon because you were promised one place where the whole firm could see the work. On that promise it delivers. The triage is the best in its category, the templates are genuinely good, and having email sit next to the job is the feature people refuse to give up once they have it.

Now the uncomfortable part. Karbon is an excellent place to put work. It is a poor assistant. And the difference between those two things is being paid for by your staff, every day, in hours.

Here is the proof, and it comes from Karbon's own documentation rather than from a competitor. An automator in Karbon can do four things: change a status, change a due date, change who a job is assigned to, and switch a section of tasks on. That is the entire list. It moves the card across the board. It does not do the work on the card.

So your team is the conveyor belt. Somebody drags the job from "Awaiting Documents" to "In Progress." Somebody sets up the folder and the channel for every new client by hand. Somebody types the client's name into the email, because there is no placeholder that fills it in. And when a client uploads their documents, they land in exactly the right place and then wait for a trained accountant to open them and retype what is inside into your tax software.

Here is what matters most:

• Karbon's automators change a status, a date, an assignee, or switch on a set of tasks. Nothing else.
• Karbon's own survey claims 18.5 hours saved per employee per week. Only 1.8 of those hours are attributed to automating admin work. Its own automation page states that same figure as 2.5. Two of the vendor's pages disagree about the same survey.
• Automators and automatic client reminders are not on the entry plan. The cheaper tier is the one that still makes you chase by hand.
• Karbon lists no integration with Lacerte, UltraTax CS, Drake, ProSystem fx or ProSeries. CCH Axcess is still marked coming soon.
• The work firms have actually removed did not happen inside Karbon. It happened in the layer around it, and Karbon stayed exactly where it was.

A destination, not an assistant

Look closely at Karbon's own 18.5 hours figure, because it is the most honest thing on their website. Of that weekly total, the amount credited to automating admin work is 1.8 hours. The rest is email, collaboration, and finding files faster. In other words the vendor's own number says the product mostly helps you locate work and talk about it. Which is what a destination does.

That is not a criticism of Karbon so much as a description of what it is. The trouble starts when a firm assumes that buying the destination also bought the assistant, then staffs the gap with people. A partner closes a deal, and a trained accountant spends the next forty minutes creating records. A client sends a folder of documents, and a preparer becomes a typist. A job gets marked complete, and three other systems find out only because somebody remembered to tell them.

Every one of those is a job. Not a status. A job that currently belongs to a person on your payroll.

What three firms actually removed

Skip the theory. These are named firms in Karbon's own customer stories, describing their own before and after, in their own words. The numbers are theirs.

The invoice that took five minutes, every single time. At Loewen Kruse in Vancouver the routine was: a partner finishes the work, an administrator saves the invoice as a PDF, files it in the client folder, looks up which contact gets billed, writes the email, attaches the file, sends it. Three to five minutes, forever. Work in progress lived in shared Outlook folders. Their director Curtis Braun afterwards: "Because we're not hiring the seasonal admin role, we're saving at least 350 hours." He also reported work in progress down 40% and receivables up 40%. Admin went from roughly three people to one and a half.

The checklist nobody needed to read. At 542 Partners in Sydney, three staff worked a 20 to 25 point checklist on every client file, every period, mostly confirming that things were fine. Now only exceptions surface. Stuart Brandman: "We would typically have had three dedicated processing staff doing period close checks. That has now reduced to one, because they're typically only needing to look at the rectification steps required rather than ticking off a 20-to-25-point checklist."

Onboarding that took a month. Tabatha Morrison at Tabworks: "Before Karbon, client onboarding took a month and we still weren't getting paid. Now, we're at 5 days from when a person contacts us." That firm added 20% more clients on 4% more staff.

Not one of those is a status changing colour. Each is work that used to belong to a person and now does not.

The three pipelines that sit around Karbon

Almost everything a partner asks us for falls into one of three. None of them happen inside Karbon on its own, and all three leave your Karbon setup untouched.

A new client exists before anyone touches a keyboard. An engagement gets signed. The organisation and its people appear, correctly spelled, in every system that needs them. The right template drops in, with the scope from the contract rather than the scope somebody remembered. Staff get assigned by role. The partner gets told it is live. One firm owner described doing all of this by hand for every client, then wiring it together with a connector tool, and said the chain "breaks all the time." That is the difference between a shortcut and a system.

Documents turn into a job that is ready to prep. Client documents arrive in a mess, as they always will. They get read, sorted, and attached to the right job, and the figures on their face get written into the fields your preparer actually uses. The job flips to ready only when it genuinely is. Your preparer opens a compiled file instead of a folder. This is the one Karbon concedes most openly: on Karbon's own integrations page, the job of getting client documents into the tax return is advertised as another company's product, and the document-reading it now offers arrives through a partner rather than from Karbon. It matters more because of what else is missing from that page. With no Lacerte, UltraTax, Drake or ProSystem fx integration listed and CCH Axcess still coming soon, if you prep in anything but ProConnect then the bridge between the documents and the return is a person. That is the same work as any tax document automation for a CPA firm, and at volume it pays back fastest.

Finishing a job actually finishes it everywhere. A senior marks the work complete and the rest of the firm updates itself: the client record, the billing, the partner who was waiting to have an advisory conversation. Right now that ripple is a person's memory. One note on this one, because precision matters: Karbon will not let an outside system raise an invoice inside Karbon, so the billing half of this only works where your billing genuinely lives, in QuickBooks, Xero or your proposal tool. Anyone who tells you otherwise has not tried it.

Each of those deserves its own article and will get one. The pattern is the same in all three: Karbon keeps being the board, and stops being the labour.

You do not need to know how the plumbing works

Here is the part I want to be straight about, because it is where most agencies start showing off.

You do not need to understand how any of this is wired, any more than you need to understand municipal water pressure to fill a glass. You do not need to hire a developer, and you should not spend a weekend reading technical documentation. Knowing the blueprint does not help you run a better firm. It just moves your attention to the one place where your judgement adds nothing.

What you do need is to be able to judge two things. First, whether the work being removed costs you more than the removal does. Second, what happens when it breaks. On that second point, be suspicious of anyone who says there is no risk, including us. Things fail. What matters is how they fail. Built properly, a stalled step means the job sits where it is and your team does what it does today. Nothing gets deleted, nothing files itself, and no client hears from a machine having a bad day. The failure mode is that you are back to manual for an afternoon, which is where you are permanently right now.

What it is costing you, in your own numbers

I am not going to hand you an hours-saved figure, because I would be inventing it, and this industry has enough invented figures in it. Karbon cannot even keep its own two pages consistent about the same survey.

Do this instead. It takes one meeting. Pick the three things above that annoy your team most. For each, ask the person who actually does the work how long it takes and how often it happens. Multiply by what that person costs per hour. Not the partner rate. The real cost of the person doing it.

Then ask the question that matters more in a compressed season: what would that person do with the time instead? If the answer is work you currently turn away, it pays for itself twice, because you have converted administration into capacity. If the answer is that they go home in March, that is also worth paying for, and you should say so out loud instead of dressing it up as a revenue case.

Keep Karbon. That is the entire point.

All of the above may read like a case for switching. It is the opposite.

Search Karbon's limitations and you get page after page written by firms selling a replacement, because there is nobody else in that conversation. That is a poor way to make the decision. Karbon's triage is genuinely the best in its class, and the firms who run it well talk about it in warm terms. One director said "Karbon makes the cracks impossible to ignore." A principal called it "my brain outside my body." You do not throw that away because the automation stops short of the work.

Migrating is also the most expensive answer on the table. It costs the implementation you already paid for, the templates you already built, the training your team already absorbed, and a season of everyone being slower. Firms who have done it twice say so bluntly.

The cheaper answer is to keep the board you like and build the missing worker beside it. Credit where due: Karbon shipped real extension handling across 2025, including standardised due and extension dates and bulk extension updates, and its chief product officer said publicly that "the way most tax firms run today is broken and we're fixing that." I believe they will keep closing gaps. But the agents they have announced are in early access with no published date and no published price, and your next filing season is already on the calendar.

FAQ

Is this just Zapier with extra steps?

No, and the difference is exactly where firms get burned. A connector tool copies a record from one place to another, which is useful and worth doing. What it cannot do is hold a process together when something goes wrong, and in a firm something always goes wrong. A client sends last year's statement, a name does not match between two systems, somebody replies to the notification instead of uploading the file. The firm owner quoted earlier had wired his onboarding together with a connector and said the chain breaks all the time. That is not a knock on the tool, it is a description of what those tools are for. A system built for a firm expects the mess and routes it to a person with the context already attached.

Will this break when Karbon ships an update?

Anything connected to anything can break, so the honest question is who is responsible when it does. The failure we see most often is not technical at all: a firm's cleverest person builds something that works beautifully, and then they leave. One practitioner put it well when discussing who maintains a firm's workflows. If the answer is everyone, the answer is nobody. Ask any vendor, us included, who owns it after go live, who watches it, and what happens the week that person is on holiday.

We already pay for Karbon. Why pay for something else on top?

Because the two are priced against different things. Karbon is priced per person per month, forever, whether or not that person is full time, which is why paying a full seat for the bookkeeper who works Tuesdays irritates so many firm owners. What you build alongside it is priced against a specific job you currently pay salaried people to do by hand. The test is not whether it adds a line to your software bill. It is whether the work it removes costs more than that line.

Does our team have to learn another system?

They should not have to, and if they do, it has been built wrong. The reason to put this beside Karbon rather than on top of it is that Karbon stays the screen everybody opens. Work still appears in triage, jobs still move through your statuses, the same person still approves the same things. What changes is that fewer items need a human to move them along, and the ones that do arrive with the missing piece already identified.

Read next: AI Automation for CPA & Accounting Firms