From scattered files to a clear thread through the entire contract lifecycle

How Plum Safety got their CLM process under control with .legal

Who is Plum Safety?

Plum Safety is a Danish company that manufactures and distributes medical devices globally. Around 65–70 people in total, but it's a small, dedicated team in the QA/RA and legal department that handles the company's contracts day to day. Three or four people with their hands deep in agreements, negotiations, and contractual obligations on a daily basis.

For Ulrik Dueholm Beckmann, QC, CM and ESG Lead at Plum Safety, the impact is clear:

"Time savings. We're far more process-efficient, and just by loading a contract into the system I save 15–30 minutes every time."

With around 250 contracts in the system and roughly 100 updated each year, that's not a small gain. Those are hours that can be spent each week on work that actually requires human judgement, rather than manual data entry.

In a regulated industry like medical devices, contracts aren't just administrative documents. They're an integrated part of the company's quality and compliance setup, and mistakes or delays have real consequences. Which is exactly why it matters that the system works for the team, not the other way around.

Life before .legal: a shared drive and good intentions

Before .legal, Plum Safety's contracts lived on SharePoint. Stored locally, followed up manually, with no real overview of the full contract lifecycle.

Everything from negotiation and approval to implementation, maintenance, and review required manual follow-up. No clear thread running through it. No automatic reminder when a contract was about to expire. No consolidated overview of which obligations belonged to which agreements. Just a shared drive, a few spreadsheets, and a lot of coordination across inboxes.

It's a way of working that many companies know all too well. And it works, until it doesn't. For Plum Safety, it wasn't a question of whether they needed a better solution. It was a question of when.

Why .legal?

When Plum Safety started looking for a contract management tool, they knew exactly what they didn't want: a heavy, complex system with a long implementation timeline and a steep learning curve. They wanted something that would actually get used in everyday work.

They chose .legal for one primary reason: ease of use. Not an impressive feature list or a flashy demo, but a system that's intuitive, easy to understand, and flexible to work in. That might sound like a small thing. It isn't. A system nobody uses isn't a system. It's an investment gathering dust.

How Plum Safety uses .legal today

The contract module is the backbone of the entire workflow. When Plum Safety receives a contract for review, it goes straight into .legal, and a task is created for the lawyer with a reference to the contract draft. From there, the contract is negotiated within the system, with all relevant versions and comments kept in one place. Once the contract is finalised and signed, the final version is saved in .legal, and tasks are created for the right stakeholders in line with the contract's wording.

That's CLM working as it should. From receipt to signature to follow-up, with nothing falling through the cracks.

The Penneo integration is used for digital signing and is currently being rolled out across the organisation. No friction so far and no requests for improvement. It just works.

And then there are the AI features. They're clearly the favourite for Ulrik Dueholm Beckmann, QC, CM and ESG Lead at Plum Safety:

"It's really great that the system analyses and data-scrapes the contracts itself. I save a lot of time on manual entry."

That's not a small saving. With around 250 contracts in the system and roughly 100 updated each year, the AI scanner saves 15–30 minutes per contract at creation. That adds up quickly to a significant number of hours annually that the team can spend on work that actually requires human judgement.

The implementation: half an afternoon

The implementation of the contract module took half an afternoon. At most.

For a company in a regulated industry with complex contract flows, that's a remarkable figure. It says something about how thoughtfully the platform has been built, and that ease of use isn't just a sales argument but something you actually feel when you're a new user.

Many companies hesitate to switch systems precisely because they're worried about a long and difficult transition. Plum Safety's experience points in a different direction.

Flexibility as a competitive advantage

Plum Safety is in the middle of the rollout. Right now, 7–9 people are using the contract module, and that number is expected to double once the implementation is fully complete across the organisation.

The biggest difference in day-to-day work is traceability. Contract management is far more process-efficient, and the team now has a real overview of what's happening, when, and with whom. Not because they've made things more complicated. Because the system provides the structure that was always missing.

Plum Safety is also in the process of rolling out a CRM system, and .legal has actively engaged in developing an API integration with the company's IT department. That's exactly the kind of openness that makes a practical difference, and something Ulrik Dueholm Beckmann highlights as one of the positive surprises about the collaboration:

"From .legal, we experience an incredibly high degree of flexibility and willingness to adapt features to our local needs."

Not all software vendors offer that. Finding that a vendor actually takes your needs seriously and translates them into concrete solutions is part of what turns a collaboration into something more than a licence agreement.

Support when it counts

In a busy working day, it's not just the features that determine whether a system is the right one. It's also what happens when something doesn't work as expected.

For Plum Safety, that fortunately doesn't happen very often. But when it does, the response is quick:

"It's rare that something doesn't work the way I'd expect. But when it does, support is very quick to respond."

A simple description, but it says a lot. Good support isn't about having all the answers immediately. It's about taking the request seriously and responding quickly so the working day can continue.

The advice for others

For companies considering making the same move, Ulrik Dueholm Beckmann has direct advice:

"Get started before your competitors do."

In an industry where contract management, compliance, and documentation are part of everyday work, it's not about finding the perfect solution. It's about getting started with the right one.