Developers, Designers: Make an Infoproduct

If I included all that too, it would be TL;DR. You know I'm right. Follow my blog, though, because I'm going to be writing a lot more about infoproducts over the next few months, and I will be creating that infoproduct course that inspired the article.

But, I will say, you're making a critical mistake if you create a product and THEN try to find customers for it.

Hi, I'm the author.

I've written 3 full-length books, and half of one. Two of the completed ones were for actual publishers, and ended up canceled or not published or I quit in disgust. The last completed one was obviously http://jsrocks.com.

But, I've written maybe 950 pages of book in my life so far.

Writing a book is easy. Giving birth is also easy. Both may hurt like hell, but they're not difficult. You pretty much have to show up and push.

Now, writing a book for the wrong reasons is impossible. If you're doing it for fame or exposure, or the cred, or the money (without finding an ongoing motivating force), yes, you will have to fight yourself every step of the way. But that's because you don't really want to write a book, you want the goodies that you think you'll get.

But, more importantly, an ebook doesn't have a page count requirement. It doesn't have to look at-least-this-thick on the bookshelf. It doesn't have to meet some stupid editorial rule.

It just has to do the job.

An ebook isn't a book.

But, like the rest of my article pointed out, _you don't have to even do an ebook_.

EDIT: Actually, make that 4 full-length books, since the text for my 30x500 Launch Class is nearly 300 pages. http://unicornfree.com/prelaunch.

EDIT: Oh, and it's not because I'm not afflicted with distractability or procrastination. Just trust me on that.

Perhaps that was unclear, but that only refers to 500 copies of the final book (most sales were made when the book was in beta.)