Situation
A large automotive parts retailer was preparing a new platform and wanted to understand competitor activity before defining its own architecture.
The objective was not simply to reproduce what market leaders already had.
It was to find advantages that could be embedded into the new system while established competitors remained constrained by legacy architectures.
What We Found
Large competitors had enormous existing catalogues and established systems.
Competing with them by simply replicating:
- their category structures;
- their search patterns;
- their homepages;
- their product cards;
would create a permanent catch-up problem.
Instead, the opportunity lay in structural asymmetry.
Decision 1 – A Customer-Oriented Catalogue
A catalogue structure was created around customer logic rather than the more conventional structures used by competitors.
That gives the customer an easier route toward the required part without forcing them to understand internal catalogue logic.
Decision 2 – AI-Assisted Product Enrichment
The imported source catalogue contained only a limited number of attributes.
Instead of accepting poor product cards as an unavoidable consequence of poor source data, a process was designed where AI could:
- identify available information about the product;
- collect additional attributes;
- structure them;
- subject them to verification;
- create substantially richer product cards.
This is a very modern case element.
Important wording:
AI was not used to invent product information. It was used to expand discovery and structuring before verification.
That protects credibility.
Decision 3 – Search as the Primary Homepage Function
Competitors typically used the homepage as:
- promotional surface;
- catalogue gateway;
- category listing.
The new architecture instead placed complex product discovery at the centre.
A large intelligent search interface was designed as the dominant homepage action.
It could support:
- contextual recommendations;
- guided search;
- immediate vehicle configuration;
- storing 1-3 vehicle configurations;
- searching for a specific part against those vehicles.
In other words:
The homepage was designed around the customer’s hardest task, not around the company’s desire to display categories.
That is fantastic Growth Architecture logic.
Decision 4 – Trust Infrastructure
Basic pages addressing service reliability and trust were introduced because competitor analysis showed that this question was inadequately addressed across the niche.
Again, differentiation did not require inventing a revolutionary feature.
It required noticing an important customer concern that competitors treated as secondary.
Result
The strongest long-term observation:
the key structural solutions have still not been replicated by competitors because doing so would require significant reworking of their existing architectures.
That’s rare evidence of defensibility.
What We Learned
Do not attack scale with less scale. Attack rigidity with better architecture.
And:
A new entrant can turn the absence of legacy constraints into a competitive asset.
Frameworks: Competitive Gap Map + Demand Map + Growth Architecture Map