Integration as a Service explained: How law firms can embrace the future of Legal Tech through composable modularity
Integration as a Service explained: How law firms can embrace the future of Legal Tech through composable modularity

Integration as a Service explained: How law firms can embrace the future of Legal Tech through composable modularity

Modern law firms have evolved very far from a traditional 'monolithic' application strategy where the majority of the firm's processes were supposed to be supported by one or two key applications. In the fast-evolving world of legal tech, the ability to seamlessly integrate various systems and services is crucial to improve efficiency and client service, while ensuring compliance with internal and external requirements (business, quality, security, regulatory etc.,).

Pace-layered application strategy

Gartner introduced the 'pace-layered application strategy' concept a couple of years ago, describing how the components in an organisation's tech stack can be categorised into different layers with regard to architecture, process change, funding, development practices, business engagement and planning horison. We believe this concept is highly relevant in today's legal tech landscape where you have your core 'systems of record' (e.g., DMS, ERP/PMS, and HR), and then want to add smart and innovative 'systems of differentation' and 'systems of innovation' on top of those core systems.

Gartner: Pace-layered application strategy

Composable modularity

The related Gartner concept of 'composable modularity' is crucial. Composable modularity refers to the design and implementation of systems, processes, and structures in a modular and flexible manner. This design principle is often realised through the adoption of containerisation and microservices, which allow for the creation of highly adaptable and scalable applications. Composable modularity extends beyond APIs and data management; applications and services needs to be inherently flexible and configurable. Such adaptability is key to supporting seamless process and workflow integration, not just within an organisation’s existing tech stack, but also in interfacing with emerging technologies and external systems.

Gartner: Composable modularity

The challenges

While a pace-layered application strategy and composable modularity are conceptually straightforward, market research reveals that organisations struggle with significant master data and integration challenges. Applications and services are often poorly integrated (if at all), master data is not consistent across applications, and the lack of a cohesive integration strategy stifles innovation and adoption of new technologies.

With those challenges outlined, let's explore how law firms can address those data management and integration challenges.

Different integration methods

Let us start by describing four common types of integrations/integration approaches:

Out-of-the-Box integrations in applications

These are pre-built connectors provided within applications designed to work with little or no configuration. While convenient and economical, they typically lack flexibility and may not cover all business needs. There is also a significant risk that the two solution providers involved may blame any issues with the integration on the other party.

Typical examples: a document automation tool that has an out-of-the-box integration to a document management system (DMS), or a practice management system (PMS) that has an out-of-the-box integration to an accounting system.

Point-to-Point Integrations

These are typically custom integrations between two applications and services, delivered by either a solution provider or a third-party systems integrator. These integrations are of course purpose-built and flexible, but can be expensive to build and maintain, and over time often become complex and hard to manage as the number of integrations increases. And there is a significant risk that the solution providers or system integrator involved may blame any issues with the integration on the other parties.

Typical examples: a CRM system that has a custom integration to a practice management system (PMS), or an HR system that has a custom integration to a learning managemet system (LMS).

Integration Platforms

Integration platforms are commonly referred to as integration platform as a service or 'iPaaS'. Generic integration platforms such as Azure Integration Services, Mulesoft and Dell Boomi allow expert users to create and manage multiple integrations in one place using a standardised approach. These platforms provide tools and connectors that facilitate the integration of a wide range of applications and services. As most law firms lack the skills and resources to build and manage integrations, they are typically built, managed and updated by consultants/systems integrators. The iPaaS approach increases flexibility, decreases the effort to build and maintain integrations, and also help organisations overcome many the pitfalls of traditional integrations (e.g., 'spaghetti integration'). The total cost of ownership can however be significant as well as unpredictable, and you also have the challenge where there are several parties involved, and noone takes the full responsibility of the integrations.

