[aspir]

I work for an competitor to an AWS product. We've grown rapidly over the past ~7 years in a generally competitive (lots of startups, some really old tough incumbent companies). Without revealing too much on our end, here's some lessons learned:

* AWS is bad at customer service, even for their large or premium customers. If you position yourself, and _seriously_ invest in making your company's culture rooted in exceptional customer service, that's a foothold.

* Don't compete on price. This is hard for most tech startups, as pricing is a very difficult thing to do properly, but resist the urge to drop price to compete. You'll never have the scale, the supply chain masterminds, or the financial modeling to compete with AWS on price, so position yourself as a premium or luxury offering and don't be afraid to price accordingly. If you do the first step properly (a deeply rooted culture of service) you'll be able to justify the price.

* AWS has great uptime, but often the actual operating performance of their service isn't that great, especially when you push the products beyond the 80% use case. They know that for the majority of their customer base, best-in-class performance isn't actually business critical (despite how flashy it sounds). However, there is absolutely a market for people who truly need best in class performance, or product flexibility, or some other best-in-class trait (latency, interaction design, etc.). Find who these people are, and optimize for that ruthlessly. This focus, in combination with the culture of exceptional service and positioning your brand as a premium provider, puts you into a completely different market space than AWS.

[philliphaydon]

Really? I’ve had better customer experience with AWS than Azure or GCE... Even their SDK devs are responsive, I raised a bug for the SDK for their queues and went to bed, woke up and they had published a new SDK with the fix after 7 hours of raising the ticket...

There is a lot to dislike about AWS but from my experience customer server isn’t one of them...

[electricEmu]

What was your experience like on Azure and GCE?

Azure had me on the phone within minutes of filing critical issues. Their engineering department provided updates all night.

Amazon issue resolution could be summarized as "won't fix" or "someday/maybe". Their API inconsistencies might be considered a poor developer experience [0].

It's great you like AWS. I do too for some use cases! I disagree their customer service is "better" though.

[0] http://apievangelist.com/2017/01/05/what-i-learned-crafting-...

[oliwarner]

> better customer experience with AWS than Azure or GCE

Yeah, they're all awful. A comparison might show one is better than another, but it's all a wash when you look at actually good customer service.

A good host has a phone number, you ring it, somebody answers and then they fix your problem, without pinging you around a call centre. You're in and out within 20 minutes.

For AWS (and their class) you submit a ticket and in 4-48 hours, you twiddle your thumbs while the cheapest labour available to Amazon wakes up on the other side of the planet to investigate your problem (also known as walking you through a script).

AWS-sized hosts have advantages but I put a lot of weight in scaling things back to the RackSpace, Linode and Hetzner size operations. They put so much more effort into their human interaction.

[aspir]

I dunno, that sounds pretty good honestly. The only info I have on AWS's service is testimonials, so I don't have anything concrete.

The industry we obsessively study/studied was hospitality, where service is literally the differentiator between the "pretty good" and the "absolute best in the world," and we've been pretty meticulous about iterating and building upon our service ecosystem (it's way beyond just one team at this point) like one might do with a software product. Most of our customers, from the small ones in the early days to the huge internet juggernauts we've had the privilege to work with use us as the standard to which all other vendors are measured, sometimes quite literally in a very odd way. So, I don't know if we got lucky with some stinker incumbents, or we stumbled on to something completely different, but we've got a good system in place that's built a pretty solid competitive moat.

I guess if folks on the thread are still reading and interested in replicating this at their startups, my advice is: study elite hospitality and restaurants, not tech. I'm very rarely impressed with the service ecosystem in the tech world, though it happens, but I can learn something massive every day from hospitality.

[superasn]

True their support has been quite helpful and pretty amazing. A dev reached out to me days after the issue was resolved for feedback and advice, and it wasn't a cookie cutter template. He actually wrote a 300 word letter to me, including asking for my feedback on a new feature they were working on.

I couldn't believe a company as big as AWS would seek out opinion of some guy just posting on their forum.