But it’s not zero revenue. If you’re asking Alexa to play something on Amazon’s music app, they’re getting revenue from your music subscription. They just need to understand where the revenue is coming from and allocate it accordingly. For setting a timer, yeah, there’s no revenue, but people are also unlikely to pay for it, so maybe they could cut out that functionality.
Pretty much the only thing I use my Alexas for is timers (for cooking) and the weather.
You're right that I wouldn't pay for just that functionality directly, but I pay for Prime, and spend a fair chunk on AWS every month. And if amazon abandons Alexa then I'll just move everything to another ecosystem.
> if amazon abandons Alexa then I'll just move everything to another ecosystem.
Why? I'm not an Alexa user, but I am a Prime and AWS user. I don't understand how having a voice interface for weather reports impacts your decision for cloud computing or package delivery. Additionally, what other ecosystem would you move to? Google or Microsoft because they offer both voice interfaces and cloud computing? Why does that impact Prime?
I really don't see how these three things are linked in your mind. I could see some link if you used AWS to provide custom Alexa services, or used Alexa to play Prime content (music, audio books) but you specifically said you don't use Alexa for anything other than two really generic use cases.