In terms of improvements for Conga Composer, we did start seeing a lot of requests related to customization, which were initially difficult. As people got to know that it's very easy to customize it, we started to get those more and more, and we saw fewer errors. Earlier, there were many requests to manually adjust the contract value, which was not possible with the CPQ quote documents. With Conga Composer, we can customize it to some level. For exception cases, we can modify the template and generate the contract in a way they want it. While we did not record any metrics, looking at the overall tickets and the reduction in errors we used to see, I think it has improved efficiency by a lot, and our stakeholders agree. However, I would say that despite being easy to set up these templates, there are limitations around looping. Some functionalities break when dealing with large templates, around 30 to 40 pages long. We jumped on their support, but we could not come to a resolution, so we ended up reducing the overall complexity of our template. I think Conga Composer could improve its adoption for Conga Composer Sign. Right now, the adoption is not very great. People use Conga Composer mainly for document generation and then go separately for DocuSign. To get a better hold of the market, Conga should definitely invest more into Conga Composer Sign.
