How to Design Profitable Hosting Plans as a Reseller

Kualo's reseller hosting gives you the raw materials - disk space, accounts, cPanel, and a fast LiteSpeed stack - but turning those materials into a profitable business takes deliberate packaging. This guide walks you through plan architecture, WHM tooling, resource boost upsells, and the add-on logic that lets you charge more without provisioning anything new.

Plan architecture: why tiers beat one-size-fits-all

A single flat plan forces every customer onto the same price point, which means you either undercharge your most demanding clients or overprice yourself out of the small-business market. A three-tier structure - something like Starter, Business, and Pro - solves both problems at once.

What actually differentiates tiers in practice is a combination of three things:

• Resource allocations - disk space, the number of addon domains, email accounts, and databases you set in the WHM package itself.
• Feature access - which cPanel tools are visible and usable, controlled separately through WHM Feature Manager.
• Perceived value - the story you tell about what each tier is for, which shapes how customers self-select.

Disk space alone is a weak differentiator because storage is cheap and customers rarely use it as a buying signal. A more compelling axis is capability: can this plan handle a WooCommerce store, or is it for a simple brochure site? Frame tiers around use cases, not gigabytes.

A practical starting point:

• Starter - one or two domains, basic cPanel features, no staging, no managed updates. Suitable for personal sites and simple landing pages.
• Business - multiple domains, full cPanel feature set, staging environment available, LiteSpeed Cache configured on setup.
• Pro - everything in Business, plus managed WordPress updates via WP Toolkit Smart Updates, priority support, and a security monitoring add-on.

The table below maps the key differentiators across tiers at a glance:

Feature	Starter	Business	Pro
Domains	1-2	Multiple	Multiple
LiteSpeed Cache	Available (self-serve)	Configured on setup	Fully configured
WP Toolkit staging	No	Yes	Yes
WP Toolkit Smart Updates	No	Optional add-on	Included
Managed WordPress updates	No	Optional add-on	Included
Security monitoring report	No	Optional add-on	Included
Resource boost alignment	Standard	Mid-tier boost	Higher-tier boost
Priority support	No	No	Yes

Setting resource limits in WHM packages

Resource limits - disk quota, bandwidth, the number of email accounts, databases, and addon domains - are set in the WHM package, not in Feature Manager. Our guide on creating hosting packages walks through the package creation screen in detail.

Keep these points in mind when setting limits:

• Set limits that reflect what each tier is genuinely for, not arbitrary round numbers.
• Leave yourself headroom: if your reseller account has a total disk allocation, over-provisioning packages on paper is fine, but watch actual usage.
• If a client's account needs higher resource limits than your reseller allocation allows - for example, more CPU or RAM under CloudLinux's LVE system - that is a server-level setting we handle. Contact our support team rather than trying to adjust LVE limits yourself.

For background on how CloudLinux isolates accounts and enforces per-account resource limits, see our CloudLinux overview.

Aligning plans to permanent resource boost levels

Beyond the standard package limits, we offer permanent resource boosts that increase the CPU, RAM, and I/O available to a specific resold account. These boosts come in defined levels, and you can use them as the backbone of a higher-tier plan.

This is particularly useful when you want to market plans that are genuinely better suited to resource-hungry sites - WooCommerce stores, membership sites, or high-traffic blogs - rather than just offering more disk space. You can price a "WooCommerce" or "High-Traffic" plan at a premium and back it up with a permanent boost on the underlying account.

See Understanding Permanent Resource Boosts for Resold Accounts for the available boost levels and how to apply them.

A practical approach:

• Starter and Business plans - standard resource allocation, suitable for brochure sites and small blogs.
• Pro or WooCommerce plans - backed by a permanent boost at an appropriate level, giving the account more CPU and RAM headroom. Price the plan to cover the boost cost and your margin.
• Custom or Agency plans - for clients with genuinely large sites, apply a higher boost level and price accordingly.

This lets you market plans around real-world use cases and charge a premium that is justified by measurable performance headroom, not just a bigger disk quota.

WHM Feature Manager: making tiers feel genuinely different

Feature Manager controls which cPanel tools each account can see and use. It does not change resource limits - that is the package's job. The two controls work together: a package sets the ceiling, and a feature list sets the interface.

To create a feature list in WHM:

1. Log in to WHM and go to Packages > Feature Manager.
2. Click Add Feature List, give it a name that matches your tier (for example starter-features or pro-features), and save.
3. Tick or untick the cPanel features you want to include, then save the list.
4. When you create or edit a package, assign the appropriate feature list to it.

