Payroll is visible. The work around the work is not. People switch tools, copy fields, chase updates, redo mistakes, and wait on someone else to answer a lead. None of that shows up as a named line on the P&L. It still consumes hours that were paid for high-value work.
The Human Work Tax diagnostic exists to make that burden specific enough to argue with. You complete a short interview. The engine runs once. You get a tax bill, ranked leaks, scores, and a 90-day plan. You do not get a live calculator, a guaranteed savings figure, or a recommendation to cut headcount.
This article explains what Human Work Tax is, how to read a diagnosis, and how not to misuse the number.
What Human Work Tax is
Use this definition throughout: Human Work Tax is the estimated annual economic burden created by repetitive, manual, and inefficient work performed by people inside a business.
The 20X V1 diagnosis can include:
- repetitive-work burden
- context-switching burden
- error and rework burden
- coordination burden
- delay burden as labour (extra handling, waiting) — not automatically lost revenue
- other friction (copy/paste between systems)
It can also estimate opportunity exposure — unanswered demand and time spent off highest-value work. That figure is separate from the headline tax. Do not add it twice and call the sum “what we would save.”
V1 does not invent attrition tax or training tax. If the product does not ask about turnover, it must not fabricate a turnover cost.
Say: “Your estimated Human Work Tax is ₹X/year.”
Do not say: “You are wasting ₹X.” Do not say: “Save ₹X with AI.”
The number is an estimate of burden. Burden might be recovered as output, as service speed, as less overtime, or not recovered at all if you do nothing operational with the hours. That is why the diagnostic is a diagnosis, not a quote.
This is not a calculator with a form attached
20X already has calculators. The AI Agent ROI Calculator, Speed-to-Lead Calculator, Appointment No-Show Calculator, and Voice AI Cost Estimator are live sliders next to a number. You change an input; the panel updates. That is the right shape when the job is “price one workflow.”
Human Work Tax is a different job. The job is “what is the tax on work around the work, and where does it leak?” That needs an interview and a report.
On the diagnostic you will see six stages:
- Business profile — type of business, employee-count range
- Workforce economics — currency, monthly cost range, weekly hours, share of time on repetitive/admin work
- Business volume — ranges for leads, calls, WhatsApp, support, appointments, follow-ups, quotations, transactions (only the fields that apply to your industry). I don’t know is allowed; the engine uses a conservative default
- Manual work — sales, support, and operations workflows: how automated they are, and time consumed when they are not fully automated
- Operational friction — switching systems, copy/paste, rework, chasing updates, delayed response
- Opportunity leakage — delayed follow-ups, unanswered leads, time off highest-value work, manager coordination of routine work
Then you choose See my diagnosis. The engine runs. The intake disappears. The report is the product.
There is no result panel ticking up while you still have four stages left. If you wanted that feeling, you opened the wrong tool — and that is fine. Use a calculator for one workflow after you know which leak matters.
Progress, back, continue, and session persistence are there so a 2–4 minute pass is actually finishable on a phone. Keyboard access is the same as the other public tools: you can move without hunting for a tiny hit target.
How to read the diagnosis
The report opens with YOUR HUMAN WORK TAX and an annual figure in your currency, plus monthly, working-day, and working-hour equivalents. Under that sits the trust line: this is an estimate based on your inputs. It is not guaranteed savings and not a recommendation to reduce headcount.
Then read in this order:
The breakdown. Where the tax comes from — repetitive work, context switching, coordination, errors and rework, delays, other. Percentages are shares of the headline tax, not shares of revenue.
The tax bill. Same components as a table. Use this when you need to put the diagnosis next to someone who only reads tables.
The leaks. Each leak is a workflow, an estimated annual burden, automation suitability, capacity hours per month, and a recommended existing 20X solution (lead qualification, appointment booking, customer support, or internal operations). The diagnostic does not invent new agent products for the slide.
The 40% card. Labelled illustrative potential impact. If a large share of the identified workload were eliminated, the economic impact could be on the order of 40% of the tax — depending on how recovered capacity is used. It is not “you will save 40%.” It is not a payroll cut.
Today versus 20X. Driven by your top leak, not a stock story about a generic lead. If your biggest leak is follow-up, the comparison is a follow-up story.
Recommendations and the 90-day plan. Three months: obvious manual work, then repetitive customer workflows, then optimize and expand. Hours per month on each phase are estimates of workload, not invoices.
Opportunity exposure. Shown separately. Unanswered leads and time off highest-value work can be large and still must not inflate the headline tax. Delay tax in the bill is labour. Lost-revenue stories belong in speed-to-lead or no-show calculators, with their own documented assumptions.
The email gate. “Get your complete Human Work Tax diagnostic report.” The headline finding is already on the page. The gate is the full write-up, not a hostage number.
Share the public finding (tax + top leak language on the card). Do not paste payroll, names, or private volume into a public URL. Unique stored share links and a benchmark warehouse are not this version.
How the engine thinks (without turning the page into a spreadsheet)
Formulas live in the engine, not in the UI. Assumptions — working days, productive-hour fraction, midpoints for ranges, minutes per switch, rework duration, industry and size modifiers, “I don’t know” defaults — are configuration. Change them in config; do not hard-code a rate in a React component.
Employee count and monthly cost are ranges with midpoints. Weekly hours default to 40 and can be changed. Volume “I don’t know” is a conservative midpoint, not an optimistic one.
Manual workflows that are fully automated drop out of the leak list. Mostly-manual workflows with volume attached rank higher. Leak burdens are scaled so they describe a located share of the headline tax rather than a second, larger universe of cost.
Scores (work-elimination, automation-readiness, opportunity) are 0–100 heuristics from your answers. They are not a measurement of a live agent and not a substitute for the Automation Opportunity Quiz, which sequences which workflow to automate first.
Currencies: INR, USD, GBP, EUR, AED, and Other. Figures format in the currency you picked. Do not screenshot an INR run and present it as USD.
How this sits next to the other free tools
Three different questions:
- Which workflow first? Quiz.
- What does one workflow cost to run vs automate? ROI / voice / speed-to-lead / no-show calculators.
- What is the tax on work around the work? This diagnostic.
If you skip the diagnostic and go straight to ROI, you will price a loud workflow. If you skip ROI after the diagnostic, you will have a tax bill and no unit economics for the first agent. If you skip the quiz, you may automate a leak that is expensive but unstable.
None of these tools deploy an agent. Start free or book a strategy call if the diagnosis is large enough to design around.
Who should use this diagnostic?
Founders and operators who feel busy without a named bottleneck. COOs who are asked “what would AI save?” and do not want to invent a savings quote. Consultants who need a structured interview before a scoping call.
Skip it if you already know the one workflow and only need a rupee figure — use ROI. Skip it if you have almost no team and almost no volume; the midpoints will still produce a number, but it will not be a useful argument.
Common mistakes
Reading the tax as cash you can fire. Recovered capacity is not a headcount plan. The copy on the page is there because this mistake is the default.
Adding opportunity exposure to the headline and presenting the sum as “the real number.” The split is the methodology.
Treating 40% as a 20X guarantee. It is an illustration. Say that.
Filling “I don’t know” on everything and then defending the output to one decimal place. Conservative defaults keep the engine from failing. They do not make a precise audit.
Comparing this number to a voice-minute invoice. Different job. Voice cost is minutes and staff rate. This is burden on work around the work.
Leaving the leaks unread. The total without a leak is a vibe. The leak is the diagnosis.
Who this is for, again, in one paragraph
If your team is spending the week on follow-up, copy/paste, and chasing updates, you already know the tax exists. The diagnostic will not surprise you with a new emotion. It will put a defensible estimate on the page, show which workflows are carrying it, and refuse to pretend the estimate is a savings quote. That is the product.
Start the Human Work Tax diagnostic — no account. Then take the quiz to sequence a leak, price one workflow, start free, or book a strategy call to review the diagnosis against live operations.
Frequently asked
Questions, answered.
- It is the estimated annual economic burden created by repetitive, manual, and inefficient work inside a business. The 20X diagnostic prices labour associated with that burden. It does not claim the figure can be removed from payroll.
Written by
20X team
Editorial · Setoo
20X is built by operators, engineers, and consultants at Setoo. We write about the operational work AI agents should complete — not the slogans around them.