Ahosting Logo
Knowledge Base

How to Price and Package Reseller Hosting Plans

Three businesses hide behind the word hostingSpace aloneHosting with real supportHosting inside a serviceCustomerprice sensitivewants somebody to callbuying the service, nothostingVolume neededhighmoderatelowYou compete withlarge hosts and theireconomicsother people timenobody directlyReplaceable bya cheaper host, in anafternoonhardernot without changingsupplierPrice against your time rather than against disk. Disk is the cheapest thing you sell and the only thing yourcompetitor advertises.

Packaging is where a reseller business is won or lost. The technical work is the same whatever you charge; what determines whether it is profitable is what each plan includes, and whether the boundaries are ones you can hold.

Decide what you are selling first

Three businesses hide behind the word "hosting", and they have different economics.

Space and nothing else. Cheap, high volume, and the customers are price-sensitive and will leave for a pound.

Hosting with real support. Fewer customers, higher price, and the support is the product.

Managed sites, where you also maintain the software. The highest price and the most obligation.

Pick one deliberately. Most struggling reseller businesses are selling the first and delivering the third, which is why the margin disappears. Best Practices for Reseller Hosting Business sets out the operational habits behind each.

Three tiers, not seven

A long list of plans looks thorough and makes the decision harder, which loses sales.

Three is enough: a small one that is genuinely usable, a middle one most people buy, and a larger one for the customers who need it. The middle plan is what you are actually selling; the other two exist to frame it.

Differentiate on something customers understand: number of sites, disk, mailboxes, rather than on internals like entry processes. If a limit needs explaining, it belongs in the terms rather than on the comparison table.

Never sell "unlimited"

Every unlimited offer has a fair-use clause, and the gap between the headline and that clause is where every dispute lives.

A generous specific number is more honest, easier to enforce, and easier to upgrade from. "100 GB" and "unlimited, subject to fair use" describe the same product, and only one of them survives a disagreement. What to Include in Your Hosting Terms and Acceptable Use Policy explains writing the clause you would actually cite.

Cost it properly before pricing it

Your reseller plan divided by the number of accounts is not your cost.

Add the things that scale with customers: support time, the payment processor's percentage, the licences you pay per account, and the churn cost of replacing customers who leave.

Then add the things that scale with nothing: your billing system, your own domain and site, backups, monitoring.

A plan priced from the first figure alone looks profitable and is not, and the shortfall appears as your own time.

Support is the cost that varies most

Two customers on the same plan can differ tenfold in what they cost you.

The cheapest customer knows what they are doing. The most expensive bought hosting expecting a web designer. The plan cannot tell them apart, so the boundary has to.

State plainly what support covers: the server is yours, the site is theirs. Then offer site help as a paid service rather than absorbing it. That converts your most expensive customers into your most profitable ones, or into someone else's customers, and either is better than the current arrangement.

Make the upgrade path obvious

A customer growing out of a plan is the best thing that happens in this business, and it should be effortless.

Upgrades should be immediate, prorated and self-service. A customer who has to email you and wait is a customer thinking about alternatives at exactly the wrong moment. How to Upgrade or Downgrade Client Accounts goes into the mechanics.

Watch usage so you can start that conversation before they hit a limit. An account consistently near its ceiling is an upgrade to offer, not an outage to wait for. For seeing it, see Managing Disk Quotas and Bandwidth in WHM.

Annual billing, honestly

Annual terms improve cash flow and reduce churn, and a discount for them is reasonable.

What is not reasonable is a discount so large that the monthly price exists only to make it look good. Customers notice, and it makes the monthly plan feel like a penalty.

Invoice before renewal rather than charging silently. The most common billing complaint is a charge that arrived without warning, and it is entirely preventable. How to Integrate Billing and Automation sets out automating that.

Do not compete on price

There is always somebody cheaper, and they are frequently selling something worse without saying so.

What you can compete on is answering quickly, being reachable, and knowing the customer's site. Those are unavailable to a large provider at any price, and they are why customers stay with small resellers.

Price accordingly. A plan priced to match the cheapest option commits you to their support model as well, and that is the part that does not scale.

Review it annually

Costs change, your upstream plan changes, and the customers you attracted three years ago may not be the ones you want now.

Look at revenue per customer against support time per customer. The pattern is usually clear: one tier carries the business and one tier costs more than it brings.

Then change the offer for new customers rather than repricing everyone at once. Existing customers on an old plan are cheaper to keep than to replace, and a price rise is what prompts someone to compare.

Pricing only works if the support boundary is decided too, since unbilled work is what actually erodes the margin. What Support to Include and What to Charge For goes into drawing it.

Work out what one customer actually costs

Pricing set by looking at competitors is pricing set without knowing whether it is profitable.

ls /var/cpanel/users | wc -l
df -h /home | tail -1
awk '{s+=$10} END {printf "%.1f GB\n", s/1073741824}' /home/*/logs/* 2>/dev/null | tail -1

Divide the server cost by the number of accounts it comfortably holds. That is the floor, and it does not include your time, the licences, the payment fees or the accounts that do not renew.

The number that decides profitability is usually not resource use at all. It is how many support requests an account generates, and that varies by an order of magnitude between customers on the same plan.

Price the exit as well as the entry

A plan structure that makes leaving difficult produces short term retention and long term reputation damage.

State plainly what happens at the end: whether a full backup can be downloaded without asking, how long the account remains recoverable after cancellation, and whether any refund applies.

Customers compare these before signing more often than providers expect, and a clear answer is a competitive advantage rather than a concession. It also reduces the disputes that arrive when somebody leaves and cannot get their data. Handling a chargeback covers what those disputes look like.