The strategic logic matters more than the mechanics. Think about what to hold back on lower tiers and what to unlock as a genuine reward for upgrading:

• Hold back on Starter - Cron jobs, Git Version Control, SSH access, Node.js/Python/Ruby selectors, and advanced DNS tools are all things a simple brochure-site customer does not need and will not miss. Removing them also reduces support load.
• Unlock on Business and Pro - Staging tools, advanced caching controls, and developer-facing features signal that the plan is built for more serious sites.
• Never hide things that cause confusion - Keep SSL management, email tools, and file management visible on every tier. Hiding them creates support tickets, not upsells.

See our Feature Manager guide for the full walkthrough of the WHM interface.

WP Toolkit as a monetisation lever

WP Toolkit is available in your reseller account and gives you a powerful managed-care story for WordPress clients. Used well, it is one of the strongest differentiators you can offer - particularly for agencies managing multiple client sites.

WP Toolkit feature lists: unlocking the full feature set

WP Toolkit has its own feature list within WHM's Feature Manager, separate from the standard cPanel feature list. The Deluxe feature list for WP Toolkit unlocks the full set of capabilities, including:

• Staging - create a private copy of a WordPress site for testing changes before they go live.
• Smart Updates - test updates on a clone before applying them to the live site (see below).
• Multi-WordPress management - manage all WordPress installations across your reseller accounts from a single WHM-level view.

The standard (non-Deluxe) feature list gives clients a more limited WP Toolkit interface. Assigning the Deluxe feature list to your Business and Pro packages - and withholding it from Starter - is a clean way to make higher tiers feel meaningfully more capable.

What Smart Updates does

Smart Updates is not the same as standard WordPress automatic updates. When Smart Updates runs an update, it:

1. Clones the live site to a temporary copy.
2. Applies the update - WordPress core, plugins, or themes - to the clone.
3. Runs a visual regression check, comparing screenshots of key pages before and after.
4. Only applies the update to the live site if no visual differences are detected.
5. Sends a report of what was updated and what was checked.

This means updates are tested before they touch the live site. For a client running a WooCommerce store or a membership site, that distinction is worth paying for. A broken update on a live store costs real money; Smart Updates reduces that risk significantly.

For a full walkthrough of the feature, see our guide to using Smart Updates in WP Toolkit.

Bulk updates and managed WordPress as a service

WP Toolkit's WHM-level view lets you see and manage every WordPress installation across all your reseller accounts from one place. This makes it practical to offer managed WordPress maintenance as a product - either as a plan tier or as a standalone retainer.

From the WHM WP Toolkit view you can:

• Run bulk updates across all client sites in one action.
• Enable Smart Updates on individual installations so each update is tested before going live.
• Monitor which installations are out of date or have known vulnerabilities.

For agencies, this is the operational backbone of a managed WordPress service. You can keep dozens of client sites up to date in the time it would take to update a handful manually, and package that efficiency as a recurring monthly retainer.

How to position WP Toolkit as an add-on or plan feature

Frame managed WordPress care as a service, not a technical feature. The client does not need to understand visual regression testing or bulk update queues - they need to understand that their site will not break when WordPress updates itself at 3am, and that someone is keeping an eye on things.

You can offer this as:

• A recurring monthly add-on on top of any hosting plan.
• A feature included in your Pro tier by default.
• A standalone "WordPress Care Plan" product that bundles Smart Updates, bulk update management, and your performance setup service - sold as a retainer.

To enable Smart Updates for a specific account, access the client's cPanel through WHM (see how to access a client's cPanel account), open WP Toolkit, and enable Smart Updates on the relevant WordPress installation. You can also manage this from the WP Toolkit view within WHM itself, which gives you an overview of all WordPress installations across your reseller accounts.

For a broader introduction to WP Toolkit in the reseller context, see our WP Toolkit introduction for resellers.

Staging environments as a paid add-on

WP Toolkit makes it straightforward to create a staging site - a private copy of a WordPress installation where changes can be tested before going live. See creating staging websites with WP Toolkit for the steps involved.

For clients, a staging environment means they can test a new theme, a plugin update, or a redesign without touching the live site. Most clients on a Starter plan will not know this is possible; positioning it as a Business or Pro feature - or as a paid add-on - gives it the weight it deserves.

Because staging sites live within the same cPanel account, you are not provisioning extra infrastructure. The cost to you is disk space; the value to the client is peace of mind.

Packaging performance as a product

