Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I worked on this for a while as well! I talked with a lot of people who deal with contracts regularly (both lawyers and laypeople, in-house and in private practice) and all of them acknowledge there are inefficiencies in the way they work. The desire for better tools exists out there, it's just a matter of figuring out the best way to deliver it.

The existence of the MS Word shackles means that an incremental solution is inherently limited by being compatible with the MS Word format, one way or another. Even if you convince one client to move to your solution, everyone else they interface with will still be using MS word, so you must take that into account. Import/export features can smooth the way, but will hold you back on the kinds of features you'll be able to develop.

Building an entire suite that delivers a new, improved workflow is more tempting for the client, but then you're building a lot more up-front and limiting yourself to clients that actually have significant legal-related costs to defray. And again, it's still likely that your client will continue to work with people who won't be using their new tool, so will have to resort to MS Word on occasion.

And to top all that off, there are a LOT of people that need to be able to use this tool. It has to be built for lawyers, sales people, procurement people, VPs, CEOs, paralegals, customer success, consultants, among others. And even if you're only talking about contracts, even contracts vary widely in length, complexity, and importance.

All in all, it's a really interesting space, and I really enjoyed working on the problems there. Someone is definitely going to crack it within the next few years. Would be glad to talk more over email.



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

Search: