Also the title made me think that this is about LESS, the CSS framework, but maybe that's not a common association.
Yeah I thought about that too, but the audience I'm going after didn't make that association so readily.
Edit: I opened the page for registration at 4pm EST yesterday (1st May).
I made the exact same connection. It was only by looking at the URL that I suspected "less" would refer to MVP rather than CSS.
Price is a way to send a signal about what you should expect from the book and can have an impact in how much attention is paid to the advice in the book.
Take me for an example. I have hired a coach to help me grow my business, but I'm also attending SCORE meetings. SCORE is free, and the coach is far from it. Sometimes, they both provide similar advice, but when they differ.. guess which one I trust more?
Your job as the author is to set up the expectations so that when I read this book I can have a sense of what it's worth to me to read. If I can take the knowledge from this to save $25,000, it's worth a whole lot more to me than $20.
The price should be based on the value I can expect from the book, not because other people thought of a number that sounded good. In practical terms, what everyone thinks is useless. The results are what determine the value of what you're sharing.
Neither am I, and the Customers aren't choosing the price here. They are signalling how much they think they would pay - there's nothing that guarantees they'll get it for that price.
I didn't choose that page layout - it's what Leanpub provides for an unpublished book. I only consider the price that customers signal as an interesting reflection on how much value the book title and subtitle convey on first reading.
I also latched onto the Lean Startup genre and didn't immediately understand the programmer/web architecture distinction. Also, in the subtitle blurb you say, "Startup Founders Open Up About Web Architectures In The Early Days." That made more sense to me after I read the rest of the page, but it might be helpful to point out they're discussing "their web architectures." At first, I thought the book was about the history of web architectures.
