Financial AI Cases

How Balyasny Built a Federated AI Platform Across 180 Investment Teams

OpenAI’s March 2026 case described about 180 investment teams. How did a 20-person central AI team support their distinct workflows on one shared platform?

A multi-strategy investment firm cannot solve every team's research problems with a single prompt. Macro, commodities, equities and event-driven teams use different data, tools and methods. Balyasny Asset Management's answer is a shared AI foundation that lets each team build within its own workflow.

In March 2026, an OpenAI customer case described approximately 180 investment teams and said about 95% of them actively used Balyasny's internal AI platform. Deep research tasks reportedly fell from days to hours; one Central Bank Speech Analyst reduced macro scenario analysis from two days to about 30 minutes. Those are task-specific figures, not evidence of investment returns. Balyasny's 20-person Applied AI team, formed in late 2022, built internal evaluations, agent frameworks, tools and compliance guardrails before giving teams scoped access to data and tools.

An October 2026 announcement by Balyasny and Google Cloud described more than 200 global investment teams at that later date. It said Gemini models had been integrated into Balyasny's multi-model platform for high-volume retrieval across more than 80 internal databases and for multimodal analysis of charts and filings. The March and October team counts describe different points in time.

Frontwise case-study graphic featuring Balyasny Chief AI Officer Charlie Flanagan
Case-study graphic supplied by Frontwise. Check the original disclosures linked below for the underlying claims.

Key points

  • Off-the-shelf chat tools alone cannot reconcile structured and unstructured data, orchestrate workflows and meet institutional compliance needs.
  • A 20-person central team evaluates models on more than 12 internal dimensions, then chooses them by task rather than brand.
  • Core agent architecture and controls are shared; teams receive scoped data and tool access and design their own workflows.
  • User assessments, outcome audits and tool execution quality feed back into models and orchestration.

Estimated reading time: 11 minutes.


1. What the 95% adoption figure actually measures

OpenAI's figure is narrowly defined: about 95% of Balyasny's investment teams actively use its internal research platform. It does not mean that 95% of all employees use it every day, or that 95% of investment work has been automated. Adoption metrics that merge logins, trials and core workflow use can conceal this distinction.

The platform serves several unlike tasks. Deep-research agents synthesize tens of thousands of filings, research notes and earnings materials. A Central Bank Speech Analyst explores macroeconomic scenarios. A Merger Arbitrage Superforecaster watches new filings and announcements and updates deal-completion probabilities. These require different data, tools, evaluations and refresh rates. The value of a shared platform is that teams can put AI into each workflow while retaining common foundations.


2. The central team's first job: define what “good enough” means

In late 2022, Balyasny formed a 20-person Applied AI group of researchers, engineers and domain specialists. It did not declare one model the answer for the whole firm. Before production deployment, it built an evaluation pipeline measuring more than 12 dimensions, including forecasting accuracy, numerical reasoning, scenario analysis and resilience to noisy inputs, against internal benchmarks, tools and proprietary financial data.

A model that performs well on a public leaderboard may still mishandle institutional metrics, time series, tool calls or anomalous data. Financial work often requires finding evidence, calculating numbers, comparing scenarios and leaving a reviewable trail. Balyasny's discipline is to define a task and expected output, test on its own data, inspect failures and then decide whether the model may enter a live workflow. Re-running those tests after model updates is more useful than debating whether a new version feels smarter. The OpenAI case says GPT-5.4 is used as one reasoning component alongside internal models, selected by empirical task performance.


3. Centralize common capabilities; let teams own workflows

OpenAI’s Balyasny customer case describes this approach as “federated deployment.” The Applied AI team builds common agent frameworks, toolchains, model research, evaluation systems and compliance guardrails. Each investment team receives scoped access to data and tools, then adapts agents to its asset class and research method. Macro, commodities and equities need not share one research template, but they can share security, evaluation and orchestration.

A fully centralized design would force a small central group to specify the details of every team's work and become a bottleneck. Fully separate team builds would duplicate procurement, data connections, permissions and compliance work, leaving fragmented logs and evaluation standards. The shared platform therefore owns the controls and reusable components; local teams own task definitions, data scope, research steps and use. The central group becomes a provider of a safe research operating system, not merely a queue for software requests.


4. Feedback must change the system

Daily use allows the platform to collect structured signals: how users assess results, what audits find, whether tool calls succeed and where people repeatedly correct the output. Those signals can improve both the underlying models and the orchestration layer. A thumbs-up survey alone cannot reveal which step failed.

Merger-arbitrage users, for example, needed deal probabilities to be reassessed when new regulatory filings or news appeared, rather than calculated only once at the start of research. The team expanded agent planning and tool access to support continuous monitoring. That shift introduces further questions: which event triggers an update, how duplicates are avoided, what evidence explains a probability change, which past conclusion is retained, who receives an alert and when a person must reassess. Classifying and reproducing failures makes the platform improve with use instead of simply collecting more conversations.


5. Faster research is not faster investment decisions

The striking “two days to about 30 minutes” figure concerns one bounded task: macro scenario analysis by the Central Bank Speech Analyst. Likewise, compressing deep research from days to hours increases research capacity. Neither figure means that an entire investment decision takes 30 minutes, nor that the system generates alpha.

Between raw material and a position lie hypothesis testing, portfolio impact, risk exposure, pricing, hedging and execution. Time saved can matter operationally, but it is not a substitute for investment performance. The efficiency figures come from public customer disclosures and have not been independently audited.


6. Federated governance depends on local ownership

Beyond technical infrastructure, Balyasny lets the teams closest to the work define what useful AI must do. In April 2026, it published an account of an annual AI hackathon held the preceding month. Employees from the US, EMEA and Asia, across business and investing teams, worked with Applied AI staff. It was open regardless of coding experience.

A hackathon does not establish that every prototype reached production. It does show a route for business teams to turn difficult daily tasks into candidate agent workflows. On a multi-strategy platform, important steps can live in a local team's habits. The central platform cannot anticipate every edge case, crucial data source or unacceptable output. Local teams keep ownership of problems and workflows; central specialists provide architecture and controls and feed common needs back into the platform.


Frontwise perspective

For an institution starting now, five components matter.

  1. A multidisciplinary central team owns evaluation, platform capabilities, compliance boundaries and reuse over time.

  2. A specific workflow names the materials, steps, output and person who uses it.

  3. Internal task-based evaluations test data, tools, definitions and failure costs rather than relying on public leaderboards.

  4. Scoped access gives teams room to customize without granting every agent every document or action.

  5. A closed feedback loop records what failed, how to reproduce it and who will fix it.

Balyasny scaled the ability for teams to define and run AI workflows on a common foundation. For your own research, advisory, risk or operations workflow, where is the actual constraint: model selection, task definition, data and tool permissions, evaluation or team ownership?


Sources and scope

Primary disclosures: OpenAI's Balyasny customer case (March 2026); Balyasny–Google Cloud announcement (October 2026); Balyasny's annual AI hackathon account (published April 2026). OpenAI described about 180 investment teams in March; the joint announcement described more than 200 in October. These are company statements from different dates.

The 95% adoption and time-saving figures are publicly disclosed company claims, not independently verified measures of returns or alpha. The Frontwise perspective is analysis based on public information. This article is for industry research and information only; it is not investment advice, a return promise or a performance claim.