Home » Case Studies » American-Asian Global Technology Company
Case study · Legal operations managed services

American-Asian Global Technology Company Legal operations run as infrastructure.

Swiftwater designed and operated the legal operations infrastructure of an American-Asian global technology company whose legal department managed thousands of active matters and hundreds of outside counsel firms across North America, Europe, Asia-Pacific, and other international markets.

$60M
Outside counsel savings
Over the life of the engagement. Outcomes are specific to this client.
ClientAmerican-Asian global technology company (media and technology)
HeadquartersUnited States and Asia
MarketsNorth America, Europe, Asia-Pacific, and other international markets
Legal environmentThousands of active matters, hundreds of outside counsel firms and legal vendors, substantial global legal spend, legal teams across multiple regions
PlatformOnit enterprise legal management and eBilling, replacing an aging eBilling system across four continents
EngagementMulti-year. Began as strategic advisory and became an embedded operating partnership
ServicesLegal operations strategy and org design · Managed legal operations · Global bill review and legal spend · Onit implementation, administration and expansion · Global investigations playbook · ELM, finance, and procurement integration
Headline outcome$60M in outside counsel savings

The bottom line

Swiftwater designed and operated the legal operations infrastructure of an American-Asian global technology company whose legal department managed thousands of active matters and hundreds of outside counsel firms across North America, Europe, Asia-Pacific, and other international markets. The engagement produced $60M in outside counsel savings and ran six recurring functions: legal operations strategy and organizational design, managed legal operations, global bill review and spend management, Onit implementation, administration and expansion, a global investigations playbook, and integration between Onit and the company’s finance, procurement, and HR systems. The department gained enterprise-scale capability without equivalent growth in permanent headcount.

What the legal department looked like

The client was a global technology company headquartered in the United States and Asia, with legal responsibilities across North America, Europe, Asia-Pacific, and other international markets. Its legal department managed thousands of active matters, worked with hundreds of outside counsel firms and legal vendors, carried substantial global legal spend, and billed in multiple currencies under multiple tax regimes and billing practices.

The company grew quickly across borders under significant regulatory scrutiny. Department structures, approval authorities, reporting lines, and cost centers changed often, and the legal function depended on Finance, Procurement, Accounts Payable, HR, Compliance, and Corporate IT for data and process.

Why a dual-headquarters model added complexity

Running legal operations from two headquarters meant the same process had to work across different regional business practices, legal and regulatory expectations, languages and communication styles, time zones, internal decision-making structures, levels of outside counsel billing maturity, and enterprise technology standards. The department needed one global operating model that stayed responsive to regional difference.

Why fragmentation was the real problem

The legal department had invested in legal technology, but growth fragmented ownership, process, systems, and governance faster than the internal team could absorb. Six conditions defined the starting point:

  1. Ownership of legal operations overlapped across Legal Operations, Vendor Management, Procurement, Finance, Accounts Payable, Corporate IT, and the practice groups.
  2. Internal capacity to run day-to-day operations was limited, and processes differed by region and team.
  3. External legal spend was rising, high volumes of invoices needed review, correction, clarification, or resubmission, and billing practices varied across an international firm ecosystem.
  4. The department ran on an aging eBilling system, and nobody had the capacity to administer and improve it as reorganizations rippled through matter assignments, approvals, reporting hierarchies, and access.
  5. Leadership wanted stronger, more consistent management of global investigations.
  6. Legal systems had to exchange data with finance, procurement, AP, HR, and reporting systems that differed by entity and region.

The underlying need was a global operating model that converted strategy, systems, policies, and data into consistent daily execution.

The operating model

The Legal Operations Infrastructure Model

Over the life of the engagement the work settled into a five-layer operating model that Swiftwater ran as five recurring functions.

Five-layer Legal Operations Infrastructure Model: Strategic, Operational, Technology, Control, Global CoordinationStrategicStrategy · Org development · Governance · Roadmap · Operating model · Executive advisoryOperationalInvoice lifecycle · Vendor coordination · Workflow · Issue resolution · Reporting · Managed servicesTechnologyOnit administration · Workflow configuration · Platform governance · Integration · MiddlewareControlBilling governance · Process standards · Approval controls · Data integrity · Reporting continuityGlobal coordinationRegional alignment · Global standards, local variation · Law firm coordination · Cross-time-zone delivery
StrategicOperationalTechnologyControlGlobal coordination

Strategic layer

Legal operations strategy, organizational development, governance, roadmap management, operating model design, and executive advisory to legal leadership.

Operational layer

Matter administration and invoice review, vendor coordination, workflow management, issue resolution, reporting, and the recurring managed services that kept the department running.

Technology layer

Onit implementation and administration, workflow configuration, platform governance, systems integration, middleware development, and technical implementation support.

Control layer

Billing governance, process standardization, approval controls, data integrity, reporting continuity, and operational oversight.

Global coordination layer

Regional stakeholder alignment, global process standards with managed local variation, law firm coordination, cross-time-zone delivery, and support for a dual-headquarters governance environment.

Together the five layers formed one operating infrastructure.

Six recurring functions

What Swiftwater ran for this legal department

01

Legal operations strategy and organizational design

