About OpenNash

Our mission To realize the potential of open and safe superintelligence for all of humanity.

AI is starting to do the work. Most enterprises are not wired for it yet.

OpenNash is an AI-native services firm. We help companies put AI to work: agents that run real processes, connected safely to company data, and teams trained to work alongside them.

A typical enterprise, drawn as a tower of systems AI agents sit on top of a tall, uneven stack: Slack and Teams, email, ChatGPT and Copilot; Salesforce, Workday, ServiceNow and Zendesk; SAP customised since 2009, a data warehouse and SharePoint; Oracle, fourteen Postgres databases and an Excel model only one person understands; a mainframe with 2.1 million lines of COBOL and a vendor claims system with no API; and identity spread across Okta, Active Directory and old LDAP servers. The whole stack rests on four small blocks: a billing script written in 1998 that nobody understands, an unpatched PHP 5 intranet, xz utils kept by one volunteer, and Log4j inside dozens of Java apps. AI agents Slack and TeamsEmailChatGPT, Copilot SalesforceWorkdayServiceNowZendesk SAP, customised since 2009Data warehouseSharePoint: final_v7.xlsx Oracle14 Postgres databasesExcel model only Priya understands Mainframe: 2.1M lines of COBOLClaims system from a vendor. No API. Identity: Okta, Active Directory, three old LDAP servers New. Needs to reachall of it, safely. "Revenue" meansfour different things. Access request:three weeks. No API. Someonere-types it everyMonday. billing.pl: written by Mark in 1998.Nobody knows what it does.Do not touch. PHP 5 intranet,never patched xz utils: onevolunteer maintainer Log4j, inside40 Java apps
A typical enterprise. The knowledge an AI agent needs is spread across dozens of systems, some with no API, many with their own permissions, and all of it resting on code few people still understand. An OpenNash drawing, after xkcd 2347 “Dependency”. Systems and names are illustrative.

01 Who we are

Built by people who ran both halves of enterprise AI.

Engineers formerly at

We are engineers from Google, Meta, Snowflake and Databricks. In Silicon Valley we built the data platforms large companies run on, and the AI systems built on top of them. Our delivery team is in New York.

AI is changing how work gets done faster than any technology we have worked with. We started OpenNash to help companies through that change: to put AI agents to work on real processes, and to train their people to work with them.

The hard part is rarely the model. It is the drawing above. What an agent needs to know is spread across dozens of systems. Each has its own owner and its own permissions. Some have no API. The oldest code is the code nobody dares to change. And every new connection is one more thing to secure.

So we start with the layer between your systems and the AI: each person’s own permissions, one agreed meaning for each business term, data that is current, and a log of every read and write. Then we put agents to work on top of it, measure what they save, and keep them running.

Exhibit 1. Where enterprise AI breaks, and where we work

The data half

  • Warehouses and lakehouses
  • Systems of record: CRM, ERP, ticketing
  • Pipelines and freshness
  • Access control

The access layer

  • Each person’s own permissions
  • Business definitions, agreed once
  • Fresh context, not last night’s copy
  • A log of every read and write

The gap. This is where we spend most of our engineering time.

The AI half

  • Models: hosted or open-weight
  • Retrieval and tools
  • Agents and workflows
  • Evaluations and monitoring

02 What the leaders already get

The companies that got this right have the numbers to show for it.

These are results companies have published themselves: on their engineering blogs, in earnings calls and in filings.

Exhibit 2. What leading companies report from AI
CompanyWhatReported result
AmazonUpgrading tens of thousands of Java apps4,500 developer-years saved, about $260M a year in efficiency gains
AirbnbMoving 3,500 test files to a new frameworkEstimated at 1.5 years of engineering. Done in 6 weeks
GoogleLarge internal code migrations80% of code changes written by AI; about half the time
SpotifyBackground coding agent for fleet-wide changes1,500+ merged pull requests; 60–90% time saved
StripeUnattended coding agents1,000+ pull requests merged a week, each reviewed by a person
LyftCustomer care with ClaudeCustomer support time down 87%+
Bank of AmericaErica, its virtual assistantNearly 700M customer interactions in 2025
UberOn-call assistant in Slack over internal docs70,000 questions answered, about 13,000 engineering hours saved
WalmartProduct catalog850M+ data points created or improved; by hand, 100 times the staff
JPMorgan ChaseAI across the bankAbout $2B of benefits a year for about $2B of spend
AnthropicFinding flaws in open-source code500+ high-severity vulnerabilities found and validated

