Streamlined, cross-functional workflows enable legal and sales teams to work together. Seamlessly.
An inevitable by-product of legal teams is the amassing of hundreds of pages of crucial documents. With the rise of technology, these are no longer stacked around offices or stuffed in filing cabinets; they rest in Wiki and Salesforce pages, but the challenge of efficiency remains the same.
A recent survey of 113 in-house legal teams revealed that only 4% of respondents find technology that properly meets their needs. With the COVID-19 global pandemic and the inescapable reality of remote work, even more legal teams believe well-designed processes and technologies are required to do their work efficiently. In fact, more than 80% of respondents believe that automation, big data, and AI are the future of their work.
In-house legal teams working at tech companies that have adopted agile practices find the need to break free of old practices even more critical. Plus, for teams working remotely or in technology silos, it means relying on channels like email and Slack conversations for internal communication, collaboration, and planning, which often results in a lack of clear communication, loss of context, late planning, and more.
Many legal teams have turned to Salesforce to create documents and keep them protected. This makes sense because Salesforce is already the go-to technology for other customer facing teams, hosts all customer-related information, and serves as the source of truth within the organization. The challenge is that much of the process of delivering services to clients still relies on collaboration with pre-sales -- who work in Jira, not Salesforce. So, how do teams using two different platforms address the challenge of effective collaboration to plan and deliver products and services in an agile way?
Using Connector for Salesforce & Jira, you can create a consolidated, streamlined approach to communication, planning and execution that minimizes unproductive context switching. This means legal teams can continue to work in the platform they are familiar with, such as Salesforce, and have the necessary means to work and collaborate with other teams to plan and deliver solutions to customers.
In this example, Mark, General Counsel at ACME, works with multiple teams to craft and prepare proposals, SOWs, and contracts. He has been working with the pre-sale team (who use Jira to keep track of their tasks) to put together a services proposal for one of their clients.
Portia, in the Pre-sales team, creates a Jira ticket to keep track of this task and, with the help of Connector, a Legal Case is created on Salesforce and assigned to Mark. Now Mark works on the details and can easily communicate with the services team, who also use Jira to get a better understanding of the scope of the work and hours required to complete this project. With full automation between fields, comments, and even status of the tasks, Mark can finish the SOW and prepare the proposal in a matter of hours rather than weeks.
While in this example the legal team is using Salesforce and the services and pre-sales teams are using Jira, this can be easily set up the other way around. Connector for Salesforce and Jira allows you to create fully automated, bi-directional integration between the two platforms.
For more information about how to create this use case, visit our docs site. To learn more about Connector for Salesforce & Jira, check out our site or blog. If you're interested in a demo or discussing your specific use case, reach out to our customer advocate.