Conga Composer Reviews

We are using Conga Composer as a document generation and automation tool, which is allowing our teams to embed the document creation directly into the custom application, website, workflows, and using the APIs and REST APIs, instead of manually copying and pasting data from one to another.

It is also helping us to pull the information directly from the CRMs and the ERPs, from the system record via JSON payload, to create contracts, invoices, and structured reports for our customers.

Conga Composer is a very good product and it heavily excels in any kind of complex and high-volume scenarios. It is very well-versed with handling dynamic content such as charts, nested tables, global currencies, and it can execute asynchronously, putting it well ahead of a basic PDF generator. It also offers many additional features.

The user interface is my personal favorite, as the interface is largely very developer-friendly, and it is a custom front end we built. Additionally, it utilizes familiar tools like Microsoft Word and Excel. Setting it up involves a complex API deployment and JSON payloads. Initially, it requires some technical heavy lifting compared to drag-and-drop and no-code tools. If you are from a technical background, then it is not a challenge.

My personal favorite features are headless execution, which helps us to trigger the document generation in the background from the buttons, workflows, or external systems without requiring the user to navigate through an interface. This gives us all the options within a single click from the UI. The second feature I love is that it supports multi-format. Generating a Word, PDF, Excel, PowerPoint, and HTML can be done from a single source and a single, central data source. The third feature which I love is that the REST API is not locked exclusively into Salesforce. It can ingest JSON data from virtually any ERP or system of record. Additionally, the seamless add-on to the sign API has helped us to create an uninterrupted, automated contract cycle.

Conga Composer is doing pretty well, but if I have to give a suggestion, the only suggestion is that they can improve on the AI features which they may release in the future. This will help not only tech users but also non-tech users to make sure that they are able to use it effectively using the AI chatbots or AI agents within the application.

The customer support was really excellent. I interacted with them three months back. There was some update from their end, and after that update, we were facing some problems. They resolved that query within 45 to 50 minutes. I love the customer support which the team provided.

The deployment went really well. It was not that tough, as it does not require heavy architecture planning or any heavy technical requirements from the system. We implemented it within two to three weeks. From the time we had the conversation, the team purchased it and it got deployed within three weeks.

We have seen a major return on investment after we implemented Conga Composer into our workflows and the organization. We have seen manual entry and data entry eliminated, and we have saved at least 90 to 99 percent of time, as it has helped to get these things automated through it, and which has helped us to save a lot of time and resources.

Second, it has helped our teams to collaborate better, which has helped to increase the team productivity by 68 percent. As things went better, they were able to deliver more than they were expected to deliver, as they had more time and used that time in a productive way. Third, we have saved at least 40 to 45 percent in cost, as we have saved thousands of labor manual hours annually by removing the manual input. It also eliminated the errors that were occurring from copy-paste mistakes by human workers. The error frequency has dropped from at least 30 to 40 percent to essentially zero. This has improved the turnaround time by at least 67 percent and significantly accelerated the quote-to-cash cycle for our revenue teams.

Team collaboration improved because they were having clear, structured data and directly eliminated the manual data entry, which helped them to save a lot of time. That time went into other team-building exercises and greater work opportunities within the organization. This impact has been tracked globally for the organization by the quote-to-cash cycle from our revenue teams.

Pricing, setup cost, and licensing are really good, as we got the support of the AWS team. We got a discount, the pricing is good, the setup cost is good, and with the licensing, the renewals are seamless with the AWS Marketplace.

Before choosing Conga Composer, we definitely did some good market research. Apart from Conga Composer, we evaluated solutions such as PandaDoc, Nintex DocGen, and S-Docs based on usage. Conga Composer turned out to be the best for our needs.

Anyone who is looking for a game changer and headless content editing without needing any code, top-tier, top-notch, API composer, and which can actually work with your Word or Google Docs, should definitely go ahead for Conga Composer. I would rate this solution as a five out of five.

