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

> it ought to read and handle well.

" For a first sale in particular, the immediate benefit of the fact of a sale probably outweighs probability times cost of any conceivable drafting flaw that doesn't produce uncapped liability, a cloud on IP, or some other existential threat."

I had to parse this sentence about 10 times and still don't entirely get what you're saying




Touche. Thanks for making such an effort to understand the sentence.

What I tried to convey is that the ability to say you've made a sale is worth a lot. It's a milestone, and it comes in the vulnerable make-or-break days of a company.

A flawed contract provision only hurts when circumstances force you to live by or enforce that provision. The chance of that happening for any provision of any particular contract is usually low. On the other hand, if the flaw in the language can shut your business down, even a small chance of that bad outcome is worth worrying about.

I assume that a very orthodox proposal will draw less attention, prompt less negotiation, and get more deals signed quickly. My conclusion is that, because the first sale is worth so much when you need it, you might be better off with a traditional, error-prone form that's easier to get signed than a modern, technically superior form that protects you in edge cases and after long negotiations. Your business might fail because you never sold, long before anyone has any reason to sue you.

In my defense, I don't choose to express myself personally in the style of my contracts. You'd probably have understood me better if I did, but no one should have to live that way.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: