Reseller runbook · Provisioning · 10 minutes
One House Build Spec, Installed the Same Way Every Time
Forty client sites installed forty different ways is not an estate, it is forty separate problems waiting for a quiet week.
Straight answer first
Use Softaculous to make every client install identical, not merely fast. One click puts WordPress or any of hundreds of other applications into a client's account, and the settings you choose in that one screen — admin credentials, directory, auto-update, install-time backup — decide how much support that site costs you for the rest of its life.
Write the house spec down, use it every time, and keep the installations list as your inventory. Softaculous is in every account you create, so the standard costs nothing to apply. The expensive alternative is improvisation, which is what produces an estate nobody but you can maintain.
Written by the Hosting Seller staff · Checked 4 August 2026
Beginner
Skill assumed
10 minutes
Bench time
5
Runbook stages
24/7
Cover for you and your clients
For a reseller the installer is a provisioning tool, not a convenience. The question is never whether you can get WordPress up in a minute; it is whether the site you just created looks like the other thirty-nine.
Standardisation is what lets you hand work to a contractor, quote a maintenance plan honestly, and answer a client's question without opening their site first to remind yourself what you did.
Why every client site should be installed identically
An estate where each site was set up by whoever was free that day cannot be maintained at a fixed price. The plugin set differs, the admin usernames differ, the table prefixes differ, and every routine job becomes an investigation. That is the cost of not having a spec, and it is paid monthly.
A house spec is short: which application, which directory, which admin naming convention, which plugins go in every build, whether auto-update is on, and what gets removed from the default install. Written on one page, it turns a two-hour setup into a fifteen-minute one and makes any of your sites legible to any of your people.
The settings that decide your support load later
The defaults in the install screen are the only real trap in Softaculous. The default admin name, the default table prefix and the blank auto-update box are all fine for a test and all wrong for a client site you will still be responsible for in three years.
Set genuine credentials from a password manager, choose the directory deliberately — root for the main site, never a folder you will regret in a URL — and tick both auto-update and the install-time backup. Those two ticks cost nothing and they are the difference between a client site that maintains itself and one quietly falling four major versions behind.
What to leave in the client's hands, and what not to
Softaculous sits inside the client's own cPanel, so anything you can do there they can do too. On most accounts that is fine and occasionally excellent: a capable client who installs their own staging copy is a client generating no tickets.
The one to think about is uninstall, which removes the database along with the files. If a client can reach it, a client can eventually use it. For accounts where that would be a disaster, restrict panel access to the features they actually need and say plainly in the handover what is out of scope for self-service.
Removing an install when a client leaves
Deleting a folder is not uninstalling. Do that and the database, its user and the configuration stay behind, occupying part of the NVMe allowance you are paying for and confusing whoever next opens the account. Multiply by a few years of churn and your disk usage stops matching your client list.
Remove through Softaculous instead, which clears files, database and configuration together. Do it as part of your offboarding routine, after you have taken and handed over a final backup — the client's site and files remain theirs, and giving them a clean copy is both correct and good for the reference.
The same tooling in every account you sell
A standard build needs a standard platform. Softaculous is in every account you create, the latest cPanel is in every account, and PHP is chosen per site so one legacy client never dictates the version everybody else runs on.
WordPress Toolkit comes with updates applied for you, and staging copies let a change be tested on a copy before any client's visitor meets it.
- Softaculous in every account you create
- One-click installs, then a list you can audit
- WordPress Toolkit with updates applied
- Staging so no client meets an untested change
Why Hosting Seller
On every plan, as standard
Provisioning, not just installing
Written for someone standing up the fortieth client site, where repeatability beats speed.
Defaults called out as traps
Each default that costs you support later is named, with the value to use instead.
Handover-ready
Every choice is judged by whether a contractor or a client could pick the site up without you.
Offboarding included
Removing an install cleanly is part of the routine here, not an afterthought discovered later in disk usage.
Same tooling in every account
Softaculous, cPanel and per-site PHP are in every account you create, so the standard actually holds.
Help for you and for them
Support answers at any hour, mid-build included, for you and for the client.
First Steps
From choosing to live
- 1
Write the house spec before you install anything
One page: application, directory, admin naming, the plugin set every build gets, auto-update on or off, and what you strip from the default install. Without this, standardisation is a good intention.
- 2
Install into the directory you meant, first time
Root for the client's main site. A folder chosen carelessly lives in the URL for years, and moving it later means redirects, a search-replace and a conversation. Ten seconds of attention here saves an afternoon.
- 3
Set real credentials from the password manager
Never the suggested admin name, never a password you typed from memory. These are the keys to a site you are contractually responsible for, and they belong in the same vault as the account's other credentials.
- 4
Tick auto-update and the install-time backup
Both are free and both are insurance. Auto-update is how a client site you rarely touch keeps taking security fixes; the install-time backup is the undo for the next ten minutes of configuration.
- 5
Keep the installations list as your inventory
Softaculous records everything it installed, and that list is where updates, clones, staging and clean removal all run from. Treat it as the estate's index rather than a screen you visit once.
In the Box
Packed with every plan
- Softaculous waiting inside every account you create
- cPanel, the panel your clients and your contractors already know
- WordPress Toolkit, with updates applied for you
- Staging on the plans that carry it, so nothing untested reaches a client
- PHP versions chosen per site, so one legacy client never blocks the rest
- WHM for you, and a cPanel of their own for every client account
- Packages you build, name and price yourself
- Daily backups taken across every client account you create
- Real people answering, for you and for your clients, at any hour
- Upgrades applied to the account in place, with no migration between plans
Across the Counter
Things people ask us all the time
Is Softaculous available inside every client account I create?
Yes — it sits in every account, so a house build spec applies uniformly whether you are provisioning your first client or your fortieth. That is what makes standardisation cheap: you are not paying per account for the tool that enforces it.
Should clients be allowed to install applications themselves?
For capable clients it removes tickets and does no harm. The setting to think about is uninstall, which removes the database along with the files. Where that would be a disaster, limit the panel features the account exposes and be explicit in the handover about what self-service covers.
Does auto-update reduce my support load or create it?
On client sites it reduces it, decisively. The releases arriving through that channel are mostly security fixes, and the alternative is a site quietly falling behind until an incident makes it your problem. Where a client's build is fragile, pair it with staging rather than switching it off.
What happens to a client's database if I just delete the folder?
It stays behind, along with its user and configuration, using part of the NVMe allowance you pay for. Remove through Softaculous instead so files, database and configuration go together — and do it after the final backup has been taken and handed over.
Read next
Mail Filtering
Spam and virus filtering on client mailboxes, before it becomes your problem.
Secure Hosting
The hardened tier for the client whose site cannot afford another incident.
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.
Build every client site the same way.
Softaculous, cPanel and per-site PHP in every account you create, with WHM and packages you define over the top.
See Mail Filtering plans