Insights / Hosting
WHMCS for a New Hosting Company: What to Decide Before You Install It
Decide the catalog, welcome emails, fraud checks, tax, and provisioning — then buy the licence. A billing panel is not a business model.
WHMCS is billing software many hosting companies use to take orders, send invoices, create services, and suspend unpaid accounts. WHMCS for a new hosting company is a sequence problem, not a shopping problem. The licence will store whatever catalog you type in. If that catalog is a copied price list with no suspend process, you have automated a mess.
WHMCS is good at taking money, creating services, sending invoices, and suspending them. It will not tell you whether to sell KVM VPS (a virtual private server on a KVM hypervisor) or reseller hosting. It will not write your acceptable use policy. It will not decide what “unmanaged” means when a customer’s CMS — WordPress or otherwise — breaks. Those are business decisions. Make them on paper. Then install the panel.
I say this as someone who has to live with billing and provisioning on a real VPS product, not as a WHMCS evangelist. Use the tool. Do not ask it to be a strategy.
A billing panel is not a business model
A billing panel is infrastructure for money and the service lifecycle. Your business model is who you sell to, at what price, with what support, and what you refuse. If those are fuzzy, WHMCS will still let you click “create product.” That is not validation.
Install too early and you will rebuild product modules twice: once for the fantasy catalog, once for the catalog you should have launched. Modules, configurable options, and welcome emails are tedious to redo. Tedious work done twice is how launch week slips.
Founders install early because a configured panel feels like a company. It is the same mistake as buying a rack first — progress you can screenshot. Read how to start a hosting company if the offer is not on paper yet. Read VPS hosting pricing if the numbers are still “a bit under the other guy.”
When the catalog is stable enough that you would not be embarrassed to invoice it for a year, then the licence is on time.
Enter the catalog you already decided
Write the three plans on a sheet: name, resources, included IPs, backup policy, support window, price, billing cycle. Then create those products. Do not invent a fourth plan in the admin because the screen had empty slots.
Configurable options should be things you can provision without a project: extra IP, extra backup slot, extra traffic. “We’ll custom-build a node” is not an option group. It is a sales conversation.
Windows vs Linux: separate products if the licence, image, and tickets differ — which they do. Reseller: a separate product line with separate terms. Do not hide reseller inside a VPS product because it was quicker.
Free trials and “first month $1” are fraud magnets unless you have checks and a reason. If you cannot review sign-ups, do not run a promo that invites card testing.
Product groups in the cart should match how a buyer thinks: Linux VPS, Windows VPS — not internal code names from your hypervisor. The cart is sales copy. Treat it that way.
| Decide on paper first | Then set in WHMCS | If you skip the paper |
|---|---|---|
| Three plans and who they are for | Products, groups, prices, cycles | You clone SKUs and confuse buyers |
| What unmanaged does not include | Welcome email and support copy | You live in CMS repair tickets |
| Unpaid invoice after N days | Overdue notices and suspend | You argue in email instead of policy |
| Acceptable use policy (AUP) breach | Terminate path you will actually use | Abuse sits on your IPs |
| Who you will not sign up | Fraud checks, manual review, KYC if needed | Chargebacks and spam campaigns |
Welcome emails: the first operational document
The welcome email is not a branding exercise. It is how the customer starts, where they get help, and what you will not do.
Include login path, a short “you are on unmanaged VPS” line if that is the product, support hours and channel, and a link to terms and AUP. If they need to point DNS, say so in one paragraph — not a 2,000-word guide in the email body.
Do not promise 24/7 if your window is not 24/7. The email will be quoted back to you.
Test the email with a real order, not a preview in admin. Merge fields that dump empty “Dear ,” are how you look unfinished on day one.
Cancellation and non-payment mail should be written while you are calm. Overdue sequences that threaten without a suspend date teach customers to ignore you. A date, a suspend, a terminate — in that order — is kinder than a month of vague warnings.
Fraud, payments, and who you let in
Open VPS sign-up on the public internet attracts stolen cards and people who want a node for a week of abuse. Your fraud settings are part of the product.
Decide: auto-provision after payment, or manual review for first orders. Manual review slows revenue. Auto-provision without checks speeds chargebacks. Neither is free. Pick based on ticket capacity, not based on “growth.”
Payment gateways: use what you can actually operate — disputes, refunds, payout timing. Your hosting company will likely take cards. Budget processor fees and dispute time into the cost stack.
Do not confuse “captcha on the cart” with a fraud program. Captcha stops some bots. It does not stop a human with a stolen card. Velocity rules, country mismatch, and a willingness to refuse the order matter more.
Document who on your team can issue refunds and credits. Unlimited courtesy credits from panic are a pricing policy you never meant to publish.
Tax: configure only what you have been told to collect
WHMCS will let you turn on tax rules that look official. That is not an opinion from a tax authority. It is a form.
Talk to an accountant or tax counsel about where you have nexus, what you sell (infrastructure vs something else), and what to show on invoices. Then configure that. Do not copy a YouTube walkthrough from another country.
If you are not ready for that conversation, do not pretend the checkbox is the conversation. Launching without tax settings you understand is a legal and accounting problem, not a WHMCS problem.
This article is not tax advice. The panel will not protect you if the rules are wrong.
Server provisioning: the path that must work before ads
WHMCS does not include Proxmox, Virtualizor, SolusVM, or any hypervisor by magic. You add a module. You test it.
The path is: paid order → service created → virtual machine exists with the right resources and IP → customer can log in → overdue invoice → suspend actually stops the virtual machine → terminate destroys or archives per your policy. If any step is “we’ll SSH it by hand,” you do not have automation. You have a panel that sends invoices.
Hand-provisioning a few early customers is acceptable while you learn. Advertising a self-serve VPS while you are still pasting passwords into email is not. Either sell a slower, assisted setup at a price that funds it, or finish the module.
Suspend is the test most founders skip. They test the happy order. They do not test the unpaid invoice at 02:00. Test suspend. Test unsuspend. Write down what the customer sees.
Backups and restores are not WHMCS features you can ignore because a module exists. Know where snapshots live and how a restore is requested. If restore is manual, price and staff it that way.
Buy the licence after the decisions are written
When the sheet is done — catalog, emails, fraud posture, tax instruction from a professional, provision and suspend path — buy the licence that matches how you will run. Do not buy the largest branded package because it felt serious.
Budget the annual renewal and paid modules in the cost stack. “We’ll add the module later” becomes a surprise margin hole.
Train whoever will click in admin. A panel with one person who understands invoices, and everyone else improvising credits, will leak money.
Other billing tools — without a tool war
WHMCS is common in hosting because the module ecosystem and the operator pool are large. It is not the only billing system. Other panels exist. Some companies build internal billing. Some use a simpler invoicing tool and provision by hand until volume justifies a panel.
Choose on: whether your hypervisor has a maintained module, whether suspend is reliable, whether you can hire or contract someone who already knows the tool, and whether the licence cost fits three plans of real customers. Do not choose because a Reddit thread declared a winner.
If you already know another panel well, that operational knowledge can beat a theoretical “industry standard.” If you know nothing, WHMCS is a reasonable default — after the catalog, not before.
I am not here to migrate your panel as part of a $199 or $499 session. I will tell you what to decide. Clicking it is implementation.
This week’s checklist before you install anything
- Three products written with prices, cycles, and who they are for.
- Welcome email draft, overdue copy, AUP link.
- Fraud posture: auto vs manual for first orders; who reviews.
- Written note from your tax person, or an explicit “not configured until we have that.”
- Provision, suspend, terminate on paper for your hypervisor.
- One test run on a staging licence or trial if you already bought — still do the paper first.
- Only then: production install, live gateway, ads.
If you are stuck between catalog and panel, a working session is cheaper than rebuilding products after you have live customers. Hosting Launch Call $199. Blueprint $499 (featured) with a concise written plan. Advisory $999 — blueprint plus three 60-minute sessions within 45 days. Implementation is not included.
Book through the consultation page. Fees are non-refundable once paid, except if I cancel and we cannot agree a new date.
Decide. Then install. Not the other way around.
Questions people ask
Do I need WHMCS to start a VPS hosting business?
You need billing, provisioning, and suspend. WHMCS is the usual tool. It is not the first decision — the catalog is.
When should I install WHMCS?
After you know products, cycles, gateways, welcome emails, fraud checks, tax treatment, and what happens on the hypervisor when an invoice is unpaid.
Does WHMCS include Proxmox or server provisioning?
Not by itself. You need a server module and a tested order-to-provision-to-suspend path.
What are alternatives to WHMCS?
Other billing panels and some custom stacks exist. Pick on modules, suspend reliability, and the team who will operate it — not on a forum argument.
Should I configure tax in WHMCS myself?
Configure only what counsel and your accountant have told you to collect. Copying another host’s tax rules is not compliance.
What belongs in the welcome email?
How to log in, where support is, what is unmanaged, and a link to AUP. Not a dump of every knowledge-base article you might write someday.
Will a consulting package install WHMCS for me?
No. Packages are strategy and a written blueprint where included. WHMCS installation and configuration are implementation, quoted separately if at all.
How does payment for consulting work?
Book through the hosting consultation page. Fees are non-refundable once paid unless I cancel and we cannot agree a new date.
Not legal or tax advice. Gateway, fraud, and tax settings have legal consequences in your jurisdiction.