You need an Alexa+ strategy

I've been on two different emergency Teams calls this evening discussing the launch of Alexa+ and the immediate implications with some clients.

Alexa and Amazon has been on the radar for the longest time. It's been sat in many of my slide decks and strategy papers languishing in the corner. We've had lots of hints (private whispers) and various updates from Amazon for quite a while but today is the first time we've formally seen what they've brought to market.

It's quite possible that the 600 million installed base of Alexas are already forgotten. It's quite possible it goes nowhere.

But, equally, it's possible Alexa+ catches on, quickly – and with the scale of Amazon behind it – and if Amazon properly aligns behind it, it could well be a highly compelling platform gateway for end customers.

Which means that you need an Alexa+ strategy.

I wrote a brief overview earlier so do check that out.

For now, my recommendation is to begin wargaming what your end-user services could look like if Alexa+ catches on, especially if you have any activities in the United States and other key markets for Amazon. For example, what do things look like if 5% of your traffic is originating via Alexa+?

I'd also recommend getting your developers to start messing about with the various SDKs and capabilities already available (if they haven't already been doing so). This might be a good place to start – but, as you'd expect, Amazon knows what it's doing when it comes to help and enable developers.

Exciting times!