One of the main use cases for Conga Composer would be to generate quote documents. We had different types of quote documents in our business process, so we used different kinds of Conga Composer templates for those. Basically, there was one template for the initial quote to give them an idea of how the price structure is going to work. Once they finalize, we have a different template, so when the deal is finalized and everything is in place, they would be able to see how much they would be paying, including the tax. That was the main use case around it. But as I mentioned earlier, we also used it for other custom objects that we had, such as POV, and to generate and print basically the invoices as well.

We used Conga Composer mainly for generating the documents, but we did not use Conga Composer Sign functionality. Instead, we opted for the DocuSign functionality. Once the document generation process was completed by Conga Composer, we integrated DocuSign into our system. Once the document is generated, it moves to a DocuSign envelope. We are able to send the document to different contacts mentioned there. DocuSign was mainly for sending the document to get it signed, and once it comes back signed, we also had an automation in DocuSign that updates some fields at the quote level. It lets us know that the document has been signed and things around that.

I would say the process of setting up those templates for different quote stages with Conga Composer is extremely easy. You do not need a lot of development knowledge for that. Even if you are just proficient with Microsoft Word, then you can definitely go ahead and customize this according to your needs. It's very simple and very straightforward. In my 2.5 years of experience with Conga Composer, I can say that it was one of the best document generation tools that I have used in a very long time. For maintenance purposes, it's very easy to maintain the existing templates or to create new ones.

Conga Composer has positively impacted my organization, and I have noticed improvements in efficiency, accuracy, and customer satisfaction since using it. Earlier, we used to generate all these documents with the native CPQ functionality that allows you to create templates and generate documents via Visualforce. Those were difficult to maintain because you needed to check the tables and manually enter width and height. They were not very easy or friendly to configure and maintain. With the introduction of Conga Composer, we see a lot of changes on a day-to-day basis. There are a lot of requests to customize our templates, and we can meet those customization requests very easily. It offers greater flexibility in terms of formatting and the data we want to show to our customers. This is where it plays a major role, so there has been a lot of improvement, and the efficiency has also improved.

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.

I have 2.5 years of experience with Conga Composer.

I would say Conga Composer is mostly stable. In my 2.5 years of experience with it, I faced one or two instances where it was down, likely due to major AWS services being down. The downtime was significantly low, and they were able to restore services quickly, typically within an hour or two. I am happy with that responsiveness and the seriousness they take in their work.

I believe Conga Composer is very scalable. We have around 3,000 to 4,000 internal users, and it handles all that workflow and simultaneous contract generations without any issues.

We found customer support to be helpful, but there were instances where we faced issues with flags that allow you to hide or show tables. In cases where your contract is complex, using many formulas or spans 30 to 40 pages, those flags do not reliably function. When we consulted support, they advised reducing the complexity of our contracts instead of proposing a fix, leading us to ultimately cut back on the number of contract documents.

As I mentioned earlier, we used to use CPQ quote document functionality, which was native and free with the Revenue Cloud. However, it was not very easy to maintain, requiring developers to create and maintain those templates, which lacked flexibility compared to Conga Composer. Seeing those challenges and the need for more customization, we opted for Conga Composer.

The initial setup for Conga Composer was not very difficult; it was very easy. As for pricing and licensing, back then we had a very good budget. We looked for a good replacement for the CPQ standard functionality we had to generate documents. We found a very good replacement in Conga Composer and were glad to pay the price they showed back then. It was not very much, but now with a lot of new tools and freeware available, the cost factor becomes a reason to consider whether we should renew our subscription.

Earlier we had a team of CPQ developers maintaining those documents in CPQ, but with the introduction of Conga Composer, certain stakeholders now have knowledge of how Conga Composer works and can go ahead and create and customize templates. Most of the time, they know the requirements themselves and can work on that without needing external help.

Before choosing Conga Composer, we evaluated DocuSign. However, there were internal questions about whether the initial setup and long-term maintainability would be as easy as with Conga Composer, leading us to decide to go with Conga Composer instead.

