Keep client boundaries understandable.
Start with a list of websites, client owners, technologies and critical services. Decide which clients need separate accounts, databases, credentials or server environments. A convenient central login should not become the only way to understand who can change an individual site.
Consider the effect of a compromised website or an unusually busy campaign on other clients. Account limits, application separation and access controls should fit the risk and workload. Larger or more sensitive clients may justify their own VPS or a dedicated arrangement.
Define the experience you will resell.
Agree which organisation contracts with the end customer and who receives technical requests. For a white-label requirement, specify the customer-visible names, control panel, notifications and support handoff you need. Those details belong in the proposal alongside the infrastructure.
Document what your agency supplies: content changes, application maintenance, domain administration, email or advice. Distinguish those services from the hosting scope so a website issue reaches the right team without the customer repeating their problem across several channels.
Size a portfolio, not an average site.
A portfolio can contain many quiet sites and a few resource-intensive ones. Share storage, database usage, peak activity and scheduled tasks for the busiest applications. Ask how account limits and aggregate limits interact, and how a single client can grow without disrupting the rest.
Include staging copies, media libraries and backup retention in capacity estimates. Clarify how additional sites, licences, transfer and management work are charged. Review the portfolio when major campaigns or new ecommerce customers change its usage pattern.
Make launches and departures repeatable.
Use a checklist for DNS ownership, source access, destination testing, certificates, forms and mail routing. Record who approves a launch and how a rollback would work. Client-specific requirements should remain visible after the original developer has moved on.
An exit process is equally useful: decide who can request an export, which files and databases are supplied, and how access is removed. Keep licence ownership and domain control clear so a client handover does not depend on informal knowledge.
