Margin Notes
Hosting for agencies with care plans — The retainer is priced on labour, so buy the thing that removes labour
Written for agencies wrapping hosting, updates and support into one monthly figure — where the hosting tier is a cost input rather than a product decision.
Straight answer first
Buy reseller hosting and pair it with WordPress Toolkit: isolation per client for the billing model, bulk tooling for the margin — on our shelf that is the Reseller 2 tier, which carries 250 client accounts on 60 GB of NVMe and 600 GB of bandwidth.
Everything about a care plan's profitability is decided by two numbers you can control: how many minutes a client costs you per month, and how many clients a single administrative action can cover. The hosting tier is the thing that sets the second number, which is why it is a commercial decision rather than a technical one.
Written by the Hosting Seller staff · Checked 24 August 2026
Free
Migration into the account
24/7
Cover at any hour
Daily
Backups across every account
$0
To open a new account
A care plan is a labour business wearing a hosting costume. The hosting fee is a small and predictable input; the hours are the variable that decides whether the retainer is worth selling more of. Every structural decision should be judged against that.
The second thing that decides it is separation. One account per client is what makes billing tidy, incidents contained, offboarding clean and access grantable — and every one of those is an hours problem before it is a technical one.
What the retainer is actually buying
Write the plan as a list of things that visibly happen: hosting, updates rehearsed on a copy, backups verified, a fixed allowance of small fixes, and a monthly note recording all of it. The note is the item that gets the plan renewed, so it is the one never to drop when a month gets busy.
Cap the small fixes explicitly. 'A reasonable amount of minor changes' is how a profitable retainer becomes an unprofitable one over eighteen months, because reasonable is defined by whoever is asking rather than by whoever is doing.
Price the exceptions out rather than absorbing them. The client with the plugin that breaks monthly and the client whose staff email you daily are not the same customer as the other eighteen, and the plan should say so.
The account arithmetic at ten, forty and a hundred clients
Reseller tiers are sized by client accounts, disk and bandwidth: 100 accounts on 30 GB of NVMe and 300 GB of bandwidth at the entry tier, 250 accounts on 60 GB and 600 GB in the middle, 500 accounts on 100 GB and 1.5 TB at the top. The plan price also carries a per-active-user line, so the cost follows the client list rather than the shelf.
Disk is the binding constraint in practice, not the account count. Forty WordPress sites with media libraries, daily backups and several years of mail will meet a 30 GB allowance long before they meet a hundred-account limit — which is why per-account quotas set in WHM at creation are the single most useful habit on this list.
Overselling is switched on from the start, which is appropriate for exactly this workload: many small accounts whose theoretical allowances vastly exceed their real usage. It is a tool for making the arithmetic work, not a licence to stop watching the disk figure.
White-label surfaces, and the ones that leak
The surfaces you control are the ones clients meet routinely: private nameservers under your own brand, a control-panel address on your domain, packages you have built and named yourself, and mail from your own addresses. Set those up once and the ordinary client path never mentions anybody else.
The leaks are almost always incidental. A staging URL on a platform hostname. A forwarded support email with a signature attached. A screenshot showing a server name. A billing link that opens somewhere unexpected. Audit those four before you launch rather than after a client asks.
Have an answer ready for the direct question, because it will come eventually. There is nothing improper about reselling; what damages a relationship is being caught concealing rather than the fact itself.
Billing: a spreadsheet, until it is not
For the first handful of clients, invoicing by hand is fine and buying software is procrastination. The point at which it stops being fine is proration, mid-term upgrades, failed payments and dunning — all of which are cheap to automate and expensive to do badly.
A standalone WHMCS licence sits on our shelf for exactly that transition, and the reseller platform is ready to wire into it so that account creation and billing stop being two separate manual jobs.
Whatever you choose, keep the client-facing invoice on your own brand and your own terms. It is the document a client reads most carefully and the one most likely to be forwarded to somebody else.
Why we write this down
We sell the reseller tiers this page recommends, so read it as a supplier making a case with the arithmetic exposed. Redo the sums with your own timings; the shape of the answer does not depend on whose logo is on the invoice.
Bulk tooling, per-account backups and isolation are inside the plan price rather than sold back per site, because a reseller whose margin works is a reseller who is still here next year.
- A cPanel per client, WHM above them
- Private nameservers running under your own brand
- Packages you build and name yourself
- Daily backups across every client account
Why Hosting Seller
On every plan, as standard
Isolation per client
An account each keeps incidents contained, billing tidy and offboarding a migration rather than an extraction.
Bulk tooling for the margin
Fleet updates from one dashboard are what turn maintenance hours into a coffee, which is where a care plan's profit lives.
Sizing by accounts and disk
250 client accounts on 60 GB and 600 GB at the middle tier, with per-account quotas you set yourself from WHM.
Your name on every surface
Private nameservers, a panel address on your domain, and packages you have named — the ordinary client path mentions nobody else.
Overselling switched on
Enabled from the start, which suits a list of many small accounts whose allowances exceed their real usage.
Billing when you need it
A standalone WHMCS licence on the shelf and a platform ready to wire into it, for the point where proration stops being a spreadsheet job.
First Steps
From choosing to live
- 1
Write the plan as visible deliverables
Hosting, rehearsed updates, verified backups, a capped allowance of fixes, and a monthly note. The note is what gets it renewed, so build the round to produce it.
- 2
Set a per-account quota at creation
Disk is the constraint that actually binds, not the account count. A limit applied in WHM on day one costs nothing and is awkward to impose after a client's media library has grown.
- 3
Audit the four common leaks before launch
Staging URLs, forwarded emails with signatures, screenshots showing hostnames, and billing links. Those are where a white-label arrangement gives itself away.
In the Box
Packed with every plan
- A cPanel account per client with WHM above it
- Private nameservers published under your own brand
- Packages you build, name and set limits on yourself
- Per-account disk and mailbox quotas applied at creation
- Overselling enabled from the start
- Daily backups across every client account
- Imunify360 on guard on every client site
- WordPress Toolkit for fleet updates across the list
- A platform ready to wire into WHMCS billing
- Free setup, with nothing to pay before you start
Across the Counter
Things people ask us all the time
Which limit does a care-plan fleet actually hit first?
Disk, well before the account count. Forty WordPress sites with media libraries, daily backups and several years of mail will meet a 30 GB allowance long before a hundred-account ceiling. Set per-account quotas in WHM when you create the account — it costs nothing then and is awkward to impose afterwards.
What should be capped in the plan wording?
The small fixes. 'A reasonable amount of minor changes' is defined by whoever is asking rather than whoever is doing, and it is how a profitable retainer becomes an unprofitable one over eighteen months. Give it a number of hours or a number of requests, and price the habitual exceptions separately.
Where does a white-label arrangement usually give itself away?
Four places: a staging URL on a platform hostname, a forwarded support email carrying a signature, a screenshot showing a server name, and a billing link that opens somewhere unexpected. Audit those before launch. Also decide what you will say if a client asks directly — being caught concealing costs more than the fact.
When should billing stop being a spreadsheet?
At proration, mid-term upgrades, failed payments and dunning. Below that, invoicing by hand is fine and buying software is procrastination. A standalone WHMCS licence is on our shelf for the transition, and the reseller platform is ready to wire into it so provisioning and billing stop being two manual jobs.
Read next
Most Secure Shared Hosting
Shared hosting judged on how much the platform does before any plugin is involved.
Hosting for Portfolios With Booking
Portfolios that also have to fill a diary, and what the booking side adds to the support load.
Reseller Hosting
WHM above a cPanel per client, private nameservers on your own brand, and packages you name yourself.
Web Hosting
cPanel hosting on NVMe with SSL, migration and the first year of the domain included.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Buy the tier that removes the hours.
A cPanel per client, nameservers under your name, fleet updates from one screen, and daily backups across the list.
See Reseller Hosting plans