Sources: Andy Jassy (2024); Airbnb Engineering (2025); Google, arXiv 2501.06972 (2025); Spotify Engineering (2025); Stripe (2026); Claude customer story (Lyft); Bank of America (2026); Uber Engineering (2024); Walmart earnings call (2024); Jamie Dimon, Bloomberg TV (2025); Anthropic red team (2026). All company-reported.

The clearest view of where this goes comes from inside an AI lab. Anthropic’s filing to list its shares, and its own research on its workforce, describe a company that now runs on agents.

90%+of contributions to Anthropic’s codebase in September 2026 were written by Claude
$6.6Mrevenue per employee over twelve months, up from $1.4M
6xmore hours of agent work than human work hours, by August 2026

Sources: Anthropic PBC, Form S-1 (October 2026); Anthropic, “How employment is changing at Anthropic” (October 2026).

Agent work overtook human work in about three months. Output per person rose in every function, not only engineering.

Exhibit 3. Hours of agent work per human work hour at Anthropic (log scale)

Source: Anthropic, October 2026. Interactive agent sessions only; read from the published chart.

Exhibit 4. Output per person at Anthropic, compared with December 2025

Source: Anthropic, “How employment is changing at Anthropic”, October 2026.

The work itself changed too. Engineers who adopted agents wrote far more code with no measurable drop in quality. The share of junior technical hires fell from about 28% to 9%, and hiring scorecards now ask about AI tools three to four times as often. Skills are moving to people who can direct agents and judge their output. Helping your teams make that move is part of our job.

Exhibit 5. Share of Google’s new code generated by AI

Source: Sundar Pichai, Alphabet earnings remarks (October 2024) and statements reported by Semafor (2025 and April 2026).

03 What AI can already do

The intelligence has arrived. It keeps doubling.

In 2023 the best AI model could reliably finish a software task that takes a skilled person about four minutes. By early 2026 the best model finished tasks that take a person twelve hours, about half the time. The length of task AI can complete has doubled about every four months.

Exhibit 6. Length of software task AI agents finish half the time (log scale)

Source: METR Time Horizons. Task length is the time a skilled person needs. Later models score above 16 hours, beyond what METR’s task suite measures reliably.

It is not only code. OpenAI’s GDPval benchmark gives models real assignments from 44 occupations in the nine largest sectors of the US economy, each about seven hours of expert work. Industry experts judge the results blind. In under two years, the share of tasks where AI matched or beat the expert went from about one in eight to more than four in five.

Exhibit 7. Expert tasks where AI output was rated as good as or better than the expert’s

Source: OpenAI, GDPval paper (2025) for GPT-4o to Claude Opus 4.1; OpenAI model launches for GPT-5.2 and GPT-5.5, vendor-reported. Once review and rework are counted, OpenAI measures the speed-up at about 1.4x, not the raw 90x.

What AI could do and what it is used for are still far apart. Anthropic compared the share of each job family’s tasks that current models could handle with the share it actually sees in use. In business and finance, models could handle almost every task. They are used for under a third.

Exhibit 8. Share of tasks AI could do, and is used for, by job family

Source: Anthropic Economic Research, “Labor market impacts”, March 2026. Computer and math (94% and 33%) and office and admin (90%) as published; other values read from the published chart.

Where it is used, it already covers most of some jobs. In Anthropic’s data, AI already appears in three quarters of a computer programmer’s tasks and seven in ten of a customer service representative’s. With AI, the average task in those conversations was done about 80% faster.

Exhibit 9. Share of each occupation’s tasks already seen in Claude usage

Source: Anthropic Economic Research, “Labor market impacts” (2026) and “Estimating AI productivity gains” (2025).

Controlled studies agree that the gains are real, largest for less experienced people, and not automatic. Experienced developers working in code they knew well were slower with AI in one study, and more code does not always mean more shipped software.

Exhibit 10. What controlled studies found
StudyWhoResult with AI
Brynjolfsson, Li and Raymond (NBER)5,179 support agents+14% issues resolved per hour; +34% for newer agents
Dell’Acqua et al. (Harvard, BCG)758 consultants+12% tasks, 25% faster, 40% higher quality; worse on tasks outside AI’s reach
Dell’Acqua et al. (NBER, P&G)776 professionalsOne person with AI matched a two-person team without it
Cui et al. (Microsoft, Accenture)4,867 developers+26% completed tasks; largest gains for less experienced developers
METR (2025)16 experienced open-source developers19% slower, though they believed they were faster
Demirer, Musolff and Yang (NBER, 2026)500,000+ developersCommits +240% with autonomous agents, but releases only +30%

