It's safe to ignore anyone complaining on the topic of price. Those of us that spend thousands of dollars every year to keep our education up for our section of

It's safe to ignore anyone complaining on the topic of price. Those of us that spend thousands of dollars every year to keep our education up for our section of the technical playground aren't going to hesitate at paying $30 for good information. I'm confident you've put at least $30 of value into every book, if not thousands more. My first ebook on software design sold for $97 starting in 2001 and that's when nobody had even heard of ebooks. I made six-figures several times over with the product. Amy, I would suggest spending more time on the sales page. I don't think it's driving home just how valuable the book can be. Put yourself in my shoes as a developer and hear all the silly questions I'm asking about the book and the problems I'm having with my code in which your book will help out. For sure, you shouldn't have your bios hanging out on the side of the page. Drop them in the middle and really allow yourselves to shine. I'm not even sure if the best angle to spin the guide is as a "is your app slow?" type of book. Some of us want to produce high-quality code and want to see useful techniques for improvements across the board. "Supercharge your Javascript" resonates more strongly with me than "Do you fall asleep waiting while your apps are running?" Feel free to ping me if you'd like some additional advice. For sure, add a box to the webpage for folks to sign up for updates. Get a cheap account at aweber.com. Regularly mail updates out about the guide. Often, it takes 7-10 impressions of a product to make the sale. And once you have thousands of folks on your list, selling the second guide you write will be much easier!