Back

How Do Corporate Legal Departments Achieve AI Adoption?

Nick Fleisher

Nick Fleisher

June 11, 2026

Nick is co-founder and CEO at Sandstone. An engineer by training, he spent the last several years leading the legal tech service line at McKinsey & Company in New York, where he focused on AI & automation for law firms, corporate legal teams, and legal tech companies.

The pressure on in-house legal has been building for years. Request volumes are up. Deal complexity is higher. Business teams expect faster answers. And through all of it, legal departments have been asked to do more with headcounts that haven't kept pace.

But the operational pressure is only part of the story. The deeper problem is structural: legal sits on a goldmine of institutional knowledge — contracts, playbooks, negotiation histories, prior redlines, policy decisions — and almost none of it is accessible when it matters most.

The result is a department that constantly reinvents the wheel. The same clause gets negotiated from scratch. The same policy question gets answered for the third time. The same context gets reconstructed before any real work can begin.

Corporate legal departments aren't adopting artificial intelligence because it's a trend. They're adopting it because the alternative — continuing to absorb more work with the same fragmented infrastructure — is no longer viable.

Before getting into the how, it's worth grounding the what.

AI in legal draws on a few distinct capabilities working together. Natural language processing (NLP) allows systems to understand and interpret written text — a contract, a Slack message, a policy document — the way a human would. Machine learning enables those systems to improve over time, getting better at classifying requests, surfacing relevant precedent, and applying institutional positions the more they're used. Generative AI produces outputs — draft language, suggested redlines, and summarized analysis — based on the patterns it has learned.

In practical terms, for in-house teams, AI handles the pattern recognition, the retrieval, and the first-pass drafting. Legal professionals apply judgment to what matters most.

This is not a replacement story. It's a capacity story. AI-native legal departments don't have fewer lawyers — they have lawyers who spend their time on higher-value work instead of administrative triage.

The real question isn't whether AI belongs in legal. It's where to start. The use cases below represent the highest-impact entry points for corporate legal teams, and platforms like Sandstone unify these AI tools in a single workspace so teams aren't stitching together point solutions.

Intake and request routing

Legal work arrives from everywhere — a Slack message, an email, a ServiceNow ticket, a calendar invite. Without structure, high-priority requests get buried, context gets lost in transit, and legal spends the first ten minutes of every matter just figuring out what's actually being asked.

