Fair Rate for Tech. Authors? 20
vbrtrmn writes: "I have been offered the opportunity to co-author a programming book for a major publisher. The publisher has made an offer, but I'm not sure if the offer is standard or if I am getting shafted. Have any of you written books before? What is a fair rate?"
Fair rate for a book (Score:1)
Standars Rates (Score:3)
Don't really exist - I've dealt with a few publishers now, the bigger ones will offer an advance between $5K - $10K or more for an entire book. You'll also get a royalty if you're the sole or co-author, starting around 10% for the book. You can try to get more, depending on:
A) How bad they want to publish your title...
B) Who you are...
C) If they can get someone else to do it...
Dealing with publishers can be very frustrating, make sure you get a sense of the editors you'll be working with BEFORE you get fully involved. Be honest with yourself, too...does sitting down sifting through tons of information to distill one good chapter sound like fun? How are your writing skills? How are you at deadlines?
The bottom line is that publishers are looking to get the best deal, and some editors are very good to their authors and some aren't. Ask the AE to speak to other authors they've worked with - or don't! Go to Barnes and Noble and browse some of their books that the AE has worked on and contact the authors without asking them. If you're talking about an entire book, you'll be giving up a huge portion of the next several months, possibly a year, of your life. (Note - tech publishers try to push books through much faster than other types of publishing - for instance, a book on gardening isn't going to change dramatically when they release Soil 2.0, but your book will likely have a very limited shelf life.)
Finally, ask about promotion. What will they do to promote your book? My first publisher was a dud on promotion, and now I'm seeing my first title in Microcenter for $3.98. Very depressing. It might not have sold well anyway, but they did nothing to promote it - not even sending it to review editors. If royalties figure heavily in your calculation, you'd better be with a publisher that will push your book.
But, even though book publishing has been frustrating and less rewarding financially than writing articles...I'll continue to do it. It does have its rewards, and it's certainly good at building respect from your peers and for your resume...
Re:My experience (Score:2)
Me too [wrox.com]. They misspelled my name on the cover and still haven't paid me!
Fair rates for books (Score:5)
I got US$20/page for something I wrote back in '96. I was dumb (well, naive) and poor back then, and I was willing to listen to the acquisitions editor when he told me that "some of [his] better authors write 4 chapters a week!" That sounded pretty good to me... US$2400 a week, maybe. Wow!
I'm not sure who these people are that can do that (hacks? machines? hack-machines?), but it's sure as hell not me. I try to budget 3 hours or so per _page_ right now, if I want for there to be any quality in it at all. Even that, that's probably not even fully-allocated time. It doesn't include:
The next book project I did, I was offered it at US$20/page again (enough though it was 2.5 years later, the market had changed, I had more experience, etc.). I asked for US$25/page, and was given it immediately. (Which can only make you wonder what the "true upper limit" on such a thing is.) Still, the money was garbage for the work I had to put into it.
Even then, don't just look at the money. The "standard contract" for a book that most tech publishers give you is... well, to call it one-sided doesn't even begin to describe it. :-) If you hope to have any kind of personal involvement or control over the project or what happens to it after publication, you're likely in for quite an uphill battle.
Love him or hate him, Philip Greenspun has some interesting things to say about the publishing business for tech books. To a greater or lesser degree, I agree with him. Check it out... http://philip.greenspun.com/wtr/dead-trees/story.h tml [greenspun.com]
Does all this mean that I won't write again? No way! I love writing, and I keep going back to it time and time again. I might even be getting better at it over the years, and that puts me in a better position to negotiate contracts, pitch ideas, plan the book the way that I want the book to be, etc. It's hard work, and there's a lot of BS involved, and the pay isn't great, but it can be incredibly gratifying to do.
Please feel free to mail me [mailto] if you'd like to talk any more about this.
Cheers,
Richard
Re:SAMBA UNLEASHED - Another SU boy! (Score:2)
I hear you! I got to save Steve Litt (my good friend and regular flamemail target ;-) in March [2000] by writing Chapter 33 (~45 pages) in a weekend (after another contributing author "flaked" -- which is quite common). I also did Appendix A and B (the ones on Solaris and BSD), although I had plenty of time to write those (pretty much all of January [2000], for only ~30 pages total).
So, as far as myself, I'm good for about 1 productive page/hour (including proofreading/revisions/reorg) -- and I assume other people are in the same boat. That means 3-4 chapters are possible per week, if you don't have a regular, 40hour/week job (which I do).
Yes, the Word markup really pissed me off, crashing numerous times resulting in no less than 2 total losses of my file (luckily I exit and save the file to a different directory every 15 minutes). The sad thing is that I regularly use LyX [lyx.org] for all my personal and semi-professional technical writing. LyX which produces LaTeX, which is probably what they were parsing the Word back into for final publication -- quite ironic IMHO.
As far as "compensation," did you read your contract? I was under the impression that you should NOT reveal any compensatory info to anyone else! Oh well, here's the "unwritten rules" on compensation:
[ Mine was none, so I did it for the exposure -- the "rate", based on my 1 product page/hour, was quite a "pay cut" from what I'm used to.
[ I'll assume MacMillian is "done with you" now
-- Bryan "TheBS" Smith
Re:Beware of books by seveal authors.... (Score:2)
MacMillian's "Unleashed" series is designed to cover everything. This includes having multiple experts and any "redundancy" being "welcomed."
Why? Simply put, the book is so thick (1,248 pages), most users are only going to move to the chapter they need. As such, you canNOT assume they read previous chapters anyway. So having multiple authors is not an issue (as long as there is only one author per chapter).
-- Bryan "TheBS" Smith
SAMBA UNLEASHED (Score:2)
Oh yeah.... (Score:2)
It's a lot of fun to see your book in stores, but it sucks up all your free time. I'm finishing up a Linux LPI Study Guide that my wife and I are doing now...and I can't wait to have some free time again to do projects I currently have on hold.
If I took the same amount of time I put in to the book and just did consulting I'd make a lot more... So, I definately don't do it for the money. But it's a nice resume builder.
Mod this up to +5 for the link.... (Score:2)
Beware of books by seveal authors.... (Score:2)
But, as a general statement I stay away from books with more than 2 authors. I've worked on some books with 6. There is no way to stay consistant and know what others will say. My wife and I are just finishing our LPI Study Guide book, and it's hard enough for us. "Hey, how well did you cover X? What chapter was Y in?" etc...etc...etc....
Now, there are of course exceptions. The UNIX System Administrators Handbook (think that's the right name...new revision has the purple cover) was written by several people and is *GREAT*, but that isn't the norm.
Re:Beware of books by seveal authors.... (Score:2)
I'm finishing my 4th book now... (Score:3)
Is it a flat rate or a royalty and advance? I've dealt with a couple of book companies and they usually have standard contracts, since they put out a lot of books. If you are a full time author with them you can negotiate better terms...but if you do one here and one there, you usually get what they offer.
I'm not sure what my confidentiality agreement says on me releasing numbers, but if you want to mail me in private we can compare notes. Just remove spam-free from my email address.
depends (Score:2)
Copies sold is more important (my experience) (Score:3)
When I wrote my book [amazon.com] on the X Windows Server (sadly, out of print now), it was typical for technical authors to get somewhere between 12% and 18% of the net proceeds to the publisher.
Notice the term net proceeds. That means the amount that the publisher actually received for the book, not the price that someone pays at the bookstore.
What the publisher recieves will vary depending on who's buying and how much they order. (You bet your bippy that Borders gets a better price than Ed's Technical Emporium.). A reasonable estimate is that the publisher will receive about 70% of the cover price, usually, and rarely less than 50% of the cover price.
So, take the cover price of the book, multiply that by say 0.70 then multiply that result by your percentage, say, 0.15 for 15%. That's the amount you'd roughly clear on the sale of a single copy.
It goes without saying that YMMV.
Much more important than all of that, however, is the promotional power of the publishing house you contract with. This cannot be overstated: Number of copies sold is much more important than the royalty amount per copy!
Don't fall for a publisher who promises you 20% without asking "20% of what?"
A 10% royalty on 10,000 copies is better than a 20% royalty on 3,000 copies.
Most publishers won't even want to sign with you unless they think you've got a book in you that's worth at least 5,000 copies. Ask them how they intend to sell it, how they'll promote it, how many other books they have that are like it, and how well they sold those books.
Get numbers.
The name of the game is number of copies sold.
Remember, there's no such thing as The New York Times Best Royalty list
Re:Copies sold is more important (my experience) (Score:1)
What I liked about Wrox was that they gave estimated numbers up front, and also gave the option to take a flat fee per-page. (Incidentally, Wrox said they wouldn't bother doing the book unless they thought it would sell 15K copies.)
Keep in mind that the "brand name" of a publisher is important, and will play a role in how it sells. Some folks will automatically buy a book on topic X if it's from publisher Y.
My experience (Score:2)
It is a lot of work, and the pay/hour may not be what you woudld accept in a "real" job, but so far I've made $15K for about 3 months work, and most of that was evenings and weekends (I kept my day job!). Plus it's been translated into Korean and Chinese, which is a kick.
I wrote some chapters for other books, but delays and moving technology led to the books being canceled. I got paid, but ...
Some tips, for what it's worth:
What are you getting? (Score:3)
I can't be karma whoring - I've already hit 50!
Fair rates... (Score:3)
The worst they can do if you ask for more money is tell you no. Always remember that. They will almost always offer you less than they will pay, generally in case you do demand more.
You also might want to have a lawyer take a peek at your contract in general. Sometimes contracts are not worth signing, if you are liable for more damages than you are paid. But contracts are boilerplate that is negotiable, so you can always try to get around that by having your lawyer creatively modify the meaning of a clause. The biggest bear is the recent influx of liability causes, which state that if somebody sues them, you generally end up footing the bill. Those can really get you.
Re:depends (Score:1)
It depends on... (Score:2)
There are a lot of variables! The software manuals I wrote were strictly "work for hire." It was part of my job and I got my regular salary.
The first two independent books I wrote were self-published, meaning I had to do everything: writing, editing, illustrating, selecting paper and cover stock, working with the printer, indexing, cover art, marketing, promotion, getting an ISBN... I make a lot more money per book on those, but it devours much too much time.
My most recent book was a straight royalty basis with a publisher. If you need cash up-front (an advance), then expect your royalty to be smaller. If you're willing to share in the risk, they'll pay better. I was asking for more than they wanted to pay, and we finally agreed on a minimum quantity. Until that many are sold, I get a standard royalty. After tha minimum, my royalty goes up. It was nice having someone else take care of all the details, although the book didn't look exactly as I would have done it myself.
The bottom line is: if you've done some writing before (tech writing, white papers, articles...), you'll have some idea how long it takes you. Figure out the number of hours you're probably going to put in, divide into what they're offering, and see if it makes you happy.
Don't forget to ask who creates the index (a high-quality index can easily take a couple of days of work), who does screen shots and illustrations (if any), who formats the text, how many free "author copies" you get (ask for lots, since it doesn't cost them much and you can always sell some of them), whether they'll guarantee minimum royalties (in case the book doesn't sell well), and their marketing plan (see what they're going to spend on peddling the book).
Watch out for penalties on missed deadlines, percentage royalties with no minimum (if they sell books cheap, you hardly make anything), royalties based on "net" sales (you have no control over their marketing costs).