OpenAI targets junior bankers. ChatGPT for Financial Services automates the work.

If you are a second-year analyst at a bulge bracket bank right now, or the VP who manages a team of them, here is the question worth sitting with: what happens to your job description when the thing you spend 60 percent of your week doing, building comps tables, drafting first-pass pitchbooks, formatting DCF models, becomes a product with a price tag instead of a headcount line?

That is the question a Reddit thread in r/artificial is circulating this week, discussing what OpenAI is positioning as ChatGPT for Financial Services. According to the discussion, the product bundles research, financial modeling, and pitchbook prep into a single offering aimed squarely at the tasks junior bankers spend their nights on. OpenAI has not published detailed pricing or a technical spec sheet for this specific offering in what the thread links to, so treat the feature list as directional rather than final. What is not directional is the intent. A company that already sells ChatGPT Work to enterprises is now naming a job function on Wall Street and building a product around it. That is a different kind of announcement than a general capability release.

What a bank actually pays to find out if this works

The sticker price of an AI seat license is the smallest number in this decision. A 200-person markets or IB division piloting a tool like this is not paying for tokens. It is paying for the compliance review that has to happen before anything touches a live pitchbook, the security team's sign-off on where model prompts and outputs get logged, and the months of associate time spent figuring out which parts of a model output can be trusted without a second pass.

Run the math on time alone. A compliance review for a new vendor tool at a regulated financial institution typically runs six to twelve weeks once legal, infosec, and the model risk management group all weigh in, and that is before a single analyst opens the tool on a live deal. Add in the retraining cost: a firm that has built its analyst training program around "build the model by hand first, understand it, then automate" now has to decide whether that sequence still makes sense if a tool can produce a passable first draft in minutes. That is not a licensing decision, it is a curriculum decision, and curriculum decisions move slower than product launches.

Then there is the migration risk nobody puts in the pitch deck: if the firm standardizes on one vendor's financial services product and that vendor changes pricing, changes model behavior, or gets outpaced by a competitor's release, switching costs are not just re-licensing. They are re-certifying every workflow that touched the old tool, because in a regulated environment, "we changed vendors" is itself an audit event.

Three ways this actually gets deployed inside a bank

Not every firm will touch this the same way. The choice mostly comes down to how much risk a desk is willing to accept in exchange for speed.

Approach	What it actually is	Compliance exposure	Who benefits
General-purpose assistant, no bank integration	ChatGPT or Claude used informally for research and drafting, outside firm systems	High. No audit trail, easy to leak deal data by accident	Individual analysts moving fast on non-sensitive work
Enterprise-tier deployment	ChatGPT Work or an equivalent enterprise contract with logging and access controls	Medium. Auditable, but still requires policy work on what data can enter prompts	Mid-size firms that want speed without rebuilding infrastructure
Vertical financial services product	A purpose-built offering like the one described in the Reddit thread, tuned for pitchbooks and modeling workflows	Lower, in theory, if the vendor builds in the compliance hooks banks need, but this is unproven at scale	Large banks willing to be early, in exchange for a competitive edge in analyst productivity

For a solo RIA or a boutique advisory shop, the general-purpose tool is the right call because the compliance overhead of anything more is not worth it yet. For a mid-size bank with an existing enterprise AI contract, the enterprise tier is the safer bet: you already paid for the audit trail. For a bulge bracket firm trying to win the recruiting war for the next class of analysts, the vertical product is the one worth piloting first, because the story you tell candidates about what their first year looks like is itself a competitive asset now.

One number that tells you how this gets priced

OpenAI's GPT-5.5, the model most likely underpinning a product like this given its release timing, runs $5.00 per million input tokens and $30.00 per million output tokens. Say a full first-draft pitchbook, with comps tables, a summary memo, and a rough valuation section, runs to roughly 150,000 to 200,000 output tokens once you count revisions. That is somewhere around $5 to $6 in raw model cost. A first-year analyst's fully loaded cost to the firm, salary plus bonus plus overhead, runs well into six figures annually. The gap between those two numbers is not subtle.

What changes if that per-draft cost were $60 instead of $6? Not much, honestly. Even a tenfold price increase leaves the economics overwhelmingly in favor of automation for the drafting stage. What would actually change the calculus is if the error rate on outputs required so much senior review time that the "savings" got eaten by partner and VP hours spent catching mistakes. That is the number nobody has published yet, and it is the one that will decide whether this product replaces junior headcount or just changes what junior headcount does all day.

A decision tree for whether your desk should touch this

Before a team commits real hours to piloting a tool like this, it helps to walk through the decision in order rather than all at once.

1. If the work in question never touches client-identifying deal data, pilot a general-purpose tool like ChatGPT or Perplexity for research first, with no formal rollout. This tells you fast whether the underlying task is even a good fit for a language model.
2. If the pilot works and the task does touch sensitive deal data, do not scale it until legal and infosec sign off on an enterprise-tier deployment. Skipping this step is the single most common way pilots turn into incidents.
3. If your firm's competitive edge is speed of execution on live deals, evaluate the vertical financial services product directly, but run it in parallel with your existing process for at least one full deal cycle before retiring anything.
4. If your firm's edge is relationship and judgment rather than volume of pitchbooks produced, skip the vertical product for now. The tool solves a throughput problem you may not have.

Where the pitchbook draft actually falls apart

The failure mode here is not dramatic. It is not a model hallucinating a fake acquisition. It is quieter and more common: a model producing a comps table that looks internally consistent, with the right formatting, the right multiples in the right columns, built from a stale or mismatched data set that nobody catches until a client asks a question the associate cannot answer on the call. The output is confident. That is the problem. A first-year analyst who is unsure of a number flags it. A model that is unsure of a number often does not, unless the product is specifically built to surface its own uncertainty, which is a much harder engineering problem than generating the table in the first place.

This is the same failure pattern that shows up whenever a model is asked to do synthesis work under a deadline: it optimizes for a plausible-looking answer, not a verified one, and the review burden shifts from "did the junior do the work" to "did anyone check the junior's tool." Firms that skip building that second check are the ones who will have a bad story to tell in a year.

The claim to check by March

Here is the falsifiable version of this story. If OpenAI's financial services push is real and not just a positioning exercise, at least one bulge bracket bank will announce, on the record, a formal reduction or restructuring of its first-year analyst class size within six months, citing AI-assisted workflows as a factor. If that does not happen by March 2027, the more likely read is that this product changes what junior bankers do hour to hour without changing how many of them get hired, because the judgment and relationship work that got them hired in the first place is still the part nobody has automated. For more on how these hype-versus-reality gaps tend to resolve, see our earlier look at separating LLM hype from reality, and our ChatGPT vs Gemini comparison if you are weighing which general-purpose tool to pilot first.