I don't think we did anything unique with Conga Composer, but we did use a lot of templates on a single object. As I mentioned, on the quote object itself, we had a couple of templates, including an initial contract template and a finalized contract template. We used it for different templates, and we also built different Conga Composer queries to pull in the data for the merge field that actually gets printed in the document.

I don't think the automation part of Conga Composer is really that good, but the template creation part is extremely easy. It allows me flexibility to send the documents. We have that flexibility for DocuSign, so there's Conga Composer Sign that you can utilize, and it very closely integrates with Conga Composer. Once your document is generated, you can send it via Conga Composer Sign to any customer. The integration part is, of course, very easy and native with Salesforce. Within Salesforce itself, you have the managed package application from where you configure different things about Conga Composer, so it's very easy there as well.

On a scale of one to 10, I would rate Conga Composer a seven. The reason I say seven is that there are a lot of freeware tools right now that offer the same functionality for free. There are many LinkedIn posts talking about people coding their own composers in Salesforce that allow document generation similar to Word templates we have in Conga Composer. That same functionality is being offered for free, although it's not as scalable or foolproof as Conga Composer. There are many new developments in the market, so they should work on the cost aspect.

I have provided enough improvements and given a lot of suggestions, which you can find in my previous answers. There is a lot of scope for improvements there. My overall rating for Conga Composer is seven out of ten.

One of our clients is looking to build case summaries or quote summaries where we list all the products they have purchased. They have a complex quote summary requirement. We use Conga Composer to build the entire quote summary, displaying all quote details, products purchased, and related information. The implementation varies according to countries, so we apply many conditions on the same templates. We use Conga Composer for document generation purposes.

We remain consistent with Conga Composer because it satisfies many business use cases. We have used it several times across multiple projects to build similar document solutions.

The best features in Conga Composer are how we navigate the merge fields and merge objects. We can retrieve data and display it on the templates, which is a strong aspect of Conga Composer and why we chose it to build documents.

Dynamic data is a feature of Conga Composer that allows us to bring data from different objects and display it on the templates. This capability is particularly valuable.

The main benefits I have seen from using Conga Composer are that while Salesforce provides features to build documents or cases that function as quote summaries, they have limitations. We cannot modify much or build complex templates using the standard features. After choosing Conga, we discovered that it already has many features that enable us to easily build complex templates. It works perfectly with our business use cases, which is why we selected it.

Conga Composer is somewhat slow. If the performance and speed could be improved, that would be helpful.

Apart from speed, Conga Composer is already enhancing on a daily basis. It is already in a good zone for improvement.

I have used Conga Composer for around two years.

Regarding stability, I find Conga Composer stable and have not experienced any crashes or downtimes with it.

Regarding scalability, I find Conga Composer scalable. That is why we use it across many companies, and many of our clients continue to use it.

I have not encountered many challenges with Conga Composer, so I have not had the opportunity to contact the technical support team.

The setup process for Conga Composer is straightforward.

I have experience with Conga Composer and have built document generation solutions for one of my clients using it.

I have not integrated Conga Composer with other Conga products such as Collaborate or Conga Contracts.

I have not utilized the automation aspect of Conga Composer.

I decided to choose Conga Composer because using the standard option, we can only build basic and simple quote templates. Our use case required a complex business template where sections display based on specific conditions and visibility rules. We needed to show data based on user input and selections, displaying information accordingly by bringing data from different objects under different conditions. Conga Composer allowed us to make queries and display data with the necessary filtration, which is why we selected it.

We have also used OmniStudio for document generation, which is a good option.

I would suggest to other organizations considering Conga Composer that if they are looking for a tool to build complex quote templates, they can definitely go with Conga Composer. It is a good option that is easy to manage and use. My overall rating for this product is 9 out of 10.

I use Conga Composer to generate email and invoices. Then we download it and send it to customers. That is the main part.

