This blog series builds on a recent joint webinar with Priori, Harbor, and LexisNexis CounselLink® on what it takes to manage legal spend end-to-end—from RFP through Accounts Payable (AP).
Speakers included Basha Rubin (CEO & Co-Founder, Priori), Kevin Clem (Chief Growth Officer, Harbor), Dan Ruderman (Director of Strategic Partnerships, LexisNexis CounselLink®), Russ Philpott (Director of Legal Operations & Corporate Counsel, Okta) and An Trotter (Senior Director of Operations, Hearst).
The debate: one enterprise tool vs a legal-specific workflow
Legal departments and procurement teams often agree on the goal—more consistency and better buying decisions—but get stuck on a practical question: Should legal run RFPs in the enterprise procurement tool, or in a legal-specific system?
It’s a fair debate. As Basha Rubin, Priori’s CEO & Co-Founder, acknowledged during the webinar, “I understand the argument from procurement teams. They want to have one tool as opposed to stitching together a lot of them.”
With that in mind, Basha emphasized that what legal needs is something different: interoperability with other systems in the legal ecosystem, the amount of data and unique data structure you need to run meaningful legal RFPs, and the user experience for your attorneys to actually use it at scale.
In Basha’s words, “The same sourcing tool shouldn’t be used to buy pens for your company that is being used to buy legal services.”
That line lands because it’s a workflow reality. Buying legal services often involves sensitive data, complex scoping, and high-stakes outcomes. If the tool isn’t built around those realities, adoption suffers—and the “RFP to AP” lifecycle breaks at the handoff.
Where enterprise procurement tools tend to break for legal
1) Legal sourcing requires legal-specific data and structure
Basha called out the “amount of data and unique data structure” legal teams need to make meaningful outside counsel hiring decisions—especially if you want more than one legal ops stakeholder to run the process.
That’s the underlying reason many enterprise tools become hard to scale in legal: they weren’t built to capture and compare the kinds of inputs legal needs to evaluate firms in a consistent, decision-ready way.
2) Attorney experience determines adoption
The other point Basha made was straightforward: the workflow has to work for attorneys. In her framing, the “user experience for your attorneys… is not being delivered by an Ariba.”
That matters because outside counsel selection is not a background procurement activity—it’s a day-to-day legal workflow. If the experience isn’t designed for how attorneys actually engage outside counsel, you don’t get adoption at scale. You get a bottleneck.
3) Integration is the difference between an RFP event and an end-to-end lifecycle
This was one of the most concrete moments in the webinar: the tool choice isn’t just about where you collect proposals—it’s about whether the outputs of the RFP can carry forward into billing and matter workflows.
As An Trotter, Hearst’s Senior Director of Operations, explained, a major limitation of generic procurement systems is that they often aren’t integrated into the legal systems where matters are managed. The practical impact is huge: if your RFP terms don’t flow into the systems that govern billing and oversight, you’re back to manual enforcement.
In her words (paraphrased tightly to the core idea she described): once agreed terms can be pushed into matter management and monitored through dashboards, teams can spot staffing or budget drift early enough to course-correct, rather than discovering problems after invoices arrive.
The simplest litmus test
If your goal is end-to-end accountability (not just “running an RFP”), here’s the question to ask:
Can the RFP workflow connect cleanly to matter management, billing, and reporting—so the deal you negotiated becomes enforceable?
That’s the difference between:
- An RFP as a one-off exercise, and
- An RFP as part of a continuous operating model (RFP → budget → billing → reporting → better future decisions).
A useful analogy: eBilling had this same debate
Kevin Clem, Harbor’s Chief Growth Officer, made a useful comparison: legal departments asked a similar question years ago—why not just use enterprise billing and attach a PDF?
The reason legal-specific eBilling won is the same reason legal-specific sourcing tools exist today: legal requires a data model and workflow built for legal work (the codes, roles, phases, and reporting structure that make the data usable).
Kevin’s point was that RFPs follow the same “fit for purpose” logic—legal-specific tools tend to have the legal-specific structure natively, rather than relying on heavy configuration.
He also noted that value from RFPs isn’t only price savings. Teams often gain clarity from how firms propose to approach and staff a matter—strategy and structure you can’t reliably compare if your process forces legal work into a generic sourcing format.
Where procurement does belong (and how to make it work)
The takeaway from the webinar wasn’t “procurement out.” It was more nuanced:
- Procurement can add value through organizational requirements and best practices.
- Legal must own the process because legal work is specialized and often high-impact.
Basha was direct on ownership: procurement should support, but legal must ultimately own outside counsel selection.
And both Dan Ruderman, LexisNexis CounselLink®’s Director of Strategic Partnerships, and Russ Philpott, Okta’s Director of Legal Operations & Corporate Counsel, emphasized a pragmatic approach. Engage procurement early, educate each other, and use procurement’s expertise (especially around things like security and vendor onboarding requirements) without ceding control of legal-specific sourcing decisions.
What to look for in a legal-specific RFP tool
If you’re building an end-to-end workflow (not just collecting bids), the webinar discussion points to a practical checklist:
- Legal-ready structure for scoping and comparing proposals
- A legal-specific data model that supports meaningful evaluation at scale
- Attorney-friendly UX (so adoption isn’t limited to a single ops user)
- Integration pathways into matter management and billing so terms become enforceable
- Reporting that closes the loop—so outcomes inform future sourcing and governance
In other words: if a tool can’t support “RFP to AP” as a connected lifecycle, it will struggle to deliver repeatable control—no matter how standardized it is across the enterprise.
If you’re building an end-to-end workflow from RFP to AP, these earlier posts lay the foundation:
In Part 1, Legal Spend Management Still Operates in Silos, we cover the why: pressure is rising, spend expectations are tightening, and most teams still don’t have their sourcing and billing workflows connected.
In part 2, we explore What End-to-End” Spend Management Actually Means (and Why It Matters).
Part 3, The End-to-End Spend Lifecycle (How It Works in Practice) walks through what this continuous loop looks like and how to make sure each stage of the matter lifecycle strengthens the next.
See what “RFP to AP” looks like in practice. Request a demo of Priori’s end-to-end outside counsel workflow.
