Wow! This might have deeper implications than you imagine.<p>Have you guys thought about the outcomes for ballot initiatives, or for enterprise sales?<p>In particular, this kind of tech might have a disruptive impact on the initiative process in California (which costs around $1M-10M in signature-gathering costs to bring something to the voters), and on the enterprise sales cycle (which involves exchange of PDFs between multiple parties, at a lower conversion rate than a streamlined web process).
This looks awesome, and something we'd love to have in Zenbox. To that end, just two requests:<p>1.) Any chance of OAuth support? Our users are in general not technical, and in any case they all appreciate one-click integrations over copy/paste API-key, or even worse, username/password ones.<p>2.) Can we retrieve a list of documents that have been signed (or sent to be signed) given an email address?
Just some friendly feedback that I found it hard to discover what this service is all about. I hit the index page to get an overview, but it took clicking through to the Real Estate and Mobile sections to piece it together - I would normally not do that, but I was extra curious in this case. I think you might want to make some of the overview/intro content available on the index page.<p>Also the FAQ has a very prominent "How does HelloSign work?", but doesn't seem to answer that question. (ie: "HelloSign lets you upload your signature and quickly apply it to documents", or whatever it actually is)
We use HelloSign at your company for easy contract signing - best of all it's free.<p>The ONE thing that I feel is missing is letting people use a purchased certificate from a trusted provider. We need that little extra "formality" before we use this for actual legal documents.
Besides being a well-established startup in the digital signature space and writing all their software in Haskell, Scrive has a good API. I have used it myself for a small project, to build a petition service, and it was very straight-forward. Of course, their typical API user is a large organization with a lot more complex requirements.<p>Fancy marketing presentation: <a href="https://scrive.com/gb/en/scriveapi" rel="nofollow">https://scrive.com/gb/en/scriveapi</a><p>Documentation for devs: <a href="http://api.scrive.com" rel="nofollow">http://api.scrive.com</a>
I'd avoid it.<p>I tried using HelloSign and HelloFax to take care of some contracts while travelling, but the messages sent look like spam (heavily branded, with almost no control over the content of the message), and the document is not sent as an attachment but requires the recipient to register and login to the service.<p>They're so focused on their viral coefficient that the service is miserable to use.<p>I dont mean to be so critical, but I exchanged a number of messages about this with their support line, and all I got back was bullshit answers, such as requiring a login gives "better security!" and so forth.<p>EDIT: The key word I'd use is that the messages are unprofessional. If you're trying to conduct serious business, it's not really suitable, because of their attempts at virality. When it comes to using an API, do you trust these guys to make customer-centric decisions or will you get stuck with something else?
Thanks guys. I am definitely going to use this, provided it is indeed a simple and straight-forward API. Much better than having to deal with existing solutions, trying to build HelloSign from scratch.
I've now used HelloSign for client SOWs, tax stuff and divorce paperwork. Absolutely awesome service and I can't recommend it any higher. Crazy that it's free.
ick. I don't love the send workflow. Lets say I send I need to send a course override form to my academic advisor and she opens the document and all of a sudden has a "hellosign" account? That download link is a little misleading.