Other advantages of a modern integration platform:

  • Typically offer standard connectors to common applications and services (one consideration is however that many US based platforms are US centric when it comes to what applications and services they support, and rarely offer standard connectors to applications and services that origins from the Nordics and other European countries).
  • Provides active orchestration and monitoring of integrations.
  • Supports many different integration methods including traditional file-based integratons.
  • Acts as the active part between two passive APIs (many APIs are passive, and can't activate or trigger workflows on their own).
  • Can validate, transform and enrich data in the integration process.
  • Can manage master data and metadata across applications and services.
  • Can manage both structured and unstructured data in integrations.
  • Can workaround limitations in APIs and integration methods, e.g., lack of webhooks in the applications and services you want to integrate.

Typical platform examples: Integration platforms can vary widely in their focus and capabilities. There are more traditional integration platforms such as Azure Integration Services, Mulesoft and Dell Boomi - robust platforms that offer extensive capabilities for complex integrations across both cloud and on-premise environments. They are well-suited for sophisticated integrations that require detailed oversight and management. On the other hand automation-focused platforms like Tray.io, Workato, and Zapier emphasise user-friendly interfaces and are geared towards business users rather than IT specialists. These platforms excel in automating workflows and integrating common business applications with minimal coding required, making them accessible to a broader range of professionals.

Integration as a Service

Integration as a Service (IaaS) is a model where a IaaS provider deliver integrations as a managed service based on an integration platform. From a customer perspective, IaaS offers several compelling advantages:

  • Less Risk: The IaaS provider manage the technical risks associated with integrations, including maintenance and compliance with ever-changing data security standards.
  • Predictable Costs: With a subscription-based model, IaaS offer a predictable and all-inclusive cost of ownership.
  • No Need for In-House Expertise: IaaS removes the need to have the technical skills dedicated to building and maintaining integrations (either in-house or through a consultant/systems integrator). This can be particularly advantageous for legal firms where IT resources are often limited.
  • Contractual support and SLA: The IaaS model includes support through a single point of contact and a contractual SLA.

However, this model is not without its considerations. As with most 'as a service' models, customers have less direct control over their integrations Customers experience less direct control over their integrations, which, while efficient, may not align with the preferences of decision-makers who favour a hands-on approach. Moreover, a firm’s reliance on their IaaS provider for critical business operations necessitates a thorough vendor evaluation process to ensure reliability and quality service.

A critical factor to assess when selecting an Integration as a Service (IaaS) provider is their geographical reach and industry-specific expertise. These elements influence the availability of standard connectors, which are essential for cost-efficient and seamless onboarding. The provider's regional presence can also impact the cost of onboarding new systems and adding additional integration points, known as 'endpoints'. Moreover, it is important to consider the provider’s commitment to expanding its offerings. This includes the anticipated introduction of new connectors and features in their development roadmap, ensuring the service will evolve in line with your business needs.

A high level comparison of the four common integration approaches

Conclusion: embracing the future of Legal Tech through composable modularity

When looking at the tech stack of a modern law firm it is apparent that a dynamic, integrated approach to legal tech is a strategic imperative. And the pace-layered application strategy and the concept of composable modularity offers a structured yet flexible blueprint for law firm's digital transformation journey.

Forward-thinking law firms have the opportunity to leverage their core 'systems of record' while introducing key 'systems of differentiation' and experimental 'systems of innovation', all aimed at streamlining operations and bolster client service. However, despite the straightforwardness of these strategies, real-world implementation highlights significant challenges, particularly related to master data consistency and integration.

The discussion around different integration methods - out-of-the-box integrations, point-to-point integrations, iPaaS, or IaaS - underscores the need for a strategic approach to integrations and master data management. Forward-thinking law firms need to implement a strategy that not only aligns with current operational demands but also positions them favourably for future technological shifts.

Integration as a Service should in our opinion be a cornerstone of a future-proof integration strategy for law firms. By shifting complexity and accountability to specialised IaaS providers, law firms can enjoy the benefits of reduced risk, predictable costs, and a diminished need for in-house expertise. The additional consideration of an IaaS provider's geographical and industry-specific focus further refines the selection process, ensuring that the solution aligns with the firm's unique business trajectory and regional compliance requirements.

IaaS shifts complexity and accountability to the IaaS provider

In conclusion, a comprehensive integration strategy help law firms overcome integration and master data hurdles in order to fully unleash the full potential of legal tech. Through integration as a service, law firms are empowered to use technology as an enabler of efficiency, innovation, and superior client service.

要查看或添加评论,请登录

社区洞察

其他会员也浏览了