Two people review paper documents at a table in San Francisco
Illustrative document review in San Francisco, photographed by Olena Kholina / Unsplash, under the Unsplash License. The people shown are not participants in the hypothetical case.

An AI subscription can help someone do their job. Its price cannot tell you what it would cost to run the business without them.

Consider a hypothetical distributor whose accounts clerk handles a disputed invoice. An AI tool reads the customer’s email, finds the invoice and drafts a polite reply in seconds. The manager sees the speed and starts comparing the software bill with the clerk’s salary.

The clerk also knows that the customer trades under two names, that a delivery was split, and that the warehouse supervisor keeps proof of the second delivery in a separate folder. The credit note needs approval. Someone must reconcile the payment and make sure the customer receives the correction.

A fast reply leaves much of that work unfinished. Remove the clerk before mapping it, and the business may discover that the person was also the connection between systems that never properly talked to each other.

Comparing the software bill with the salary counts the visible output and loses the work required to make it useful.

First, know what the bill buys

A token is a unit a model uses to process information, often a word or part of a word for text. A subscription buys access under a product’s plan and limits. An application programming interface, or API, lets software call a model. Its bill can depend on input and output tokens, tools, storage and other services.

These are different purchasing arrangements. For example, OpenAI bills API usage separately from ChatGPT subscriptions. Paying for one does not include the other. OpenAI billing documentation

Neither bill, by itself, buys a completed business process. Someone still has to provide the right records, set permissions, connect systems, test the output and decide what happens when the tool cannot finish.

The work you cannot see in a demo

A job bundles tasks, relationships and responsibility. The same person may process routine requests, spot an unusual pattern, explain a decision and rescue a failed handover. Automating the first task does not establish that the others have disappeared.

Return to the invoice. The useful endpoint is a correctly resolved account, with approval and records in place. A generated email is an intermediate output. If the AI prepares it in seconds but an employee spends half an hour checking mismatched records, the demonstration has measured only part of the process.

Tacit knowledge is what people know how to do without having fully written it down: which document is trustworthy, which exception matters and who can settle a dispute. Some can be documented and put into a reliable system. That requires work with the people who hold it, before their knowledge is lost.

Follow the whole invoiceSix steps run from customer query to confirmed resolution. Missing evidence at reconciliation routes to an owner before the process continues. The diagram is illustrative.Follow the whole invoiceA draft reply is one part of the process.01Receive the queryRecord the customer’s issue.02Retrieve the evidenceFind invoice and delivery records.03Reconcile the discrepancyCheck what differs and why.04Authorise the correctionKeep the approval boundary.05Update the accountRecord the authorised change.06Confirm resolutionCheck that the case is complete.Missing evidence? Pause and assign an owner.Return to reconciliation before approval.Conceptual workflow. No measured performance shown.
Invoice workflow with an exception route for missing evidence.

Follow the whole invoice. AI can assist preparation; missing evidence needs an owner before work proceeds. Conceptual illustration, not a measured deployment.

Read the employment claims carefully

Klarna provides a useful warning against loose arithmetic. Its 2025 IPO prospectus reported that full-time employment fell from 5,527 at the end of 2022 to 3,098 by June 2025, linking the reduction to a strategy that included AI. Its estimate of work equivalent to more than 700 agents was based on reduced human-handled conversations, not a count of 700 people fired. Klarna prospectus, pages 152 and 247

Its later annual report says AI handled 80% of customer-service chats during 2025, while customers could still choose human support. Those are company-reported results, not an independent experiment. They do not establish a simple story in which AI replaced everyone, failed and forced the company to rehire them. Klarna 2025 annual report, page 184

A company can achieve genuine automation savings and still need people. Before borrowing its staffing assumptions, examine the dependencies in your own operation.

Count the cost of getting it right

Build the comparison around a completed outcome that meets the business’s quality standard. Include implementation, data cleanup, integration and training. Add recurring model or subscription charges, maintenance, monitoring, human review and exception handling. Include the effort to correct errors and maintain a fallback when the service is unavailable.

Compare that with the current process on the same basis. People make mistakes too, and existing software has costs. The comparison should count both rather than loading every imperfection onto one side.

Count the whole operating costSix equally sized boxes name model access, implementation, integration, review and exceptions, maintenance, and recovery. Equal boxes are categories, not measured cost shares.Count the whole operating costModel access sits inside a wider budget.AccessSubscription or API usageImplementationDesign, data preparation and trainingIntegrationConnect records, tools and permissionsReview and exceptionsCheck outputs and resolve failuresMaintenanceMonitor changes and update the systemRecoveryRestore service and correct mistakesCategories only. Box area does not represent cost.Apply the same cost boundary to the current process.
Model access shown within the wider costs of operating an AI workflow.

Model access is one cost category. The diagram shows what to count, not how much each category costs.

Then measure cost per correctly completed case, alongside quality and completion time. Track reopened cases and serious errors separately. A low average cost does not make an unacceptable privacy breach or unauthorised payment acceptable.

Test with your people before redesigning their jobs

Start with one workflow and record how it performs now. Include ordinary cases and awkward ones: incomplete documents, conflicting records, an unavailable system and a request outside policy.

Run a limited trial with staff. Keep the same quality standard and record the time spent checking, correcting and escalating the AI’s work. Decide in advance who owns each exception and what would stop the trial. Give reviewers enough time and authority to reject an output; a person clicking “approve” under pressure is a weak safeguard.

A 2025 study of 5,172 customer-support agents found a 15% average increase in issues resolved per hour with AI assistance. Results varied by experience, and the agents remained responsible for the conversation. This was one firm and one tool, not a universal productivity promise. Brynjolfsson, Li and Raymond, Generative AI at Work

In your own trial, check whether the team resolves more cases correctly and spends less time chasing information. Decide where any recovered capacity is useful. It may reduce a backlog, improve service or let an experienced employee coach someone new. Time saved becomes a business benefit only when there is a credible plan to use it.

For a first check, use the AI Subscription Value Calculator. Enter your actual fee, net time saved after checking and rework, and a chosen hourly value in the same currency. In a hypothetical example, a JMD 3,000 monthly fee, four net hours saved and a JMD 2,000 hourly value produce JMD 8,000 of time value and JMD 5,000 after the fee. These are illustrative inputs, not market prices or measured savings. The calculator excludes other costs and risks, so carry those into your workflow comparison. Its result does not establish a person’s value or justify a staffing cut.

Before putting a salary beside a token bill, ask the employee to walk you through a difficult case from start to finish. Write down everything the demo left out. That is the process your AI investment must improve.

More research

Analysis. The invoice example and diagrams are illustrative. Sources checked on 28 October 2026.

Sources & further reading

token ↗OpenAI billing documentation ↗Klarna prospectus, pages 152 and 247 ↗Klarna 2025 annual report, page 184 ↗Brynjolfsson, Li and Raymond, Generative AI at Work ↗ILO: Generative AI and jobs, 2025 update ↗

Sources checked 2026-10-28. Sources checked on 28 October 2026. Analysis and hypothetical examples are labelled.

KEEP GOING

I Am Three Minds About AI →