I went straight into customer segmentation which felt right but I probably spent too long there.
Start by framing the problem as a classic competitive displacement strategy: understand why energy clients choose AWS today, identify unmet needs in HPC workloads, and build a differentiated value proposition that leverages Azure's unique strengths. Then outline a phased GTM plan that includes technical proof points, migration support, and ecosystem partnerships to reduce switching costs.
Pro tip: Acknowledge that energy clients are risk-averse and have long sales cycles; emphasize that a successful strategy must include a compelling business case (TCO, performance, compliance) and a migration path that minimizes disruption, rather than just feature comparisons.
Identify the specific energy sub-sectors (e.g., oil & gas, renewables, utilities) and their HPC workloads (seismic imaging, reservoir simulation, weather modeling). Research their current AWS usage, pain points, and decision criteria.
Map AWS's HPC strengths and weaknesses against Azure's offerings (e.g., InfiniBand, NVIDIA GPUs, Azure CycleCloud, proximity to energy hubs). Define unique value props such as hybrid cloud, compliance, or cost advantages.
Craft a clear, quantifiable value proposition tailored to each segment, highlighting performance benchmarks, TCO savings, and risk mitigation. Create messaging that addresses switching costs and migration concerns.
Outline a multi-touch GTM strategy: pilot programs with key clients, technical workshops, proof-of-concepts, and migration accelerators. Include partnerships with ISVs and system integrators to ease transition.
Establish KPIs such as pipeline growth, win rate, migration time, and customer satisfaction. Use feedback loops to refine the strategy and scale successful tactics.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.