Item: Adobe Acrobat Sign
Rating: 9
Author: Ryan Claeys

Use Cases and Deployment Scope

I am a contractor who did an implementation of it for another organization. This organization is using it across the entire organization, we were implementing it as part of their sales solution, embedded into existing custom software. The custom software sends documents to customers for signature and processes them within the system when the customer signs. This enables obtaining signatures from customers when they are not in the office, and allows quicker and easier processing of signatures.

Pros and Cons

Emails customers
Allows legally binding signatures
Webhooks back to the original application
End user friendly

Requesting signatures via text messaging requires use of a third-party SMS solution.
Email not being able to be the same for production accounts, and developer accounts prevented us from being able to use development accounts. It is against company policy to use external emails for work functions.
Customization of email templates(Html templates), requires assistance from adobe, and limits functionality.

Return on Investment

Not, applicable. outside my area of expertise. I have not officially heard the cost savings compared to other vendors.

Support Rating

Support to my questions was always fast, and they did their best to work with me to solve a variety of issues we were having. Any case where they were not able to solve the issue was always due to a limitation of their product, not an issue with support or those providing support. And in cases where the product had a limitation, they worked with us to

Usability

The programmatic interface with the product was easy to set up, and quick to develop. The effects of the settings on the account on how it will affect the rest API, is sometimes unclear. (A byproduct of having so many customizations available). Some places the API documentation was a little unclear, however since their web interface uses the API's themselves, it is relatively easy for developers to watch what it is doing, and duplicated the behavior when having issues.

Industry Usefulness

When delivering products to customers, we require a signature. Often the customer isn't available on location when the product is dropped off, so we needed a remote signature method. Using Adobe Sign allows us to receive the signature, and keep the whole process automated. The signed documents are able to be processed within the application after being notified of the signature. The documents can be displayed within the application, and the business process can be completed undisturbed

Key Insights

Do you think Adobe Acrobat Sign delivers good value for the price?

Not sure

Are you happy with Adobe Acrobat Sign's feature set?

Yes

Did Adobe Acrobat Sign live up to sales and marketing promises?

Yes

Did implementation of Adobe Acrobat Sign go as expected?

Yes

Would you buy Adobe Acrobat Sign again?

Yes

Alternatives Considered

DocuSign

DocuSign is a slightly more robust product than AdobeSIgn, ahead of them in available features. (to name a few)

Linking emails to both production and development accounts.
Email customization
SMS signature solution

AdobeSign is stable, and provides enough features to meet the business needs. Having implemented solutions in both, I would still always have the business consider AdobeSign.

Likelihood to Recommend

It does a very good job of sending emails, and getting legally binding signatures. Supports multiple languages. If you wish to also send via text message, this can be accomplished if you have a third-party SMS gateway, but one might want to consider other solutions.

If you strongly wish to have a tagged, customized email sending the documents to sign, rather than a generic one, other solutions provide better options for this.

Overall, this is a good product, that was easy to integrate into our solution.

Embedded Adobe Sign into existing application for remote signatures

Overall Satisfaction with Adobe Sign