Ask HN: Someone's writing a book about my app. Do I ask for money?
I have a free piece of software and someone has contacted me asking if they can include comprehensive guides for it in a book.
Specifically, they're asking for permission to publish my logos, screenshots, etc. and have suggested they'll use my software as a selling point (on the cover, in promo, etc.)
My gut reaction is "cool, go for it!" but I'm curious what the "norm" is in this situation. Should I be asking for something here?
I'm not too concerned about the money. I've just missed enough opportunities in the past to know I'm bad at this stuff. I'm mostly just trying to improve my business sense!
(
22 comments
| 22 points
| on HN
)
Long story short: you're happy about this. Buy the author a bottle of wine to thank them.
[1] scare-quotes applied because I've never seen someone be concerned about it
This way you can make suggestions ("Why didn't you include a paragraph or two about feature X?") and correct mistakes ("this bug was fixed in version 1.3.4" or "this feature is available under the Tools menu").
You might even take the feedback from the authors, improve your software and have the book reflect your updated version if you are fast enough. Just beware the feature creep, as always, and don't try to delay or annoy the guy, he's just doing his job too.
This is great marketing for you and the least thing you want is regret the way it was done after it hit the shelves.
(The last time it happened, it was an American state's educational standards committee wanting to write me into their standards document. Why on earth would I say no to that?)
P.S. "Thanks for offering to add me to the acknowledgements. Why don't we save a tree and you can just credit me on the project's website?" (PR7 link for free!)
Offer to review a draft before publication. You'll catch some of the (inevitable) mistakes, which will make the book better. If it turns out to be a useful book, offer to write a foreword, which will give the book something of an official imprimatur.
If you are particularly protective of your product's logo, you could refuse to allow general use of it on books without explicit permission (this is true of the Ruby on Rails logo and DHH, for example).
Second, you could offer to take a look at the material before he publishes it, make suggestions, etc. This would benefit him because you are a superuser, and it would benefit you because you can make suggestions and help make it the best advertising tool.
Additionally, if you have a new software release coming up, you should offer to give him a beta version and at least let him know about the latest features, since books become outdated very quickly. This may even motivate you to get stuff done!
If there was a bunch of money in writing the book, you probably would have already written the book... and your book would be infinitely if not markedly better since you wrote the app/software.
Nothing wrong with not wanting to document your free software to the point where the book is useless, but asking money from someone that wants to do this for you for free isn't something I would personally recommend.
I don't know how disruptive your app is, but Geoffrey A. Moore goes into detail on this in his book Crossing the Chasm. He discusses how the support from others(such as this book) boosts your product in the eyes of your customers and future customers.
Perhaps make an offer to do some (paid) work on the book, for example, proof reading, a forward etc.
Maybe highlights of the book should be included free with your software as documentation.
What happens if they never complete the book or publish it? Maybe agree that it goes public domain if that happens, so what is done is not wasted.
Give the author as much flexibility. Than start developing a premium option in anticipation of the increase in potential users that the book will bring.
Many people in your situation would beg or pay to have that kind of exposure. Don't be greedy. Give and ye shall receive.