Right now the main benefits I have seen from using Conga Composer is that it is easy to customize. However, we wish we could have some AI features in Conga. That would help us to create Conga templates or anything a little faster. It would help a lot.

Currently, we just use it for sending invoices.

What I appreciate about Conga Composer is that it lets you customize it. You can customize and add colors. There are a lot of features. I can download to my OneDrive, Google Drive, or anywhere I can save it. If I want to change any fields on my Conga template, I can go and change it in the query. It helps me quickly update it. That is an easy part of using Conga Composer.

We utilize Conga Composer's dynamic data feature.

Conga Composer helps to create documents faster and saves time.

I think Conga Composer is good for ensuring brand consistency in our documents. There have been no issues until now. We are using it easily.

Apart from the AI functionality, there is one thing I would like to see improved in Conga. When you write a Conga query, it is too old and looks too classic with its UI. That can be improved.

I have worked with the automation capabilities in Conga Composer. We use flows and Conga parameters. It helps you to automate everything. There are no issues with that. However, it should be more user-friendly.

I would assess the automation benefits that Conga Composer provides in reducing manual document tasks as good right now. However, it is not user-friendly. The UI is a little confusing. We should have more Conga videos on YouTube or elsewhere that help us to learn and use it on our PC or system and the Salesforce system.

Regarding my experience with the setup process, initially it was difficult. I had to go through YouTube or documents from Conga and then do it by myself. It is a little difficult. If we had a step-by-step guide on how to use Conga Composer and how to create templates, that would be easier. Whatever videos are available on YouTube for Conga are too old, from five, six, or four years ago. Those should be updated. If they were updated, it would be useful for customers or a Salesforce admin.

I have been using Conga Composer for almost four years.

Overall, I have not had any crashes, stability issues, or performance issues with it. It is going on well.

I do not have any scalability issues right now.

We often escalate questions to technical support and we get a solution quickly. There are no issues from there.

I would rate the technical support on a scale of one to ten as eight or nine.

Prior to adopting Conga Composer, I did not use any different product for document management.

Regarding my experience with the setup process, initially it was difficult. I had to go through YouTube or documents from Conga and then do it by myself. It is a little difficult. If we had a step-by-step guide on how to use Conga Composer and how to create templates, that would be easier. Whatever videos are available on YouTube for Conga are too old, from five, six, or four years ago. Those should be updated. If they were updated, it would be useful for customers or a Salesforce admin.

My setup was done in-house. I did that by myself.

We just set up Conga Composer. It was already downloaded and installed on our PC. We just had to set it up and assign permissions, then create the solution.

My setup was done in-house. I did that by myself.

Since we bought Certinia, we got Conga Composer for free. Right now, we do not have issues with that.

Since we bought Certinia, we got Conga Composer for free.

Prior to adopting Conga Composer, I did not use any different product for document management.

I have Conga Composer experience. Basically, we are a consulting firm, so we work on client's organizations. I have experience with that.

I would rate the technical support on a scale of one to ten as eight or nine.

Given my experience with Conga Composer, I would say go with YouTube first and learn the basics. Then use Conga Composer documentation website to understand more in depth. After that, anyone can set it up. There are no issues.

I purchased Conga Composer directly from Certinia.

I would assess the automation benefits that Conga Composer provides in reducing manual document tasks as good right now. However, it is not user-friendly. The UI is a little confusing. We should have more Conga videos on YouTube or elsewhere that help us to learn and use it on our PC or system and the Salesforce system.

I would rate this review an eight overall.

I don't use Conga Composer anymore daily; we have our setup, and it's working fine, so I don't have to touch it. We have something external for contract management. I think we use DiliTrust for the contract management, but mostly our French colleague uses that. In the past, my clients would generate documents using a template through a button or automation, and they could send them afterward using Conga or DocuSign because we can plug them together.