Swiftwater advised legal leadership on the operating model, decision rights, governance, and roadmap, and turned every reorganization into operational and system change.

Clear ownership and one governance framework.

Read the case study →
02

Managed legal operations

Swiftwater acted as an extension of the internal Legal Operations function: program management, workflow, escalation, vendor support, reporting, and continuity through leadership transitions.

Enterprise-scale capability without equivalent growth in permanent headcount.

Read the case study →
03

Global bill review and legal spend management

Swiftwater’s seven-person Matter Administration and Invoice Review (MAIR) team ran every step from matter setup to invoice payment and reconciliation, across hundreds of firms.

$60M in outside counsel savings.

Read the case study →
04

Onit implementation, administration and expansion

Swiftwater moved the department from an aging eBilling system to Onit, migrated millions of records, deployed across four continents, then administered and expanded the platform.

Onit live on four continents and grown into the department’s operating platform.

Read the case study →
05

Global investigations playbook

Swiftwater designed one investigations framework with defined stages, roles, intake, triage, and reporting, and built a proprietary tool within Onit to deploy it globally.

One global framework with managed local variation.

Read the case study →
06

ELM, finance, and procurement integration

Swiftwater connected Onit with finance, procurement, AP, HR, and reporting systems through proprietary middleware where standard integrations fell short.

Information moved between Onit and the corporate systems.

Read the case study →

Results

$60M in outside counsel savings was the headline. Behind it sat six changes in how the department ran.

Stronger governance

Roles and responsibilities were defined across legal operations, financial management, technology, vendor management, and operational delivery. Workflows were consistent across regions, escalation paths were explicit, and Legal, Finance, Procurement, AP, and Corporate IT worked from the same operating model.

Improved legal spend management

Invoice compliance got stronger and review became consistent. Clean invoices reached the attorneys, and rejected and stuck invoices fell. Billing leakage went down. The department gained visibility into external spend and ran preferred provider management, rate governance, outside counsel performance, and financial reporting as a discipline.

More value from Onit

Onit replaced the aging eBilling system and stayed aligned with organizational structures, approval authorities, reporting requirements, matter ownership, billing processes, and evolving business needs. The platform ran as part of the operating model.

Scalability without headcount

The department added strategic leadership, operational management, bill review resources, system administration, technical expertise, and program management through one coordinated delivery model, without equivalent growth in permanent internal headcount.

Global consistency with regional flexibility

Global operating standards applied everywhere, and regional variation was explicit and managed. For a dual-headquarters organization working across diverse jurisdictions, firm markets, regulatory environments, and internal operating cultures, that balance kept one global standard in use in every region.

Continuity through change

The operating model held through changes in legal operations leadership, internal ownership, organizational structure, team composition, and strategic priorities, and institutional knowledge stayed with the function through every change in personnel.

The $60M figure reflects outside counsel savings over the life of the engagement. Outcomes are specific to this client and depend on spend profile, firm mix, and platform maturity.

Who this model fits

  • Global or multi-region legal departments with hundreds of outside counsel firms
  • Departments with an ELM platform in place, or moving off an aging eBilling system
  • Departments where ownership of legal operations is split between Legal, Finance, Procurement, and IT
  • Organizations that reorganize often

Frequently asked questions

What is a legal operations infrastructure model?

A legal operations infrastructure model is an operating structure in which the recurring functions of a legal department (strategy, operations, technology, controls, and global coordination) run as continuous, staffed and measured layers. Swiftwater’s five-layer version was built for this client.

How does managed legal operations differ from hiring internally?

A managed model gives access to strategic, operational, financial, and technical capability at once, scales with demand, and keeps institutional knowledge when individuals change. Hiring the same capability internally requires several specialized roles and leaves the department exposed at each departure.

What does global bill review involve for a department with firms in many countries?

It starts at matter setup, where most invoice issues begin, and runs through compliance validation of every invoice, substantive review of complex or higher-risk invoices by experienced reviewers, regional tax invoice handling, and structured management of rejections and resubmissions, through to payment and reconciliation.

Who administered Onit in this engagement?

Swiftwater implemented and administered the platform (users, workflows, reporting, data integrity, releases) and the client owned the decisions. Every organizational change was translated into a system change so the platform kept matching how the department operated.

How were investigations kept consistent across jurisdictions?

One global playbook defined stages, roles, decision points, intake, triage, and reporting, and a proprietary tool Swiftwater built within Onit deployed it globally. Local legal requirements, employment rules, confidentiality restrictions, and regulatory obligations were handled as documented variations inside that framework.

How is this different from fractional staffing?

Swiftwater provides fractional support as part of the model. The difference is in how the people are chosen and what stands behind them: Swiftwater matches the level of experience to the work and the cost to the level, and every person on the account is backed by Swiftwater’s frameworks and the broader team, so the client is never dependent on one individual.

Talk to the team

Talk to the team that ran this model.

    Thanks, there. Someone will respond to your message shortly. While you wait, grab a 30 minute discovery call with one of our practice team leaders.

    Select a Meeting Time
    Next step

    Ready to run legal operations as infrastructure?

    A 30-minute discovery call on how your legal operations run today and what a managed operating model around your team would look like.

    Book a Discovery Call

    No commitment. No pitch deck. Just a direct conversation with an expert.