Sources: NBER w31161 (2023); HBS 24-013 (2023); NBER w33641 (2025); Management Science, SSRN 4945566; METR (July 2025); NBER w35275 (2026).

That is the pattern we see in practice. The value comes from redesigning the work around what AI does well and checking what it produces, not from handing people a tool.

04 The gap

Most enterprises are nowhere close.

Outside the frontier, the picture is very different. Every two weeks, the US Census Bureau asks firms whether they used AI. Even after it widened the question to cover any business function, only about one US firm in four says yes.

Exhibit 11. Share of US firms using AI in the last two weeks

Source: US Census Bureau, Business Trends and Outlook Survey. Until October 2025 the question asked about AI in producing goods or services; from November 2025 it asks about AI in any business function, so the two series are not directly comparable.

The gap between companies is widening. OpenAI’s enterprise data shows the top tenth of firms producing about eight times as much AI output per employee as typical firms. Boston Consulting Group finds that only 5% of companies get value from AI at scale, while 60% get hardly any. Those few leaders pull ahead on every financial measure.

Exhibit 12. AI output per employee, frontier vs typical firms

Source: OpenAI Economic Research, output tokens per active user, September 2026, relative to typical firms in May 2026.

Exhibit 13. AI leaders compared with laggards

Source: BCG, “The Widening AI Value Gap”, survey of 1,250 executives, 2025.

And spend is still tiny. Among Fortune 500 companies that pay Anthropic more than $100,000 a year, that spend is on average less than 0.1% of their total expenses. The problem is not access to the model. It is everything between the model and the work: your data, your permissions, your processes and your people.

05 Where the value is

The money is in the work, not the software.

For every dollar companies spend on software, they spend about six on services: people doing work, in house or outsourced. That is where AI agents create the most value, because they can take over the work itself instead of selling another tool to the people who do it.

Exhibit 14. Spend on services for every $1 spent on software

Source: Sequoia Capital, 2026.

The pools are large. The work that is already outsourced and mostly rule-based, such as accounting, claims and revenue cycle, is where agents can start today. The McKinsey Global Institute estimates that today’s technology could in principle automate about 57% of US work hours.

Exhibit 15. Labour spend AI agents can take on, by category (midpoint of estimate)

Source: Sequoia Capital, 2026. “+” marks a lower bound. Highlighted: outsourced, rule-heavy work that is the best place to start. Work-hours estimate: McKinsey Global Institute, November 2025.

06 The risk

The same intelligence works for attackers.

Look again at the drawing at the top of this page. Every block is something an attacker can reach, and over 90% of codebases contain components four or more years out of date. Attackers now have AI to find the weak blocks.

They are much faster. Mandiant tracks the average time from a patch being released to attackers exploiting the flaw. It fell from 63 days to 5 days in five years. For 2025, Google estimates minus 7 days: on average, exploitation now starts before the patch exists.

Exhibit 16. Average days from patch release to exploitation

Sources: Mandiant (2018 to 2023); Google M-Trends 2026 (2025 estimate).

Exhibit 17. Hours per stage of a typical attack

Source: Bain & Company, 2026. About four weeks in total before AI, about 18 hours with it.

And there is more to find. After a steady 2025, the number of vulnerabilities disclosed each month doubled in 2026. Exploitation in the wild rose sharply with it, and most of those flaws had no patch when they were attacked.

Exhibit 18. Vulnerabilities disclosed per month

Source: Google Threat Intelligence Group, “Vulnerability discovery and exploitation trends in the AI era”, 2026. January, July and August 2026 as published; other months read from the published chart.

Exhibit 19. Vulnerabilities exploited in the wild per month zero-day after a patch

Source: Google Threat Intelligence Group, 2026. Read from the published chart; totals match the reported 127 in 2025 and 141 from January to August 2026.

The flaws AI finds are also the dangerous kind. Half of AI-discovered vulnerabilities let an attacker run code on the target, against about a quarter of all others.

Exhibit 20. What a vulnerability leads to, found by AI vs others

Source: Google Threat Intelligence Group, 2026.

October 2026 showed what this looks like. Two critical flaws in PHP, the language behind about 69% of websites whose server language is known, were found with the help of an AI model. Exploit attempts started the day the patches shipped.

