How to Create Hosting Packages in WHM (and Price Them So You Actually Profit)

How to Create Hosting Packages in WHM (and Price Them So You Actually Profit)

Creating a hosting package in WHM is a straightforward technical task; pricing that package so a reseller business actually profits after real underlying costs is the part that gets skipped when new resellers simply copy a competitor's price without understanding their own cost structure.

Creating a Package in WHM: The Technical Steps

1. In WHM, navigate to "Packages" → "Add a Package."
2. Set a clear internal name (customers won't usually see this directly — your storefront or billing system typically presents its own branded name).
3. Set disk space and bandwidth limits — these become the resource ceiling for any cPanel account created under this package.
4. Configure the number of allowed email accounts, databases, subdomains, addon domains, and FTP accounts per this tier.
5. Set CPU and memory (entry process) limits under the "Resource Limits" section if you want tier-specific performance isolation, distinct from the storage/bandwidth limits above.
6. Save the package — it's now available to assign when creating new cPanel accounts.

The Real Cost Structure Behind a Package

Before setting a price, know your actual per-account cost: your reseller hosting cost from your own upstream provider (or server cost if you're running your own infrastructure) divided by a realistic number of accounts you can actually fit at that resource tier, plus support time cost (even if it's your own time, it has a real opportunity cost), plus any per-account licensing (cPanel, if not already bundled, or third-party tools like backup or security add-ons).

A Common Pricing Mistake: Copying a Competitor's Number

Matching a competitor's advertised price without knowing whether their cost structure resembles yours is a common way new resellers end up unprofitable — a larger, more established host can sustain lower margins per account because of scale efficiencies a small reseller doesn't have. Price from your own actual costs and a realistic margin, not from a competitor's number.

A Practical Pricing Framework

Tiering Packages Sensibly

A common structural mistake is creating too many similarly-sized tiers that confuse buyers without meaningfully differentiating value — three to four clearly distinct tiers (entry, standard, business, and perhaps a higher unlimited-feeling tier) generally serve buyers better than seven marginally different options. Each tier jump should represent a genuinely meaningful resource or feature increase a buyer can articulate, not just a slightly bigger number.

Setting Resource Limits That Protect the Whole Server

Overly generous per-account limits on a lower-priced tier can let one account consume disproportionate server resources, degrading performance for every other account on the same physical server — setting sensible CPU/memory ceilings per package tier protects your other customers' experience, not just your own margins. This is a genuine technical responsibility, not just a business consideration.

Frequently Asked Questions

How often should package pricing be reviewed?

At least annually, or whenever your own underlying infrastructure or licensing costs change meaningfully — pricing set once and never revisited tends to quietly erode margin as costs shift over time.

Should packages include a free trial period?

Can be effective for customer acquisition, but factor the real cost of trial-period accounts (which consume the same resources as paying ones) into your overall pricing model rather than treating them as free.

Running a reseller business and want infrastructure priced to actually support healthy margins? See our reseller hosting plans or ask our team.