“What revenue model should I use? = the wrong question to ask.
Why will people pay me? = the right question“
The Board of Innovation.
There are so many different revenue models in OSS that there are no simple apples-for-apples comparisons on price. There are perpetual licenses, annual licenses, processor-based licensing, node-based licensing, named user licensing, concurrent user licensing, data volume-based licensing and so many others.
The potential customer may have to prepare a comprehensive Total Cost of Ownership (TCO) analysis to get some level of comparison, but even then there are many variables/assumptions being made along the way.
The vendors’s products are already highly differentiated so I wonder whether the revenue models don’t necessarily need to be? Each vendor’s pricing strategists have far more expertise than me in this area, but my mind always goes back to the saying, “a confused mind says no” and many customers end up confused with the different pricing models presented to them.
Do you think that a “clear / simple pricing model” combined with a “clear / obvious reason why people will pay” would make it easier for the customer to say yes? Or am I being too naïve?
Earlier this week, I was lucky enough to be introduced to a talented RAN automation expert. He’s one of Australia’s foremost, hands-on, experts on SON
I was listening to a group of telco experts on a podcast the other day. As they were talking, I kept picturing the image of
Earlier in the year, we wrote a series of articles about the chasm that exists between OSS/BSS buyers and sellers (pt1, pt2, pt3, pt4, pt5, pt6). “The chasm” is
Actually, maybe a few related questions. As you’ve seen from recent articles such as this, I’m increasingly interested in the cross-over worlds of comms and
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
