What WordPress Agencies Get Wrong About Hosting — And What to Use Instead

Where These Lessons Come From

Kinsta recently published something I didn't expect to find genuinely useful: a free series of candid video interviews with four WordPress agency founders — Fixel, Pronto, Built Mighty, and 40Q — talking honestly about what worked as they scaled, what didn't, and what they'd do differently.

No polished playbook. No success theatre. Just four people who've been through it talking straight. You can watch the full series free here — I'll reference specific moments from it below.

Reading through it with 18 years of web hosting experience behind me, I kept seeing the same thread underneath the hiring stories and pricing regrets: the agencies that scaled well had sorted their infrastructure early. The ones that struggled were still firefighting hosting when they should have been winning clients.

Here are the hosting mistakes I see WordPress agencies make at every growth stage.

Mistake 1: Growing the Team Before Growing the Infrastructure

One of the most striking moments in the Kinsta series comes from a founder who describes how growth felt like success — right up until he stopped recognising his own team. The agency had scaled headcount fast without building the systems to support it. Everything became reactive. Client work suffered.

The hosting equivalent of this is something I've watched happen repeatedly. An agency takes on three new clients in a quarter, the developer spins up new sites quickly on whatever host they're already using, and nobody stops to ask whether that host can actually handle the load. It works fine at first. Then a client site goes down during a product launch. Or a shared server gets hammered by someone else's traffic spike and takes three client sites with it.

Infrastructure decisions made under growth pressure are almost always the wrong ones. The time to evaluate your hosting stack is before you need to scale it, not during. For agencies managing multiple WordPress client sites, Kinsta's enterprise-grade hosting infrastructure — with isolated containers per site and a client management dashboard that lets you hand off access without sharing credentials — is designed specifically for this growth phase.

See Kinsta for Agencies →

Mistake 2: Underpricing Hosting in Client Proposals

The Kinsta series has a blunt segment on pricing fear — one founder describes knowing for years that they should charge more, but holding back because of what a client might say. What finally changed things was running the actual numbers on what underpriced work was costing them in time, stress, and bad-fit client relationships.

Hosting is where this plays out in a specific, avoidable way. Many agencies either absorb hosting costs themselves, resell at cost to look competitive, or quote the cheapest option to keep proposal numbers down. What they're actually doing is taking on full infrastructure responsibility — uptime, backups, security, support escalations — without pricing for it.

A managed hosting plan at $35–$115/month per site, billed to the client at a modest margin, covers your costs and gives you a product that won't generate 2am support calls. More importantly: when you host client sites on a platform with a real SLA, real performance guarantees, and a support team that actually knows WordPress, you have something concrete to point to when justifying your retainer. Hosting becomes a value-add, not a line item you're embarrassed about.

Kinsta's pricing includes free migrations, staging environments, automatic backups, and WordPress-specialised support. For most agencies, that's worth far more than the delta between Kinsta and whatever budget shared host they're currently reselling.

See Kinsta Plans and Pricing →

Mistake 3: Saying Yes to Every Client Regardless of Their Infrastructure Needs

Several founders in the Kinsta series talk about the value of learning to say no — to bad-fit projects, out-of-scope requests, and clients who aren't ready to move. One agency built a simple three-part test for every new project. When all three criteria line up, they go for it. When they don't, walking away gets easier.

From a hosting perspective, the equivalent mistake is treating every client site the same. A five-page brochure site for a local business has completely different infrastructure needs from a WooCommerce store processing 300 orders a day. Putting both on the same hosting plan is either overpaying for the small site or dangerously under-provisioning for the large one.

Agencies that scale without chaos tend to run a tiered approach: a flexible entry-level option for simpler client sites, and Kinsta for any client where site performance directly affects their revenue. WooCommerce stores, membership sites, high-traffic blogs — these are the sites where Kinsta's optimised server environment, full-page caching, and CDN actually move the needle on conversions, not just load times. Recommending the right host for each client is part of the service. It's also what prevents the 2am call when Black Friday traffic takes the site down.

Mistake 4: No Migration Plan When a Client Outgrows Their Host

One insight that runs through several of the Kinsta founder interviews: the agencies with the most stable recurring revenue weren't constantly finding new clients. They were deepening relationships with existing ones. A client who starts with a basic site becomes a retainer client, then a larger infrastructure client, then a referral source.

That relationship breaks the moment you're the agency that recommended the host that failed. I've seen it happen. A WooCommerce store hits a traffic spike — sale event, press mention, email blast — and the host can't handle it. The site goes down. The client blames the agency, not the host, because you're the expert they trusted.

The fix is to have a migration plan before you need one. Know which host you're moving a client to when their current setup stops working, what breaks during migration (redirects, email, DNS TTL), and how long it takes. Kinsta's free migration service handles the technical lift and reduces the friction substantially — but the plan needs to exist before the emergency call comes in, not after.

The Kinsta Agency Growth Insights Series — Worth Your Time

The reason I referenced the Kinsta series throughout this piece is that it's one of the more honest pieces of agency content I've come across. Four founders talking candidly about the calls they got wrong — overhiring, underpricing, saying yes to bad-fit clients, waiting too long to niche down — without the polish that usually sanitises this kind of thing into uselessness.

The sections on pricing fear, finding a niche accidentally, and what actually drives long-term referrals are particularly worth watching. It's free to access, organised by topic, and structured so you can watch the segments that are relevant to where your agency is right now.

Watch the Kinsta Agency Growth Insights series free →

If you're at the stage where you're also evaluating whether Kinsta is the right hosting stack for your agency clients, our full Kinsta review and Kinsta vs Rocket.net comparison cover the infrastructure details in depth.

FBWH earns a commission if you sign up to Kinsta through links on this page. This doesn't affect our recommendations — we've covered Kinsta extensively and recommend them independently of this campaign.