Before you start
Prepare your business activity, service families, approximate client count and support capability. Do not send client lists, passwords or third-party personal information in a sales enquiry.
Choose the commercial relationship
An agency may administer services bought directly by its clients. A reseller may invoice a service under its own responsibility within the supplier agreement. A referrer directs a prospect without operating their hosting. These models differ in billing, permissions and support. Describe the arrangement you want rather than asking only for a reseller price. The public referral route is separate from a professional resale agreement and does not establish the same obligations.
Define the product you can support
List websites, domains, email, VPS and game hosting separately. A VM does not necessarily include an administration panel or application maintenance. For WordPress, decide who updates plugins; for games, decide who manages resources and backups. Do not copy another provider’s promises into your own offer. Its scope must match verified functions and the work your team can deliver. Check the exact service rather than assuming every family shares identical tools.
Plan first-line support and escalation
Define which access, configuration, incident and billing questions your team handles. When escalating an incident, include the affected service, time, symptom and steps already tried, without passwords. Agree applicable channels and support hours. Network protection is not application support. Do not advertise a guaranteed response time unless the parties have agreed it. Clear diagnostic information is more useful than passing on an entire customer conversation containing unnecessary personal details.
Separate clients and permissions
Avoid sharing one administrator account across several customers. Record the service owner, authorised people and exit procedure. An agency managing several applications should assess access isolation and maintenance before combining databases or deployments. Buying additional VPS does not automatically solve that organisation: someone must administer them. Keep secrets outside tickets and collect only necessary information. Review access when a staff member or customer leaves, and make recovery ownership clear before an incident occurs.
Account for renewal and recovery
Compare supplier cost, billing term, renewal, licences, options and support time before setting a retail price. A guide cannot guarantee your margin. Confirm backup retention, coverage and the process for returning files and databases. A local copy is not protection against every failure. Plan the end of the relationship as carefully as onboarding: identify the domain holder, access rights and recoverable data. A provider’s sales headline does not replace that written operational agreement.
Prepare a useful partnership enquiry
The CubixServ Resellers page lets you describe activity, service family, estimated client count and timing, then prepare an editable message. Use the commercial range pages to check current characteristics. Consider Linux VPS only when you can maintain the operating system. Terms, responsibilities and any supporting tools are reviewed before agreement. The form does not create a reseller account, take a payment, change stock or provision infrastructure. Direct contact remains available if the short assistant does not suit your situation.
For your situation
| Situation | Next check |
|---|---|
| An agency with several websites | Agree maintenance and access separation before choosing shared hosting or independent services. |
| An IT or hosting business | Describe your first-line support and the information needed for technical escalations. |
| A straightforward recommendation | Use the public referral route and distinguish it from a resale contract. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.