
Curt McDaniel and I have been talking about Legal Operations for a long time, and not just theoretically.
Before retiring in 2025, Curt spent 19 years at Ferring Pharmaceuticals, including six as Chief Legal Officer, where he led a significant evolution in how the global legal function delivered its services. Curt and I have spent years looking at Legal Operations from opposite sides of the table.
Over the years, we’ve stayed in touch, and Curt and I still regularly compare notes about where the profession is headed. Not surprisingly, lately those conversations have included a lot of artificial intelligence “what-ifs.”
We agree on a lot, including that AI needs to be part of a broader legal strategy, not a standalone technology project.
But one question has generated more debate between us than most:
Where should AI expertise actually live inside Legal?
My perspective is that Legal Ops may have to become the AI expert inside the legal department. As AI’s capabilities have evolved, so has Curt’s view. He sees a need for deep AI expertise in an in-house legal team, led by Legal Ops and supported by lawyers with some level of expertise.
Our discussion led us to ask: What kind of AI expertise does Legal Operations truly need?
Legal Ops Shouldn’t Become IT
Curt raises an important concern: AI isn’t a Legal-only technology. It cuts across the entire enterprise, and organizations already have teams responsible for technology, data, security, privacy, finance, and other areas critical to implementing it responsibly.
Legal can’t simply build its own AI universe.
We’ve seen versions of that problem before with legal technology. A department identifies a problem, buys a solution, and only later discovers it doesn’t fit the organization’s technology architecture, raises security or integration concerns, or duplicates capabilities the enterprise already has.
AI makes that risk even greater because so much of the underlying infrastructure will be shared across the organization.
Curt says the reality is that Legal is usually not a priority for technology investment or IT expertise from a company perspective. R&D, Manufacturing, and other areas typically get more funding and attention. As CLO, he used his own budget for IT expertise while coordinating with IT and other affected groups. One example of this was hiring a legal data scientist.
Curt’s legal team at Ferring collected large amounts of data through legal technology tools, like a CLM and an e-billing/matter management tool, and wanted to analyze the data to continuously improve our processes. The team needed a data scientist, but IT did not prioritize it. So Legal hired for this role on their own. Legal informed IT and HR, gave their rationale, and offered to pay for it. The role reported to Legal Ops but coordinated with IT to ensure compliance with company IT policies. Legal created a data lake within the company IT structure. Everyone agreed, and Legal hired the legal data scientist, and the project proceeded.
Someone Has to Understand the Work
This is where I think Legal Operations has an increasingly important role. IT often understands the technology better than we do, data teams understand the architecture, and security understands the risks. But Legal Operations understands how the legal department works, something none of these other groups can say.
We know how matters move through the department, where approvals happen, where work gets stuck, what should be standardized, what requires judgment, and where lawyers are spending time on work that doesn’t require a lawyer.
That knowledge becomes incredibly important when you’re trying to determine where AI belongs.
I’ve said many times that the starting point shouldn’t be, What can this technology do?
It should be, How should this work get done?
That means starting with the people and processes in place. What does the business actually need from Legal? Which steps add value? Which can be simplified or eliminated? Where do we need a lawyer? Where don’t we? Only then should we ask where technology, including AI, can make the work better.
Curt’s legal services vision is based on scoping the company’s legal services needs and triaging them into a pyramidal structure, with high-risk/complexity matters at the top and low-risk/complexity matters at the bottom. He wants internal lawyers to focus on the top of the pyramid, on matters critical to the company, with targeted support of outside counsel, and believes it’s crucial that internal lawyers, the company’s most precious legal resources in his view, are not bogged down by working on mid- to low-risk/complexity matters because, Curt says, there are better and more effective solutions for these other matters.
Legal Ops, technology (including self-service tools), and ALSPs help drive these solutions, with legal expertise embedded upfront in systems and processes (e.g., templates, playbooks, policies) to minimize ongoing involvement of internal lawyers. Legal Ops is fundamental to this vision, because these teams see the big picture Legal leadership is trying to achieve, know the world of modern legal services, bring a broad range of needed expertise, and help the Legal team work better and faster.
The Definition of AI Expertise Is Changing
My prediction is that over the next few years, the line between “legal technology” and AI will become increasingly fuzzy.
For years, Legal Ops teams became experts in evaluating and implementing specialized systems: e-billing, matter management, CLM, workflow tools, knowledge management platforms, and so on.
I think we’re moving toward an environment where more solutions will be configured or built around foundation models and agents. Instead of always buying a tool designed to solve one particular legal problem, teams will increasingly be able to build solutions around how their own organization works.
If I’m right, Legal Ops can’t simply understand AI conceptually. Some people within the function will need enough hands-on expertise to prototype, configure, test, govern, and continually improve these solutions.
That doesn’t make them data scientists or software engineers; it makes them translators between the technology and the work.
Frankly, I think that’s the natural evolution of Legal Operations. We’ve always sat at the intersection of people, process, technology, and the business. AI doesn’t fundamentally change that role. It raises the level of expertise we’ll need to play it well.
Curt’s view on the AI expertise an in-house legal team needs has evolved over the past year or so as the pace of AI change has increased and change in legal services has exploded. He sees the need for an overall AI subject matter expert for a company; he also believes every function will need some level of AI expertise, often quite deep. Also, given the pace of change, the AI noise, and top-down pressure to “do something with AI,” he expects companies, in order to manage budgets, will not prioritize AI support and investment for Legal. Curt says, “Legal teams will need to move ahead on their own, and they should. This should not be in isolation, but coordinating with the IT team, as we did with our legal data scientist.”
He also believes Legal Ops is a natural home for AI expertise, as it sits where non-legal expertise lives in a well-functioning in-house team (e.g., finance, technology, process improvement, project management, etc.), focused on supporting and enhancing the team’s legal services. However, he also sees a need for lawyers to have AI expertise themselves. In the US, the American Bar Association, in its Official Opinion 512, made it clear that when lawyers use an AI tool, they must understand the tool’s capabilities and limitations, and lawyers remain fully responsible for any legal work done through AI. This requires lawyers to have a certain amount of AI expertise. Legal Ops (aligned with the corporate IT function) can provide deep AI expertise and training, but lawyers themselves will also need AI expertise.
As a former CLO, Curt sees the head of Legal Ops as a brainstorming partner for mapping out the future of our in-house legal services. The speed and impact of AI make these brainstorming sessions more critical than ever. To be effective, he says, “these conversations need to be framed by a deep understanding of AI’s capabilities today and tomorrow. This expertise will likely need to come from Legal Ops, though CLOs and GCs also need to develop sufficient expertise to build an AI-powered vision for their legal team.”
Legal Can’t Always Wait
In an ideal world, every organization would have a well-resourced enterprise AI team ready to help each business function identify use cases, redesign workflows, build solutions, and implement them.
That’s not the reality in many organizations.
Legal competes for the same resources as every other function, and it isn’t always at the top of the priority list. Meanwhile, the technology keeps moving, and the business increasingly expects Legal to move with it.
That doesn’t mean Legal should go rogue. It does mean Legal Ops needs enough knowledge and capability to keep making progress while staying coordinated with the broader organization.
This is one place where thoughtful pilots can be extremely useful. A focused pilot tied to a real business problem gives teams a relatively low-risk way to learn what the technology can do, where the process needs work, what governance is required, and whether there’s enough value to justify going further.
The key is that the pilot should be part of a strategy, not a substitute for one.
Curt agrees. “AI needs to be part of a strategy, a strategy embedded in your legal services vision,” he said. “You should ask: What are the legal services needs of your company today and tomorrow? Where can AI drive the most value in this vision? And be pragmatic. Dreaming is great and should be part of the long-term plan, but you need to start with successes. What can you realistically implement? But do it. Move forward.”
Curt continues, “Pilots are a great, minimally risky, way of trying out something new. You learn what it takes – careful planning, involvement of internal customers, measurable goals, change management, quickly adapting to unexpected situations, etc. The risk should be appropriately bounded in case the project fails, and some will. The resources for a pilot are usually fairly limited and easier to fit in a GC’s budget. Also, the limited nature of a pilot makes it easier for IT to accept, as long as they are kept in the loop.”
So Who Owns AI in Legal?
At this stage, I have to ask: Is “ownership” even the right word?
AI will require shared expertise across the enterprise. IT should own what IT is best positioned to own. Security, Privacy, Data, Legal, Finance, and other functions all have roles to play.
Legal Operations has a different responsibility.
Legal Ops teams need to understand AI well enough to identify where it can improve legal work, challenge assumptions about how that work gets done, translate Legal’s needs to technical teams, and help people adopt the solutions we put in place.
In some organizations, that may mean having someone on the Legal Ops team who develops significant hands-on AI expertise. In others, Legal Ops may work closely with centralized AI resources. Most likely, we’ll see many different models as organizations figure this out.
I don’t think waiting for someone else to figure out what AI means for Legal is one of them.
Legal Ops doesn’t need to become the deepest technical AI expert in the organization. Curt has convinced me of that. But I stand behind the idea that Legal Ops does need to become the expert on how AI can make legal work better.
Increasingly, I think that will require knowing how to do more than talk about it.
Stephanie Corey is Co-founder and CEO of UpLevel Ops and an award-winning pioneer in Legal Operations. She co-founded CLOC and LINK, now part of The L Suite, and has held senior Legal Operations roles at Flex, VMware, and Hewlett-Packard. She advises legal departments on operating models, AI strategy, governance, and service delivery.
Curt McDaniel is a Legal Innovation Advisor with more than 25 years of experience in the global pharmaceutical industry. He spent 19 years at Ferring Pharmaceuticals, including six as Chief Legal Officer. Curt holds a J.D. and M.B.A. from Indiana University, a B.A. from Purdue University, and is a published fiction writer.
The post Where Should AI Expertise Live In Legal? appeared first on Above the Law.

