Resources > Articles

Ask the Experts: Are There Advantages to Creating Product Add-Ons Over Bundling?

Post Author
Ask the Experts: Are There Advantages to Creating Product Add-Ons Over Bundling?

There are advantages to both add-ons and bundling, depending on the circumstances.

Before you make a decision, here are some things to consider.

An add-on is when we create a new product capability and sell it as an option to another product.

An advantage of add-ons is that they are often “Will I?” products; they have no direct competition because they are options to our products. This generally implies we can charge more money for add-ons.

Another advantage of add-ons is that they present an opportunity to segment the market. Those who want the new capability will pay more for it, and those who don’t want it won’t pay.

When there are too many options, however, buyers become confused. They don’t buy because they are afraid of making a mistake.

The main advantage of bundling is that it simplifies product offerings.

Competition is another reason to bundle.

If your competition includes a capability that your product doesn’t, you could be at a competitive disadvantage, particularly with buyers who want the new feature. Buying a complete product is always easier than buying a base product and then choosing the options that are best for you. Also, pay attention to whether the price of your base product plus the option is competitive with the price of your competitor’s bundled product. If it’s not, be sure that your sales team is prepared to explain the associated value.

If you are creating a new capability for a single product, consider a hybrid of the two techniques. Instead of selling the new capability as an add-on, create two product versions: one with the new feature and one without. You now have good and better products (and of course, the intention to create a best version in the future).

Alternately, if you have a product or even a product line in which only a small number of customers will want the new capability but those customers find it very valuable, it probably makes more sense to sell it as an add-on.

Other characteristics also help drive this decision. For example, how different is the new capability? How big is the segment that wants it? What is the distribution of willingness to pay for that option?

There are a lot of nuances to consider before choosing between product add-ons and bundling. It’s not an easy choice to make; consider your options and your goals carefully.

Author

Author:

Other Resources in this Series

Most Recent

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.
Article

Benefits of Bundle Pricing

Bundle pricing is simply a strategy where services or products are packaged together for one (often reduced) price rather than priced separately. This article covers some benefits of bundle pricing followed by a system for getting started.
Article

A Quick Guide to Value-Based Pricing

Value-based pricing begins with knowing the customer’s willingness to pay based on the perceived value of your product. You can charge less than a customer’s willingness to pay, and they feel like they’ve received an

OTHER ArticleS

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.