How to make procurement and legal work together

The short version

Procurement and legal are working toward the same goal, but they rarely talk to each other until a contract lands on a Friday with a Wednesday deadline. Your legal team gets a vendor agreement with no context, while procurement chases savings without seeing the contractual risk. Stakeholders bypass your team until the last minute, and the result is slower deals, weaker terms, and renewals that surprise everyone.

Tom Mills is a 25-year procurement transformation veteran and the author of Procure Bites. He sat down with Laura Garcia, managing counsel and head of commercial legal at Ironclad, to break down what a high-functioning procurement and legal partnership looks like inside a scaling company.

Most useful for: Procurement leads, commercial counsel, general counsel, and ops leaders running vendor intake at a company where contract review is starting to feel like a bottleneck.

What does procurement and legal partnership mean?

A procurement and legal partnership is the working arrangement where both teams share intake, context, and visibility into every vendor deal from kickoff through renewal. You own different parts of the same contract:

• Procurement owns the commercial side: Pricing, scope of work, delivery timelines, vendor performance, and savings
• Legal owns the risk and compliance side: Liability caps, indemnification, data privacy, termination rights, and regulatory exposure

Your job is to protect the business so it can move forward—not by gating deals but by clearing the path for the next round of revenue, growth, and vendor relationships. When both teams start working together at the beginning of a project instead of at the contract stage, deals close faster and late-stage surprises drop. The "legal is slow" narrative falls apart once you look at the data.

When you don't work together, you get the pattern most companies live with today: Friday contracts with Wednesday deadlines, vendor agreements with no business context, and renewals nobody saw coming.

What the partnership looks like in practice

Procurement and legal work best as an alliance, not a sequential workflow. In the article that opened the conversation, Tom listed off Lennon and McCartney, Batman and Robin, Han Solo and Chewbacca, Scooby Doo and Shaggy, and Sonny and Cher, the point being that procurement and legal are most powerful when they collaborate rather than work in sequence.

That framing matters because you and your counterpart on the other team are doing the same job. You protect the business so it can move forward, not by policing but by clearing the path for future revenue, deals, and scale. You also face the same challenges, since stakeholders engage you too late and both teams end up sidelined or ignored.

Laura described the same dynamic from the legal side. At Ironclad, commercial legal was doing procurement work for years before the first procurement hire, asking the same questions procurement asks. Has the right department approved this? Are we getting the best value? What happens if the vendor fails to deliver?

5 insights for commercial teams

1. Meet the general counsel in week one

Your first week at a new company is the best time to meet the general counsel. When Tom joined Bibby as its first procurement hire at a business of just over 1,000 employees, that's exactly what he did. It wasn't on his induction plan, but he put it there.

The legal team was relieved that someone had finally arrived to help with vendor-facing work, and risks they hadn't seen before started surfacing once Tom became the go-to for vendor conversations.

Laura saw the same dynamic from the other side at Ironclad. When Sean McGill became Ironclad's first dedicated procurement hire at a company size of over 500 employees, the commercial legal team was the first group celebrating, because they'd been wearing the procurement hat by default.

This single meeting sets the tone for everything that follows. The rule Tom points to is that the moment either team has visibility on a project, the other gets a heads-up.

You can do this in your first week at a new company, or at the company you're already at. The cost is one calendar invite.

"As I mentioned coming into an organization as the first procurement professional, one of the fundamental things was within the very first week, even if it wasn't on my induction plan, I made sure I met the general counsel in the legal because I knew that that was a foundational relationship."

2. Run a monthly stand-up for forward visibility

Tom recommends a monthly procurement and legal stand-up, where the real value is giving legal a heads-up on upcoming projects with enough context to prioritize.

Most legal teams receive a contract with zero context on what it's for or why it matters to the business. Procurement closes that gap, and the stand-up is where the heads-up happens.

In a live poll, more than 50% of attendees said they meet weekly, and close to 20% said they never meet at all. Laura confirmed that Ironclad's commercial legal and procurement teams have a standing call to make sure the partnership is working.

"Very often procurement teams will have visibility of projects or things that might be coming up that the legal team wasn't perhaps aware of. We can almost help manage the workflows in a way that we're giving information and giving forward visibility, but also context around what's happening. Because a lot of the times, legal team will get landed a contract, but they won't really be given any explanation of the basics of what this is for, how does this relate to our strategy. So it's very difficult for the legal team to be able to then prioritize."

3. Add an AI disclosure question to your intake form

About a year ago, Ironclad added a question to its procurement intake form asking whether the software being purchased includes AI. If the answer is yes, you route the request through a data classification matrix that determines what data you're sharing and under what conditions before contract review begins.

Laura reviews the intake form questions quarterly with the procurement team to make sure they're still capturing what legal actually needs. The form is launchable from Slack and from the CRM, so stakeholders submit from where they already work.

The goal isn't to block AI adoption but to let people use AI tools inside your company's governance policies, which Laura framed as enablement rather than gating. Tom made a related point: he hadn't seen an AI policy at any business he'd worked in, and he thinks procurement and legal are the right teams to write one.

Add an AI disclosure question to your intake form, pair it with a data classification step for any vendor that answers yes, and review the form questions every quarter to make sure they're still relevant.

"Not recently, but about a year ago, we had to add, with the explosion of AI, a section in our procurement intake to say, does this software include AI? Go through our data classification matrix and all of that to make sure what type of data are we sharing. But all of that is to say, we want our employees to use AI. We just want them to also comply with our AI policy, governance policy, and make sure we're not giving away the house."

