Hacker News new | past | comments | ask | show | jobs | submit login

We're building exactly this for contract analysis: upload a contract, review the common "levers to pull", make sure there's nothing unique/exceptional, and escalate to a real lawyer if you have complex questions you don't trust with an LLM.

In our research, we found out that most everyone has the same questions: (1) "what does my contract say?", (2) "is that standard?", and (3) "is there anything I can/should negotiate here?"

Most people don't want an intense, detailed negotiation over a lease, or a SaaS agreement, or an employment contract... they just want a normal contract that says normal things, and maybe it would be nice if 1 or 2 of the common levers were pulled in their direction.

Between the structure of the document and the overlap in language between iterations of the same document (i.e. literal copy/pasting for 99% of the document), contracts are almost an ideal use-case for LLMs! (The exception is directionality - LLMs are great at learning correlations like "company, employee, paid biweekly," but bad at discerning that it's super weird if the _employee_ is paying the _company_)




That makes sense, how are you guys approaching breaking down what should be present and what is expected in contracts? I've seen a lot of chatbot-based apps that just don't cut it for my use case.




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

Search: