One of my favorite bloggers in the whole wide world, Eric Sink of Sourcegear and Vault fame, just published an article on MSDN about properly pricing your hot new software package. The Product Pricing Primer contains interesting points like product positioning, determining expenses, and one of the best inferred Star Trek references I've seen in a long time. This is definitely a must-read for anyone developing shareware (or any other type of software). What do you think about Eric's advice? Do you have similar stories to share? Common pitfalls that aren't covered by the article? I'd be interested in getting your thoughts on this.