Introducing legal tech and AI in the legal department: project roles and capacity

Short answer: Implementing legal tech or AI in a legal department takes more than software: it needs a small legal tech implementation project team with a project lead from legal, legal operations for processes and data, lawyers for templates and clauses, and IT and data protection. A CLM project typically takes three to nine months or more. Interim professionals can cover day-to-day work or take on project roles.

This guide is for general counsel, heads of legal and legal operations leads in Switzerland and Germany. It sets out how a legal tech implementation runs, which roles the project team needs, how much capacity is realistic and what AI tools add to the list.

The starting point: why legal tech projects run out of capacity

Legal tech projects rarely fail because of the software. They fail because the same lawyers carry both the day job and the project. Contract lifecycle management (CLM), matter management, document automation and AI assistants all need the same groundwork: describing processes, cleaning up templates, capturing legacy contracts and training users.

• Data quality: legacy contracts sit across drives, inboxes and paper files. Without structured capture, the new system stays empty.
• Templates and clauses: automation needs agreed templates and a clause library. That work is legal, not technical.
• Adoption: business units and lawyers only use a tool if it makes their work simpler. That takes training and support after go-live.
• AI questions: AI tools add confidentiality, data protection and internal usage rules to the scope.

Seven steps to a legal tech implementation

A legal tech implementation usually follows seven steps, from target picture to steady operation. The sequence prevents buying a tool before the problem it should solve is clear.

1. Target picture and use cases: which tasks should become faster, safer or measurable, such as contract approvals, deadlines or requests from the business?
2. Current-state review: capture workflows, volumes, templates, data sources and existing systems.
3. Selection: requirements, market scan, demos with your own cases, data protection and security review, negotiation with the vendor.
4. Configuration: define workflows, user roles, metadata, templates and the clause library.
5. Data migration: capture legacy contracts, extract metadata against a review grid, check samples.
6. Pilot and roll-out: start with one business unit, evaluate, then roll out and train.
7. Operation: settle ownership, metrics and template maintenance for the long term.

In our experience, legal operations reach a first usable state after about three months. How data, clauses and roll-out fit together for a contract management system is covered in Legal operations for a CLM implementation.

Project roles for a legal tech and AI implementation team

A legal tech project needs five to seven roles. Not every role is a separate person, but each one must be covered. The table shows typical tasks, the right level and whether the role can be filled on an interim basis.

Alpinum Solutions provides professionals for legal & compliance transformation through staff leasing or freelancing, part-time or full-time, as individuals or as a project team. The client steers the assignment.

Roles and capacity: how much support is realistic

How much support a legal tech implementation needs depends mainly on contract volume, the number of business units and the timeline. Two set-ups are common:

• Fill a project role externally: an interim project lead or legal operations professional runs the project; the internal team provides know-how and decisions.
• Free up the core team: an interim legal counsel takes over day-to-day contracts and requests so experienced in-house lawyers can work on the project. This keeps template knowledge in the department.

For data migration, a small team of project lawyers with a clear review grid and an experienced team lead often pays off. Data protection and compliance input is usually needed at specific points: before selection, before the pilot and when AI features are approved. Workload can range from 20 to 100 %. Experienced is the most common level for interim assignments; for project leadership and the clause library, senior experience makes sense. How to build processes, metrics and tools that last is covered in Legal operations as a project.

AI tools: what else needs to be settled

AI tools for contract review, research or drafting add three topics: usage rules, data protection and obligations under the EU AI Act.

• AI literacy: providers and deployers of AI systems must take measures to promote the AI literacy of their staff (Art. 4 AI Act, applicable since 2 February 2025, amended with effect from 27 July 2026). A legal department using an AI tool in its professional work is usually a deployer (Art. 3(4)).
• Data protection: if the tool processes personal data with a likely high risk, a data protection impact assessment is required (Art. 35 GDPR; Art. 22 of the Swiss Federal Act on Data Protection, FADP).
• Usage rules: which data may go into the tool, who checks the output and how AI drafts are marked? The company sets these rules.

How to build a lasting structure with an inventory, roles and a committee is explained in Setting up AI governance.

Switzerland and Germany: what differs

The approach is the same in both countries. Differences lie in the legal framework for AI and data protection and in the contracting entity for staff leasing.

Limits and risks

• Responsibility stays with the company: the legal department decides on selection, template approval and usage rules. Interim professionals prepare and implement.
• No legal advice from Alpinum: Alpinum is not a law firm. Contested questions on the AI Act or data protection are for the company and, where needed, its external counsel.
• Keep the knowledge: document configuration, review grids and decisions so the internal team can maintain the system after the assignment.
• Confidentiality: project lawyers in data migration work with personal access rights, a confidentiality agreement and company devices.

Frequently asked questions about legal tech implementation

How long does a legal tech implementation take?

It depends on the tool and the data. For a CLM project, three to nine months or more is realistic in our experience, and about three months to a first usable legal operations set-up. Cleaning up templates and capturing legacy contracts usually take longest, not the technical configuration. A pilot with one business unit shortens the path to the first benefit.

Who should lead the project?

The project lead should know how the legal department works and be able to steer business units, IT and the vendor. An experienced lawyer or legal operations professional often takes this role. If the department lacks capacity, an interim project lead can run the project while sponsorship and decisions stay with the general counsel or head of legal.

Do we need an AI officer for AI tools?

Not by law: the AI Act does not require an AI officer. It does require measures to promote staff AI literacy (Art. 4). A named owner for usage rules, role-based training and documented records are sensible. Where personal data is involved, data protection belongs in the project from the start.

Staff leasing or freelancing for a legal tech project?

Staff leasing fits when the professional works in your team for months, uses your systems and takes professional direction from you, for example in data migration. Freelancing fits defined packages such as a requirements analysis or building a clause library, delivered independently within the agreed mandate. Both models work part-time or full-time.

How quickly can the project team be strengthened?

Selected profiles are usually available within 48 hours; the start date is agreed between the company and Alpinum. Two to four profiles per search are typical. Plan the support as soon as selection or data migration is in sight, so the professional knows the templates and review grid in good time.

Next step

Alpinum Solutions is the leading provider of interim legal & compliance in the DACH region. Tell us about the tool, timeline and bottleneck, and we will send selected profiles for a project role or for day-to-day work.

• Legal & compliance transformation: professionals for projects
• Legal operations for a CLM implementation
• Roles & practice areas: all guides on roles and practice areas
• Discuss your needs

Last updated: 10 November 2026.