Sometimes a SaaS splits up their offerings into different products, each with a different pricing model. While making things a bit more complicated for customers, being able to have multiple products allows SaaS companies to tailor specific offerings for specific personas that are not interested in the features provided in the other parts of the business.
When a business sells multiple products, each product is now able to target a specific market segment directly; for example, Atlassian is able to target a wide range of personas, developers with BitBucket, Project Managers with Jira.
A customer looking for a specific product is in a perfect position to be upsold on additional offerings in the form of a discounted bundle. Companies may even create soft-dependencies between products where products integrate very closely together to unlock new functionality.
If a company tries to enter a new market with a new product, they will often find it is very difficult to gain a foothold in the already established market where competitors have been for a long time. It takes a lot of resources to enter this new market, and there if the product is not executed properly, they risk failure.
The difficulty involved with offering multiple products is especially true for smaller stage companies. These companies frequently do not have the resources needed to manage multiple products, as they often require entire teams dedicated to managing them.
Companies could use multiple products if they meet any of the following criteria:
In Stripe, there is already a product construct. To model this billing strategy just map each product you want to sell to a Stripe product.
In Stripe, there is already a product construct. To model this billing strategy just map each product you want to sell to a Stripe product.