Every account on our servers already benefits from LiteSpeed Web Server. The server-level performance advantage is there by default - you are not providing new infrastructure when you sell a "performance" tier. What you are selling is configuration and activation as a service, which is a legitimate and valuable thing to offer.

LiteSpeed Cache for WordPress is not enabled or configured automatically on a fresh WordPress install. A client who signs up and installs WordPress themselves will not have it set up unless someone does it for them. That gap is your opportunity.

How to position this:

• On your Starter plan, LiteSpeed is available but not configured. Clients can set it up themselves.
• On your Business plan, include LiteSpeed Cache installation and basic configuration as part of the onboarding. This is a one-off task per site that takes under 30 minutes but has a measurable impact on page load times.
• On your Pro plan, include full LiteSpeed Cache configuration - page caching, image optimisation, CSS/JS minification, and browser cache settings - as a setup deliverable.

You can also offer performance configuration as a standalone paid service for clients who upgrade from Starter later.

For the technical steps involved, see our guide to configuring LiteSpeed Cache with WordPress and how to enable LiteSpeed Cache in cPanel.

Security monitoring as a recurring add-on

Our servers run both Imunify360 and Patchman, which means your clients already benefit from server-level malware detection and vulnerability patching. What you can sell is visibility and response - turning a background process into a named, managed service.

Imunify360 provides real-time malware scanning and intrusion detection at the server level. You can reference it as part of your security story without needing to configure anything per account. See our introduction to Imunify360 for background.

Patchman scans for outdated applications and known vulnerabilities, and patches them automatically. Clients can access their own Patchman dashboard from cPanel. As a reseller, you receive notifications about vulnerabilities across your accounts. See Patchman information for resellers and an introduction to Patchman for what is covered.

How to package this:

• On all plans, include a line in your plan description noting that accounts are protected by Imunify360 and Patchman. This is a genuine differentiator versus budget hosts.
• On your Pro plan or as a paid add-on, offer a monthly security report: a summary of what Patchman found and resolved, any Imunify360 alerts, and a confirmation that WordPress core, plugins, and themes are up to date. This is largely a reporting and communication service built on tools that are already running.

Add-on logic: building revenue without new infrastructure

The principle behind all of the above is the same: you are packaging configuration, monitoring, and expertise - not hardware. Before you build out a new add-on, ask:

• Is the underlying capability already on the server? (Usually yes.)
• Is the gap between "available" and "configured and working" something a non-technical client would pay to close? (Usually yes.)
• Can you deliver it consistently and at a reasonable time cost per account?

The table below summarises the add-ons that work well on this model:

Add-on	What you deliver	Pricing model
Performance setup	LiteSpeed Cache configuration, image optimisation, speed report	One-off fee
Managed WordPress updates	Smart Updates enabled, bulk updates managed, monthly report	Recurring monthly
WordPress Care Plan	Smart Updates + bulk management + performance setup, sold as retainer	Recurring monthly
Security monitoring report	Monthly Patchman and Imunify360 activity summary	Recurring monthly
Staging environment	WP Toolkit staging site created and documented	One-off setup, or included in higher tier
Priority support	Named response time SLA	Recurring monthly
WooCommerce / high-traffic plan	Permanent resource boost applied, higher CPU/RAM headroom	Higher monthly plan price

Avoid add-ons that depend on server-level changes you cannot make yourself. Shared IP reputation management, server-level DKIM signing, and LVE resource tuning are all things we handle - do not sell these as services you provide, and contact our support team if a client's account genuinely needs them.

Practical pricing psychology

A few principles worth applying when you set prices:

Use anchoring. List your Pro plan first or most prominently. When clients see the highest price first, your mid-tier Business plan looks reasonable by comparison, even if it is the price you actually want most clients to pay.

Make the middle tier the obvious choice. Price Starter low enough to be accessible, Pro high enough to feel premium, and Business at the sweet spot where the value-to-price ratio is clearly best. Most clients will choose the middle option if you frame it correctly - this is sometimes called the "compromise effect".

Name plans around outcomes, not specs. "Business" and "Pro" signal who the plan is for. "10GB" and "20GB" signal nothing useful. Names like "Starter", "Growth", and "Agency" work because they let clients self-identify.

Avoid too many tiers. Three is the right number for most resellers. Four or more creates decision paralysis; two removes the anchoring effect of a premium option.

Price add-ons as monthly recurring where possible. A client who pays £10/month for managed updates is worth more over 12 months than one who pays a one-off £50 setup fee. Recurring revenue also makes your business easier to value and plan.