Today, we're basically doing the same thing. We use a Conga Composer template, and through a button, because some of my colleagues prefer verifying the data and changing a few things before sending the document, while others don't care. We have a button or we have automated the generation and sending of the document using mostly DocuSign. We want our partners to sign the document we are sending them. So we use Conga Composer to generate the document and we use DocuSign combined with Conga Composer to send it and to capture the signature back. That's the use case we have today.

As an implementer, what stands out for me is that I've been on it for more than ten years now, so I kind of saw some change in the UI, and it's very nice. It's user-friendly, I will say that in IT, it's user-friendly. The documentation is pretty good actually, so you can find easily what you are looking for. I also like the fact there is Conga University where you can do things and get certified, which reminds me that maybe I should go update my certification.

In terms as an implementer, it's user-friendly, documentation is good, and help is also good. I have good contact with Conga people throughout the years, and it's good. It helps a lot because when you use a template, you don't have to do manual work. You have merge fields, and when you use a template, you can use merge fields, and that's great because that's why you're using a template. If you use a button for the user, again, it helps. If you use automation too, you have a trigger point that helps you send everything, generate the document, and do other things.

Conga Composer is not especially something new; back then, Conga Composer was very something new for me, and I really liked the Conga Composer product. Today, I don't know if they are still ahead compared to some competitors, but at some point I feel like automation is basically made to make the work faster and easier for everyone, and that is not specific to Conga Composer.

I know that back then we wanted to use Conga Composer for other things than just generating the document, but Conga Composer was getting too expensive, so we didn't. I cannot say if there are improvements because I don't know anything about that and I didn't use that feature yet.

What I can say is back then and today, what we do in our template is we integrate some images and some logos; so the brand consistency is made outside and then we use it in the template. Maybe now there is a feature where you can set the color directly or other things, but I'm curious how they do that. I haven't seen that feature yet.

Back then we couldn't use Conga Composer offline, but I think they did some improvements on that side. I didn't work on that lately, and it's been a while since I did a new implementation on that, so I didn't hear anything negative lately.

My personal experience with the product is that I think since the beginning I started working on Salesforce in two thousand fourteen.

Conga Composer is pretty stable; I would rate it an eight.

For scalability, I would rate it an eight.

When it comes to technical support from Conga, I would rate it an eight.

I work for a company and in the company, we use Conga Composer and I'm implementing Conga Composer for my colleagues to use.

It is pretty easy to install; you just need to make sure that you choose the right option, so I would rate it an eight.

Here at Basic-Fit, I think they already had it when I was hired; I started working in two thousand twenty-one, so it's a few years, even more now.

I haven't evaluated the setup cost because back then as a consultant in a consultancy company, when we tried to check on the prices of the product, it was too expensive for our customers, so we didn't.

Honestly, when I was a consultant, Conga Composer was okay, but then when you went a bit outside and wanted to take Conga Sign, which was called Conga Sign back then, but maybe they changed the name now, all those things were getting very expensive. I think even Conga Composer went high at some point. Right now, I don't know what the cost of a Conga Composer license is. I haven't checked lately. I would say I don't know. I think Conga Composer was affordable to some point, and then everything was getting more expensive, but I can't say how much it is now.

As I said, I haven't checked lately what is in Conga Composer. I think I haven't checked since last year probably, so maybe there's something that I don't know, and I need to check.

DiliTrust is spelled D I L I T R U S T.

It's not that we stopped dealing with Conga Composer extensively; we are still using it. We just don't have a new implementation because we have an implementation that is working fine. The users are using it almost daily. I didn't have a new implementation since the last time I made the review. That's what I meant.

I would rate my overall experience with Conga Composer as an eight.

We use Conga Composer for document generation. For instance, our clients need reports showcasing opportunities they've secured recently, categorized by employee ownership. 

Additionally, in the healthcare sector, we generate reports detailing the number of patients treated and their conditions.

So, most use cases are around document generation, as I work in the health sector. 

