DocuSign supports transactions with document sharing and electronic signature, as well as automated and guided data collection and entry, record updating across disparate systems and payment collection upon agreement, as well as analytics and reporting.
$15
per month
Salesforce Revenue Cloud
Score 8.3 out of 10
Mid-Size Companies (51-1,000 employees)
Salesforce Revenue Cloud (formerly Salesforce CPQ or SteelBrick) is built and delivered on the Salesforce Platform and Salesforce1 Mobile App which enables users to create accurate sales quotes quickly and submit error-free orders on the fly from any device.
Vice-President, Business Applications, IT & Facility Operations
Chose DocuSign
Looked at PandaDoc about 18 months ago because of the interesting functionality around tracking redlines in contracts. This is something we are interested in, but PandaDoc was not PCI compliant (we capture billing info on our DocuSign forms). At that time they were pursuing it, …
CPQ is a more inline, integrated and user-friendly product compared to Apttus's offering. The fact that it was bought and embedded by Salesforce into the platform and the support that entails, was the big differentiator for us.
It was not my choice to move to Salesforce CPQ. Our organization chose to move to this platform because Octiv gave the reps too much flexibility. They wanted to tighten the reins. Everyone hates Salesforce CPQ and the guy who implemented it isn't even at the company anymore.
We looked into using BigMachines and FPX but decided to implement Apttus many years ago. The Apttus implementation never went live after several hiccups along the way and we shifted our focus to Salesforce CPQ which has had it's moments as well. Overall, Salesforce CPQ is the …
CPQ is much more intuitive and user-friendly than JDE. JDE is clunky and was not native to the Oracle CRM tool, which created problems when it came to quote creation and consistency in how deals are moved through the pipeline. We chose CPQ because we were already using SFDC as …
We evaluated Aptus against SteelBrick. SteelBrick had an edge because of low Implementation cost, fewer custom components, clean user interface, and good client references
I am going to speak of a personal experience- on multiple occasions: I need my husband to sign documents during the day and I don't need him here- physically. He sometimes works in different parts of the state as well at his own company. There is no problem at all, as long as he has access to his cell phone, email, and cell phone service- he can sign the documents I need him to. It is AMAZING- I can't speak highly enough of Docusign.
What I like best is the ease of use to be able to track all opportunities and quotes in my daily sales tracker I also like the fact that you can reorganize the view for your opportunities. For instance, it is very similar to a spreadsheet where you can filter them by date, dollar amount, name, and several other ways. I found this to be less appropriate when we have to do multiple roles while assigning one task to multiple users. Column resizing within the Quote Line Editor is not supported in the Salesforce mobile app.
Salesforce CPQ easily maps to standard and custom fields within the opportunity in SFDC, allowing you to avoid time spent duplicating effort or copying and pasting deal criteria.
Salesforce CPQ connects directly to pre-determined price book, making it very easy to provide a proposal based on standard cost and/or add discounts to standard cost and reflect those reductions on the order form as appropriate.
Salesforce CPQ provides the ability for administrators to configure workflows for approval based on certain discount %'s on the standard cost, offering a quick and easy way to route automatically through the organization for approval.
Tracking, particularly when collecting signatures through connected applications, such as an ATS, is not always clean or easily traceable.
Formatting documents to handle electronic signature types (signatures, initials, etc.) is not always easy, and highly dependent on the partner's technology.
It is not convenient to have to use DocuSign as a stand alone product if the signatures are required for 3rd party applications. It definitely excels on its own, but the scope of that usage, at least for us, is slim.
Our Salesforce is very messy, which tells me it's not super easy to clean up.
I always have a really hard time removing a contacts from an account - it seems like you can't simply remove the relationship so we have lots of people named DO NOT CONTACT or things of that nature.
Sometimes when saving it doesn't seem like things actually save.
I can't imagine doing business without DocuSign now. I would never want to go back to the way we used to do things. The "new way" is "the way" is "the right way." We can honestly be proud of a "one right way" process and not have to suffer through "5 ways for 5 days."
Generally user-friendly once you have command of the basics, but also has a lot of nuances that can make it difficult to train others on. DocuSign University is a helpful tool, but understandably a lot of content to get through to become a well-versed user. A lot of different functionalities but only a few I use on a weekly basis.
I'd give them a 10, but there has been 1 or 2 small cases that seemed to fall to the wayside, but I was able to call them up and get them resolved. We were having a bad implementation night (after midnight) and we needed assistance from Docusign. They were able to get an engineer to help us in the early morning hours
There have been some issues with multi-year pricing of certain products and services which we have been assured will be resolved but I guess are still underway, the support team apart from this has not been needed much and in the rare scenarios, it has been needed the resolutions of conflicts has been prompt and quick, so the overall support would have my high regards for being so helpful and customer-oriented so as to assure good performance of their toolset and customer satisfaction.
Docusign is super easy to use, and apart from a few administration details, there was really nothing to train on. Post implementation, there were issues with configuration of auto-filled documents with the integrating 3rd party. That training required some time, because the DocuSign expert took the time to walk me through the 3rd party's configuration (how often does that happen?) so I could see how DocuSign should be best used to overcome weaknesses in the 3rd party platform. 10/10 expert care.
Until you get the hang of it, I recommend doing several internal tests before sending a document to a client. As I mentioned earlier, you have to go through a bit of trial and error at first to verify that the workflow works as expected.
I would say that DocuSign's biggest competitor and a most similar product is Adobe Sign. They both offer almost identical features with Adobe offering a slightly better interface. Adobe Sign is also less costly than DocuSign while offering templates that can be useful for various activities. If you are looking for more branding options then Adobe offers a slight advantage but for corporate control, I would say DocuSign offers more security.
There is no comparison to a fully functional instance of CPQ. Nothing comes close due to the amount of customization and ease of use that CPQ offers once it's fully built out. Other solutions may be easier to build or administer, but for the users and business needs, CPQ is the best solution possible.
Salesforce CPQ has helped a lot with overall visibility to the quote to order process. Reps have more insight into the business and the business has more insight into Sales Rep interactions. This makes troubleshooting issues much easier.
Our reporting capabilities have improved immensely. The ability to easily create fields allows you to capture new data points very easily.
Communication in Salesforce CPQ and Salesforce, in general, is a big improvement for our business. The ability to have a chatter feed on any object is very helpful. This can also be used for feed tracking to give some basic change management controls/history.