Analyzing the Market-Facing Portfolio

Strategic intent: Make the upper layers of the Portfolio Map (Customers, Needs, GTM, Value Propositions) coherent. Find gaps, eliminate overlaps, fix maturity-GTM mismatches, and frame the offering through the horizontal-vertical taxonomy and the ILC innovation cycle.

#Overview

This is the first of two dual-focus analyses on the Portfolio Map. While Organizational Elements Analysis looks inward at the org, this technique looks outward at the market: are we covering the customer needs we should? Is our product taxonomy coherent (horizontals + verticals + bundles)? Is GTM aligned with offering maturity?

The Boundaryless framing introduces two key conceptual lenses (from Horizontals, Verticals, and the ILC Model):

• The horizontal-vertical taxonomy of B2B offerings (and how bundles emerge across verticals)
• The ILC Model (Wardley's Innovate → Leverage → Componentize cycle) as the dynamic that drives platform-portfolio companies forward

The output is a refined product taxonomy, a list of bundling opportunities, GTM realignment recommendations, and a set of market-facing quick wins.

#When to use it

• After Portfolio Data Collection has produced a validated preliminary map
• Can run in parallel with Organizational Elements Analysis; synthesis comes after both
• When the team suspects offering overlaps, missing market needs, or mismatched GTM
• When refreshing the product taxonomy after acquisitions or organic growth

#Composition

This technique works on the upper 4 layers of the Portfolio Map Canvas.

1. #1. Position customer needs in the 2×2

   Place each identified customer need into the 2×2:

   • Horizontal axis — specific/tailored ← → standardized/commoditized
   • Vertical axis — strategic differentiation ↑ ↓ operational

   The 4 quadrants:

   • Strategic + Specific → differentiation needs (high-touch, custom)
   • Strategic + Standardized → competition/scale needs
   • Operational + Specific → enablement needs (custom internal tooling)
   • Operational + Standardized → efficiency/compliance needs

   Empty quadrants are signals: a strategic gap, a competitive blind spot, or a deliberate non-play. Also tag needs along the Operate / Innovate / Integrate / Optimize axis — different operating models serve different segments differently.

2. #2. Refine the product taxonomy: horizontals, verticals, bundles

   Apply the horizontal-vertical taxonomy:

   • Horizontals — enabling technology platforms with deliberate abstraction from specific use cases. Long cycles, significant up-front investment in architecture and design, low fluctuation to specific customer needs. Pay dividends through reduced complexity and consistent baseline performance across the portfolio. Examples: avionics platforms, lab-tech infrastructure, design systems, OS/firmware foundations.
   • Verticals — units (often Micro-Enterprises or Product Units) that perform productization for specific customer segments. Strong system-integration capabilities. Often formalized organizationally. Respond to typical needs of a more specific segment.
   • Bundles — integrations across verticals, sometimes across third-party products too, that respond to specific customer needs. "This customer-facing bundling and integration occur at varying levels of depth" — from HubSpot-style self-service activation to heavy enterprise sales with system integration work.

   Then map each offering to its actual maturity stage (one-off / bespoke / productized / API/module).

   Look for:

   • Overlapping verticals — multiple things solving the same need (candidates for merge)
   • Duplicated effort across MEs — same horizontal capability re-built (candidate for SSP consolidation)
   • Bundling opportunities — natural groupings users would pay for as a package
   • Maturity drift — offerings stuck at one-off when they should evolve

3. #3. Align GTM with offering maturity

   Each maturity stage matches a GTM motion:

   Maturity	Best GTM motion
   One-off	Consulting / bespoke sales
   Bespoke	Solution selling
   Productized	Product sales
   API/module	Self-service / API / marketplace

   Find mismatches: a productized offering being sold through bespoke consulting (rescue the GTM, or demote the maturity). Bespoke consulting being marketed as self-service (the team will overpromise and underdeliver).

   Also identify integration depth per bundle: self-service activation (HubSpot pattern) vs heavy enterprise sales with system integration. The depth determines GTM team composition.

4. #4. Apply the ILC innovation cycle

   The ILC Model (Innovate → Leverage → Componentize, formalized by Simon Wardley) is the dynamic that drives platform-portfolio companies forward.

   For each offering, ask:

   • Innovate — was this created to address an emerging customer need? Where in the lifecycle is it?
   • Leverage — has it been deployed across multiple products and segments to maximize value extraction?
   • Componentize — has the mature capability been modularized into a reusable platform service consumable by internal teams and external partners?

   Amazon's playbook is the textbook: AWS componentized internal infrastructure; Amazon Basics componentized top-performing third-party products. The strategic move: modularize horizontals → expose to ecosystem → capture emerging value → re-innovate on top of new modules.

5. #5. Generate quick wins and strategic moves

   Quick wins (3 months):

   • Merge two overlapping verticals under one name
   • Retire a low-maturity offering
   • Reposition a misaligned GTM
   • Create a bundle from existing offerings

   Strategic moves (6–24 months):

   • Productize a bespoke vertical
   • Componentize a productized horizontal into APIs (ILC step)
   • Enter an empty needs quadrant
   • Acquire / build a missing horizontal capability
   • Open a horizontal to external partners (componentize externally)

#Inputs

• Required: validated preliminary Portfolio Map
• Required: stakeholder interview transcripts (for grounding)
• Recommended: revenue / margin data per offering for prioritization
• Recommended: competitor mapping (especially in horizontal categories)

#Outputs

• Customer Needs 2×2 populated, with empty quadrants explicitly noted
• Horizontal-vertical-bundle taxonomy with each offering classified
• Maturity assessment per offering (one-off / bespoke / productized / API)
• GTM alignment matrix with mismatches highlighted
• ILC stage assessment per offering
• List of quick wins (3-month horizon, 5–10 items)
• List of strategic moves (6–24 months, 3–5 items)
• Bundling opportunities identified

#Process heuristics

• Maturity is a spectrum, not a binary — most offerings are between stages
• Aspirational placement is dishonest — place by today's reality
• GTM mismatches usually indicate a maturity classification problem — fix the maturity diagnosis first
• Quick wins build credibility — execute them before tackling strategic moves
• Bundle opportunities reveal taxonomy issues — if two offerings naturally bundle, they may already be one offering
• Apply the ILC cycle deliberately — most organizations innovate but never componentize, leaving value on the table

#Validation criteria

• All 4 quadrants of Customer Needs explicitly addressed (covered or noted as gap)
• Every offering classified as horizontal / vertical / bundle
• Every offering has both a maturity stage and a GTM alignment
• Mismatches between maturity and GTM are flagged
• ILC stage identified for at least core offerings
• At least 3 quick wins identified
• At least 3 strategic moves articulated
• Bundling opportunities listed (or "none found, here's why")

#Common mistakes

• Aspirational maturity placement — "we're productizing X" doesn't make X productized
• Ignoring empty quadrants — they may be the biggest opportunities or biggest risks
• Quick wins that aren't quick — if it takes 6 months and political negotiation, it's not a quick win
• Bundling without taxonomy clarity — bundling overlapping offerings just makes the overlap bigger
• Innovating without leveraging or componentizing — the I in ILC is just one step; missing L and C leaves value uncaptured
• Treating horizontals as "nice-to-have" — they're the differentiator that makes long-term portfolio cohesion possible

#Used in pipelines

• Portfolio Mapping — as Phase 2 (dual focus, market side)

#Connections

• Requires: Portfolio Data Collection
• Pairs with: Organizational Elements Analysis — same map, opposite side
• Feeds: Portfolio Strategy Implementation

#Related reading

• Horizontals, Verticals, and the ILC Model — the taxonomy and innovation-cycle framework
• The Portfolio Map Canvas Application Guide v0.1 — full long-form narrative in Legacy Portfolio Map