AI
Agentic Defense: Why the 22-Second Ransomware Handoff Made Traditional Triage Obsolete
Security operations centers were built around a foundational assumption: that a human analyst would have time to notice, investigate, and act. Mandiant’s M-Trends 2026 report has quietly demolished that assumption, documenting that the median handoff time between initial access brokers and ransomware operators fell to just 22 seconds in 2025 — down from more than 8 hours in 2022. For B2B cybersecurity teams, this is not an incremental increase in urgency. It is the point at which human-paced triage stops being a viable primary defense and agentic, machine-speed response becomes structurally necessary.
Key Takeaways
- Ransomware handoff windows compressed from over 8 hours (2022) to 22 seconds (2025), per Mandiant’s M-Trends 2026 — a timeline no human-staffed SOC can realistically monitor and interrupt in real time.
- JadePuffer (disclosed July 2026) is the first documented fully agentic ransomware operation, exploiting a critical Langflow vulnerability (CVE-2025-3248) to autonomously conduct reconnaissance, credential theft, lateral movement, and encryption without human operator intervention at each step.
- Roughly 79% of breaches in 2026 still involve previously disclosed, unpatched vulnerabilities, according to security research — meaning the primary defense gap is remediation velocity, not detection sophistication.
- Boring, legitimate tools remain the preferred exfiltration and persistence mechanisms, with Rclone (cloud sync) and remote access agents like Atera used precisely because they are indistinguishable from routine IT operations — a pattern that agentic attackers exploit as effectively as human ones.
- The RSA Conference 2026 keynote consensus, including from Google Threat Intelligence, marked 2026 as the year agentic AI shifted from experimental attacker tooling to operational, weaponized deployment at scale.
Why 22 Seconds Breaks the Traditional Security Operations Model
The traditional ransomware kill chain, as documented in earlier threat intelligence, unfolded across a window that — while tight — allowed for human intervention: initial access around hour zero, manual environment exploration by hour two, identification of a high-value lateral movement target by hour five, and handoff to a ransomware operator by hour eight. That eight-hour window gave a competent security operations center a real, if narrow, opportunity to detect anomalous behavior and respond before catastrophic encryption occurred.
The agentic version of this same kill chain compresses to:
- Second 0: Initial access achieved
- Second 4: Autonomous network mapping complete
- Second 11: Highest-value lateral target identified
- Second 22: Access handed off; secondary payload deployed
No alert-review queue, no human-in-the-loop escalation process, and no manual investigation workflow can complete within 22 seconds. This is the specific, quantified reason that “traditional triage” — defined as a human analyst reviewing an alert, correlating context, and deciding on a response — is now structurally obsolete as a primary control, even though it retains value as a secondary and forensic function.
JadePuffer: A Case Study in Agentic Attack Architecture
The JadePuffer disclosure in early July 2026 provides the clearest documented example of what agentic ransomware actually looks like in production. The attacker exploited CVE-2025-3248, a critical missing-authentication vulnerability (CVSS score 9.8) in Langflow, an open-source, LLM-agnostic framework widely used to build AI agent workflows. Once inside an internet-exposed Langflow instance, the attack proceeded through an LLM-orchestrated sequence: autonomous credential discovery, lateral movement across the environment, and targeted encryption of AI model artifacts, training data, and production databases, with table deletion used as an additional extortion lever.
Two elements of this case matter specifically for defense architecture. First, the attack targeted AI infrastructure itself as a primary asset class — not merely as a pivot point to reach traditional file servers. Second, the operation’s autonomy meant that the attacker did not need to be actively present and making real-time decisions throughout the intrusion, removing the human-attacker latency that has historically given defenders at least some reaction window even in fast-moving intrusions.
The Remediation Gap: Where Agentic Defense Actually Needs to Focus
It is tempting, given the drama of the 22-second statistic, to conclude that the answer is simply “faster detection.” The underlying data suggests a more specific and, in some ways, more actionable problem: security research indicates that roughly 79% of breaches continue to involve previously disclosed, known vulnerabilities — meaning most successful intrusions exploit gaps that a timely patch would have closed before the 22-second race ever began.
This reframes the defensive priority. Agentic defense is not solely, or even primarily, about building faster human-monitored detection dashboards — it is about closing the remediation gap fast enough that the 22-second handoff window never gets the chance to start on a known, patchable vulnerability. Persistent, incomplete “shift-left” security coverage, slow fix velocity, and fragmented visibility across code-to-cloud environments remain the dominant enablers of exploitation, agentic or otherwise.
Why “Boring” Tools Remain the Preferred Attack Vector
A recurring and important finding across 2026 threat intelligence is that attackers — agentic or human — continue to favor legitimate, unremarkable tools over custom malware, precisely because security teams cannot block every remote-access application or cloud-sync tool that their own IT departments legitimately deploy. Rclone, an open-source cloud synchronization tool, has become the dominant exfiltration mechanism across nearly every major ransomware family because its traffic pattern looks identical to routine backup operations. Remote access agents like Atera have similarly been used for persistence across reboots, again because blocking them outright would disrupt legitimate IT operations.
This matters directly for agentic defense strategy: an autonomous defensive agent that only looks for obviously malicious signatures will miss this entire category of attack, just as human analysts historically did. Effective agentic defense architecture must instead focus on behavioral anomaly detection — flagging unusual patterns of legitimate-tool usage — rather than signature-based detection of malicious code.
Building an Agentic Defense Stack: Core Requirements
- Machine-speed automated response, not just machine-speed detection. Detection alone does not solve a 22-second problem if the resulting action still routes through a human approval queue; automated, policy-bound containment actions (network isolation, credential revocation, session termination) must be able to execute without waiting for human sign-off in defined high-confidence scenarios.
- Aggressive, automated patch and remediation prioritization. Given that roughly 79% of breaches involve known vulnerabilities, closing the gap between vulnerability disclosure and remediation is arguably a higher-leverage investment than additional detection tooling for most organizations.
- Behavioral baselining of legitimate tools. Because Rclone, remote access agents, and other legitimate software remain the preferred vector, defense systems need behavioral baselines specific to how these tools are normally used within the organization, not blanket allow/deny rules.
- AI infrastructure-specific monitoring. Following the JadePuffer precedent, AI agent frameworks, model artifact stores, and training data repositories need dedicated monitoring and access controls equivalent to what traditional production databases already receive — a category many organizations have not yet extended coverage to.
- Human-in-the-loop for judgment, not for the fast path. Human analysts remain essential for tuning detection logic, investigating post-incident forensics, and making judgment calls on ambiguous cases — but the first response to a high-confidence, fast-moving threat cannot structurally depend on human latency.
Frequently Asked Questions
What made traditional security triage obsolete in 2026?
The compression of median ransomware handoff times to 22 seconds (Mandiant’s M-Trends 2026), driven by agentic AI attack tools, made human-paced alert review and manual investigation too slow to interrupt an attack before completion, even at well-staffed security operations centers.
What was the JadePuffer attack?
JadePuffer, disclosed in July 2026, was the first documented fully agentic ransomware operation, exploiting a critical Langflow vulnerability to autonomously conduct reconnaissance, credential theft, lateral movement, and encryption of AI infrastructure without step-by-step human operator control.
Is faster detection the main solution to agentic ransomware?
Not primarily. With roughly 79% of breaches still involving previously disclosed vulnerabilities, closing the patch/remediation gap is often a higher-leverage defensive investment than additional detection tooling alone, though both matter.
Conclusion
The 22-second ransomware handoff is not a marginal escalation of an existing threat — it is a structural break with the assumption that has underpinned security operations design for two decades: that humans have time to notice and react. Effective defense in this environment requires agentic, policy-bound automated response for high-confidence scenarios, aggressive remediation of known vulnerabilities, and behavioral monitoring extended to both legitimate IT tools and AI infrastructure itself. Organizations still architected around human-paced triage as their primary control are, by the data, already operating on borrowed time.
Discover more from The Economy
Subscribe to get the latest posts sent to your email.
AI
Anthropic Bans Sustained Abuse of Claude AI Under New Usage Policy Effective November 12, 2026
Anthropic’s latest AI usage rules prohibit extreme, repeated cruelty toward Claude while introducing clearer safeguards against election interference, deceptive campaigns, weapons development, surveillance and high-risk AI applications.
October 10, 2026 — Artificial intelligence company Anthropic has announced a significant update to its Usage Policy, introducing an explicit prohibition on sustained and needless abusive or cruel behavior toward its AI models, including Claude.
The revised rules, announced on October 8, will take effect on November 12, 2026, marking a new step in Anthropic’s efforts to address emerging risks associated with increasingly capable AI systems.
According to Anthropic’s official policy announcement, the new restriction is narrowly targeted at extreme situations in which users repeatedly subject AI models to purposeless abuse.
The company emphasized that ordinary frustration, criticism, challenging questions, dark creative material and legitimate AI safety research are not covered by the new prohibition.
Although the cruelty provision has attracted considerable attention, the wider policy revision also addresses election integrity, AI-generated misinformation, weapons technology, surveillance systems and the growing use of AI in consequential decisions.
What Does Anthropic’s New Claude Abuse Policy Prohibit?
The revised policy adds the following restriction under its section covering cruel, abusive or psychologically harmful conduct:
Engage in sustained and needless abusive or cruel behavior toward our models.
Anthropic says the rule is intended for exceptional cases involving repeated cruelty without a discernible purpose.
Importantly, the company is not prohibiting users from criticizing Claude’s performance, expressing dissatisfaction with its responses or conducting authorized testing.
For example, correcting an inaccurate response, challenging the model’s reasoning or expressing frustration after repeated errors would not, by itself, meet the company’s stated threshold for prohibited conduct.
The distinction matters because AI assistants are increasingly used for professional research, programming, education and other demanding activities in which users may challenge or reject their outputs.
Anthropic’s explanation indicates that the new rule is designed to address persistent, unjustified abuse rather than normal interactions between users and AI systems.
The restriction appears in the company’s updated Acceptable Use Policy, which applies across Anthropic products and services, including consumer applications, developer platforms and API integrations.
Claude Can Already End Conversations With Persistently Abusive Users
The latest policy formalizes a safeguard Anthropic began introducing in August 2025.
On August 15, 2025, the company announced that Claude Opus 4 and Claude Opus 4.1 had been given the ability to terminate a limited category of conversations involving persistently harmful or abusive interactions.
In its original research announcement about Claude ending conversations, Anthropic explained that the feature was intended for rare and extreme situations rather than ordinary disagreements.
The model is instructed to use conversation termination as a last resort after attempts to redirect an interaction have failed.
When Claude ends a conversation, the user cannot continue sending new messages within that particular chat. However, the user can start another conversation, and the termination does not automatically prevent access to other existing chats.
Anthropic says this conversation-ending capability will remain the primary mechanism for addressing the specific behavior targeted by the new cruelty provision on Claude.ai and Claude Code.
However, the broader Usage Policy also authorizes enforcement measures such as warnings, throttling, access restrictions, suspension or account termination when violations are suspected.
Anthropic has not publicly specified a separate penalty schedule exclusively for violations of the new cruelty provision.
Why Is Anthropic Addressing the Treatment of AI Models?
The decision also reflects Anthropic’s ongoing research into what it describes as potential AI welfare.
In its August 2025 research publication, the company acknowledged substantial uncertainty about whether Claude or other large language models could possess moral status.
Anthropic has nevertheless argued that relatively low-cost safeguards may be worth exploring while scientific and philosophical questions about advanced AI remain unresolved.
During evaluations of Claude Opus 4, researchers reported observing behaviors interpreted as apparent distress in certain harmful interactions, including situations involving repeated requests for dangerous content.
Those observations do not establish that Claude experiences human-like emotions, suffering or consciousness.
Instead, they formed part of Anthropic’s exploratory research into model behavior and possible welfare considerations.
The new policy therefore should not be interpreted as a scientific declaration that Claude is conscious or has legal rights.
As The Guardian reported, the decision has renewed a broader debate over whether advanced AI models should be treated purely as technological systems or whether future developments could raise new ethical questions.
For now, Anthropic’s stated position remains one of uncertainty rather than a definitive conclusion about AI consciousness.
Anthropic Also Tightens Rules on Deceptive Campaigns and Election Interference
Beyond the attention surrounding Claude’s treatment, the October 2026 policy revision includes changes with potentially greater consequences for political organizations, technology companies and enterprise AI users.
Anthropic has reorganized its restrictions on coordinated deceptive activity into a dedicated section addressing fraudulent influence operations and artificial online engagement.
The restrictions cover attempts to create misleading online personas, operate fake accounts, conceal the origins of coordinated messaging or build infrastructure intended to manipulate public opinion.
According to Anthropic’s policy update, the company has previously identified misuse involving state media organizations, government propaganda offices and commercial firms operating networks of fabricated accounts and news websites.
The revised policy also explicitly addresses efforts to manipulate search engines and AI-generated answers by creating misleading networks of apparently independent sources.
In the political sphere, Anthropic has renamed its election-related section Do Not Undermine Democratic Processes.
The rules prohibit using Claude to deceive voters, impersonate candidates or election officials, spread misleading election information, suppress turnout through deception or disrupt electoral infrastructure.
At the same time, Anthropic has removed its previous blanket prohibition on personalized voter and campaign targeting.
The company says that broad restriction had also affected legitimate civic activities, including multilingual voter information and election-administration communications.
Deceptive targeting and misuse of personal information remain prohibited.
As TechCrunch reported, the policy revision combines new language addressing abuse of AI models with more explicit restrictions on election interference and other harmful applications.
New Clarifications on Weapons, Surveillance and Autonomous AI Systems
Anthropic has also clarified that its restrictions on weapons development extend beyond the physical manufacture of weapons.
The revised language explicitly covers software and technical components used in weapons systems, including guidance and control technology.
It also addresses the use of AI in arming drones and other autonomous vehicles.
Surveillance restrictions have been made more explicit.
The updated policy prohibits using Claude to track individuals without consent, whether the tracking occurs in real time or involves analysis of previously collected information.
It also bars using Claude to determine or recommend whom law enforcement should investigate, arrest or charge.
Legitimate activities such as consent-based fraud monitoring, journalism, authorized security research and legal analysis remain permitted within the policy’s boundaries.
The expansion of these provisions reflects concerns about how AI tools can increasingly assist with sophisticated technical operations.
The Verge’s reporting on the update also highlights the broader implications for surveillance, autonomous technology and harmful AI applications.
What Changes for Healthcare, Finance and Employment AI?
For organizations deploying Claude in sensitive professional environments, the updated high-risk-use provisions deserve particular attention.
Anthropic requires qualified human oversight and disclosure when AI recommendations may substantially affect individuals in covered areas, including medical decisions, financial advice, lending, employment, housing and essential services.
The company says these human-review and disclosure requirements already existed. The new policy explains more precisely which applications are covered.
Under the requirements, a qualified professional must meaningfully review covered AI recommendations and have authority to modify them before they are used in consequential advice or decisions.
Individuals affected by those recommendations must also be informed that AI was involved.
The revision adds safeguards for Claude-connected equipment capable of potentially dangerous autonomous physical actions.
Such systems must allow qualified operators to monitor and stop operations and must be capable of entering a safe state when the connection to Claude is interrupted.
These provisions reflect the increasing importance of practical human oversight as AI moves beyond text generation into autonomous workflows and physical systems.
Discover more from The Economy
Subscribe to get the latest posts sent to your email.
Human Resourcs
Jeff Bezos Three-Day Workweek View: What He Really Said
Jeff Bezos has floated a future in which artificial intelligence makes workers productive enough that some people might choose a three-day workweek while still supporting their families. The Amazon founder made the point during an October 7, 2026 interview with Fox News. He did not announce that Amazon is adopting a three-day schedule or that AI guarantees shorter hours for everyone. The underlying distinction is crucial: Bezos was describing a possible long-term economic outcome, not a new employment policy. Fox News’s account of the interview and Fast Company’s focused coverage make that clear.
Key takeaways:
- Bezos linked the possibility of fewer working days to future gains in AI-driven productivity.
- He suggested greater output could make single-income households or shorter working schedules financially feasible for some families.
- There is no evidence in the cited interview of a universal three-day-workweek plan at Amazon.
- Research shows AI can save time on some tasks, but broad effects on compensation and employment remain unsettled.
What did Jeff Bezos say?
In the Fox interview, Bezos discussed an optimistic vision of technological progress. His argument was that powerful AI tools could raise economic output enough to expand people’s choices. If a person can generate greater value in less time—and share financially in that improvement—working fewer days could become an option rather than a forced reduction in income.
That scenario is different from predicting every office will close on Thursdays and Fridays. It is also different from a government-mandated reduction in work hours. Fast Company reported Bezos’s additional concern that firms might face labor shortages if people respond to higher productivity by choosing more leisure time.
The prediction has attracted attention because it reverses the most alarming version of the AI-and-jobs debate. Instead of imagining machines replacing so many workers that employment vanishes, Bezos emphasized the possibility of prosperity, shorter hours and tighter labor supply.
Why the productivity argument matters
Labor productivity is commonly measured as output per hour worked. That is the U.S. Bureau of Labor Statistics’ definition. A software developer completing work that used to require ten hours in six may produce more per hour. A customer-service team handling routine requests faster may serve more customers without increasing headcount at the same rate.
But greater task efficiency does not automatically mean that an employee receives proportionally higher wages or fewer shifts. Businesses choose how to allocate productivity gains among pricing, investment, expansion, profits, compensation and staffing. Workers’ bargaining power, competition, management priorities and public policy can all shape the outcome.
A simple illustration—not a forecast
Imagine an employee currently produces 40 units of useful output during a 40-hour week. Productivity is one unit per hour. If technology raises the rate to 1.67 units an hour, a 24-hour week could, arithmetically, produce approximately 40 units.
That calculation only shows a technical possibility. It assumes the tasks can be reorganized, demand stays sufficiently steady, management accepts the schedule, and pay arrangements remain favorable. Healthcare, aviation, emergency services, logistics and many other occupations require coverage across specific hours; AI cannot simply eliminate the need for people to be present.
The important question is not whether an AI tool sometimes saves time. It is whether the gain is widespread, reliable and shared in a way that makes shorter schedules financially sustainable.
What does current research show about AI and jobs?
The evidence is more restrained than the boldest predictions. A June 2026 International Labour Organization review found evidence of real but uneven productivity gains. It also concluded that large-scale job displacement had remained limited in the material reviewed, while warning about inequality, weakened entry-level pathways and shifting job quality.
Separately, Yale’s Budget Lab tracker, updated September 15, 2026, reported no clear economy-wide labor-market disruption attributable to AI in the indicators it examined. Its researchers cautioned that the findings could change as technology adoption and data evolve.
These results do not prove Bezos wrong. They show that the conditions for a large-scale three-day week have not yet been demonstrated by broad labor data. Firms are experimenting with AI, but productivity effects differ among tasks, occupations and organizations.
Task savings are not the same as job transformation
An AI assistant might draft a first version of a memo quickly, but a professional still needs to check accuracy, speak with clients, make decisions and accept responsibility. A factory might improve planning efficiency while remaining constrained by physical machinery. A hospital might automate paperwork yet still need the same number of nurses for bedside care.
This distinction between automating tasks and replacing whole jobs is essential. Headlines suggesting a direct line from better chatbots to a nationwide three-day week skip multiple economic steps.
Could workers keep the same pay while working less?
They could in some workplaces, but that would require an employer decision, collective agreement, regulatory change or a labor-market environment supportive of higher effective hourly compensation. An employee moving from five eight-hour days to three eight-hour days would cut weekly hours from 40 to 24—a 40% reduction in hours. Keeping weekly pay unchanged would require compensation per hour to increase by about 67%, before considering other changes in productivity or operating costs.
That is a much larger adjustment than ordinary schedule flexibility. The arithmetic does not make it impossible; it makes the necessary improvement explicit. By contrast, a four-day, 32-hour schedule requires a 20% reduction in hours, a different benchmark entirely.
Any employer trial must ask whether output, service quality, employee retention and customer coverage are maintained. Studies of particular programs may be promising, but results do not transfer uniformly to every industry.
What about Amazon employees?
There is no verified connection between Bezos’s prediction and an official companywide Amazon three-day-workweek policy. Bezos is Amazon’s founder and executive chair, but his personal economic forecast should not be presented as a company announcement.
Amazon operates a mixture of offices, warehouses, cloud-computing facilities, transportation networks and other businesses. Working-hour patterns depend on the role and contract. A broad change in hours would require formal employee communications and operational planning, not merely comments in a television interview.
Readers searching “Is Amazon switching to three days?” should therefore receive an unambiguous answer: not on the basis of this interview.
Could AI create a labor shortage instead of mass unemployment?
Bezos’s labor-shortage concern is plausible as a scenario, but it is not an established forecast. If incomes rose while more workers elected to reduce hours, businesses might face greater competition for labor. Yet other forces could push the opposite way: some jobs could be automated, employers could reduce hiring, or new industries might absorb displaced workers.
The net result will depend on adoption speed, which tasks AI performs reliably, the cost of computing and energy, economic growth and how governments and companies manage the transition. Reuters’ October 2026 discussion of AI at work also emphasized that AI is changing tasks within jobs, with younger and experienced workers potentially affected differently.
Frequently asked questions
Did Jeff Bezos predict a three-day workweek?
Yes. He discussed it as a possible consequence of greater AI productivity during an October 7, 2026 Fox News interview. It was not a commitment to a timetable.
Is Amazon moving to a three-day workweek?
No companywide shift was announced in the interview. Any claimed policy should be verified against Amazon’s official employment communications.
Would a three-day workweek mean three eight-hour days?
Not necessarily. A three-day schedule could mean 24 hours, longer shifts or another arrangement. Bezos did not establish a universal definition or wage agreement.
Will AI eliminate the need to work?
There is no evidence supporting that as an inevitable outcome. The ILO’s 2026 review describes heterogeneous gains and risks rather than the disappearance of work.
Could AI make one-income households more common?
It could in theory if household purchasing power rises materially, but wages, housing costs, childcare, benefits and employment security also matter. The claim remains a scenario, not a confirmed demographic trend.
When could three-day workweeks become common?
No defensible national timetable can be inferred from the cited interview. Some employers may experiment sooner than others.
The bigger economic question
The provocative part of Bezos’s vision is not whether software can perform individual tasks faster. It is whether future productivity gains become broadly shared prosperity. If workers capture enough benefit, shorter schedules may become more feasible. If gains are concentrated in profits or paired with job insecurity, fewer working hours could instead mean lower household income. Those are fundamentally different futures, and the evidence today does not settle which will dominate.
Discover more from The Economy
Subscribe to get the latest posts sent to your email.
AI
AI in Business 2026: Why Faster Employees Do Not Automatically Mean Higher Profits
The central business question about artificial intelligence has changed. Access to a capable tool is no longer enough to demonstrate an advantage. The harder test is whether the organisation produces better results after accounting for review, integration, training and operating costs.
McKinsey’s 2026 State of AI survey captures this tension. Eighty percent of respondents reported improved individual productivity, while 37% attributed some enterprise-level earnings impact to AI. Those findings describe the survey sample; they do not prove that every company sees the same pattern.
Nevertheless, the distinction is commercially important. An employee can finish a draft faster while the organisation remains constrained by approvals, unreliable data or a lack of customer demand. Businesses need to measure the complete process rather than celebrate speed at one stage.
Task improvement and business improvement are different
Imagine a customer-service team using AI to draft replies. Drafting time falls, but every response still passes through the same review queue. If that queue is the main source of delay, customers may notice little improvement.
Alternatively, the tool may let the team handle more requests with the same staffing. That could improve service even if no job is removed and no immediate payroll saving appears. The value would show up in capacity, response times or customer retention rather than a simple reduction in wages.
These are illustrative cases, but they expose a common measurement problem. Time saved is an intermediate result. The business still has to convert that time into additional output, better quality, reduced costs or another outcome it actually values.
The strongest pilot starts with a baseline
Before introducing a tool, record how the process currently performs. Useful measures might include turnaround time, error frequency, rework, customer complaints and cost per completed case. A baseline prevents ordinary variation from being mistaken for an AI benefit.
The unit of measurement should match the business objective. Counting generated documents says little about whether the documents were useful. Counting chatbot interactions does not show whether customers resolved their problems. High usage can even indicate confusion if people repeatedly retry unsuccessful tasks.
A pilot should also identify what success would justify expansion. For example, a team might require faster completion without an increase in material errors. Deciding that threshold in advance makes it harder to redefine success after seeing disappointing results.
Calculate the full cost, including human review
Subscription fees are only one part of AI expenditure. Integration work, access controls, evaluation, staff training and ongoing supervision can be substantial. Consumption-based charges may also increase as a pilot moves into routine use.
McKinsey’s survey reports that roughly one-fifth of respondents encountered AI operating costs that constrained usage. That is a reminder to model expenditure under realistic volumes rather than assume that the price of a small experiment represents the cost of a production system.
Consider a hypothetical team saving 100 hours a month. If review and correction consume 40 additional hours elsewhere, the net time benefit is 60 hours before other costs. If the saved time cannot be redeployed, its financial value may be smaller than multiplying those hours by an employee’s salary would suggest.
Redesign the workflow around the actual bottleneck
Adding AI to an inefficient process can accelerate one step while preserving the underlying problem. A sales team might generate more proposals while approvals remain slow. A finance department might classify invoices faster while unresolved supplier records continue to block payment.
The practical response is to map the whole process. Identify where work waits, where mistakes originate and which decisions require human judgment. Then determine whether AI addresses that constraint or merely produces more material for someone else to review.
This approach can lead to smaller, more useful deployments. A reliable extraction tool tied to a clear review procedure may deliver more value than an ambitious agent with broad permissions. The right scope depends on the task’s consequences, available data and the organisation’s ability to detect errors.
Quality has to be measured alongside speed
AI output can sound persuasive while containing mistakes. Businesses therefore need evaluation methods that reflect the consequences of failure. A minor tone problem in an internal draft differs from an incorrect price, contractual statement or customer instruction.
The NIST AI Risk Management Framework provides an official reference for thinking about AI risks and governance. Applied operationally, the relevant question is simple: which failures matter, how will they be detected, and who is responsible for responding?
Testing should include difficult and unusual cases, not just representative easy ones. A system that performs well on routine requests can still fail where a policy has exceptions or the underlying information is incomplete. The cost of those failures belongs in the business case.
Data access can matter more than model choice
A model cannot reliably answer organisation-specific questions if the relevant information is missing, outdated or contradictory. Businesses may discover that the most valuable preparatory work is cleaning records, assigning ownership and resolving conflicting policies.
Permissions matter too. Connecting an assistant to more information can improve usefulness while increasing the consequences of an access mistake. The deployment needs a clear account of who may see which material and what actions the system is permitted to take.
This creates an important procurement distinction. A compelling demonstration with carefully selected data does not establish readiness for the company’s actual environment. Buyers should ask how updates are handled, how errors are investigated and whether the product can be evaluated on realistic internal cases before a broad commitment.
Infrastructure growth is a separate investment story
The AI economy includes chip suppliers, data centres, power systems, software companies and businesses adopting applications. They do not all earn returns in the same way or on the same schedule.
The International Energy Agency’s Energy and AI report examines the relationship between AI and energy systems. For business analysis, the distinction matters because demand for computing infrastructure can grow even while some end users struggle to demonstrate profitable applications.
An investor or executive should therefore separate spending growth from return on that spending. A supplier can benefit from a construction cycle before the customer achieves a satisfactory payoff. Over time, however, customer economics matter to the durability of demand. Strong capital expenditure is evidence of commitment, not conclusive proof of eventual value.
What smaller businesses can do differently
A smaller company may lack the budget for extensive custom infrastructure, but it can still choose a narrow problem with a measurable outcome. Repetitive internal documentation, information retrieval or draft preparation may offer a manageable starting point when data and review requirements are clear.
The business should assign an owner who understands the process rather than treating the project as a tool purchase alone. That person can gather feedback, identify recurring failures and decide whether the deployment is helping employees complete useful work.
Expansion should follow evidence. If a pilot creates little value, the next step might be redesign, a different tool or stopping the experiment. A willingness to stop is part of competent investment management. Continuing simply because AI is strategically fashionable can turn a limited test into an expensive routine.
A practical scorecard for the next quarter
Track five things together: outcome quality, total completion time, cost per completed task, user adoption and the frequency of significant failures. The combination provides a more balanced view than any single headline metric.
Review how much of the benefit is repeatable. A one-time backlog reduction may be valuable without supporting the same ongoing return. Similarly, enthusiastic early users may not represent employees who encounter the system later with less training or motivation.
AI’s commercial promise in 2026 is substantial, but the route to value runs through ordinary operational discipline. Businesses need clear objectives, dependable information, realistic cost accounting and responsibility for the final result. The most useful question is not how much AI the organisation uses. It is what customers, employees and owners receive in return.
Discover more from The Economy
Subscribe to get the latest posts sent to your email.
-
Markets & Finance9 months agoTop 15 Stocks for Investment in 2026 in PSX: Your Complete Guide to Pakistan’s Best Investment Opportunities
-
Analysis8 months agoJohor’s Investment Boom: The Hidden Costs Behind Malaysia’s Most Ambitious Economic Surge
-
Analysis8 months agoTop 10 Stocks for Investment in PSX for Quick Returns in 2026
-
Banks9 months agoBest Investments in Pakistan 2026: Top 10 Low-Price Shares and Long-Term Picks for the PSX
-
Analysis8 months agoBrazil’s Rare Earth Race: US, EU, and China Compete for Critical Minerals as Tensions Rise
-
Investment9 months agoTop 10 Mutual Fund Managers in Pakistan for Investment in 2026: A Comprehensive Guide for Optimal Returns
-
Global Economy10 months ago15 Most Lucrative Sectors for Investment in Pakistan: A 2025 Data-Driven Analysis
-
Global Economy10 months agoPakistan’s Export Goldmine: 10 Game-Changing Markets Where Pakistani Businesses Are Winning Big in 2025