The best aspects of Conga Composer are its ease of use, efficiency, time-saving capabilities, customization, flexibility, seamless integration with Salesforce, and the excellent support and resources provided by Conga. These are essential factors that every user should be aware of before adopting this solution.

The biggest area where Conga needs improvement is its documentation. The documentation is good but not up to par with other platforms like Salesforce, which has extensive documentation and a helpful community. 

In Conga, there aren't many people with in-depth knowledge, and while the documentation can provide some guidance, it's not comprehensive enough. It is not up to the mark. Conga should focus on improving its documentation.

I have been working with Conga Composer for the past two and a half years. Prior to that, I worked on the Salesforce platform, handling development and admin tasks. Currently, I work on Conga within the Azure environment.

There are occasional bugs that cause the system to crash, but these are manageable and usually resolved within a day or two. 

While working on a PowerPoint template, I encountered issues with pie chart applications that took some time to resolve. Overall, the stability is good, and any issues are resolvable.

Currently, there are three other people on my team who use Conga Composer.

Conga Composer offers extensive customization and flexibility, that allows us to create documents that perfectly align with our branding and specific business requirements. 

We have successfully used Conga to generate complex reports, dynamic data, and visually appealing invoices. The level of customization available is very impressive, which is why we prefer Conga over other document-generation tools.

The deployment and setup process for Conga is very easy. It doesn't require a lot of time or effort, and it's not something to stress over. 

This ease of use is one of Conga's biggest advantages compared to other platforms like DocuSign or Nintex. The flexibility that Conga offers is the best in the market at the moment.

It's not cheap, but it's not overly expensive either. It's manageable. If you're looking for a developer in India, it would cost you very little.

Not many people are familiar with Conga Composer. There aren't many developers in the community. So, starting without any knowledge would be difficult. Having proper guidance or training would be a great advantage. If you have someone who knows how to work with Conga Composer, it's very easy to learn.

The organization I work with allows you to directly coordinate with us, so you can receive tutoring or mentoring. You'll have someone to guide you through the process.

It is easy for a beginner to learn to use Conga Compose. A weekly crash course session would be enough to get you started. The rest you can manage through development.

Overall rating:

I would rate Conga Composer around seven out of ten because there are challenges with every tool. The learning curve is associated with fully understanding the capabilities of the tool, and time and practice are required. For complex document generation tasks, some advanced knowledge of Salesforce data structures and Conga features is necessary.

We use Conga Contracts, Conga Composer, Conga Grid, and Conga Orchestrate. We have a business all over the world, and due to currency symbols, alphabetical changes, logos, and entity names, we need to build a formula where the template remains the same but the contract terms are different for various countries. 

Another use case is loss tracking, where we track transactions and collections through Salesforce with Conga Composer and Conga Contracts. We also handle the contract signing in Adobe, which integrates with Conga, storing signed contracts in Salesforce, Check Point, and Amazon S3.

Conga Composer has made the contract signing easy and streamlined. Previously, we had a team of five people reviewing contracts, which is now reduced to two, thus optimizing resources.

Conga Composer is easy to use, especially for C-level executives, as it simplifies the contract signing process. Automation has significantly reduced manual reviews.

The debugging skills could be improved as we need to stay alert for issues. After acquiring Conga, the support is less responsive than before.

I have been using Conga Composer for almost five years.

I have not experienced any breakdown issues with Conga Composer.

The automation of the contract process is excellent, allowing us to scale easily.

The Conga Composer service response time and knowledge leave room for improvement. I rate their support six out of ten.

Neutral

Before Conga Composer, I used DocuSign and Adobe.

The initial setup was straightforward for me as a developer, yet documentation was key.

It's crucial to learn the tool and understand the contract process. If you are familiar with the contract process, using Conga Composer becomes easier.

I'd rate the solution eight out of ten.

We utilize it for contracts, account statements, and summary reports.

The solution has helped us with contract consistency. Before this, sales reps would save a template to their desktop and update it as needed. Over time, people's templates and terms and conditions were outdated. This forced our reps to start using the most current approved contracts.

Once you understand how to build the templates, it's a pretty straightforward process. It allows you to create both Word and Excel documents.

The query builder could probably use some updates. When Salesforce switched from Classic to Lightning, there were many gaps. For the most part, those have been resolved, but it still operates a bit clunkily. It works great once you have your queries built and are trying to build out the template.

I have been using Conga Composer for seven years.

The product is stable.

I rate the solution’s stability a nine out of ten.

The solution is 100% scalable. We've seen our act adopted by a global enterprise. It's remarkable to see a business of our size using the same tool as a global entity.

We currently have 65 licenses.

We've used them once for an issue, and they were able to help. Then, there was another time when we had a general question, and they couldn't assist us. However, with the help of the community, we got it answered.

We were utilizing a free version of S-Docs at the time, but it wasn't scalable.

The initial setup is easy, but we still have some issues with the coding for writing data back.

The product is priced fairly. We're actually in the process of trying to renegotiate our contracts across all the different business groups into a single enterprise-wide contract. Looking at all the existing contracts, they're mostly pretty consistent. It's definitely worth the investment.

Creating a single report summarizing multiple areas of an account has been invaluable for us. You can pull in sales information, contact data, and usage information from our subscription service into one Conga report, which an account executive can quickly review instead of hunting for all the pieces. Additionally, from a contracting standpoint, creating consistent, formal contracts that display all the necessary information in the required format is crucial.

I recommend the solution and advise you to go through the training to learn how to configure and set up templates or get someone with experience in it. It would help if you knew how to structure it and the end-to-end process.

It would speed things up for us if we had a dedicated resource to manage it, but it's doable if you're on a smaller scale. It's just going to take a little bit of relearning each time.

Overall, I rate the solution a nine out of ten.

I primarily use Conga Composer for sales proposals and quotes. Whenever I need to auto-generate proposals using opportunity data and determine whether to include pricing discounts and product details, I use Conga Composer.

The process begins when the opportunity is ready and a sales rep is working on an opportunity in Salesforce that contains the account information, products, total value (ACV), and a stage designation of proposal, price, or quote. All this data is already stored in Salesforce. The sales rep then clicks a custom button labeled generate proposal, which is configured to trigger Conga Composer and passes the opportunity ID and related data.

Conga Composer fetches data automatically, pulling account details, opportunity details, and product line items. The system then performs template merging using a pre-built template in MS Word that includes company branding, dynamic fields, static fields, and tables for product line items. Finally, the document generation process produces a PDF or Word proposal instantly, followed by auto delivery and the e-signature process.

Conga Composer offers plenty of features, including one-click document generation, template-driven automation, and dynamic data merging.

If I had to pick one feature that makes the biggest difference day to day, it would be dynamic data merging in combination with Salesforce. This feature actually drives everything else and matters the most because it eliminates manual work completely, ensures accuracy, and enables true personalization at scale. When you have fifty proposals a day, each one should be customized.

Conga Composer has impacted our organization in a quite positive manner. We have saved a significant amount of time, closed deals faster, and improved accuracy. We can now maintain all the proposals we currently have in the system using standardized templates.

Conga Composer can be improved because it has a steep learning curve, especially for new users. Setting up templates can sometimes be complex and requires a good understanding of Salesforce data structures. As an improvement, the product should have a more beginner-friendly user interface and better guided setup or wizards. Template management can get complex, making it difficult to maintain versions and updates.

There are some other improvements that can be made, such as reducing the dependency on technical knowledge and addressing integration complexity. Integrating with tools beyond the Salesforce ecosystem can require effort. The product should have plug-and-play integration methods to make it much easier.

I have been using Conga Composer for seven years.

In my experience, Conga Composer is stable as I have worked closely within the system. While the user interface could be more user-friendly, overall it has been a good experience.

Conga Composer is built for high-volume enterprise use and is designed to handle large-scale document generation. It can be used by enterprises generating proposals, invoices, and contracts.

We reached out to the support team a couple of times, and the issues were fixed quickly. It has been a great experience with the support team.

Before Conga Composer, the proposal creation time was ten to fifteen minutes per document, with manual steps including copying data from Salesforce, pasting it into Word, then formatting tables and pricing. After Conga Composer, proposal generation takes only about ten to twenty seconds. The overall time saved for a proposal is ten to forty minutes.

In our organization, Conga Composer is deployed as a public cloud because it runs on top of Salesforce, which itself is a cloud-based platform. Conga Composer is installed as a managed package inside Salesforce.

It is clear that we have seen a return on investment from using Conga Composer. It has reduced document generation time from around ten to fifteen minutes to under twenty seconds, translating to about three to four hours saved per sales rep per day. At a team level, that is equivalent to the workload of one to two full-time employees. Using Conga Composer helps us send proposals much faster—within minutes instead of hours—thus improving our sales cycle by roughly twenty to thirty percent. Overall, it allows us to scale operations without increasing headcount.

Pricing is based on a subscription model, which I consider moderate to slightly premium compared to basic tools. Overall, it is not the cheapest but is good value for automation at scale.

Before choosing Conga Composer, we evaluated a few other document generation and e-signature solutions, including DocuSign, which was strong in e-signatures but lacks the document generation capabilities or flexibility that Conga Composer offers for our use case. We also evaluated PandaDoc.

The best advice I could give to those looking to use Conga Composer is that it is effective, saves time, and is efficient. I recommend starting simple and then scaling gradually. It is not required to automate everything at once. You can begin with one use case and one clean template, then gradually expand to contracts and invoices while investing time in template design and understanding the Salesforce data model.

Overall, Conga Composer is a good tool to use and enhances the Salesforce ecosystem. I gave this product a rating of eight out of ten.

I work for a Salesforce consulting composer, and I'm mostly a developer, sometimes an admin. Sometimes the clients require us to set up things in Conga, either Conga Composer, Conga Sign, or any other similar application. So most of the times, the request is just to update existing templates or create new templates for them to use on Conga.

There's nothing in particular. It's just what the client decides to use. I just use it. It's quite simple. Most of the clients do have it. It's better than having to go in and do it manually, creating a Visualforce page to use as a template, which is another thing that we do here. If the client only has one template to use, then we recommend that they go that route. However, if they do have many templates or they need to be changing them constantly, and it's more expensive for them to hire us to change them every time, then we usually recommend that they use something like Conga.

The documentation could be improved. The one time that I learned a bit more on how to use it was when I got into Conga University to get my certification. There are a lot of small steps that you don't see in the standard documentation or you cannot find it. A couple of years ago, they changed stuff from what I learned five years ago when I started, which is great. However, they need to update documentation to match that. Sometimes, you find the documentation for the old version, and you try to do it, and it just doesn't work. 

I've used the solution for five years.

Most of the time, I haven't had an issue like that, not human-related. If I made a mistake of adding something that shouldn't be there, or sometimes you start with a template that somebody else made, and then you paste it and think, 'Okay. That's just going to work,' but it doesn't because it has a little bit of something that it doesn't like. 

It's always better to start from scratch. Otherwise, I've never had a significant issue. Maybe once I got a weird error, and then I noticed that there was a crash on the servers from Conga, and that's probably the reason it failed.

I'm not sure if the solution is sclable. I don't see any issues in adding more templates as the company is growing. However, I've never done anything big with it. Everything is just like, 'Okay. We have these five templates, ten templates at most.'

I've reached out to support many times based on the documentation. I'm trying to follow it, and it doesn't match what I'm seeing, so I end up having to contact Conga directly for them to let me know that the issue was that I do not have the license that they need for that.

Neutral

I would recommend this product to other people. If they need to have a lot of templates and need to make changes often, like every three months or less, then I would say they should go the route of using either Conga Composer or any other similar application.

I'd rate the solution eight out of ten.