3 ms·
I'm sure Graham & co are on the level (I've never met him/them), but I was warned that there are vc who are scum. The advice I received was to document everyth
by dhimes 18y ago
I'm sure Graham & co are on the level (I've never met him/them), but I was warned that there are vc who are scum. The advice I received was to document everything. Make sure you document who is at any meeting, and what info is passed along. Keep careful track.
- patio11 18y agoKeeping careful track of who you tell what does not sell widgets to customers.
- dhimes 18y agoSorry, I don't get your point. Do you mind elaborating?
- randallsquared 18y agoThe expected value of extra documentation for a possible lawsuit is lower than the expected return on just carrying out the business plan with the same resources. That is, it's almost certainly a waste of time.
- dhimes 18y agoAbsolutely not. In fact, it is standard practice in most laboratories to have a research notebook that documents such things for patent purposes. This is relatively easy to do, and isn't much bother at all.
- euccastro 18y agoWhat do you use that documentation for?
- dhimes 18y agoIf you need to go to court, they become legal documents showing you had the idea, and whom you told, and when. VC won't sign NDAs, so this is your best protection. At the least, it can stop ugly boards (think: Blackboard) from coming after you once they gain traction ('cuz they got the VC funding, remember?).
- pg 18y agoI've never heard of a single case where a startup made a claim against anyone based on such information. Nor is it necessary to protect oneself; commit logs should be fine for that.
- dhimes 18y agoThe advice I got didn't only apply to startups. But, hey, you would know a lot more about this than I. commit logs should be fine for that You have commit logs for business plans? You're a good man.
- dhimes 18y agoMr. Graham, do you take requests for essays? You've been on both sides of the table on this. What would you honestly tell your younger self about protecting your work from "bad guys?" What is worth worrying about, and what is not, in your estimation? That would be very cool.
- pg 18y agoWe don't have to go back to my younger self: I constantly have to advise YC startups about this. What I tell them is short enough to put here. The only effective protection is secrecy. But you never want to seem overtly secretive. So the optimal policy is to seem to be explaining everything about what you're doing, but to omit the important but non-obvious details that you get right but someone trying to reproduce your project would initially get wrong. By definition, no one who's not an expert will notice when such details are omitted. Part 2: Err on the side of openness. Your valuable secrets are not as valuable as you think, and the danger of telling people stuff is not as great as you think.