Subscribe to EDN

Pricing: vases and coffee pots

April 3, 2009

My father-in-law was an executive at Wedgwood and responsible, among other things, for pricing every piece of china they made. Wedgwood has recently been run into the ground by Waterford Crystal who had acquired it, and it is now in administration (roughly chapter 11), but that is another story.

Anyway, a Wedgwood coffee pot sold for $80 (I’m guessing these numbers). It is a complicated piece to make consisting of a body, a handle, a spout, a lid and a little piece that goes inside to stop all the coffee grounds going down the spout. However, if we throw away the lid, don’t bother to put on the spout, forget the handle and the little filter piece then we have a much simpler item. It’s a vase. It sells for $100. Paradoxically, the vase, which is much simpler to manufacture, has higher value to the consumer and so sells for a higher price.

It is important not to assume that the value to a customer of every product is a fixed industry markup over its cost. That will be true in a competitive mature market since any differentiation that leads to a higher price will get copied and competed away, but it is not true when products are differentiated. That is why it is so important to have differentiation, otherwise you are stuck selling silicon at a small markup to cost and you probably are not the lowest cost supplier. You either want to be Walmart (lowest cost supplier) or Whole Foods (lots of differentiation), not Safeway.

When I was at VLSI Technology in the late 1990s, one of the things I did was help run the strategic planning process for VLSI’s communication business (mostly GSM chips). We had a relationship with a French company called Wavecom that had a GSM software stack and a GSM radio design. VLSI made the baseband chip. At the time, understanding the GSM standard well enough to build a baseband chip was a big differentiation, and we were one of a couple of semiconductor companies with a standard product, which gave us some pricing power. But it was easy enough to see that, just as had happened in the PC chipset business, lots of competitors would enter the market and it would become a cutthroat cost-plus business. Digital design, no matter how complex, is not defensible for long. I told our communication group that we had better have a plan for acquiring Wavecom (which didn’t want to be acquired, certainly at any price we could afford) or else we should have a plan for finding a new software/RF partner since that is where the differentiation would move. Otherwise we would eventually get pushed out of the market. In the end Philips Semiconductors acquired VLSI in a hostile takeover, and they already had a software stack and RF and so the problem got solved that way. But it wasn’t a message the communication division wanted to hear since building those chips was so hard they wanted to believe that it would continue to be differentiation for a long time.

Software has a disadvantage over hardware in that the manufacturing cost is known. It is basically zero. All the cost of software is really an R&D cost being amortized over product sales. It is like a pharmaceutical business in that sense, pills that are incredibly expensive to formulate but incredibly cheap to manufacture. But unlike the pharmaceutical business where IP protection works, there is very little that can be done in practice to keep a product proprietary. It is thus hard to keep differentiation and pricing power for long. And hard even when there is no competition. Hardware accelerators such as Cadence’s Palladium or Eve’s products have a large hardware cost and sell for a high price. But despite that proven value, you know that if a software product had the same performance it would not sell at the same premium price point.

Of course these things are relative. In most software businesses, the prices we get for EDA tools are prices that other companies dream about. This is a challenge as the ESL market grows and starts to meld with the embedded software market. We may think a Verilog simulator is cheap, but it is a lot more expensive than a compiler or a debugger (even ignoring open source where the price is often zero). But that is a topic for another day.

The main implication for EDA is that the value of a product is determined by the customer not by the EDA company. There is plenty of pressure from customers to reduce prices on non-differentiated products, but very little from the EDA companies to get more return from the strongly differentiated products. Too many coffee pots and not enough vases.

Posted by Paul McLellan on April 3, 2009 | Comments (3)

February 14, 2010
In response to: Pricing: vases and coffee pots
ff commented:

fefhoefhoefhopfhof


November 11, 2009
In response to: Pricing: vases and coffee pots
abby@Make14Me.com commented:

I was just doing soome searches out vases.....lolllll....i are less coffe pots and more vases...htt://Make14Me.etsy.com...hows my pricepoint to you?


April 3, 2009
In response to: Pricing: vases and coffee pots
Meredith Poor commented:

Another way of understanding software cost is the cost of discovery. A customer determines that they need something, typically in response to an inefficient process. They hand this to a contractor or an IT manager, who identifies the parameters of the problem, and then assigns the coding work to one or more programmers. The programmer starts to assemble a framework: data structures, classes, and user interface (UI) components, and discovers there is something he or she doesn't understand. This is routed back to the manager, who doesn't know, who routes this back to the client, who is now faced with what is basically a design decision. There are several possible pathways from here: 1, the client answers the question based on common sense in their context and hands the answer back to the programmer. 2, the client instructs the programmer to propose an approach, and the IT department then becomes responsible for architecting the solution. 3, the client realizes that the programmer has exposed an operational non-sequiter, and the client will need to make operational changes to address what has been learned from deep inspection. At this point the software development component of the solution may no longer matter at all. ~~~ Cost, in this context, is a measure of the involvement of the various parties in coming to an understanding of what needs to be done. The value proposition is nearly always far in excess of cost. An afternoon of work by an operations manager (the client) and programmer can produce $100,000 in savings per month. If the developer is a contractor, the liklihood of the savings being shared are close to zero. About all that's assured is further work.

POST A COMMENT
Display Name
captcha

Before submitting this form, please type the characters displayed above. Note the letters are case sensitive:

Advertisement
Advertisement
Advertisement
About EDN   |   Site Map   |   Contact Us   |   Subscription   |   RSS
© 2012 UBM Electronics. All rights reserved.
Use of this Web site is subject to its Terms of Use | Privacy Policy

Please visit these other UBM Canon sites

UBM Canon | Design News | Test & Measurement World | Packaging Digest | EDN | Qmed | Pharmalive | Appliance Magazine | Plastics Today | Powder Bulk Solids | Canon Trade Shows