What Is Your Human Work Tax?

Payroll is visible. The work around the work is not. People switch between tools, copy fields across, chase updates, redo mistakes, and wait on someone else to answer an enquiry. None of that appears as a named line on your accounts. It still uses hours you paid for to do valuable work.

The Human Work Tax diagnostic makes that burden specific enough to argue with. You answer a short set of questions and get a figure, a ranked list of where it leaks, and a 90-day plan. You do not get a savings guarantee or a recommendation to cut jobs.

What the figure means

Human Work Tax is the estimated annual cost created by repetitive, manual, and inefficient work done by people inside your business. That includes repeat tasks, the time lost switching between systems, mistakes and the rework they cause, coordination, and the extra handling that delays create.

The report also estimates the revenue you may be missing through unanswered demand and time spent away from your highest-value work. That is shown separately and on purpose. Adding the two together and calling the total "what we would save" is the most common way this figure gets misused.

Say your estimated Human Work Tax is a certain amount a year. Do not say you are wasting that amount, and do not say AI will save it. The burden might come back as output, as faster service, as less overtime, or not at all if nothing changes operationally. That is why this is a diagnosis rather than a quote.

Why it is not a slider

The other free tools are live calculators, and that is the right shape when the job is pricing one workflow: the ROI calculator, the speed-to-lead calculator, the no-show calculator, and the voice cost estimator.

This job is different. The question is what the work around the work costs and where it leaks, and that needs a few minutes of context first: what kind of business you run, roughly what your team costs and how many hours they work, the volumes you handle, which workflows are still manual, where the friction sits, and where opportunity leaks away. Where you genuinely do not know a volume, saying so is fine, and the model uses a cautious assumption rather than a flattering one.

Then you ask to see the diagnosis. The questions disappear and the report is the product. It takes two to four minutes and works on a phone.

How to read the diagnosis

It opens with your annual figure, plus monthly, daily, and hourly equivalents, and the line reminding you it is an estimate rather than guaranteed savings.

After that, read in this order.

The breakdown. Where the burden comes from, as shares of the total rather than shares of revenue.

The leaks. Each one is a workflow with an estimated annual burden, how suitable it is for automation, the hours it could free each month, and which existing solution fits: lead qualification, appointment booking, customer support, or internal operations. This is the part worth arguing about. A total without leaks is just a mood.

The reduction illustration. It shows what the impact could look like if a large share of the identified work were removed, depending on how you use the recovered capacity. It is an illustration, not a forecast, and the numbers researchers publish on AI productivity carry the same caveat about how much depends on the operating changes around the tool (McKinsey on the economic potential of generative AI).

Today against a run with agents. This is built from your own largest leak. If follow-up is your worst leak, the comparison is a follow-up story.

The plan. Three months: the obvious manual work, then repetitive customer workflows, then tightening and expanding. The hours shown are estimates of workload, not invoices.

The headline finding is already on the page. Emailing yourself the full write-up is optional. When you share the public finding, share the tax and the top leak, not payroll figures or names.

Where it sits next to the other tools

Three different questions. Which workflow first is the quiz. What one workflow costs to run or automate is the calculators. What the work around the work costs is this diagnostic.

Skip the diagnostic and you will price whichever workflow was loudest. Skip the calculators afterwards and you will have a figure but no unit economics for the first agent. The order matters more than the tools.

Who should use it

Owners and operators who feel busy without a named bottleneck. Operations leads asked what AI would save, who do not want to invent a number. Consultants who want a structured conversation before scoping.

Skip it if you already know the one workflow and only need a rupee figure, and skip it if you have almost no team and almost no volume, because the cautious assumptions will still produce a number that is not a useful argument.

Two warnings worth repeating. Answering "I do not know" everywhere and then defending the output to the decimal point is not an audit. And reading the total while ignoring the leaks wastes the whole exercise.

Start the Human Work Tax diagnostic. Then sequence a leak, price one workflow, start free, or book a strategy call to review the diagnosis against live operations.

What to do in the first week

The diagnosis is only useful if something changes. Three steps are usually enough to start.

Show the leaks to the people inside them. The person who chases updates all day already knows the leak exists. What they do not know is that it has a number attached, and they will correct your assumptions faster than any analysis.

Pick one leak, not the biggest total. The right first choice is the leak that is large, predictable, and inside your control. A large leak that depends on another department's process is a second-quarter project.

Write the rule. Before anything is built, write down in one sentence what should happen automatically and where a person steps in. That single sentence prevents most of the disappointment that follows automation projects.

How to talk about the figure internally

The figure invites two bad conversations. One is a finance conversation about payroll, which this is not. The other is a vendor conversation about a platform, which is premature.

The conversation you want is operational. Here is where the hours go, here is the workflow carrying most of it, here is what we would change first, and here is the one number we will check in four weeks. Present it that way and the estimate stays useful even if people argue with the total, because the leaks stand on their own.

If someone asks what AI would save, the honest answer is that nobody can say until one workflow has run for a month. That answer earns more trust than a confident percentage.

Why the burden is so easy to miss

Nothing in the burden looks like waste while it is happening. Checking a record twice is diligence. Chasing an update is being on top of things. Copying a field between two systems is just how the systems are. Each one is a few minutes, done by someone competent, for a sensible reason.

That is exactly why it never reaches a management meeting. It has no owner and no line item, and everybody involved is doing their job. Putting a figure on it is not an accusation. It is the only way the work around the work gets discussed at all.

When to use the diagnostic again

Run it once to find the leaks. Run it again after two or three months of change, on the same definitions, to see whether the shape has shifted rather than only the total. Shape matters more: if repetitive work drops and coordination rises, you have automated the task and left the handover alone, which is a fixable and very common outcome.

Beyond that, annual is plenty. This is not a dashboard.

What acting on it costs

Nothing about the diagnostic requires a purchase. If you do act on it, the spend splits in two. The platform runs on usage, billed in tokens where 1 token is ₹3 and a standard voice minute inside a package costs about one token, with top-ups that do not expire. A package fee, if you use one, pays for the people who design and build the workflow with you: Explore at ₹4,999 for a discovery session, Start at ₹25,000 plus ₹9,999 a month for a first workflow live, then Transform at ₹75,000 plus ₹24,999 a month and Scale from ₹1,50,000 plus ₹49,999 a month for wider programmes.

Price the first leak against that before committing anything. A diagnosis that leads to one well-chosen workflow is worth more than one that leads to a programme nobody finishes.