How to manage multiple client websites

Work out your real surface area first

Before you change platforms, count what you are already carrying. Every client site has a login, an update schedule, a backup, a domain renewal date, an SSL certificate, a contact form that can stop sending without telling anyone, an invoice, and a person who asks for things. Twelve sites at six moving parts each is seventy-two items to track, and none of them announce themselves until they break.

Put it in one spreadsheet before you decide anything. One row per client, with these columns:

• Platform and plan, what it costs, and the renewal date
• Who pays the vendor: your card or theirs
• Domain registrar, expiry date, and whose name the account is in
• DNS and business email provider
• Where backups go, and the date you last tested a restore
• Integrations that would break on a move: payments, booking, analytics, ad pixels
• Who at the client can log in, and what they are allowed to do
• Open requests, and the hours you spent on them last month

Most agencies find two or three unpleasant surprises in that exercise: a domain sitting in a former employee's personal account, a client paying for a plan three tiers above what they use, and at least one site with no backup anyone has ever restored.

The four setups agencies actually use

Every arrangement is a version of one of these four. The right answer depends less on features than on who you want holding the card and how often clients log in.

A separate account for each client

Each client has their own subscription in their own name and you are added as a collaborator. It is the simplest arrangement and the one lawyers like: the client owns the asset, pays the vendor directly, and nothing is held hostage if the relationship ends.

The cost is operational. You have as many logins as clients, two-factor codes land on client phones at the worst possible moment, there is no single screen showing which sites need attention, and you spend part of every month chasing expired cards that are not yours to update.

Both of the big design platforms support this well. On Wix you can add the client as a collaborator with specific permissions, where they can edit but cannot delete or transfer the site, or transfer full ownership to them. On Webflow, client payments put the client's card on the site plan while you keep working in it.

Choose this when clients are larger than you, when procurement requires the asset in the client's name, or when you genuinely only have a handful of sites.

One agency account with every project inside it

Here everything lives in your workspace: one dashboard, one card, team seats for your staff, consistent setup across sites. For a small team doing all the work themselves, this is the least friction per site.

Three things to watch. First, one account is now the keys to every client, so per-seat roles and two-factor authentication stop being optional. Second, your card carries the churn risk, because a client who stops paying you does not stop the platform billing you. Third, clients have no access at all unless you grant it, which is fine until someone wants to change their opening hours on a Sunday. Webflow, for instance, gives clients the content editor role by default and lets you widen permissions in site settings.

Handover from this setup is usually fine at site level. Webflow lets you transfer a site with an active plan to the client's own workspace and card, with a prorated credit for the remainder of the cycle coming back to you. Wix sends a transfer invite the recipient has three days to accept, you choose whether the plan, domain and premium apps travel with it, and you can stay on as co-owner afterwards. Moving an entire workspace to another account was still only a posted feature request when we checked, so plan around the site-level flow.

WordPress multisite and the blast radius problem

Multisite is excellent for what it was designed for: one owner running related sites on a shared design and plugin stack, such as a franchise with a site per location, a multi-brand retailer, or a school with departmental sites. If that is your situation, use it.

For unrelated clients who simply happen to share a web designer, the trade-offs land badly:

• Shared codebase, shared fate. One bad update, one incompatible plugin or one compromised component reaches every site in the network at the same time.
• Install rights sit at network level. Individual sites can activate plugins and themes but not install them, so every specialist request from one client becomes a decision that affects everyone.
• Restores are not per-site in the usual sense. The network shares a database, with separate tables per site, so rolling back one client is far more delicate than restoring a standalone install.
• Conflicts have no clean fix. When one client needs a plugin another cannot tolerate, there is no tidy answer on a single network.
• Leaving is a rebuild. Pulling one site out later means exporting content, rebuilding tables and fixing paths, not restoring a backup somewhere else.

Most agencies that want to stay on WordPress end up with separate installs plus a central management dashboard such as ManageWP, MainWP or WP Umbrella. You get one list of update statuses, backups and uptime across the fleet without merging your clients' infrastructure. ManageWP's own pricing page offers core features free for every site, with premium add-ons billed per site per month and bundles for larger fleets. If you are weighing this against a hosted builder, our comparison of an AI builder versus WordPress goes through the maintenance load in more detail.

Client sub-accounts under an agency dashboard

This is the shape most agencies settle on past ten sites. You have one parent account. Each client is a sub-account with its own plan, its own limits and its own users, and you see them all in one list. When a client asks for something, you open their account and do it.

