Tech & Sourcing @ Morgan Lewis

Morgan Lewis’s technology, outsourcing, and commercial transactions team often advises on transactions where there is some form of intellectual property being transferred from one party to another party. This may be due to a corporate transaction, a cooperation or joint venture arrangement, or some other form of commercial agreement.

While the regulatory landscape around artificial intelligence (AI) continues to evolve, navigating contractual arrangements and apportioning risk for the use of AI may seem like stepping into the unknown. In this blog post, we consider how a few familiar concepts within commercial contracts may be applied to the provision and use of AI tools as part of services.

As noted in our recent blog posts, The Rise of Next-Gen Business Process Outsourcing and Key Contracting Issues to Consider, the core premise of next-gen business process outsourcing (BPO) includes (1) the leveraging of automation, bots, performance tools, and other technology to transform and optimize workflows and business processes and (2) the implementation of solutions to collect and analyze data to improve user experiences and business outcomes. Next-gen BPO drives the development and implementation of transformative technology and the generation of critical business data. As such, the identification of key intellectual property (IP) and the allocation of IP use and ownership rights invariably becomes a gating issue in contract structuring and negotiations.

Our recent blog post, The Rise of Next-Gen Business Process Outsourcing, highlighted the importance of understanding the exciting opportunities and the challenges of next-gen business process outsourcing (BPO) in order to effectively negotiate contract provisions that maximize the benefits of next-gen BPO and minimize the risks. In this blog, we take a look at a few key issues to consider when developing and negotiating a next-gen BPO contract.

Business process outsourcing (BPO) transactions are on the rise, with bullish forecasts from industry analysts including a projected revenue annual growth rate (CAGR 2023–2027) for the global BPO market of 6.48%, reaching a market volume of $450 billion by 2027 and global revenue exceeding $500 billion by 2030, and the North American market alone projected to achieve 8.9% CAGR 2023–2030.

The use of open-source software (OSS) is ubiquitous. Depending on what license governs the type of OSS a company uses and how it uses the OSS, OSS use impacts the valuation of the intellectual property (IP) used by a company or transferred in a merger or acquisition (M&A). Thus, OSS-related representations and warranties have become an integral part of the IP representations and warranties in M&A transactions and financings.

In the era of digital transformation, businesses increasingly rely on software-as-a-service (SaaS) solutions for various operational needs. For a buyer, it is crucial to prioritize data security when negotiating SaaS contracts to safeguard sensitive information and comply with data protection regulations. In this post, we explore the essential data security provisions buyers should consider when entering into SaaS agreements.

Software as a service (SaaS) is a distribution model where the software vendor hosts their software on their own servers, or the cloud, as opposed to the customer purchasing the software for use on their own on-premises servers.

The decision to terminate an agreement cannot be taken lightly. In exercising the option, understanding the key terms of the agreement and necessary steps to effectuate the termination are critical. As we have previously highlighted in past Contract Corners, termination provisions may include a variety of mechanisms built into them and one cannot assume that all termination provisions require the same steps to be taken. When considering a termination, a party must take the time to assess the actual termination rights under the agreement, what, if any, notice period will apply, and whether the termination will result in any payment or other obligations.

In Part 1, we discussed what a dependency in a technology integration is and how to deal with it in a contract. In this installment, we’ll consider how to address the risk of the assisting party not providing required information or assistance.