3 ms·
This is exactly the problem we're trying to solve at Leanpub. 1) We pay 90% royalty, not 10% (with a flat fee of $0.50 per purchase) 2) We think you should st
by spatten 14y ago
This is exactly the problem we're trying to solve at Leanpub.
1) We pay 90% royalty, not 10% (with a flat fee of $0.50 per purchase)
2) We think you should start selling your book before it's done, so that you can find out if you have a market for it, and so that you get feedback from your readers as you are writing.
3) Once someone buys your book on Leanpub, they get updates to the book for free. This is great for technical books, as you can keep your book up to date when technology changes.
4) You own your book. You are free to get a publishing deal with a "real" publisher once the book is done (if you can stomach the hit to your royalties). Imagine going to a publisher and being able to say: the book is done. I have sold 2000 copies on Leanpub, and have tons of great feedback. Here is the manuscript. Oh, and right now I make 90% on every sale. I bet that gets you a better royalty rate than approaching a publisher with just an idea. We all know how much those are worth :).
5) We think our workflow is the least painful way to write a book right now, and it's getting better every day. You write in Markdown in a text editor, save to a Dropbox folder, and hit the publish button on Leanpub.
- currywurst 14y agoExcellent work on Leanpub guys, and a well written summary .. I think you can replace this succinct 5-point blurb in your "How Leanpub Works" section ;)
- stevejalim 14y agoI'm a former journalist and have rejected a traditional-publisher book advance in the past (£2k for something that'll take me 6 months to write? No thanks!). Not wishing to sound like a fanboy, but I'm really loving the Leanpub experience, even though I'm waiting till I'm mostly finished before publishing v 0.9 of my book [1]. (It isn't the same one for which I was offered and advance; this one took a about 6 months of a few evenings a week.) The ability to push updates, etc, does really make a big psychological difference to me as an engineer-meets-author - I'm creating something which I plan to evolve/do point releases on, based on user feedback. It's a little like Agile meets publishing, I guess. [1] <shameless> http://leanpub.com/freelancedeveloperbook http://leanpub.com/freelancedeveloperbook </shameless>