$150/Month to Host a $12 Website

Pull the invoice. The one that renews every month whether or not a single word on your website changed. Find the line that reads "hosting & maintenance," or "care plan," or "monthly management." Whatever it's called, it's the line I want you to decompose.

Because the raw cost of putting a small-business website on the internet in 2026 is close to zero. A static site — real HTML and CSS served from a global edge network — runs on tiers that are free for the traffic a local service business generates, and single-digit dollars if you outgrow them. The certificate that puts the padlock in the address bar is free and auto-renews. The domain is ten to twenty dollars a year, paid to a registrar, once. That's the infrastructure. That's the whole hard cost.

So when the recurring number is a hundred and fifty, decompose it into three buckets and see what's left.

Bucket one: infrastructure

This is the honest part. Servers, bandwidth, the certificate, the DNS. On a modern static stack it rounds to a rounding error. On a heavy WordPress stack it's genuinely more — a database has to run somewhere, PHP has to execute on every request, and a shared host that oversells its capacity gets slow enough that you "need" managed hosting to paper over it. Notice what happened there: the fragile architecture creates the hosting bill. The bill isn't buying you performance. It's buying you a splint for a stack that breaks under its own weight — which is why I don't build on it in the first place.

Bucket two: insurance

This is the part nobody itemizes but everyone is paying for. A WordPress install is a database, a theme, and a stack of plugins that all update on their own schedules and occasionally disagree with each other. Something in that pile will break. When it does, you want a human who can log in and fix it before you lose a day of leads. The monthly fee is, in large part, a retainer against that breakage — insurance premiums on a car that's designed to need a mechanic.

I'm not mocking the person who pays it. If your site can go down at 2 AM from an automatic update, paying someone to watch it is rational. What's not rational is never asking why the site was built to need watching.

Bucket three: air

Whatever's left after infrastructure and insurance is air. It's margin on a service that isn't being performed. The tell is simple: ask what actually shipped last month. If the answer is a plugin got updated and the site stayed up, you paid a hundred and fifty dollars for the absence of a disaster. That's not maintenance. That's a subscription to the status quo, and it renews forever.

Here's the test I'd run before your next renewal. Add up twelve months of that line. For a lot of businesses it clears eighteen hundred dollars a year, every year, indefinitely — real money that traces to no shipped work and buys down a risk a better-built site wouldn't carry. Two or three years of that number is a full custom build against the $6,000 floor I publish, except the build is an asset you actually own instead of rent you pay.

None of this means hosting should be free-as-in-nobody-does-anything. A site that's genuinely being worked on — content added, rankings watched, pages rewritten — is worth a retainer, and I charge one. The distinction is whether the number maps to work you can see. If it doesn't, the invoice is the product, and the website is the pretext.

Bring me the invoice. Genuinely — the actual line items. I'll decompose it with you: what's infrastructure, what's insurance against a stack that shouldn't be fragile, and what's air. Some of it might be fair. The exercise is finding out which part. Inquire about a project →