The established platforms do this properly. Duda separates team members, who can reach every site in the organisation, from client accounts, which are granted access site by site. It offers predefined roles such as site editor and blog contributor plus custom roles, an audit trail showing when clients log in and what they changed, white-label branding across the domain, login screen and help content, scheduled client billing through your Stripe account, and the option to unpublish a site automatically when a payment is missed. GoHighLevel works through sub-accounts too, with its entry plan capping how many you get and the next tier removing the cap. At the time of writing (October 2026) GoHighLevel lists Starter at $97, Unlimited at $297 and Agency Pro at $497 per month.

The honest trade-off is lock-in. Your whole operation now depends on one vendor's roadmap and pricing, and leaving means rebuilding client sites rather than moving files. Test the export path before you migrate twenty clients in. If you are shortlisting, our rundown of white-label client portals for agencies and the Duda alternatives for agencies comparison cover who suits which size of shop.

The access model to insist on

Platform features change, but these capabilities are what actually decide whether twenty clients feel manageable. Check each one in a trial before you commit, not from the marketing page.

• Per-client plan limits. You set how many websites, team members and features each client gets, so a client on your basic package cannot quietly switch on things you are not charging for.
• Sub-users inside each client account. The owner, the office manager and the intern should not share one password.
• Roles that actually restrict. Content-only access for clients who should edit text but never touch layout or payment settings.
• Log in as the client. Nearly every request is quicker to fix than to explain. Without this you spend your week writing instructions.
• Suspend without delete. The civilised way to handle non-payment: access pauses, nothing is destroyed, everything comes back when they pay.
• An audit trail. Who logged in, who changed what. This settles the "the site was fine yesterday" conversation in thirty seconds.
• Your brand on the client-facing panel. Login page, notification emails, invoices, ideally on your own dashboard domain, so clients associate the tool with you.
• Your own sending domain. Client notifications that come from your address rather than a vendor's.
• An API and single sign-on if you plan to pass more than fifty clients, so account creation and login links can be automated.

On your own side, add two things: per-seat accounts for your team rather than one shared login, and a written note of which staff member can reach which clients. Offboarding a contractor should take one minute, not an afternoon of password changes.

Billing: whose card is on file

This single decision drives most of the admin pain, so make it deliberately. There are three models.

1. The client pays the vendor directly. Lowest risk, cleanest exit, zero platform margin for you. You invoice only for your work.
2. You pay the vendor and resell at your own price. One bill for the client, recurring margin for you, and all of the churn risk on your card. Workable if your packages are priced for it and you cancel promptly when a client leaves, which is the model our guide to reselling websites to clients walks through.
3. The platform bills the client on your behalf. Payments go to your own Stripe or PayPal account, the platform handles the recurring charge, and suspension can be automatic when a card fails. This is the best of both when the platform supports it properly.

Whichever you choose, separate the platform fee from your retainer in the client's mind. Hosting and tooling at cost plus a margin is one line. Your time, updates, content changes and reporting is a different line, and it is the one that should grow. There is more on structuring that in our notes on web design pricing packages and monthly website care plans.

Handover when a client leaves

Every client eventually leaves, moves agency or gets acquired. Decide what happens then while everyone is still friendly, during onboarding, and put it in the contract in plain language. The checklist:

1. Domain. Register it in the client's name, or in your account with a written promise to transfer on request. This is the item that causes the ugliest disputes, and it is the easiest to get right.
2. Content and media. Keep an export schedule, monthly is enough, so text, images and product data exist outside the platform.
3. Documentation. One page per client: DNS records, email provider, analytics and ad accounts, payment gateway, booking tool, who holds which login.
4. Plan continuity. Name the plan the client moves onto and who pays for it from the handover date. If the platform supports transferring a site with its active subscription, use that rather than cancelling and hoping.
5. Expectations about design. Be explicit that content and domain move, but a layout built on one platform does not transfer to another. A client switching platforms is paying for a rebuild, and they should hear that from you early rather than from their next agency.
6. Notice period. Thirty days either way, with the exit steps listed, so nobody improvises under pressure.

A routine that still works at fifty sites

Tooling only helps if the work has a rhythm. The agencies that cope at scale all do roughly this:

1. Weekly. One maintenance window, same day each week. Run updates, scan the backup report, check uptime alerts, and submit a test enquiry on every site that depends on forms. Silent form failures are the most common complaint clients discover before you do.
2. Monthly. Pick one client at random and actually restore their backup somewhere safe. An untested backup is a rumour. Send reports, raise invoices, and clear anything older than thirty days from the request queue.
3. Quarterly. Review domain and SSL expiry dates for the next six months, audit plugins and integrations nobody uses, review who still has access on both sides, and offboard dormant clients instead of carrying them.

One more rule matters more than any tool: every request goes into one queue. Not personal messaging apps, not your mobile, not a colleague's inbox. Route website enquiries and client requests into a single system so nothing depends on one person remembering, which is the argument our guide to a CRM for a web design agency makes in practice.

How WebNewBiz handles client accounts

WebNewBiz is built around the sub-account model described above, with white-label for agencies. You create each client account, put it on a plan with limits for websites, team members and features, and add sub-users inside it. You can suspend a client without deleting anything, and you can log in as a client to do the work yourself, which is the agency-managed route, or leave them to edit their own site, which is self-serve. Clients log into a panel branded as your agency, including the login page, invites, notification emails and invoice PDFs, on your own dashboard domain such as app.youragency.com, and you can send email through your own SMTP.

Billing works on your terms. You set your own packages, recurring, one-off or free, on weekly, monthly, quarterly or yearly cycles, with an optional setup fee and a choice of currencies, list them on your own storefront page, and connect your own Stripe or PayPal account so client payments come to you. For platforms that want to offer websites inside their own product, there is a REST Partner API for creating sites, generating single sign-on links and receiving webhooks. Team seats come with role-based access, plus priority onboarding and a dedicated account manager.

Client sites are built the same way as any other WebNewBiz site: describe the business, the AI drafts the pages and copy, then edit by chatting to the Copilot. Depending on the plan you sell, the client gets an online store, the AI CRM with lead scoring, deals, tasks and invoices that chase themselves, and an AI funnel builder. Agency pricing is not published, so you have to ask us for it.

The honest limits: WebNewBiz is younger and smaller than Duda, GoHighLevel or Webflow's agency programmes, with a smaller app ecosystem and community than Wix, Squarespace or Shopify. There is no public agency price list. The AI first draft still needs your own edits, photos and facts. And a site cannot be exported as files to another host: content and the domain move, but the layout gets rebuilt. If you want to see the client-facing plans for context, they run from $1 for the first month, then $9 for Lite up to $199 for Ultimate, with the CRM starting on Growth at $79. There is a related write-up on white-label CRM for agencies if the CRM side is what you are weighing.

Quick answers

How many client websites can one person realistically manage?

With a central dashboard, a weekly maintenance window and clients trained to send requests to one inbox, one person can keep on top of roughly 20 to 40 simple sites. Without those three things, it usually falls apart somewhere between 8 and 12, because the work is not building, it is remembering.

Is WordPress multisite a good idea for client sites?

Usually not for unrelated clients. Multisite suits one owner running related sites on a shared design and plugin stack, such as a franchise or a multi-location business. For separate clients, the shared codebase means one bad plugin or a compromise can reach every site, only the network super admin can install plugins and themes, and pulling one site out later is an export and rebuild rather than a restore.

Should the client's card or my card pay for the platform?

If you want clean handover and no cash-flow risk, put the client's card on the plan and charge separately for your work. If you want margin and a single relationship, pay the vendor yourself and resell at your own price, but price in the churn risk and never let your platform bill exceed what you have actually collected.

What is the single most important permission to have?

The ability to log into a client account and do the work yourself, with an audit trail. Almost every support request is faster to fix than to explain, and without that access you spend your week writing instructions. Suspend without delete comes a close second, because it is how you handle non-payment without destroying anything.

What happens to a client's site if they leave?

It depends on what you agreed at the start. The domain should already be in their name or transferable. Content and media should be exportable. On most builders the plan and site can be transferred to the client's own account, but the layout itself does not move to a different platform, so a client moving away is rebuilding. Put all of this in writing during onboarding, not during the argument.

Do I need white-label, or is my own branding enough?

White-label matters when clients log into a dashboard regularly, because an unfamiliar vendor name invites them to wonder what you are charging for. If clients never log in and you do all the work, white-label is a nice-to-have and you can spend the budget elsewhere.

Related guides

• Duda vs WordPress for agencies: updates, costs and client editing compared
• How to scale a web design agency without doubling your hours
• The best website builder for freelancers: 7 options compared

Where to start

If you are past ten clients and the spreadsheet exercise above was uncomfortable, the next step is a conversation rather than a signup. Talk to us about white-label and we will walk through your client list, the access model you need and what the agency pricing looks like for your volume.

If you would rather poke at the product first, the AI website builder is the same tool your clients would use, and you can start for $1 for the first month at builder.webnewbiz.com/register. You can also try the free AI Website Preview, which designs a homepage from one sentence, which is a quick way to see what a client's first draft would look like before you commit to anything.