TL;DR; Dried ramen comes with a fork - not chopsticks. Ramen makers know that their product isn't bought by people looking for a gourmet authentic Japanese meal - they're college students and busy people who just want quick carbs. Look at your product: are you lying to yourself about who your customer is?
So the reason I choose to send a PDF over a Word Doc is total visual control of the end product. If people open word docs on different versions, or with certain fonts missing or whatever, the layout can get screwy and messed up.
With a PDF I can guarantee what the end product will look like on every device, every software version. Even if they open it on a Windows XP machine, a PDF will look the same.
How will this API + HTML5 guarantee the same thing?
(For the record I think this sounds awesome and I'm a huge fan of PandaDoc, but I didn't see anything in the blog post announcement around visual consistency across browsers/devices)
I launched the pre-orders at the beginning of June and had some great feedback, plus plenty of suggestions for the next release.
I've found it really liberating and relaxing to write something that has a "flow" like a story. Any blog posts or guest posts need to be "standalone" where as the book has to flow and take the reader on a much longer journey, and I've found it hugely challenging but I've learnt tons from it already.
As the book is aimed at "data-driven beginners" (who are mostly really experienced marketers/CEO's but perhaps new to SaaS or tech startups) so it's a very specific target reader. I'll definitely work on more books in the future after the experience so far!
This is one of the introductory chapters to the book, so it's intentionally aimed at people who are either new to modern metrics/analytics or are looking to get into Growth Hacking, but don't yet have the foundation theory knowledge to get started with the strategy.
Any questions, or if anyone would like to be one of the case studies for the book, please get in touch!
Updated the post to include input from Mike Butcher after he checked out the first draft. He offered his advice on what to do if you want to get covered by TechCrunch's writers
Sorry I've changed the wording to better reflect that I'm encouraging discussion on here. Thanks for the headsup
I've noticed on a lot of blogs, there'll be 1-5 comments on the blog itself, but 30+ HN comments, so seems like a good idea to allow people to discuss on the forum that they're most comfortable with.
Cost Per Macaw