For an agency, choose the account and maintenance arrangement before the host. WP Engine is worth evaluating for its site-transfer and development workflows, Cloudways Flexible for resource allocation across a portfolio, and Kinsta for a consistent managed WordPress workflow. None automatically makes a maintenance retainer profitable.

First decide who owns the hosting

Decide whether the client will own and pay for hosting or whether your agency will provide it within a retainer. You can provide a professional service under either arrangement, but the billing, permissions, and eventual handoff differ.

Arrangement Advantage Responsibility to settle
Client owns the hosting account Client pays directly and can retain the account when the agency changes Your access, service scope, and who can approve changes
Agency owns the account and resells hosting Consistent operations and one supplier relationship Billing, capacity, backups, and an exit process for every client
Separate accounts or servers for demanding clients Easier cost attribution and separation Additional administration and configuration

Document who gets renewal notices, who can contact support, and who authorizes a restore. Do not share an owner login with every contractor. Use roles appropriate to the work and remove access when someone leaves.

What each platform contributes

WP Engine: evaluate its current site-transfer process, environments, and permissions. These can suit an agency that builds sites and hands them to client-owned accounts. Confirm any separately sold agency or billing products; a generic hosting subscription is not evidence of a white-label invoice portal.

Cloudways Flexible: evaluate how you would divide clients across servers and how those servers would be maintained. Cloudways has team and transfer capabilities; it is inaccurate to describe it as having no agency tools. A whole-server transfer is useful for a single-client server but does not separate one client from a shared portfolio.

Kinsta: evaluate the MyKinsta workflow with the people who manage releases and support. Judge it by the tasks you can repeat reliably across accounts and sites. A higher invoice may be acceptable if it reduces work you otherwise pay for, but the dashboard alone does not prove that saving.

Calculate margin per paying client

Start with revenue from hosting and maintenance, then subtract hosting, paid services, licenses, and labor. Do not treat the full retainer as hosting margin when it also includes content edits or support.

An illustrative ten-client portfolio charges $60 per client monthly, producing $600. Hosting and tools cost $180; four hours of maintenance at $50 cost $200. That leaves $220 before other business costs. If maintenance takes eight hours, it leaves only $20. The provider has not changed; the workload has.

The same principle applies to plan slots. A plan with twenty slots and ten paying clients should be divided by ten for current margin, not twenty. For rates and comparison arithmetic, use the pricing guide.

Group sites by workload and consequence

Site count is an inventory measure, not a capacity estimate. Record which clients run stores, scheduled imports, memberships, large media libraries, or frequent deployments. Consider separating a demanding application from lightly used brochure sites.

Separation is not automatically redundancy. Two servers can still depend on the same account, region, or external service. Write down what happens if an account is inaccessible or a server fails, and keep the recovery instructions somewhere the team can still reach.

Pilot the whole client lifecycle

Before moving the portfolio, take one representative site through these steps:

  1. Onboard the site, its domains, integrations, and required access.
  2. Create staging and make a small approved release.
  3. Check forms, customer actions, scheduled jobs, and email.
  4. Restore a backup into a safe environment and verify the result.
  5. Rehearse a client departure, including files, database, DNS, credentials, and billing.

Record actual time and anything requiring provider support. The developer guide covers release requirements; the migration guide covers the live cutover.

Which arrangement should you choose?

Choose WP Engine if its handoff and release process fits your team and the appropriate subscription makes financial sense. Choose Flexible when you have technical ownership of the server arrangement and useful portfolio economics after labor. Choose Kinsta when its managed workflow is the one your team can operate confidently at the quoted cost.

A split portfolio can be sensible: keep a demanding store separate while standardizing simpler clients elsewhere. Only add another platform when the benefit exceeds the burden of maintaining two procedures. Once you have tested the process, review the matching provider offer rather than moving every client based on a headline cost per site.