A business website costs more than the hosting bill. The real total is six lines: hosting, a domain, premium plugin and theme licenses, email, someone's time on maintenance, and occasional development work. Hosting is usually the smallest one.
The largest line is almost always maintenance time, and it never shows up on a statement. Somebody pays for it: you, an employee whose job is something else, or a provider you hire on purpose. The cost is there either way, whether or not you can see it.
Start with the whole list, not the hosting bill
When people compare hosting, they compare the one number that is easy to compare. It's the wrong number to anchor on, because it varies the least and has the least effect on the total. A site on cheap hosting can cost a fortune to run, and a site on expensive hosting can cost almost nothing else.
Once a year, write the list down (hosting, domain, licenses, email, maintenance, development) and put a real figure next to each line, including the ones paid in hours instead of dollars. Most owners we talk to have never done this, and it usually reorders their priorities within about ten minutes.
The recurring lines: hosting, domain, email, licenses
Hosting is a monthly or annual subscription that buys a place for the files to live and a machine to serve them. On most plans, it doesn't buy anyone paying attention to what happens on that machine.
The domain is the smallest line on the list and the most dangerous one to lose track of. It renews annually, the reminder goes to whichever inbox registered it years ago, and if that inbox belonged to a former employee or an agency you no longer work with, you find out the hard way. Check who owns your domain today. It should be you, not your web person.
Email is its own category, and it's worth keeping separate from hosting. Running business email on the same server as the website is a habit from an older era. It ties together two things that should fail independently, and it usually delivers worse. Mailboxes should be a per-user line you can count on your fingers.
Licenses are the sneaky one. A WordPress site of any real complexity is running paid software: a form plugin, a booking or ecommerce extension, a premium theme, maybe a security or SEO tool. These renew annually, often at different times, often on a card nobody remembers adding. Two things go wrong. First, the total creeps up as plugins get added and never removed. Second, a license lapses without anyone noticing, updates stop arriving, and a plugin sits unpatched for months while everything appears to work fine. That gap is where most of the trouble we clean up starts.
Maintenance is the biggest line, and it has no invoice
A WordPress site needs a handful of things to keep working. Core, theme and plugin updates need applying and then checking, because occasionally an update breaks a layout or a form. Backups need verifying rather than assuming. Uptime and SSL certificates need monitoring. Someone has to notice when a plugin gets abandoned by its author, review the PHP version before the host forces it, and read the one security notice that's relevant while ignoring the four that aren't. We wrote up the full picture in what website maintenance should include.
None of that is difficult, but all of it recurs, and recurring work has a cost even when nobody bills for it. If you're doing it, put your own hourly value next to the hours. If it's a marketing manager or an office administrator, you're paying them to do something other than the job you hired them for. If nobody's doing it, you're building up risk instead of saving money, and risk gets paid in one lump sum later.
The lump sum is the part people underestimate. A site that goes down or gets defaced costs the emergency fix, the lost enquiries during the outage, and the time you spend on it instead of your actual job. That last one is usually the largest and the least recoverable.
Development work is lumpy, not monthly
Separate from maintenance is the work that changes the site: a new landing page, a redesigned services section, a rebuilt contact form, an integration with a booking system, cleaning up whatever the last person left behind. This is project work. It doesn't happen every month, and it shouldn't be baked into a monthly retainer as an all-you-can-eat promise, because that promise is either padded or can't be kept.
Budget for it as an annual allowance instead. Most small-business sites need a few pockets of development work a year, clustered around whatever the business is doing at the time. The trap is skipping it entirely for three years and then paying for a full rebuild. The numbers on that are in what a cheap redesign ends up costing.
Cheap hosting moves the cost, it doesn't remove it
Budget shared hosting is cheap on the invoice. It works because the provider does less: more sites per machine, no proactive patching, and support that reads from a script and points you back at your own plugins. The work still exists, and it lands on you.
You notice it in specific ways: updates you apply nervously on a Friday, a support ticket that takes three days and ends in "that's a plugin issue, please contact the developer," a backup you've never tested, an afternoon lost to figuring out why the contact form stopped sending. Each one is small, but added up over a year they're the most expensive line on the list, and you pay for them in attention rather than money.
That's a legitimate trade-off, and for some sites it's the right one. A brochure site that gets thirty visits a month and generates no leads doesn't need managed anything: keep it cheap, keep a backup and accept the risk. The math changes once the site brings in customers.
What it costs with us
Ours is one line, and it covers maintenance too. It's $50 a month for one site, $42 each for two to five, $36 each for six to fifteen, and $30 each for sixteen to fifty. Mailboxes are $2 a month, flat. That includes twice-daily verified off-site backups with 30-day retention, a 100 GB per-site soft limit, patching, monitoring, and same-day replies from an engineer who can actually read a stack trace. Migration onto our platform is free, and we do the moving for you.
Work outside the plan, such as a new page, an integration or a redesign, is $95 an hour, always quoted before we start. You keep paying for your own domain and your own plugin licenses, because those should belong to you, not to your host. Full detail is on the pricing page.
That's the whole model, and it won't be the lowest hosting price you find.
What isn't worth paying for
A few things get sold hard and rarely earn their cost for a small-business site. Standalone CDN subscriptions, when a well-configured server handles the traffic you get. Premium security suites layered on top of a host that already patches. Analytics tools you won't open. A separate staging environment sold as an upgrade, on a site you change twice a year.
Paying twice for maintenance is also common. If your host includes patching and backups and you also pay an agency retainer that lists patching and backups, ask each of them what they're doing. Usually one is watching the other do it.
Frequently asked questions
What is the single biggest hidden cost of running a website?
Maintenance time. Updates, backup checks, monitoring, and the occasional broken thing add up to real recurring hours, and those hours get paid by you, by an employee doing it instead of their real job, or by a provider. Only the third one appears on an invoice.
Should my email be on the same host as my website?
Usually not. Tying them together means one problem takes out both, and website-attached email tends to deliver worse than dedicated mail hosting. We charge $2 a month per mailbox as a separate line for exactly that reason.
Do I still pay for plugin licenses on a managed plan?
Yes, and you should want to. Licenses for premium plugins and themes belong in your name so you keep the software if you ever leave. We keep them updated and tell you when one has lapsed, but the account stays yours.