AI-native intake changes that. Instead of requiring business teams to submit requests through a formal portal (which they won't use), AI agents capture requests across the tools where work already happens. They understand the intent behind the request, gather the context legal needs, and route to the right owner automatically — with business signals like deal value, urgency, and counterparty history surfaced alongside the work from the start.

Less back-and-forth. Fewer dropped requests. The full picture, immediately.

Knowledge management and playbooks

Most legal departments have playbooks. Most of those playbooks are out of date.

The problem isn't that teams don't value consistency — it's that updating playbooks manually never makes it to the top of the priority list. So the guidance drifts from how the team actually negotiates, and enforcement becomes inconsistent.

AI-assisted playbooks solve this by learning from the work itself. Past redlines, approved positions, and negotiation outcomes continuously feed back into the playbook, keeping guidance aligned with current practice. The result is institutional knowledge that compounds instead of decays — one that enforces clause positions and fallback terms without requiring a lawyer to remember them from scratch every time.

Contract drafting and review

First-pass contract review is one of the most time-consuming, repetitive tasks in legal. AI handles the pattern work: flagging deviations from standard positions, suggesting fallback language, checking consistency across clauses. Lawyers engage where judgment is irreplaceable — on high-stakes terms, novel risk, and negotiating strategy.

This isn't about removing lawyers from the loop. It's about making sure their expertise is applied where it actually moves the needle, not on boilerplate that should have been handled before it ever landed in a queue.

When a lawyer needs to know how the company handled a similar deal two years ago, or what the standard position on limitation of liability has been across the last dozen negotiations, the current process usually involves asking around, digging through folders, or hoping someone remembers. That search is expensive — in time, in attention, and in the quality of the answer.

AI changes this by enabling natural language querying across the department's full contract and policy landscape. The question gets asked in plain language. The answer surfaces from actual institutional history, in context, at the moment of work, not an hour later after the meeting has already started.

Workflow automation and approvals

Legal work doesn't end when the first-pass review is done. There are approvals to route, status updates to track, and stakeholders to loop in. Without automation, this coordination work falls on individual lawyers — creating administrative drag that slows turnaround and frustrates the business teams waiting on the other side.

End-to-end workflow automation handles routing, escalation, and status tracking based on matter type, risk level, and counterparty parameters. Business context surfaces automatically. The department tracks what's in progress, what's stuck, and what's been resolved — without building a manual reporting system.

Business teams measure legal by responsiveness. When intake is automated, context is surfaced immediately, and playbooks apply institutional knowledge without manual intervention, the time from request to resolution is significantly reduced. Teams that once measured turnaround in weeks start measuring it in days or hours.

Inconsistent clause language isn't just an operational problem — it's a risk exposure. AI-assisted playbooks ensure that standard positions, fallback terms, and approved language are applied uniformly across all negotiations. The department's posture stops varying depending on which lawyer happens to be reviewing.

The most important benefit is the hardest to quantify. When administrative burden is removed — when intake, triage, first-pass review, and knowledge retrieval are handled systematically — lawyers have the capacity to operate as genuine strategic advisors. Not just signing off on deals, but shaping them. Not just managing risk, but influencing business outcomes.

That's the shift AI-native legal departments are designed to enable.

1. Identify high-impact use cases

Start with operational friction, not aspirational capability. Where are requests getting dropped? Where is review inconsistent? Where does knowledge walk out the door when someone leaves? For general counsel and legal operations leaders alike, mapping those pain points to specific workflows is the foundation of a credible business case.

High-volume, repetitive processes are the natural starting point — not because they're the most interesting, but because the impact is visible and measurable from day one.

2. Quantify time and cost savings

Time savings are a real benefit of legal AI, but a business case built on efficiency alone rarely lands with the stakeholders who matter. The more compelling framing is capacity: hours freed from intake triage and first-pass review translate directly into hours available for strategic work the department otherwise couldn't prioritize.

Estimate volume, estimate time per task, and then translate the freed capacity into outcomes — faster deal cycles, reduced backlog, improved responsiveness to business teams. That's a different conversation from "we'll save X hours."

3. Align AI goals with business priorities

Legal AI that connects to business outcomes is legal AI that gets funded. Faster contract review doesn't just help legal — it accelerates the deal cycle for the sales team waiting on the other side. Consistent risk management doesn't just reduce legal exposure — it improves the confidence of every stakeholder who needs to sign off.

Frame the case in terms the business already cares about, and the path from approval to implementation gets shorter.

1. Engage the general counsel early

The general counsel — and corporate counsel more broadly — are the ultimate decision-makers, and the right framing for that conversation is strategic rather than operational. AI isn't a tool for automating away work; it's an enabler of the legal function that legal leaders have always wanted to build. One where the department leads on risk, not just reacts to it. One where institutional knowledge compounds rather than disappears when someone leaves.

That's a mission-level conversation, and it's the one worth having first.

2. Communicate value to business teams

The business teams who interact with legal most frequently — sales, product, HR — are also the ones with the most direct experience of legal as a bottleneck. Show them what faster turnaround looks like in practice. Show them that requests submitted through their existing tools will actually get acknowledged, routed, and resolved. Their support turns a legal initiative into a cross-functional priority.

AI is only as good as the data it can access. A system with no memory of past decisions starts from scratch every time — which is precisely the problem legal departments are trying to solve.

The departments that get the most from AI adoption are the ones that treat their institutional knowledge as an asset: contracts, playbooks, negotiation histories, policies, and precedents, unified in a single repository. That foundation is what transforms AI from a generic drafting assistant into a system that actually knows your company's positions, your counterparties' patterns, and your team's risk tolerance.

Sandstone's AI-native repository is purpose-built for this. It aggregates the scattered data of in-house legal work — across tools, systems, and channels — and makes it available in context, at the moment of work. Not as a search engine you have to query manually, but as an always-on knowledge layer that surfaces what's relevant as work arrives.

From bottleneck to business enabler

For most corporate legal departments, the function's identity has been defined by what it can't do fast enough. Contracts stuck in review. Requests that disappear into the queue. Context that has to be reconstructed before the actual work can begin.

AI-native legal changes the frame. When institutional knowledge is structured, accessible, and applied automatically, legal stops being a bottleneck and starts delivering legal services the way the business actually needs them — proactively, consistently, and at scale.

The departments building on this foundation now aren't just getting faster. They're getting smarter with every matter, every negotiation, every decision. Generative AI, applied to a unified base of institutional knowledge, produces outputs that improve over time — that's the compounding value that makes AI adoption a structural shift, not a tool upgrade.

Sandstone is the legal relationship management platform designed to enable this shift — built specifically for in-house legal departments that are ready to work differently.

Learn how Sandstone enables in-house legal departments with AI.

Time savings are the starting point, but not the finish line. Teams that have moved through the early stages of AI adoption tend to track consistency of legal positions across negotiations, reduction in request backlog, and stakeholder satisfaction among the business teams who thatlegal serves. The most meaningful signal, though, tends to be qualitative: whether the legal function is being brought into strategic conversations earlier, and whether it's seen as a partner rather than a processing step.