Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Building vs. Buying an eSignature API (hellosign.com)
15 points by encorekt on Dec 13, 2018 | hide | past | favorite | 3 comments


I built a very rudimentary digital / electronic signature tracking app in Django several years ago and I would have gladly paid for this product.

Just like stripe, offering a service with a developer friendly API-first approach is great and I happily pay for someone else to be the domain expert.

Sucks when services go down or are complete black boxes but I've been using HelloSign for several years as a consumer and it's always been fantastic. This was a neat article and I'll be sure to use them the next time I need to integrate signing in an app.


We built our own because it was about the same work to use an api as it was to just build a canvas solution. Inline pdf signatures are a little harder but we will be building that next. The first build literally took a few days. I understand paying $50 a month for docusign but it's baffling why anyone would pay $50k or $100k per year for what is essentially a feature.


Realistically, probably most organizations out there really don't need to spend the time or resources building a solution when super-customizable options like this exist. Just gotta get out of that mindset.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: