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

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

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