TL;DR
- Rationalised an 8-product enterprise portfolio by retiring low-margin products, freeing meaningful capacity and redirecting investment to growth-driving products
- Applied a keep/grow/wind-down framework that assessed each product on strategic fit, margin contribution and opportunity cost of continued investment
- Portfolio rationalisation funded the acquisitions, capability builds and platform investments that generated the portfolio's strongest growth outcomes
The Problem
Product portfolios at established companies grow through three mechanisms: organic development (someone had an idea and built it), acquisition (the company bought it), and inertia (nobody decided to retire it, so it persists). Over time, this creates a portfolio where some products are strategic assets, some are legacy obligations and some exist primarily because stopping them feels harder than continuing.
Cotality's portfolio accumulated through all three mechanisms. It included flagship products with strong market positions, growth products with expanding addressable markets, acquired products requiring integration decisions, and specialised products serving niche segments. Engineering resources were finite. Every product on the active roster consumed maintenance, infrastructure, support and product management attention.
The fundamental question was: across this portfolio, where should the next dollar of investment go to maximise long-term value? Answering that required being honest about which products weren't earning their keep.
The Approach
I assessed each product across three dimensions, applying the prioritisation frameworks I use across all portfolio decisions: strategic fit (does this product advance where the company needs to go), margin contribution (does this product generate healthy returns relative to its cost-to-serve), and opportunity cost (what would the resources currently allocated to this product deliver if redirected elsewhere).
Products that scored low across all three dimensions were candidates for retirement. Products that scored high on margin but low on strategic fit were candidates for maintenance mode (collect revenue, minimise investment). Products that scored high on strategic fit were candidates for growth investment.
Key Decisions
1. Retire Low-Margin Products to Fund Growth
Several products in the portfolio generated modest revenue but consumed disproportionate resources. Legacy architectures required specialised engineering knowledge. Support volumes were high relative to revenue. Feature requests were infrequent, signalling a stable but static customer base with limited growth potential.
Retiring these products freed meaningful capacity across the portfolio, redirected to growth initiatives: the platform modernisation of RP Data, the integration of Rita and Plezzel, and the establishment of new capabilities like lead generation funnels and AI features.
2. Distinguish Between Revenue and Strategic Value
Some products generated reliable revenue but created no strategic leverage. They didn't feed other products. They didn't serve as data sources. They didn't create customer relationships that could be expanded. They were standalone revenue streams with no compounding potential.
Contrast this with OnTheHouse, which generated minimal direct revenue but was one of Australia's highest-traffic property portals, creating the consumer audience that powered lead generation funnels, which in turn connected to agent workflows and advertising products. OnTheHouse's strategic value far exceeded its P&L contribution. Portfolio decisions that optimised purely for margin would have underinvested in OnTheHouse and overinvested in standalone products with higher margins but no ecosystem leverage.
3. Portfolio-as-Funnel Thinking
The most important framing shift was viewing the portfolio not as a collection of independent products but as a connected system. Consumer traffic (OnTheHouse) fed lead generation (give-to-get funnels). Lead generation fed agent workflows (Rita, 2-way SMS prospecting). Agent workflows fed digital advertising (Plezzel). Advertising revenue funded consumer traffic acquisition.
This funnel view made rationalisation decisions clearer. A product that appeared marginal in isolation might be critical as a connection point. Conversely, a product that looked healthy on its own P&L might be consuming resources that would generate more value invested in strengthening a funnel connection.
4. M&A Integration as Portfolio Rationalisation
Rita and Plezzel were each acquired and required integration decisions that were, fundamentally, portfolio rationalisation questions. Should the acquired product maintain its standalone roadmap? Should it be folded into an existing product? Should its technology be rebuilt?
For Rita, I took full ownership following a leadership transition, learning the AI models, SMS orchestration, agent workflows and unit economics deeply enough to make build-versus-maintain decisions. Rita achieved significant growth in users and revenue under this ownership because the investment was directed by portfolio-level strategy, not the original product's momentum.
For Plezzel, the answer was a complete replatform. The legacy architecture couldn't scale, and iterating on it would have consumed engineering resources without closing the gap. The rebuilt Plezzel achieved substantial market share growth. Both decisions were driven by where each product sat in the portfolio funnel, not by product-level optimisation in isolation.
5. Protect Revenue During Rationalisation
Killing products has a revenue consequence. Even low-margin products generate revenue that appears on the P&L. The rationalisation process included migration planning for customers of retired products, communication strategies that maintained client trust and financial modelling that showed the net impact after reinvestment of freed resources.
The discipline was patience. Portfolio rationalisation generates costs in the near term (migration effort, potential revenue loss) and benefits in the medium term (freed capacity, focused investment, growth from reinvestment). Securing executive sponsorship required modelling the full trajectory, not just the immediate impact.
Results
- Freed meaningful capacity across enterprise portfolio through product retirements
- Freed engineering and product management capacity redirected to growth initiatives
- OnTheHouse grown 25% organically into one of Australia's highest-traffic property portals (funded by redirected investment)
- Rita integrated following a leadership transition, significant growth in users and revenue
- Plezzel replatformed, substantial market share growth
- Lead generation funnels created from zero (funded by portfolio rationalisation)
- Portfolio-as-funnel strategy enabled connected growth across consumer, lead gen, agent workflow and advertising products
Tech Stack
Cotality (CoreLogic) product portfolio, enterprise-scale P&L, 8 products (RP Data, OnTheHouse, PropertyHub, ValConnect, Cordell Connect, Rita, Plezzel, GoVal/ValAssist), portfolio assessment framework, M&A integration, Tier 1 enterprise relationships, GTM/SEO/CRO as portfolio disciplines