Practice

How the work is organized

Technology and RD&I contracts are rarely settled at a single moment: the relationship is structured, negotiated, performed and revisited over years, and each stage calls for a different reading of the same instrument.

This page describes the four workstreams that make up that engagement, the two contractual contexts in which they apply — technology products and services, and research and innovation projects — and the instruments and recurring issues typical of each.

SCOPE

Workstreams

01 / STRUCTURING

Legal and contractual structuring

An engagement may begin before any draft exists. Legal structuring means understanding the subject matter of the relationship, the responsibilities of each party, how performance will occur, the material risks, and the mechanisms needed to give the transaction legal form.

On that basis, the contracts, agreements, terms, policies and other instruments required to formalize the relationship are drafted.

Those instruments are what define, as applicable, scope and deliverables, service levels and acceptance criteria, ownership of background and foreground intellectual property, confidentiality and data processing, liability and warranties, subcontracting, governance of the relationship, change control, business continuity and termination.

The same path applies to technology projects developed jointly by companies, science and technology institutions, and other participants in RD&I initiatives.

02 / REVIEW

Review and negotiation

Contract review is carried out by reading the instrument together with the operation it is meant to govern.

Beyond the legal drafting, the review examines the allocation of responsibilities, the risks of the engagement, the dependencies between the parties, whether the obligations assumed are workable, and the consequences of performance or termination.

Where appropriate, the engagement includes direct negotiation with the counterparty and participation in discussions with legal departments, commercial, procurement, technology, engineering, product, project management and executive teams.

Contracts already negotiated or in final approval may be submitted for a second opinion.

03 / PERFORMANCE

Performance, renegotiation and dispute prevention

Technology contracts frequently need to be interpreted and adjusted while being performed.

The engagement covers changes in scope and requirements, late delivery, disagreements over acceptance criteria, service levels, liability, additional costs, technological change, amendments, renewal, termination and other events affecting the contractual relationship.

In those situations the work includes legal analysis of the contract, definition of the negotiation strategy, drafting of notices, renegotiation and the pursuit of a pre-litigation resolution.

04 / ORGANIZATION

Contract organization and governance

There are also engagements aimed at organizing how technology contracts are handled within an organization, and at making that treatment more consistent.

This work involves drafting or revising templates, model agreements, fallback clauses, negotiation playbooks, escalation criteria, risk benchmarks and other contracting support materials.

It is complemented by preventive review of contracts in force and by portfolio analysis intended to identify instruments requiring attention, updating, amendment or renegotiation.

CONTEXTS

Contractual contexts

The four workstreams apply to two contexts, which follow distinct contractual logics.

Technology products and services

Technology contracts

Relationships among companies, suppliers, developers and customers around technology products and services: software development and licensing, SaaS and subscription models, cloud computing, supply and acquisition of technology, hardware, IoT and connected systems, integrations and APIs, use of open source components, confidentiality and protection of know-how.

Artificial intelligence and generative AI, robotics and autonomous systems, personal data protection and privacy, cybersecurity and incident response, intellectual property and other matters associated with the technologies involved are addressed where relevant to the structuring and performance of the legal relationship.

Recurring issues
  • Artificial intelligence and generative AI
  • AI agents and autonomous systems
  • Privacy, LGPD and data transfers
  • Cybersecurity and incident response
  • Cloud computing
  • SaaS, IaaS and subscription models
  • Software and hardware development
  • Intellectual property and code ownership
  • Software licensing
  • APIs and integrations
  • Open source and license compliance
  • Confidentiality, know-how and trade secrets
  • IoT and connected systems
  • Portability and reversibility
  • Continuity and technology lock-in
  • Support, maintenance and sustainment
Instruments
  • Software development agreements
  • SaaS, IaaS, PaaS and cloud agreements
  • Data processing agreements (DPAs)
  • Service level agreements (SLAs)
  • License and distribution agreements
  • Non-disclosure (NDA) and non-compete (NCA) agreements
  • LGPD and information security clauses
  • AI supply and integration agreements
  • Terms of use and policies
  • Assignment of rights and source code
  • Support and maintenance agreements
  • Hardware supply agreements
Research and innovation projects

RD&I contracts

Research, development and innovation projects carried out by companies, science and technology institutions and other participants. The contractual analysis covers the structuring of partnerships, ownership and exploitation of results, background and foreground intellectual property, scientific publication, confidentiality, project governance, contributions, liability and exit mechanisms.

Where a project is carried out with statutory incentive funding, the funding regime adds its own set of requirements to the contract: qualification of the project and of eligible expenses under the applicable rules, definition of counterpart contributions, ownership and exploitation rules consistent with the instrument, and reporting obligations toward the managing and funding bodies. Each regime — the Brazilian Informatics Law, the PPI Fund, ANEEL R&D, FINEP, FAPESP and the Legal Framework for Innovation — imposes distinct requirements, which must be reflected in the instrument from the outset.

Funding regimes and statutes
  • Brazilian Informatics Law (Lei de Informática)
  • PPI Fund
  • ANEEL R&D programme
  • FINEP
  • FAPESP
  • Legal Framework for Innovation
Recurring issues
  • Ownership and exploitation of results
  • Co-ownership and technology licensing
  • Partnerships between companies and ICTs
  • Artificial intelligence in research projects
  • Confidentiality and scientific publication
  • Project governance and contributions
  • Eligibility and reporting
  • Research data and LGPD compliance
Instruments
  • RD&I partnership agreements
  • Research and development cooperation agreements
  • Technological order contracts (encomenda tecnológica)
  • Grant award terms
  • Co-ownership agreements
  • Technology licensing agreements
  • Research confidentiality undertakings
  • Material transfer agreements
REACH

Domestic and cross-border transactions

Technology and RD&I contracts frequently involve parties located in different countries. In those matters, the four workstreams apply to instruments drafted in English and to negotiations conducted directly with foreign counterparties, legal departments and technical teams.

The practice is limited to Brazilian law: it covers those aspects of the transaction governed by Brazilian legislation, including where the client is a foreign individual or organization that contracts for, supplies or develops technology in Brazil.

CONTACT

Office address

Rua Comendador Tórlogo Dauntre, 74
Suite 1207 — Cambuí
Campinas — São Paulo — Brazil — 13025-270

Meetings

In person or remote, by appointment.
In Portuguese or English.

Rolar para cima