Skip to main content

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.
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.

Popular posts from this blog

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

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem