Agencies rarely churn off a management tool because it stopped working. They churn because the invoice quietly tripled while their site count grew. That is the structural problem with per-site and per-feature pricing: the tool's price scales with your success, not with its costs.
Let's do the arithmetic properly. All prices below are the public list prices as of August 2026; check the vendors' pricing pages for current figures, and email us corrections at hello@wpclienthub.com if anything has moved.
The four pricing models on the market
- Per-site, all-inclusive (WP Umbrella). €1.99 per site per month for the core product — clean and transparent, but linear. Optional add-ons (security scanning, hourly backups) are priced per site too, so an "all-in" site can carry several line items.
- Per-site, per-feature (ManageWP). A free core with paid add-ons in the $1–2 per site per month range — backups here, uptime there, white-label reports somewhere else. Bundles exist, but agencies routinely report ~$150/month at the 100-site mark once the add-ons they actually need are on.
- Flat, self-hosted (MainWP). Roughly $199/year for unlimited sites — by far the cheapest sticker at scale. The catch is that you are the SaaS: you host, secure, update, and back up the dashboard server itself, and that time isn't free.
- Flat subscription with a bundle (WPMU DEV). Around $10/month manages unlimited sites, but the product is one arm of a hosting-and-plugins bundle, and the stickiest features (like 0%-fee client billing) sit on higher tiers.
The worked example: one agency, four sizes
Take a typical care-plan agency and price the same job — updates, backups, uptime, security scanning, white-label reports — at four agency sizes. For the per-site tools we assume the add-ons a care plan genuinely needs.
| Monthly cost | 10 sites | 25 sites | 50 sites | 100 sites |
|---|---|---|---|---|
| WP Umbrella (core €1.99/site) | ≈ €20 | ≈ €50 | ≈ €100 | ≈ €199 |
| WP Umbrella (core + security + hourly backups) | ≈ €65 | ≈ €162 | ≈ €324 | ≈ €648 |
| ManageWP (typical add-on mix) | ≈ $15–30 | ≈ $40–75 | ≈ $75–150 | ≈ $150+ |
| MainWP ($199/yr + your server + your hours) | ≈ $17 + ops | ≈ $17 + ops | ≈ $17 + ops | ≈ $17 + ops |
| WPClientHub (flat tiers) | $29 | $79 | $199 | $199 |
Three things jump out of that table.
First, per-site pricing is a growth tax. Between 25 and 100 sites, an all-in WP Umbrella configuration quadruples from ~€162 to ~€648 a month — roughly €7,800 a year — for the same product doing the same job. Your site count grew; the tool's marginal cost of serving you barely did.
Second, per-feature pricing is a negotiation with yourself. On à-la-carte models, every add-on becomes a small internal debate: does this client's site really need uptime monitoring? Should we skip the backup add-on on the cheap plans? You end up shipping an inconsistent service because your tooling bills inconsistently. The clients on your lowest tier — usually the least technical ones — quietly get the least protection.
Per-site pricing means every new client makes your tooling decision worse. Flat pricing means every new client makes it better.
Third, "cheap and self-hosted" isn't free. MainWP's sticker price is unbeatable, and for some agencies it is genuinely the right call. But be honest about the ops line: the dashboard is a WordPress site you must now host, harden, monitor, and back up — a single point of failure with admin-level reach into every client site. Two hours of maintenance a month at your billable rate is often more than every SaaS on this list.
Why per-site pricing exists at all
It isn't malice — it's cost structure. Cloud tools that store your backups pay real storage and egress bills that scale with every site you add, so their pricing has to scale too. ManageWP keeps backups on its own AWS S3; that S3 invoice is yours, laundered through per-site pricing.
That's the part we built differently. WPClientHub's backups are built into the client's own server and stay there; we receive the manifest and the checksums and never a byte of the archive. Our servers hold no backup payloads at all, so our costs barely move when your site count grows, and the pricing can honestly stay flat: $29/month for 10 sites, $79 for 40, $199 for 150, every module included, no add-ons. (More on the backup architecture in Where should your WordPress backups actually live?)
How to evaluate any tool's pricing in five minutes
- Price twice the number of sites you have today. Whatever you pay now, you're really buying the number two years out.
- Configure the tool the way you'd actually run it — all add-ons a real care plan needs — not the teaser sku.
- Check what happens to margins per plan. If a $59/month care plan carries $6.50 of tooling, that's an 11% cost of goods before you've done any work.
- Ask where the backups live. If the vendor stores them, per-site pricing is probably structural and will never go away.
- Count the invoices. Per-feature tools generate line-item creep; flat tools generate one predictable number your accountant will love.
Run the math for your own site count — it takes ten minutes and usually pays for itself hundreds of times over. And if you want the flat-tier column of that table for real, WPClientHub is free for your first three sites.