Skip to main content

Effect of Fees on Your Brand

Sometimes fees above and beyond the base price of your product are a lucrative part of your business. For example, late fees, though they purportedly are exceptional and merely for recouping revenue that would otherwise be lost, are in fact a major cash cow for video rental stores.

From a narrow economic point of view, such fees are good for your business. After all, business is about making money, and the fees bring in revenue.

But the long-term impact of such fees is hard to measure and may be negative. Fees affect the long-term perceptions of your product and company. They affect the equity of your brand.

For details, see this post by Roger Dooley on the Neuromarketing blog.

Comments

Jeff said…
Great point. Unfortunately, it's often a struggle for product managers, stuck between short-term (financial) objectives and building long-term value. Actually, it's an issue for companies in general, but quite often product managers seem to get stuck in the middle, with the voice of the customer on one side and the voice of senior management on the other.

Ultimately, if you can create a fantastic customer experience and have the right margins on your "base price" product, you can have the best of both worlds.

Contrast your example of video rental late fees with Netflix, who lowered our monthly subscription by $1 after we had already committed to subscribing following our trial month. Yes, they lost $1/month in revenue, but they gained lots of goodwill, free advertising (here), and lots of that newfangled "viral marketing" that companies are going after. (Hint, the key isn't in your marketing, it's in your product!) The long-term impact on their brand from lowering the monthly fee vs. raising the monthly fee is likely huge.


Jeff
My blog: How to be a Good Product Manager

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

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing

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