So I’m writing a short ebook on writing better WordPress code. Something like 10 Tips to Write Btter WordPress Code Next Month. The thing I’m wondering about is ebook pricing.
Does Length = Price
I know I want to charge $10 for the book but I keep coming back to how the user determines if the cost is appropriate. I keep thinking that for a short book (under 1000 pages) length will have some factor in the user feeling the product is worth the cost. If that’s how they’re deciding a 2 page book may not seem worth it.
Value Should be the Gauge
Really the value of the information is what should be used to determine if the book is worth it. When I’m looking at purchasing something for my business I think about how it will help me save time or bring in more income. So when I purchased Beanstalk I just tested how much time I saved pushing files to client sites and how many mistakes were saved.
When I look at marketing, I see how many projects I get from the money spent. If its enough more at the end of the year I keep doing it.
So I need to convince my users that by reading the book, and enacting the tips, they will be faster write better code that is easier to maintain and be able to charge more.
Guess I need a marketing page for the book.
4 responses to “Determining ebook Pricing”
Have you tried asking WordPress Ddvs what they would pay for such a book?
Put up a web site with a bio of the book and an example of a chapter. Then ask people what they would pay for the full book.
It will give you a better idea of what you can charge for the book. Also, the WordPress community is large, so I imagine you wouldn’t have too much trouble getting feedback on pricing as well.
You could also ask for people to sign up for release dates on the book. Perhaps an early bird offer as well if people buy the book now?
Just some ideas for you to consider.
I have touched base with a few WordPress devs about it, but the book isn’t really for them. The book would be geared towards programmers that have dabbled in WordPress themes but aren’t sure of best practices or a strong beginner that can build a theme and basic plugin looking to take it to the next level. The book is not geared towards me or devs like me. They might get a few workflow tips as they have insight in to how I do it, but that’s about it.
I do think I’ll get LeanPub going once I have a chapter edited and ready to go. I have the chapter outline already.
Fully realizing I’m not the target audience for this book, I’m trying to imaging what a good length for a $10 tutorial book would be. Say, one with 10 tips on getting started with Ruby (since I’m learning). With that in mind, I think 10 pages would be a good length.
Basically, 1 tip per page, with some practical example of how it’s used. So not just “Internationalize your strings” but the point and an explanation – maybe with code – on why and how it’s done.
I’ve got 90% of 1 chapter done and I’m at 2000 words, which is more than 1 page. I’m thinking it’s going to be 20 – 50 pages when I’m done so probably worth more than $10 I’m thinking now. Probably more in the $29 – $39 range.