How AI-native companies turn workflows into operating

What happened

OpenAI’s latest Enterprise Signals shows enterprise AI moving from assistance to execution at sharply different speeds. 6× in January. The widening gap points to a deeper operating shift: leading firms connect agents to company context and tools, delegate more substantive work, and make successful workflows easier to repeat. For leaders, the challenge is to turn that depth into work people can trust, measure, and improve.

Each subagent reviews primary sources and updates its deal folder overnight. Every morning, a coordinating agent turns those updates across all her accounts into a short list of priority moves: answer a lingering customer question, fill a gap in the buying committee, or give a prospect a reason to re-engage. The workflow saves her roughly an hour of inbox triage each night, according to Clay.

The daily priorities help her follow through on the small actions that can add up over a long enterprise sales cycle. The supporting evidence stays close to each recommendation, so sellers can inspect the primary sources before acting. Enterprises could extend that shared context to account executives, BDRs, solutions engineers, and sales leaders, subject to existing account permissions.

Clay shows what evolving work needs in order to scale: a consistent structure, a useful refresh cadence, shared evidence, and human judgment at the point of action. Exa Labs, which builds web search infrastructure for AI agents, wants to make its search API available wherever developers could use it.

” Pursuing it once required developer relations and account teams to monitor repositories and the wider ecosystem, identify promising integrations, gather context, and coordinate work across systems. Although the opportunities varied, the path from discovery to implementation followed a consistent sequence. Exa turned that sequence into a defined workflow for Codex, with clear priorities, access to the necessary sources, and human review before anything ships.

Together, Basis, Clay, and Exa put the patterns we see across Enterprise Signals into operational terms. Basis turns a proven process into a reusable skill. Clay gives an agent the context and persistence to keep an evolving body of work current. Exa adds tools, tests, and review so an agent can carry a signal into bounded execution.

Why it matters

Leaders should also leave room for experimentation, including use cases whose value is not obvious on the first try. Startups Basis⁠(opens in a new window), Clay⁠(opens in a new window), and Exa Labs⁠(opens in a new window) have built agents into employee onboarding, account management, and developer ecosystem growth.

Their workflows differ, but the progression is instructive: teach an agent a stable process, give it persistent context as work changes, then let it carry opportunities into tested action. Together, these examples show how teams can build agents into familiar work and improve the process over time. Onboarding has long been cumbersome for employers and employees.

At Basis, which builds AI agents for accounting firms, first-day onboarding now takes 30 minutes instead of two hours, giving HR more time for culture and support. On day one, employees receive immediate access to Codex and a company-specific onboarding skill (a reusable set of instructions and resources for a specific workflow). Codex welcomes them, introduces key company concepts, and uses their computer to complete integration setup in the background.

When recurring questions or exceptions appear, HR can update the skill before the next cohort. ” The process no longer depends on one person’s availability, yet the team can step in for exceptions or complex questions. Onboarding is now more consistent, repeatable, and easier to improve, and new employees gain an immediate model for working with AI.

Clay, a company building a self-learning revenue engine for go-to-market teams, faces a familiar sales challenge: critical deal context is scattered across CRM records, email, Slack, calls, presentations, text messages, and conversations with internal teams and customer champions. To keep that context current, one of Clay’s GTM engineers experimented with a better approach—a persistent workspace and dedicated subagent for every account.

What to watch

Codex now monitors for high-priority integration opportunities, gathers the relevant context, creates pull requests, runs tests, and prepares weekly updates using sources such as Slack and Notion. When appropriate, it can also draft the next step, including an initial announcement, for the team to review. The workflow carries an opportunity from signal to tested artifact while reducing handoffs across research, engineering, and communication.

People still decide which opportunities matter, which commitments Exa should make, and how external relationships should be managed. Tests and review points make the agent’s work visible before it ships. Test results and human review can show the team where to adjust the workflow before the next run. As the work becomes more consequential, permissions, evidence, and decision rights become a larger part of the workflow design.