Exhibit 21. PHP2Shell: from leak to confirmed attacks in four days
  1. Oct 20Details of two PHP flaws leak, two days before planned disclosure
  2. Oct 21PHP ships patches. Exploit attempts start the same day
  3. Oct 24First confirmed remote code execution in the wild
  4. Oct 26CISA adds both flaws to its Known Exploited Vulnerabilities list

Sources: PHP.net, watchTowr, BleepingComputer, CISA Known Exploited Vulnerabilities catalog; usage share from W3Techs.

Post on X by Prime Minister Sanae Takaichi, 21 October 2026, 9:55 PM Japan time, asking everyone to act tonight on two serious PHP vulnerabilities.
The night the patches shipped, Japan’s Prime Minister asked website operators to act that same night. Prime Minister Sanae Takaichi on X, 21 October 2026, 9:55 PM JST: “An urgent request for everyone to act on tonight. The PHP security team has issued a warning about two serious vulnerabilities in PHP, which is used by many websites.”

The losses are already real. Cybercrime losses reported to the FBI have grown five-fold since 2020, past $20 billion a year, and card chargebacks are forecast to keep rising. Meanwhile, the agents companies deploy are a new target: in IBM’s study, 97% of organizations that had an AI-related breach lacked proper AI access controls.

Exhibit 22. Cybercrime losses reported to the FBI, per year

Source: FBI Internet Crime Complaint Center, annual reports 2020 to 2025. Reported losses only; actual losses are higher.

07 How we help

We close the gap with you.

The leaders did not get there with a better model. They connected AI to their data, rebuilt processes around it, secured it, and trained their people. That is the work we do for you, delivered by the same forward-deployed engineers on the same foundation.

01

OpenNash Work

The gap: people have AI, but it cannot see company data, or sees too much.

We connect the AI your people already use to your systems through reusable MCP servers, with each person’s own permissions and a log of every read and write. Shared agents run in Slack and Teams.

More on Work →
02

FDE Agents

The gap: the value is in whole processes, and chat tools do not run processes.

Our engineers learn how your best people do the work, then build and run agents that take over whole processes: support, back office, revenue operations, finance, legal and compliance. A person approves the exceptions.

More on FDE Agents →
03

Software Factory

The gap: agents can write code fast, but no one trusts them with code nobody understands.

Our coding agents map and document legacy code, pin its behaviour with tests before any change, use formal verification where it matters, and ship reviewed pull requests through your CI.

More on Software Factory →
04

Security

The gap: attackers move at machine speed, and most defence still runs on office hours.

Our agents watch your systems around the clock, triage and investigate alerts, help respond to attacks, and help patch new vulnerabilities fast, with a person approving every production change. They also red-team the agents you run.

More on Security →
05

Your people

The gap: the tools change every few months, and most teams were never shown how to work with agents.

Our AI 101 and 201 sessions get executives and teams productive with tools such as Claude Code, Codex, Hermes and OpenClaw, on their own work. We agree with you who reviews what agents produce, who handles exceptions, and how each workflow improves week by week.

Also live: OpenNash CX, an AI customer support team for phone, text, email and web chat.

08 How we work

Build for what will not change.

“I very rarely get asked ‘What’s not going to change in the next five to ten years?’ That second question is actually the more important of the two.”

Jeff Bezos, 2012

Models will keep getting better. The work will still have to be right, the answer will still live inside your company, and someone will still own the result. So we work like this:

We sit with your experts and aim for a step change.

We work on your hardest problems, side by side with the people who know the work best. We are not looking for a 10% gain. We redesign how the work gets done: agents run the steps that do not need judgement, and your expert reviews and signs off.

1GatherAgent
2CheckAgent
3DraftAgent
4Review and sign offYour expert

Open: you own everything we build.

The code, prompts, tests, evaluations and data live in your accounts. It runs on the AI you already pay for or on open-weight models you host. When a better model ships, we swap it in and keep everything else. Your team can take it over at any time.

Safe: an agent never does more than the person it works for.

Every agent acts with the asking person’s own permissions, through your identity provider. Anything that moves money, sends messages or changes records can require a person’s approval. Every read and write is logged, every prompt and workflow can be rolled back, and your data is never used for training.

Honest about limits.

When a process is not ready for agents, we say so. Your first workflow is usually live in 4 to 8 weeks, then we take on the next one, on a flat monthly fee.

Further reading

Our engineering notes

Main data sources

Bring us your hardest problem.

A 30-minute call with an engineer, not a salesperson. We will tell you what agents can do for it today, and what they cannot yet.