nuvenio ensures deep, smooth, secure collaboration with Documill Leap

Nuvenio Leap success story cover image

nuvenio ensures smooth contract negotiation between enterprises by deploying Documill Leap.

Documill Leap benefits for nuvenio’s customers 

  • Simplifying contract collaboration with customers 
  • Minimizing errors and confusion 
  • Ensuring security for sensitive data 
  • Establishing smooth Salesforce workflow 
  • Easy user adoption, thanks to ‘everything in Salesforce’ approach. 

Documill Leap benefits for nuvenio 

  • Seamless integration with Salesforce and Documill Dynamo 
  • Easy collaboration workflow design 
  • Smooth rollout across different countries and languages 
  • Quick proof of concept (POC) production for customer 
  • Superb customer support and partner program. 

Last week, we spoke about building team spirit with customers and the importance of end-to-end Salesforce integration with nuvenio, a German Salesforce-focused IT consultancy. We also talked about how to implement some unorthodox Documill Dynamo use cases.

nuvenio has also an exciting Documill Leap project underway, being built on top of Dynamo and Salesforce. We asked nuvenio’s founder and Salesforce architect Maximilian Wingbermuehle, why Documill Leap? And how does it help expand the team spirit to nuvenio’s customer’s customers? 

Contract collaboration with Documill Leap: redlining, legal support, security

Max, there is now a new project starting, where Documill Leap is integrated alongside Documill Dynamo in Salesforce for deep collaboration… 

Yes, it is an exciting implementation for a big international health and life sciences manufacturer. The customer wanted to roll out a controlled collaborative process for negotiating service contracts with its customers.  

First, we mapped out together, what the complete process would look like. We then checked, which parts of the process can be supported by the customer’s existing technical solutions. One blank spot was collaboration on documents with the internal and external people: redlining, commenting and such. 

Documill Leap looked like the perfect building block for the purpose. It took the process away from the unreliable email back-and-forth. Instead, we got a controlled process with proper workflow automation, audit trail and collaboration tools. 

These service contracts are quite detailed and complex documents. This is actually one of their most important projects right now and technology plays a big role in it

What’s the process like?

We will first generate the base document for each service contract, populated with Salesforce data. Dynamo is the perfect fit here. 

Then, between generating and signing the document, there is usually a lot of legal discussion going on and the document is constantly sent back and forth. A lot of commenting and redlining takes place and Leap simplifies all that. 

Leap moves the whole negotiation to Salesforce. There are actionable task notifications for the contributors when it’s their time to act. There is solid version control and everything that is needed to keep the process in check and on track.

What made you take a look at Documil Leap and suggest it to the customer? 

We could have continued using the email ping pong like before. But that’s not really secure. It’s not reliable. Maybe a document version goes missing or someone involved is responding to an old e-mail thread. 

And of course, from the security perspective, a lot of sensitive data is going back and forth in a non-encrypted e-mail. 

So not the best way to do it. We had to find a more secure solution that would be very closely aligned with Salesforce because it is the master database for the service contract data and the overall sales processes.  

And yeah, having been in touch with Mark [McGinn, of Documill] a lot back then, and also having scanned the Documill website, we found that Leap looked like exactly what we need. 

It manages the redlining process between the internal and external parties. For the external collaborators, the customers that is, it makes things easy. They don’t need to have like a fancy login and whatsoever. They can easily access the document, add the redlines and approve and sign it. 

So Documill Leap is nicely in line with my quest for the team spirit I told you about. It enables extending the team spirit from my customer to their customer.

Quick POC through smooth implementation 

What is your experience of deploying Leap? 

Implementing Leap is also pretty simple if you know the Salesforce platform. That was a big benefit since many other solutions that we could have considered would have taken time and effort to get up and running. 

With Leap, we could easily show the customer: “ok, this is how the solution could look in like a week or two in your Salesforce environment with your data.” So why even look for another solution? 

And when do you expect this solution to go live?  

We expect that within two months from the project kickoff, somewhere during the next month [October], an early pilot version will go live in one test country. We already chose one particular country, since the people there are pretty open to changes and stuff, so it suits us well. 

However, there will still be a fallback process in place, like the old pen and paper process today.  

We’ll gather our learnings from the pilot and have next year the actual release. Then, it’ll grow. There’ll be a bigger audience, more countries, more templates and so on. 

Multi-country, multi-language, multi-template… 

It sounds like you will have a multilingual solution in the future. 

Yes, exactly, it will be multi-country, multi-language, multi-template. Everything you can potentially multiply will be somehow multiplied.

And will your approach be that you will have a separate template for each language? Or how will you do that? 

So far, for the translation part, we haven’t planned too much. Now it looks more like we will have different templates for different countries and contract types. They will hopefully become fewer over time because harmonizing them would be wise. 

But especially with countries like Canada or Switzerland, the idea is that we will switch between languages and say, “ok, this template will be generated first in, let’s say, Canada in English”. The customer might then say, I need it in French as well. 

And then, why not take the same template to, say Switzerland, with the same pieces of information? So that will definitely be a use case that we will need to cover. 

Are you also using the Dynamo clause library to cope with the different differences in legislation between countries? 

Most likely this will be the case. So especially for these multilingual templates, that will be used in different countries.  

Some templates will be so country-specific that there will not be many common building blocks. But the goal is to have the possibility, using clauses or whatever, to have these drag-and-drop building blocks to build individual contracts from a company library. 

So that’s the way it goes: you first multiply anything you potentially can, to meet the business needs. Then you look for common denominators and consolidate, for efficiencies. 

Ok, this was a pleasure. Thank you for your time and these unique learnings, Max! 


Related Articles