Operator's Guide
Hosting for local businesses — Hosting a town's worth of clients without becoming their hostage-taker
Written for the freelancer or small agency that has quietly become the hosting provider for a dozen local firms — and now has to decide how that is structured, billed and eventually handed over.
Straight answer first
Put each client on their own account rather than on a folder in yours, and be explicit in writing about who owns it — a Launch plan per client is the cleanest arrangement when the client pays the bill, and a reseller account is the cleanest when you do.
Everything else on this page follows from that one structural decision: what the client sees when they log in, what an inherited fleet costs you per month, which failures reach them on a Saturday morning, and what has to be written down before the relationship ends rather than after.
Written by the Hosting Seller staff · Checked 24 August 2026
24/7
Cover for you and the client
1-click
WordPress into a new account
Free
SSL on every client site
Daily
Backups across the client list
Local business hosting has a peculiar shape. The sites are small, the expectations are modest, and the money is not the point — the retainer is. What makes the arrangement profitable or painful is administration: how many accounts you touch, how often, and how much of that touching is billable.
It also has an ethical shape that the trade rarely discusses honestly. A local firm's website, domain and email frequently sit in an agency's name because that was convenient once. That convenience becomes a hostage situation the moment the relationship sours, and the reputational cost of being on the wrong side of it lands entirely on you.
What the client sees, and what that says about you
A local client interacts with hosting perhaps four times a year: a password reset, a mailbox on a new phone, an invoice, and the one bad afternoon when something is down. Those four moments are the whole of their experience of your infrastructure, so they are worth designing rather than inheriting.
On a reseller account each client gets a cPanel of their own, reached through nameservers running under your brand, with SSL on their site and mailboxes on their domain. Nothing in that path needs to mention where you buy. On a shared account with addon domains, by contrast, the client either sees everything or sees nothing — there is no middle setting.
The mailbox is the part that gets emotional. Quotes, bookings and invoices live there, and a client who loses access to mail for an afternoon will remember it for years. Give every client their own account and their own mail, and that failure stops being shared.
Ownership, and the paragraph that prevents a hostage situation
Decide, per client, who is the account holder — and write it down. There are only two honest arrangements. Either the client holds the account and pays for it and you have access, or you hold the account, bill them for it, and undertake in writing to hand over or migrate the site on request within a stated period.
Both are defensible. What is not defensible is the accidental third arrangement, where the account is in your name, the client has never seen a login, and nobody has ever discussed what happens if you are ill, bored or busy. That is the arrangement that produces the 'my web person has vanished' enquiries we field weekly.
The domain deserves the same treatment as the hosting and rarely gets it. Registrations should be in the client's name with you as technical contact. A domain registered to an agency is the single most effective way to turn a routine parting of ways into a dispute.
Twelve shops: what the arrangement actually costs to run
Do the arithmetic on accounts rather than on sites. A reseller plan is sized by client accounts, disk and bandwidth: the entry tier carries 100 client accounts on 30 GB of NVMe and 300 GB of bandwidth, the middle tier 250 accounts on 60 GB and 600 GB, the largest 500 accounts on 100 GB and 1.5 TB. Note that the reseller price carries a per-active-user line on top of the plan figure, so the cost tracks the client list rather than the shelf.
For a dozen small local sites, disk is the constraint that arrives first and nobody plans for. Brochure sites are tiny; the media libraries, the daily backups and the six years of mail behind them are not. Set a per-account quota in WHM when you create the account, not after the disk fills.
Bandwidth is rarely the problem for this kind of client, which is why the number on the tin is misleading. A dozen local firms will never trouble 300 GB. Overselling is available and switched on from the start precisely because these accounts are small and predictable.
The Saturday-morning failure, and who answers it
A local site is down on Saturday morning when the phone would otherwise ring. That is the failure that matters, and the client will phone you rather than a supplier, whatever the contract says. Your support arrangement therefore has to be a second line behind you, not a first line you point clients at.
That is a genuine reason to care whose desk sits behind yours. Ours is staffed at every hour and its scope covers the practical work — mailbox configuration, DNS records, certificate reissues, restores — rather than stopping at 'the server responds'. The uptime target is 99.9%, with a pro-rated credit on any month that falls short through a fault at our end.
Back it with the boring hygiene. Daily backups run across every client account with restores you run yourself, and Imunify360 sits on every client site, which means the two most common Saturday emergencies — a bad update and a compromised plugin — have a route out that does not begin with an apology.
What we get out of writing this plainly
We are the supplier, so treat this as a supplier's argument rather than a neutral survey. The trade is that we say what we sell and why, and you get reasoning specific enough to check rather than a table with our own name at the top of it.
Everything described here — the reseller tier, the per-client cPanel, the nameservers on your own brand — is on one catalogue, so testing the arrangement does not require committing to it.
- A cPanel per client, reached through your own nameservers
- Per-account quotas set when the account is created
- Daily backups across every client account
- A second line behind your desk at any hour
Why Hosting Seller
On every plan, as standard
One account per client
Isolation, a quota and a backup per client, which is what makes a fleet of small local sites administrable rather than merely survivable.
Your brand on the path
Private nameservers run under your own name, so nothing a local client touches has to name where you buy.
A company they can look up
IGI Security Services Ltd, registered in England and Wales — a supplier with a public record, which matters when your client asks who is really behind it.
Mail treated as first-class
Mailboxes on the client's own domain with spam and virus filtering fitted, because quotes and bookings are the part they cannot lose.
A cost you can quote against
The joining figure and the renewal figure match, which is the only way a fixed monthly retainer stays profitable in year two.
Handover without a fight
An account moves as an account, so ending a relationship well is a migration ticket rather than a dispute.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Settle ownership in writing at the start
Name the account holder and the domain registrant for each client, and state what happens on request. One paragraph at the beginning prevents the argument that otherwise arrives at the end.
- 2
Set the quota when you create the account
In WHM, a per-account disk and mailbox limit costs nothing to apply on day one and is awkward to impose later. It is also what stops one client's media library becoming everybody's problem.
- 3
Rehearse the Saturday failure once
Restore one client's site from the daily backup on a quiet afternoon, and time it. Knowing the number turns the worst call of the year into a routine job you have already done.
In the Box
Packed with every plan
- A separate cPanel account for every client on the list
- Private nameservers running under your own brand
- Per-account disk and mailbox quotas set from WHM
- Daily backups across every client account, restored by you
- Imunify360 on guard on every client site
- Free SSL issued and reissued on every client domain
- Mailboxes on each client's own domain with filtering fitted
- A 99.9% uptime target with a pro-rated credit when it is missed
- Second-line support at any hour, covering mail, DNS and restores
- Account-level migration in and out, done by our staff at no charge
Across the Counter
Things people ask us all the time
Should the hosting account be in my name or the client's?
Either, provided it is written down. If the client pays the supplier directly, put it in their name and take access. If you bill them a retainer that includes hosting, hold the account yourself and undertake in writing to hand it over or migrate it on request. The failure mode is the unstated third option, where nobody has decided.
How do I give a local client access to their own site without exposing the others?
By giving them their own account. On a reseller plan each client has a cPanel of their own, so a login is scoped to one site, one mailbox set and one backup. On a shared plan with addon domains there is no partial access to grant — it is all or nothing, which is why that structure stops working at the first client who asks.
What is the first limit a dozen small local sites will hit?
Disk, almost always, and not through the websites. Media libraries, daily backups and several years of mail are what fill an account. Bandwidth is rarely troubled by brochure sites. Set per-account quotas in WHM at creation time and the problem never arrives.
What should I tell a client who asks who actually runs the servers?
Whatever your agreement with them says. White-label surfaces exist so that the client-facing path carries your name, and there is nothing dishonest about that — you are the supplier as far as they are concerned. If they ask directly, answering plainly costs nothing; being caught concealing it costs a client.
Read next
NVMe Hosting Plans
Why the disk under a client fleet decides how the whole arrangement feels day to day.
cPanel vs Plesk
Choosing the panel your clients will be looking at for years, weighed by support load rather than features.
Web Hosting
cPanel hosting on NVMe with SSL, migration and the first year of the domain included.
VPS Hosting
KVM virtual servers with root access, DDoS filtering at the edge and one flat price.
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.
Put every client on an account of their own.
A cPanel each, nameservers under your name, per-account quotas and backups, and a second line behind you at any hour.
See Web Hosting plans