Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You should explain it clearly on your page, not here.

I also was confused by the model. The model you try to use is obvious for you but in order for people to understand you need to make an effort in communication, because most people are not used to it.

You have to be extra careful because people have fear of the unknown, so you need to also get rid of people's fears, you do it here("if you don't like it,just don't continue the subscription"), but you should do where people take the decision.

I think the model makes sense but you need to explain it in the buying page as a benefit they we will be getting. For example:

With this subscription you will be supporting the development of free open source libraries that will become yours forever.

Now I see that you display this information but I did not see it while being interested on the book, so it is not visible enough.

If I were you I would not try to train my customers, it is too much work, I would offer the book plus code plus 8 months of subscription for just $119!!

Then in the subscription I would give my customers something they can not get easily out of it, like the network connections and support with people interested in this area all around the world(the people that buy your book), so once they are subscribed, and they are used to it, they have to remain subscribed.

The value for me of those open source libraries is zero because I don't use them. Only if people use them, they can value it. You need to get people in the loop first.



Thanks for the tip. I was wondering about these concerns early in the process, but my target audience, programmers, seem to be getting the point as I am satisfied with ther reaction to the current model.

Maybe it could work better, maybe I could get more money with different approach, but I am a programmer; my goal is to concentrate on writing good software and good books. If I was a marketing genius, I would have probably chosen different career path :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: