DEV Community

Cover image for The Hosting Decision That Determines Whether a Client Ever Calls You Angry
аЛЕКС ЛИР
аЛЕКС ЛИР

Posted on

The Hosting Decision That Determines Whether a Client Ever Calls You Angry

I run a small WordPress studio — webmaster.co.ua, 18 years, 235+ projects. If I had to isolate the single decision that predicts how many angry calls I get post-launch, it's not the code, the design, or the CMS. It's which hosting plan the client picked.

Cheap shared hosting generates support tickets that look like your fault. A site that's technically well-built on a $3/month shared plan still goes down during traffic spikes, still runs slow on shared CPU, still gets flagged when a neighboring site on the same server gets blacklisted. None of that is your code failing. All of it reads to the client as "the website you built is broken."

Clients choose hosting on price, because nobody explains what the price is trading away. Left alone, most small-business clients pick the cheapest hosting option, because from their side, hosting is an undifferentiated commodity line item. It isn't — it's the difference between a site that survives a local news mention and one that falls over from it. Explaining this once at project start costs five minutes and prevents most of the "your website is down" calls that come six months later.

We stopped treating hosting recommendation as optional. It's not in most contracts, and it's easy to let clients self-select their host to keep the sales conversation simple. But vetting hosting has quietly become part of the actual deliverable for us, even when it's not billed as one — because an outage on bad hosting damages the same trust that a bug in our own code would.

The client's mental model is "is the website working," not "whose responsibility is this." When something breaks, they don't parse out hosting versus code versus DNS versus their own domain renewal lapsing. They just know something they paid for stopped working. Being the person who explains and fixes it — regardless of whose layer it's actually in — is what keeps the retainer, technically at fault or not.

If you build sites and hand off hosting decisions entirely to clients, it's worth revisiting — the support burden that follows is often a hosting problem wearing a "the website is broken" costume.

Top comments (0)