Flexible Rails

As readers who are subscribed to the private flexiblerails Google Group know, I have been approached by two major publishers regarding publishing Flexible Rails. When confronted with any major decision involving the book, I have solicited feedback from my readers on the flexiblerails Google Group.

I took a poll which asked the following question:

"Obviously everyone gets the final PDF copy of the Lulu edition of the book (about Flex 2 + Rails 1.2), which should be done in 2-3 months. In addition to that, which would you prefer (in order):

A) $20 off the print book from Lulu (about Flex 2 + Rails 1.2), and 50% off all subsequent PDF editions (Flex 3 + Rails 2, Flex 4 + Rails 3, etc)

B) a decent size percentage discount (better than the Amazon discount) off of a professionally produced print version of this book (about Flex 2 + Rails 1.2) in approx. 3-4 months

C) a decent size percentage discount (better than the Amazon discount) off of a professionally produced print version of the next version of this book (about Flex 3 + Rails 2) in approx. 9-12 months

D) approximately 50% off of a professionally produced PDF version of the next version of this book (about Flex 3 + Rails 2) in approx. 9-12 months"

I got tons of very thoughtful replies. The people on the flexiblerails Google Group are great.

The typical response was essentially the following: "I just expected the final PDF of the first edition, so do what you want on a book deal. If you want one, you deserve it. That said, my preference is A." Almost everyone who expressed a preference chose option "A" as their most preferred choice. This was what I expected, and was primarily why I turned the book deal down in the first place. (There were other confidential reasons, of course.)

So, the resolution is that I am going with option A: Flexible Rails is going to remain published and sold on Lulu as a PDF and (when it's done) as a print book. Anyone who buys the PDF will get $20 off the print book from Lulu, and 50% off all subsequent PDF editions (Flex 3 + Rails 2, Flex 4 + Rails 3, etc.).

In terms of getting distribution for the print book, Lulu can sell books on Amazon and other online merchants (as well as directly from lulu.com). So, while the book won't be quite as widely distributed as it would have been with a traditional publisher, it will be fairly good.

One thing that a couple of readers have said to me is that they saw this book as more of a service and community than "just a book". I agree: this is something that just kind of evolved accidentally over the last 10 (!) months, but which I'm really happy about. I have felt that this book is as much a group conversation as anything else, and there is no reason to change that now.

So, I am starting to see Flexible Rails as an example of a new model in publishing: BaaS (Books as a Service). [I couldn't help parodying SaaS.] Since PDF books, like software, have essentially zero variable cost, they should also have a proper upgrade process--just like software. (This is especially true with a topic which is as fast-moving as the Flex + Rails combination.)

In my opinion, this is the next step in the evolution of the "Beta Book" process pioneered by the Pragmatic Programmers. I am not saying that it is right for every book--a book like Getting Real probably wouldn't have benefited from it as much. However, I think that the BaaS model is the right model for this book and potentially for many others. The excellent royalty rates and control to the author that Lulu offers enables a lot more creativity in this regard.

I really appreciate the generosity of my readers: essentially everyone was willing to free me from my future discount promise if I really desperately wanted a book deal. Also, I'm not knocking all traditionally published books--I may even write one in the future, partially out of curiosity to see what that process is like. However, the Lulu + BaaS approach seems hard to beat...