Re:You’re Pricing It Wrong: Software Pricing Demystified
by danielsoneg on Wednesday September 28, 2011 @01:16PM
(#3048895)
One of my favorite anecdotes about that comes from an article found here (can't remember the exact article): The author (a developer) went along with their lead salesperson on a call to MIT. After demoing the product, which normally sold for $150k, the MIT rep asked about the price. The salesperson immediately said "$1 Million" - the MIT rep chuckled and said, "Oh come on, that's ridiculous - you know we don't pay more than $650k for software." The salesperson responded, "Ok, we'll let you have it for $650k - now let's talk extras."
So yes, price is a function of demand first - don't tell the customer what it's worth, let them tell you.
Re:You’re Pricing It Wrong: Software Pricing Demystified
by ohashi on Wednesday September 28, 2011 @04:32PM
(#3049770)
I was expecting this to end with a couple of kids at MIT built the thing for free and open sourced it.
Re:You’re Pricing It Wrong: Software Pricing Demystified
by aaronbrethorst on Wednesday September 28, 2011 @08:55PM
(#3050642)
I think you're referring to this story: http://venturehacks.com/articles/pricing
Re:You’re Pricing It Wrong: Software Pricing Demystified
by HeyLaughingBoy on Wednesday September 28, 2011 @01:33PM
(#3048972)
I think the author was Steve Blank. I have an MP3 where he mentions this happening, but I can't for the life of me remember the name. You can probably find it on IT Conversations.
Re:You’re Pricing It Wrong: Software Pricing Demystified
by damoncali on Wednesday September 28, 2011 @10:48AM
(#3048079)
Agreed. Value, price, and cost are three independent variables. When they line up advantageously, you have a viable product. But one does not determine the others.
Re:You’re Pricing It Wrong: Software Pricing Demystified
by hammock on Wednesday September 28, 2011 @11:23AM
(#3048292)
Good point. There are actually four variables - one of them is usually money though, so we don't think about it that much. The four are
buyer price (= contracted price + opportunity cost to buyer)
buyer value (what the product is worth to her)
seller cost (cost to create product + opportunity cost to seller)
seller value (value of what he will be receiving in return, usually face value of money)
Yes, the article is about subjective value (and finding it), not objective value, but taking the developer's (biased) perception of value as a starting point is a bad idea.
Pricing should be determined early in the development process to inform go/no-go, and the amount of development effort to apply. Starting from scratch on pricing after the product is ready is backward.