advertisement

Search


Sponsored Developer Resources

Atom 1.0 Feed RSS 1.0 Feed RSS 2.0 Feed


Webloggers
Login
Home




Right of First Refusal Clauses in Book Contracts

   Print.Print
Email.Email weblog link
Discuss.Discuss
Blog this.Blog this

Tim O'Reilly
Jan. 02, 2004 11:37 AM
Permalink

Atom feed for this author. RSS 1.0 feed for this author. RSS 2.0 feed for this author.

One of my editors just wrote to our internal editors list an impassioned email about Right of First Refusal Clauses -- and since I agree with him that right of first refusal clauses are pernicious, I thought I'd publish his comment, and challenge publishers who use them to justify the practice, if they can:

I'm increasingly running into authors who have really strong non-compete clauses, right of first refusal on subsequent books, and other stuff like that in their contracts.

[Names of some offending publishers omitted.]

I'm tempted to suggest that we add similar clauses to our contracts, but frankly, they're repugnant to me. And that would only make the situation worse, not better.

What we really need to do is broadcast the word far and wide that a first time author should never sign a contract that limits what he can do in the future--particularly with respect to his publisher. That's just standard good advice for first time authors. And it's advice I've given authors ever since I started working here.

And then another of our editors chimed in:

I've run into the same thing [right of first refusal on all subsequent projects]. In one case, the author was released for a particular book. While he's since been promised release from all further books, they're not really moving on fulfilling that promise. So he's in limbo.

I can sometimes see non-compete clauses if they are restricted to a very specific title or subject. We don't have them at O'Reilly, and it does burn me somewhat when we see an author go and write a very similar book for another publisher (it's happened to us once or twice). But we generally find that common sense keeps authors from doing that. If a book is doing well, an author should put his or her energy into updating it and promoting it, trying to build on the success, rather than dividing the audience. If you compete with yourself, you can often drive both books below the level of ongoing retail viability. On the other hand, if a book flops, and the author wants to try again with another publisher, he or she should be free to do so. So on balance, we don't think even non-compete clauses make a lot of sense -- at least not unless the publisher has made a major investment in the author or series. (For example, it might be a legitimate component of a major multi-book deal with unusually high advances and royalties, or appropriate in a case in which the publisher developed an unusual book concept and just asked the author to execute on it.)

But right of next refusal for a first time author? And coming from publishers who have limited marketplace success? That's really bad business. And it does seem that many of the publishers offering these kinds of contracts are in fact the second tier publishers, the very publishers whose lack of success with a title is likely to drive an author to want to try again with someone else who has better distribution, sales and marketing. (They also are common in contracts from one of the top publishers in the industry.)

Advice to authors: If you're offered a contract with a right of first refusal clause, strike it out. You'll very rarely find it a deal breaker for the publisher, and if you do, let it be so. It should be a deal breaker for you. If you're offered a contract with a non-compete clause, think hard about whether or not it's fair, and unless there is a compelling reason for the publisher to bind you to such a promise, strike it out too.

Advice to publishers: if you want to keep your authors, treat them well, and sell lots of copies of their books. Locking them up by contract is not the way to go.

I'd love to hear from publishers who feel strongly that these clauses are justified, and why.

(I posted a version of this message to the Computer Book Publishing List, and author John Levine replied with an interesting hack: "Computer book proposals are a dime a dozen, so fish a few of your old ones out of the pile, send them to the publisher, they say no, and you're off the hook. Or they say yes in which case you either negotiate a contract you're happy with (I've never seen an option clause that required that you accept their offer) or you don't, and you're still off the hook." I haven't looked at enough of these clauses to know if this would work -- send in a proposal that is completely unpublishable, and then be released from the obligation -- but it's an interesting idea for authors, if their publishers are so unreasonable as to try to hold them to publishing any future books, despite an unsatisfactory first experience.)

Tim O'Reilly is the founder and CEO of O'Reilly Media, Inc., thought by many to be the best computer book publisher in the world, and an activist for open standards. O'Reilly Media also publishes online through the O'Reilly Network and hosts conferences on technology topics, including the O'Reilly Open Source Convention, the O'Reilly Emerging Technology Conference, and the Web 2.0 Conference. Tim's blog, the O'Reilly Radar "watches the alpha geeks" to determine emerging technology trends, and serves as a platform for advocacy about issues of importance to the technical community. For everything Tim, see tim.oreilly.com.

Return to weblogs.oreilly.com.



Weblog authors are solely responsible for the content and accuracy of their weblogs, including opinions they express, and O'Reilly Media, Inc., disclaims any and all liabililty for that content, its accuracy, and opinions it may contain.

Creative Commons License This work is licensed under a Creative Commons License.



Sponsored by:



Weblog authors are solely responsible for the content and accuracy of their weblogs, including opinions they express, and O'Reilly Media, Inc. disclaims any and all liability for that content, its accuracy, and opinions it may contain.

For problems or assistance with this site, email