Negative Pricing

One important step in determining a price for your product is to determine how much it's actually worth. But what does that mean?

Your product is worth exactly the same amount as the cost of not using your product. Analyze the way prospective customers currently achieve the goals your product would satisfy and determine the costs they face in achieving these goals.

No, "negative pricing" does not mean paying your customers to use your product. It's the term I use for basing the price of your product on how much it costs for your customers not to use it.

Comments

Balu said…

What you said is partly right. But its tricky to price your product if ppl miss-understand the concept. For example an excel-automation might save few millions to a company where it hardly save few Tonne to other. In that case how would you place your product. I would be glad if you can post some best methodologies that can be used/currently being used.

Tue Jul 21, 09:12:00 AM 2009

Roger L. Cauvin said…

Thanks for pointing out that the "negative price" of a product (the cost to not use the product) varies by customer.

There are at least two ways of dealing with this challenge:

1. Vary the price of the product based on factors (e.g. number of "seats") that reflect the value to the customer.
2. Identify the largest market segment with the highest "negative price" and price the product to that segment.

Tue Jul 21, 10:00:00 AM 2009

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

Cauvin

Search This Blog