4. Pull cycle-time data to end the "legal is slow" narrative

You can end the "legal is slow" narrative for good with cycle-time data. At the end of each month, Laura pulls data showing how long a contract sat with legal versus elsewhere in the cycle. In the example she shared, the contract had been with legal for less than 24 hours before being sent back out, and CLM (contract lifecycle management) software makes this transparent to the whole organization.

Without that data, perception fills the vacuum and legal gets blamed for delays caused elsewhere in the chain. With the data, the conversation changes.

Pull a cycle-time report on the last 30 days of contracts, show how long each one sat with legal versus elsewhere, and bring the data the next time someone says legal is the holdup.

"What I really deeply love about Ironclad is you can really see where in the process or who's holding up the contract and what the issues are. Maybe it's not a hold up. Maybe it's just gathering more information, but it sheds light. And actually, legal's not the hold up here. We can track turns. We can track where the contract is actually sitting. For me, that's a game changer. I'm able to pull that data at the end of the month and say, hey, actually, we had the contract for a couple of hours. We had the contract for less than twenty four hours before we sent it out."

5. Involve legal the moment you have project visibility

Tom's hardest-earned lesson came from his time as head of procurement at Clarks, the shoe business. He was leading a print management vendor selection, focused on stakeholder buy-in and commercial savings, and sat on the contract for a few months before passing it to legal. The legal team's response was effectively, "Did you not think to involve us earlier?" and the project went sideways from there.

Tom saw the flip side of that lesson with a different vendor. A "quick look" request to bring on a new sales tool surfaced cybersecurity risks once procurement and legal got involved, and nearly killed the deal. The team almost had to go back to the drawing board, but as Tom put it, that was the right thing to do.

When you surface a risk, frame it as protecting the individual stakeholder, not just the company. That's the principle Tom kept coming back to, and done right, the stakeholder ends up relieved that the issue surfaced before signing rather than after.

"I think the key is actually in the explanation of the risks and how we do that simply in a way that shows to the stakeholders not only we're trying to protect the business, we're actually trying to protect them as individuals in the business. With the correct explanation to both the individuals and the stakeholders involved, we were able to almost give them the feeling of relief in terms of, thank goodness we didn't just jump in here because this could have cost us a lot."

3 steps you can take this week

1. Put a recurring 30-minute procurement and legal stand-up on the calendar. If you're procurement, you send the invite. If you're legal, you send the invite. The first agenda item is the list of projects coming over the horizon in the next 60 days
2. Open your procurement intake form and add an AI disclosure question. If the answer is yes, the request routes through a data classification step before contract review starts. Borrow Laura's quarterly review cadence to keep the form current
3. Pull a cycle-time report on the last 30 days of contracts. Show how long each one sat with legal versus with the counterparty. Send it to the GTM lead who's been complaining about review speed

Final thoughts

"Open those doors of communication between legal and procurement. If things aren't working, have a conversation about it. Bring the context. People are coming from different point of views, but at the end of the day, you're on the same team. You're on whatever company that you're at. You're on the same team. You're trying to bring forth value, whether it's in the legal role, the procurement role. You want to shine and work with your cross functional partners."

The procurement and legal partnership isn't a tooling problem, and it isn't a process problem. It's a relationship that needs a regular rhythm and a shared starting point. If you get this right, your teams stop trading contracts back and forth and start running the calendar together.

See how Ramp fits in

You're already protecting the business at the contract layer. Ramp helps you catch renewals before they auto-renew and spot spend trends before they become problems. You can see all your vendor spend, upcoming renewals, and contract terms in one place, so the heads-up Tom and Laura describe has real data behind it.

Common questions about unifying procurement and legal together

What does procurement own versus what does legal own?

Procurement owns the commercial layer of a vendor deal: pricing, scope of work, delivery timelines, vendor performance metrics, and savings. Legal owns the risk and compliance layer: liability caps, indemnification, data privacy, termination rights, and regulatory exposure. The two layers overlap on the same contract, which is why the partnership only works if both teams have visibility from the start of a project, not just when the contract shows up.

What is a procurement and legal negotiation playbook?

A negotiation playbook lists your standard contract clauses, acceptable fallback positions, and redlines that need legal review. The point is to let procurement handle routine negotiations without pulling legal into every back-and-forth. Legal stays in the loop on anything the playbook flags as non-standard.

Tom and Laura didn't go deep on this in the session, but it's a common follow-on once the cadence and intake pieces from Insight 2 and Insight 3 above are running.

When should a company hire its first dedicated procurement professional?

In Tom's case, he was the first procurement professional at Bibby, a business of just over 1,000 employees. At Ironclad, Sean McGill came on as the first dedicated procurement hire when the company was over 500 employees.

Laura's signal from the legal side is that if commercial legal is already asking questions about vendor selection, approval, and value that no one else owns, you need a procurement hire. If that pattern is showing up in your week, the business case is already written, and the legal team will be the first group celebrating.

What questions should be on a procurement intake form?

Add an AI disclosure question that routes any yes-answer through a data classification step before contract review. Laura recommends reviewing the form quarterly to confirm the questions still capture what your team needs to move deals forward. Make the form launchable from where stakeholders already work, like Slack or your CRM, so submission isn't the friction point.

What does a usable AI policy for procurement and legal look like?

The policy doesn't have to be a huge document, but it does need to cover the basics: what data can be shared with AI tools, which vendors need extra review, what approval is required for AI-enabled software purchases, and how you verify what a vendor's subprocessors can do with your data. Procurement and legal are the two teams positioned to write the policy together, and most companies know they need one but haven't written it yet.