Curt McDaniel and I have been talking about Legal Operations for a long time, and not just theoretically.
Before retiring in 2025, Curt spent 19 years at Ferring Pharmaceuticals, including six as Chief Legal Officer, where he led a significant evolution in how the global legal function delivered its services. Curt and I have spent years looking at Legal Operations from opposite sides of the table.
Over the years, we’ve stayed in touch, and Curt and I still regularly compare notes about where the profession is headed. Not surprisingly, lately those conversations have included a lot of artificial intelligence “what-ifs.”
We agree on a lot, including that AI needs to be part of a broader legal strategy, not a standalone technology project.
But one question has generated more debate between us than most:
Where should AI expertise actually live inside Legal?
My perspective is that Legal Ops may have to become the AI expert inside the legal department. As AI’s capabilities have evolved, so has Curt’s view. He sees a need for deep AI expertise in an in-house legal team, led by Legal Ops and supported by lawyers with some level of expertise.
Our discussion led us to ask: What kind of AI expertise does Legal Operations truly need?
Legal Ops Shouldn’t Become IT
Curt raises an important concern: AI isn’t a Legal-only technology. It cuts across the entire enterprise, and organizations already have teams responsible for technology, data, security, privacy, finance, and other areas critical to implementing it responsibly.
Legal can’t simply build its own AI universe.
We’ve seen versions of that problem before with legal technology. A department identifies a problem, buys a solution, and only later discovers it doesn’t fit the organization’s technology architecture, raises security or integration concerns, or duplicates capabilities the enterprise already has.
AI makes that risk even greater because so much of the underlying infrastructure will be shared across the organization.
Curt says the reality is that Legal is usually not a priority for technology investment or IT expertise from a company perspective. R&D, Manufacturing, and other areas typically get more funding and attention. As CLO, he used his own budget for IT expertise while coordinating with IT and other affected groups. One example of this was hiring a legal data scientist.
Curt’s legal team at Ferring collected large amounts of data through legal technology tools, like a CLM and an e-billing/matter management tool, and wanted to analyze the data to continuously improve our processes. The team needed a data scientist, but IT did not prioritize it. So Legal hired for this role on their own. Legal informed IT and HR, gave their rationale, and offered to pay for it. The role reported to Legal Ops but coordinated with IT to ensure compliance with company IT policies. Legal created a data lake within the company IT structure. Everyone agreed, and Legal hired the legal data scientist, and the project proceeded.
Someone Has to Understand the Work
This is where I think Legal Operations has an increasingly important role. IT often understands the technology better than we do, data teams understand the architecture, and security understands the risks. But Legal Operations understands how the legal department works, something none of these other groups can say.
We know how matters move through the department, where approvals happen, where work gets stuck, what should be standardized, what requires judgment, and where lawyers are spending time on work that doesn’t require a lawyer.
That knowledge becomes incredibly important when you’re trying to determine where AI belongs.
I’ve said many times that the starting point shouldn’t be, What can this technology do?
It should be, How should this work get done?
That means starting with the people and processes in place. What does the business actually need from Legal? Which steps add value? Which can be simplified or eliminated? Where do we need a lawyer? Where don’t we? Only then should we ask where technology, including AI, can make the work better.
Curt’s legal services vision is based on scoping the company’s legal services needs and triaging them into a pyramidal structure, with high-risk/complexity matters at the top and low-risk/complexity matters at the bottom. He wants internal lawyers to focus on the top of the pyramid, on matters critical to the company, with targeted support of outside counsel, and believes it’s crucial that internal lawyers, the company’s most precious legal resources in his view, are not bogged down by working on mid- to low-risk/complexity matters because, Curt says, there are better and more effective solutions for these other matters.
Legal Ops, technology (including self-service tools), and ALSPs help drive these solutions, with legal expertise embedded upfront in systems and processes (e.g., templates, playbooks, policies) to minimize ongoing involvement of internal lawyers. Legal Ops is fundamental to this vision, because these teams see the big picture Legal leadership is trying to achieve, know the world of modern legal services, bring a broad range of needed expertise, and help the Legal team work better and faster.
The Definition of AI Expertise Is Changing
My prediction is that over the next few years, the line between “legal technology” and AI will become increasingly fuzzy.
For years, Legal Ops teams became experts in evaluating and implementing specialized systems: e-billing, matter management, CLM, workflow tools, knowledge management platforms, and so on.
I think we’re moving toward an environment where more solutions will be configured or built around foundation models and agents. Instead of always buying a tool designed to solve one particular legal problem, teams will increasingly be able to build solutions around how their own organization works.
If I’m right, Legal Ops can’t simply understand AI conceptually. Some people within the function will need enough hands-on expertise to prototype, configure, test, govern, and continually improve these solutions.
That doesn’t make them data scientists or software engineers; it makes them translators between the technology and the work.
Frankly, I think that’s the natural evolution of Legal Operations. We’ve always sat at the intersection of people, process, technology, and the business. AI doesn’t fundamentally change that role. It raises the level of expertise we’ll need to play it well.
Curt’s view on the AI expertise an in-house legal team needs has evolved over the past year or so as the pace of AI change has increased and change in legal services has exploded. He sees the need for an overall AI subject matter expert for a company; he also believes every function will need some level of AI expertise, often quite deep. Also, given the pace of change, the AI noise, and top-down pressure to “do something with AI,” he expects companies, in order to manage budgets, will not prioritize AI support and investment for Legal. Curt says, “Legal teams will need to move ahead on their own, and they should. This should not be in isolation, but coordinating with the IT team, as we did with our legal data scientist.”
He also believes Legal Ops is a natural home for AI expertise, as it sits where non-legal expertise lives in a well-functioning in-house team (e.g., finance, technology, process improvement, project management, etc.), focused on supporting and enhancing the team’s legal services. However, he also sees a need for lawyers to have AI expertise themselves. In the US, the American Bar Association, in its Official Opinion 512, made it clear that when lawyers use an AI tool, they must understand the tool’s capabilities and limitations, and lawyers remain fully responsible for any legal work done through AI. This requires lawyers to have a certain amount of AI expertise. Legal Ops (aligned with the corporate IT function) can provide deep AI expertise and training, but lawyers themselves will also need AI expertise.
As a former CLO, Curt sees the head of Legal Ops as a brainstorming partner for mapping out the future of our in-house legal services. The speed and impact of AI make these brainstorming sessions more critical than ever. To be effective, he says, “these conversations need to be framed by a deep understanding of AI’s capabilities today and tomorrow. This expertise will likely need to come from Legal Ops, though CLOs and GCs also need to develop sufficient expertise to build an AI-powered vision for their legal team.”
Legal Can’t Always Wait
In an ideal world, every organization would have a well-resourced enterprise AI team ready to help each business function identify use cases, redesign workflows, build solutions, and implement them.
That’s not the reality in many organizations.
Legal competes for the same resources as every other function, and it isn’t always at the top of the priority list. Meanwhile, the technology keeps moving, and the business increasingly expects Legal to move with it.
That doesn’t mean Legal should go rogue. It does mean Legal Ops needs enough knowledge and capability to keep making progress while staying coordinated with the broader organization.
This is one place where thoughtful pilots can be extremely useful. A focused pilot tied to a real business problem gives teams a relatively low-risk way to learn what the technology can do, where the process needs work, what governance is required, and whether there’s enough value to justify going further.
The key is that the pilot should be part of a strategy, not a substitute for one.
Curt agrees. “AI needs to be part of a strategy, a strategy embedded in your legal services vision,” he said. “You should ask: What are the legal services needs of your company today and tomorrow? Where can AI drive the most value in this vision? And be pragmatic. Dreaming is great and should be part of the long-term plan, but you need to start with successes. What can you realistically implement? But do it. Move forward.”
Curt continues, “Pilots are a great, minimally risky, way of trying out something new. You learn what it takes – careful planning, involvement of internal customers, measurable goals, change management, quickly adapting to unexpected situations, etc. The risk should be appropriately bounded in case the project fails, and some will. The resources for a pilot are usually fairly limited and easier to fit in a GC’s budget. Also, the limited nature of a pilot makes it easier for IT to accept, as long as they are kept in the loop.”
So Who Owns AI in Legal?
At this stage, I have to ask: Is “ownership” even the right word?
AI will require shared expertise across the enterprise. IT should own what IT is best positioned to own. Security, Privacy, Data, Legal, Finance, and other functions all have roles to play.
Legal Operations has a different responsibility.
Legal Ops teams need to understand AI well enough to identify where it can improve legal work, challenge assumptions about how that work gets done, translate Legal’s needs to technical teams, and help people adopt the solutions we put in place.
In some organizations, that may mean having someone on the Legal Ops team who develops significant hands-on AI expertise. In others, Legal Ops may work closely with centralized AI resources. Most likely, we’ll see many different models as organizations figure this out.
I don’t think waiting for someone else to figure out what AI means for Legal is one of them.
Legal Ops doesn’t need to become the deepest technical AI expert in the organization. Curt has convinced me of that. But I stand behind the idea that Legal Ops does need to become the expert on how AI can make legal work better.
Increasingly, I think that will require knowing how to do more than talk about it.
Stephanie Corey is Co-founder and CEO of UpLevel Ops and an award-winning pioneer in Legal Operations. She co-founded CLOC and LINK, now part of The L Suite, and has held senior Legal Operations roles at Flex, VMware, and Hewlett-Packard. She advises legal departments on operating models, AI strategy, governance, and service delivery.
Curt McDaniel is a Legal Innovation Advisor with more than 25 years of experience in the global pharmaceutical industry. He spent 19 years at Ferring Pharmaceuticals, including six as Chief Legal Officer. Curt holds a J.D. and M.B.A. from Indiana University, a B.A. from Purdue University, and is a published fiction writer.

