View Project
Qobuz · 2026 · Product Manager

Search Infrastructure Migration

A structured consulting engagement to help a global music streaming platform evaluate whether to migrate from its current SaaS search provider to a self managed infrastructure on AWS, with a focus on scalability, search quality, and long term cost reduction.

Product StrategySearchVendor EvaluationTCO ModellingAWS MAP
Search Infrastructure Migration
Overview
ClientQobuz
RoleProduct Manager
Date2026
Scope of workProduct Strategy, Search, Vendor Evaluation, TCO Modelling, AWS MAP

The challenge.

The client was running their search on a third party SaaS provider that had served them well early on, but was no longer a viable long term fit. A hard technical ceiling was approaching, operational autonomy over search relevance was limited, and costs were scaling poorly relative to catalogue growth.

The question was not just whether to migrate, but to what, at what cost, and in what sequence.

My role was to lead the engagement end to end: structure the discovery process, facilitate the client workshops, frame the vendor evaluation, and produce a recommendation the client could take to leadership.

Process

Process.

01
DiscoveryMapped the current search experience, identified user facing pain points, and documented the existing analytics and measurement gaps. Established the hypotheses that would drive the evaluation.
02
Architecture and data reviewAudited the current index structure, ETL pipeline, regional configuration, and API integration layer. Translated technical constraints into product and migration risks.
03
Requirements structuringRan a structured MoSCoW exercise with the client team to validate 35+ requirements across 7 domains. This gave the evaluation a shared, client owned scoring framework rather than a consultant's opinion.
04
Vendor evaluation and TCO modellingScored three candidate engines against the validated requirements. Produced a 3 year total cost of ownership comparison with two migration scenarios, incorporating real contractual cost data and cloud programme funding.
05
Recommendation and packagingProduced the final recommendation document in the client's language, with a primary recommendation, a conditional Phase 2 option, and a clear rationale for what was not retained. Coordinated AWS cloud programme funding to make the migration path financially viable.
Deliverables

Deliverables.

D1: UX and product discovery report
D2: Architecture and data audit
D3: API and IR review
D4: 35 requirement RFI with MoSCoW scoring
D5: 3 vendor evaluation report
D6: 3 year TCO comparison
D7: Migration scenario plans
D8: Search quality metrics framework
D9: Final recommendation document
Reflection

How I approached it.

The core challenge was making a technically complex decision legible to a leadership audience. The MoSCoW framework was the key tool: it meant the recommendation was grounded in requirements the client had validated themselves, not in our preferences as consultants.

I also treated the AWS cloud programme coordination as a product output, not an administrative task. Aligning the technical recommendation with available migration funding meant the client had a financially defensible path, not just a technically correct one. That kind of alignment between what is right and what is viable is where product thinking adds the most value in a consulting context.

The full assessment phase was funded through an AWS cloud programme, at zero cost to the client. The recommended migration path was structured to qualify for additional migration credits, giving the final recommendation both technical and commercial grounding.

Skills exercised
Workshop facilitationMoSCoW requirements structuringVendor evaluationTCO modellingTechnical writingStakeholder managementAWS MAP coordinationRisk identification

All Projects

Back to work