A legal ops platform rollout almost never lands in one phase, which makes the sequencing decision one of the first a legal operations lead has to defend. Starting with intake gives the department visibility into demand quickly and puts a new process in front of the whole business. Starting with matters gives lawyers a working system of record before anyone asks them to change how work arrives. Each order produces a different first year, and this article covers what each buys, what each costs, and how to choose.
What does sequencing a legal ops platform rollout actually decide?
Sequencing a legal ops platform rollout decides which group experiences the change first and what evidence the department holds when it asks for the next phase. For context, a 2024 operations index found 79 percent of law departments saw the volume of legal work increase over the past year. Both consequences outlast the phase itself.
Three things follow from the order chosen.
- Who has to change behavior first. Intake first asks the business to change. Matters first asks lawyers to change.
- What data exists at the end of phase one. Intake produces demand data. Matters produce workload and spend data.
- What the next phase inherits. Each order leaves the following phase with different foundations and different gaps.
The decision belongs at scoping, because retrofitting the other half is more expensive than building both in the right order.
What does starting with intake give a legal department?
Starting with intake gives a legal department visibility into demand within weeks, which is usually the fastest available answer to the question of how much work the function absorbs. It also puts a structured process in front of every business user at once.
The visibility argument carries weight in current conditions. CLOC’s 2026 State of the Industry Report, based on the 2025 Harbor Law Department Survey, describes a structural productivity gap where workload surges while budget and headcount growth flatten. A department arguing for resources needs demand data, and intake is what produces it.
Speed of response improves alongside visibility. Progress Software’s State of Legal 2026 report, based on a nationwide survey of US lawyers, found 47 percent saying intake takes four days or longer while most believe two to three days or less is appropriate. Structured intake with automatic routing closes much of that gap without adding people.
The build detail sits in building legal service request intake.
What does starting with intake cost?
Starting with intake costs the department a place to put the work once it arrives. Requests land in a queue, get routed correctly, and then need somewhere to live as matters, budgets, and documents.
Three difficulties recur when intake runs ahead of the matter layer.
- Requests accumulate with nowhere to convert. A request needing sustained work becomes a matter, and without a matter structure it stays a ticket.
- Reporting stops at the front door. Volume by type and business unit becomes visible while spend and cycle time remain invisible.
- Lawyers see effort without benefit. They receive better-formed requests and gain nothing else, which weakens their support for phase two.
That last point matters more than it appears. Lawyers who experience phase one as administrative overhead become harder to bring along later.
What does starting with matters give a legal department?
Starting with matters gives lawyers a working system of record before anyone changes how work reaches them, which usually produces less resistance from the people whose support the whole program depends on.
Matters first also establishes the taxonomy, the security model, and the reporting structure that intake will later feed into. Those decisions have to be made regardless, and making them first means intake forms map onto a structure that already exists. The operating model is covered in legal matter management and what good looks like.
Financial control becomes available earlier on this path. Matter budgets, invoice rules, and accruals all attach to matters, and none of them work without the matter layer in place.
What does starting with matters cost?
Starting with matters costs the department demand visibility for the length of phase one, and work continues arriving by email throughout. Nothing about the intake problem improves while the matter layer is built.
Two further costs are worth planning for. Matter data quality stays dependent on manual entry, so the fields that drive reporting get filled inconsistently until structured intake populates them. And the business sees no change at all, which makes the program invisible to the stakeholders whose budget eventually funds it.
Manual matter opening also produces the taxonomy problem in reverse. Lawyers select matter types inconsistently when nothing upstream constrains the choice, and correcting that history later is a remediation exercise.
Which sequence suits which legal department?
The right sequence depends on which problem the department is currently unable to answer for its leadership. That question resolves most cases faster than a general principle.
- Choose intake first when demand is invisible, when the business complains about legal responsiveness, or when the department needs evidence to justify headcount.
- Choose matters first when outside counsel spend is the pressing problem, when matter data already exists somewhere and needs consolidating, or when lawyer adoption is the main risk.
Spend pressure often decides it. Many legal departments still have no formal outside counsel guidelines, and most of those that do enforce them lightly. A department facing that problem gains more from the matter and spend layer first.
Is there a third option?
A thin slice of both is the third option, and it works well for departments that can define a narrow enough scope. One or two matter types run end to end, from intake through matter creation to closure, for a single business unit.
That approach delivers three things a single-layer phase cannot. It proves the whole chain works before scale is attempted. It produces a reference implementation the next business unit can be shown. And it surfaces integration problems while the blast radius stays small.
The constraint is discipline about scope. A pilot that expands during delivery becomes a full rollout without the planning of one.
What stays constant regardless of rollout sequence?
Four decisions carry the same weight whichever phase runs first, and settling them early avoids rework in both directions.
- The matter taxonomy. Intake forms and matter records both depend on it, so define it before either is configured.
- The security model. Access rules apply across both layers, and retrofitting them is expensive.
- The data migration plan. Historical matters need cleansing whenever they move, a pattern covered in why messy legacy data can ruin a perfect platform build.
- The support model. Each phase generates its own wave of questions, and each needs staffing.
On one enterprise legal platform rollout, Basla’s delivery team handled roughly two hundred tickets in the first week after go-live, around sixty percent of which were users asking how to complete a task. The hypercare window ran for eight weeks, and a phased program repeats that pattern at every phase, as described in why launches fail without a dedicated hypercare triage desk.
Conclusion
A legal ops platform rollout sequenced well makes each phase easier to fund than the one before it, because each produces evidence the next phase needs. Sequenced badly, phase one consumes goodwill and produces data nobody asked for.
Four principles hold across the choice. Start with whichever problem the department currently cannot answer for its leadership, since that is what makes phase two fundable. Define the taxonomy and the security model before configuring either layer, because both depend on them. Consider a thin end-to-end slice covering one or two matter types, which proves the chain works while the blast radius is small. And staff the support model for every phase, since each one puts a new group of users in front of an unfamiliar system for the first time.
How Basla can help
Basla provides delivery teams for legal technology implementation, covering business analysis, configuration support, data migration support, testing coordination, documentation, and post-go-live support. Basla has delivered legal technology services across more than a hundred jurisdictions, with hands-on experience supporting Onit legal service request, matter management, eBilling, and contract workflows.
Frequently asked questions
Should a legal ops platform rollout start with intake or matters?
The sequence should follow whichever problem the department currently cannot answer for its leadership. Intake first suits departments where demand is invisible or responsiveness is criticised. Matters first suits departments where outside counsel spend is the pressing issue or lawyer adoption is the main risk.
What does starting with intake achieve first?
Starting with intake produces demand visibility within weeks, showing request volume by type and business unit. It also improves responsiveness through automatic routing and puts a structured process in front of the whole business at once.
What is the risk of implementing intake before matter management?
The main risk is that requests arrive with nowhere to convert, so work needing sustained effort stays as tickets. Reporting also stops at the front door, showing volume while spend and cycle time remain invisible, and lawyers experience the change as administrative overhead.
What is the risk of implementing matter management first?
The main risk is that demand stays invisible for the length of phase one while work continues arriving by email. Matter data quality also depends on manual entry, so reporting fields get completed inconsistently until structured intake populates them.
Can intake and matter management be implemented together?
A thin end-to-end slice covering one or two matter types for a single business unit works well, running from intake through matter creation to closure. It proves the whole chain before scale is attempted, provided the scope holds during delivery.
What decisions apply regardless of rollout sequence?
The matter taxonomy, the security model, the data migration plan, and the support model all apply across both layers. Defining the taxonomy and security model before configuring either avoids rework in both directions.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*