ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

Anthropic: Which Economic Tasks Are Performed with AI? Evidence from Millions of Claude Conversations

Jeremy WeaverFebruary 11, 2025
Premium

The study analyzes four million Claude.ai conversations mapped to US occupational tasks, revealing that AI is mainly used to augment specific tasks—especially in software development, writing, and other cognitive roles—rather than to replace entire jobs. It finds that mid-to-high wage occupations are using AI significantly, with different models specializing in distinct tasks, highlighting a nuanced, task-specific impact of AI on the economy.

Anthropic: Which Economic Tasks Are Performed with AI? Evidence from Millions of Claude Conversations



Summary of Read Full Report (PDF)

This research paper uses data from four million conversations on the Claude.ai platform to empirically analyze how artificial intelligence (AI) is currently used across various occupational tasks in the US economy.

The study maps these conversations to the US Department of Labor's O*NET database to identify usage patterns, finding that AI is most heavily used in software development and writing tasks. The analysis also examines the depth of AI integration within occupations, the types of skills involved in human-AI interactions, and how AI is used to augment or automate tasks.

The researchers acknowledge limitations in their data and methodology but highlight the importance of their empirical approach for tracking AI's evolving role in the economy. The findings suggest AI's current impact is task-specific rather than resulting in complete job displacement.

Here are some surprising facts revealed by the analysis of AI usage patterns in the sources:

  • AI is not primarily used for automating entire job roles, but rather for specific tasks within occupations. While there is a lot of discussion about AI replacing jobs, the data suggests that AI is more commonly used to enhance human capabilities in specific tasks. This is reflected in the finding that only about 4% of occupations use AI for at least 75% of their tasks.
  • The peak AI usage is in mid-to-high wage occupations, not in the highest wage brackets. It might be expected that AI would be adopted most in the highest-paying professions, but the analysis shows that occupations requiring considerable preparation, such as those needing a bachelor's degree, and those with mid-to-high salaries are seeing more AI use. This could be because these roles involve tasks that are well-suited to current AI capabilities.
  • AI is being used for both augmentation and automation almost equally. While there's a lot of focus on AI replacing human work, the study found that 57% of AI interactions showed augmentative patterns (enhancing human capabilities), while 43% demonstrated automation-focused usage (performing tasks directly). This reveals that AI is serving both as an efficiency tool and a collaborative partner.
  • Cognitive skills are highly represented in AI conversations, but not necessarily at an expert level. Skills like Critical Thinking, Reading Comprehension, and Writing are prevalent, however, the analysis only captures whether a skill was exhibited in the AI's responses, not whether that skill was central to the user's purpose or performed at an expert level. For example, active listening appears as a common skill because the AI rephrases user inputs and asks clarifying questions, rather than because users are seeking listening-focused interactions.
  • There is a clear specialization in how different AI models are used. For instance, Claude 3.5 Sonnet is more used for coding and software development, while Claude 3 Opus is preferred for creative and educational work. This suggests that different models are not interchangeable, but rather are being adopted to meet specific needs in the economy.
  • A significant portion of "non-work" interactions still mapped meaningfully to occupational tasks. For example, personal nutrition planning related to dietitian tasks, automated trading strategy development related to financial analyst tasks, and travel itinerary planning related to travel agent tasks. This suggests that AI is influencing a variety of tasks, even in informal contexts.
  • AI usage is not evenly distributed across all sectors. The study found the highest AI usage in tasks associated with software development, technical writing, and analytical roles. Occupations involving physical labor and those requiring extensive specialized training showed notably lower usage.

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.

  • Model-agnostic

    Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

Related Articles

Moritz Helped Close $2.3B in Contracts in Months. AI Expanded Legal Demand.

Moritz, an AI-native San Francisco firm formerly called Arcline, had helped over 100 companies close more than $2.3 billion in contract value at a four-hour average turnaround by May 2026, and now says it serves 200+ in-house teams. The constraint AI removed was turnaround, not headcount, and turnaround is a property of infrastructure you either own or rent.

Mikel AmigotSeptember 30, 2026

Apollo Asked If an Agentic Bank Run Is Coming. The Question Is Who Runs the Agent.

Apollo chief economist Torsten Sløk asked on 27 September 2026 whether agentic AI assistants could sweep household cash out of 0.1% checking accounts into the 3.3% to 5.0% accounts his note lists. The mechanism he describes needs an agent holding account access, and the bank that does not operate that agent does not get a vote in what it optimizes for.

Jaione AmigotSeptember 30, 2026

Bad Theory Labs' Interference Search: Check the Scope

Bad Theory Labs published a paper, Apache-2.0 code, trained judge weights, raw results and a log mapping every number to the command that produced it. The figures are real measurements — on Countdown, an arithmetic puzzle with an exact solver. The unsupported step is not the lab's; it is the leap from that benchmark to enterprise agent reasoning.

ibl.ai EngineeringSeptember 29, 2026

Microsoft's Agent Identity Layer: Who Actually Owns It?

Microsoft's rebuilt Copilot puts its persistent Autopilot agent behind a governed identity and meters it with usage-based billing rather than the per-seat licence. The governance is good and the metering is the right shape. What you cannot get is ownership of the control plane, which is the part worth pricing before you standardize on it.

ibl.ai EngineeringSeptember 29, 2026

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work — so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope · fixed timeline

A time-boxed proof of value on your real data — not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time · not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data · run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Custom quote

perpetual license · you own the stack

We transfer the full source code. You own and self-host the entire platform — outright.

Best for: Organizations and enterprises that benefit from perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable · zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM — Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY