How to Bill Clients for Server Management (Pricing Models)

The Flat Monthly Retainer Per Site

A flat retainer charges every client the same fixed fee per site per month, regardless of how much traffic or resources it actually consumes. This is the model most agencies start with because it is the easiest to sell: "$40/month for hosting and management" fits on a single line of a proposal, and clients can budget for it without needing to understand server internals.

The weakness shows up as your client base grows unevenly. A five-page brochure site and a busy WooCommerce store both pay the same $40, but the store might need three times the CPU and RAM. Flat retainers work well in the 0-20 site range where usage is roughly homogeneous; past that, agencies typically layer in tiers or move heavy accounts to a dedicated server billed separately.

Tiered Plans Based on Resource Usage or Traffic

Tiered pricing sets three or four bands — say Starter, Growth, and Scale — priced by monthly visits, PHP-FPM memory allocation, or database size, so heavier sites pay proportionally more without you having to negotiate a custom quote for each one. This is the model most agencies graduate to once they have a mix of brochure sites and e-commerce stores on the same infrastructure.

The practical way to define tiers is to pick one or two metrics you can actually measure — monthly pageviews from analytics, or the PHP-FPM pool's peak memory from your control panel's process view — and set thresholds that map to real infrastructure cost, not guesswork. A common split is Starter (under 10k visits/month, shared pool), Growth (10k-100k, dedicated pool with higher memory limit), and Scale (100k+, isolated resources or a dedicated server).

Bundling Hosting Into a Care Plan

A care plan folds server hosting into a larger monthly retainer that also covers plugin/core updates, uptime monitoring, backups, and a support-hour allowance, so the client sees one line item instead of a hosting bill plus a maintenance invoice. This is the highest-margin model because you are charging for outcomes ("your site stays online and up to date") rather than for infrastructure, and clients rarely benchmark a bundled care plan against raw server costs the way they would a bare hosting fee.

Care plans also improve retention: a client paying $150/month for "we handle everything" is far less likely to shop around than one paying $15/month for "hosting only." When you build a care plan, itemize the components internally even if the client sees one price — hosting cost, backup storage, SSL, support hours — so you can recalculate margin as any one input changes.

The Margin Math: What You Pay vs What You Charge

Margin on server management is the gap between your per-site infrastructure cost and what you invoice the client for it, and that gap only holds up if your underlying cost per site stays flat as you add more sites to a server. A rough breakdown for a mid-size agency running WordPress sites on a shared VPS looks like this:

At roughly $4.20 in true per-site cost, a $40/month retainer clears about 89% gross margin before you account for support labor. The number that actually determines whether that margin survives growth is the control panel line — if it charges per site or per account instead of per server, it scales linearly with your client count and eats directly into the number that is supposed to be your profit.

Why Per-Site Licensing Fees Erode Margin at Scale

Per-account control panel licensing punishes exactly the growth you are trying to profit from: cPanel-style pricing charges per cPanel account, so every new client site you onboard adds a direct line item to your cost base on top of the VPS itself. At 20 sites that might be a manageable add-on; at 100 sites it can rival the cost of the server hardware, and the fee keeps climbing indefinitely as you win more clients.

Choosing Your Model and Setting It Up

Start with a flat retainer if you have fewer than 20 relatively similar sites, move to tiers once usage diverges, and layer in a care plan whenever you want to sell outcomes instead of infrastructure. Most established agencies end up running a hybrid: a care plan as the primary offer, with a tiered surcharge for sites that cross a defined traffic or resource threshold.

Whichever model you pick, calculate your true per-site cost first — VPS cost, control panel licensing, backup storage, and support time — before you set the client-facing price, and re-run that math every time your client count changes materially. The agencies that protect margin as they scale are the ones whose cost base grows in resources, not in per-site fees.