Product Portfolio Rationalization: The Revenue That Appears When You Cut Complexity

A 2022 Bain analysis found that companies reducing active SKU count by 30% or more saw gross margin improve 3 to 7 percentage points over 18 months. For a $50M revenue business, that's $1.5M to $3.5M in margin recovered without a single new customer. The mechanism is straightforward: fewer products mean lower development and maintenance costs, lower support burden, and a pricing architecture buyers can actually navigate.

What You're Paying For It

The full cost of a portfolio SKU includes not just production cost but also the sales friction it creates and the engineering attention it consumes. A sales team quoting from a 200-SKU catalog is slower and less confident than one quoting from 20. A customer evaluating eight overlapping tiers is more confused, not more informed. Portfolio complexity rarely appears on a single budget line but shows up in every commercial interaction.

The Operating Play

Step 1: Audit every product against contribution margin and sales velocity

Build a two-variable matrix: contribution margin (revenue minus all costs to serve this product, including support, maintenance, and customer success) and sales velocity (number of times this product was sold or renewed in the past 12 months). Products in the high-margin, high-velocity quadrant are your core. Products in the low-margin, low-velocity quadrant are your retirement candidates. Products in the other two quadrants need a specific decision: reprice, reposition, or retire.

Step 2: Identify overlap and consolidation opportunities

When two companies merge, their combined product catalog almost always contains overlapping products that serve the same customer need with different names and slightly different feature sets. Map every product in your catalog to the customer problem it solves. Products that solve the same problem are consolidation candidates. The consolidation decision should be driven by which version has the better margin profile and the stronger customer feedback, not by which version came from which predecessor company.

Step 3: Move from customization to standardized configurations

A SaaS company that offers 40 custom configurations of the same underlying product has effectively created 40 products. Each custom configuration requires its own support documentation, its own renewal process, and its own implementation playbook. Replace custom configurations with standardized tiers that have modular add-ons. The modular approach gives buyers flexibility without creating internal complexity. Customers who currently require custom configurations are almost always served by two or three standard configurations with optional additions.

Step 4: Build retirement plans with customer migration paths

Retiring a product without a migration plan creates churn and relationship damage. For each product scheduled for retirement, map the customer base and identify the appropriate alternative product for each customer. Communicate the retirement with enough lead time for customers to plan, a clear explanation of the alternative, and an incentive (pricing protection, dedicated migration support) for customers who move proactively. Hardware manufacturers that have successfully rationalized overlapping product lines consistently cite advance notice and migration support as the two factors that protected retention.

Step 5: Use rationalization to reset pricing architecture

Portfolio simplification creates an opportunity to rebuild pricing architecture around clear value differentiation rather than historical accident. When you've consolidated overlapping products and retired low-value SKUs, the remaining catalog should be priced against the value each product delivers, not against the cost of building it. Conduct a willingness-to-pay assessment for your core products as part of the rationalization process. The data often reveals underpricing in the products that customers value most.

The Hidden Failure

A B2B software company at $52M annual recurring revenue (ARR) had grown through three acquisitions over five years. The combined product catalog contained 47 SKUs across six product lines. Sales reps spent an average of 4.5 hours per week navigating internal product documentation to answer customer questions. The win rate on competitive deals was 27%, partly because competitors had cleaner, easier-to-understand packaging.

Before: $52M ARR, 47 SKUs, 4.5 hours per week per rep on catalog navigation, 27% competitive win rate.

The company ran a rationalization program over four months: eliminated 19 SKUs with low velocity and negative contribution margin, consolidated six overlapping products into two, and rebuilt the pricing architecture around three clear tiers with two optional add-ons. Sales enablement was rewritten from scratch using the simplified catalog.

After 12 months: competitive win rate moved from 27% to 38%. Average sales cycle shortened by 14 days. Gross margin improved by 4.2 percentage points as the engineering and support teams refocused on the core product lines.

Start Here This Week

Pull a report of every product or SKU your company sold in the past 12 months. Count how many had fewer than five transactions in that period. Those are your first-pass retirement candidates. Calculate the full cost to serve each one including support tickets, engineering maintenance, and sales time. The business case for rationalization is almost always stronger than leadership expects.

For a full portfolio and product assessment, take the FintastIQ product assessment.