Delivering client websites under your own brand

What white-label covers, exactly

It helps to be precise with clients, because "white-label" gets used loosely. On Anticode, sites on the free plan carry a small "Made with Anticode" badge; paid plans drop the badge. The Agency plan goes further and removes Anticode branding from client sites altogether, so the published pages on a client's own domain show only the client, plus your agency's credit if you add one. That's what a white label website builder for agencies should mean in practice.

It covers the published sites, not your tools. The dashboard where you build, the review links you send for feedback and the sign-in screens are Anticode's. Tell clients that plainly at the start rather than letting them discover it: most don't mind which tool you use, but they do mind being surprised.

Setting up the delivery pipeline

1. Create the Agency workspace and invite your team. Owners and admins invite and remove people; members build, edit and publish but can't delete projects or take sites down. Most agencies keep two admins so leave and holidays don't block anything.
2. Agree a project naming rule. Client name first, then site purpose ("Harbour Dental: main site", "Harbour Dental: Invisalign campaign"). With many projects in one workspace this matters more than it sounds; see managing multiple client websites.
3. Build each site from a brief. The Architect asks up to three questions that change the build and shows a short plan before anything is built. Paste the client's brief or their old site's link; links are read once and summarised into the brief.
4. Collect feedback through review links. The client opens the current preview with no account and leaves comments tied to sections. Links expire after 14 days by default and can be revoked.
5. Connect the client's own domain. Custom domains are verified with a CNAME or TXT record and the certificate is issued automatically. Ask for DNS access early; it's the step that most often stalls a launch.
6. Route the client's form submissions with care. Connectors belong to the workspace, not the project: each enabled one receives submissions from every site in it, labelled with the site's name. So don't connect one client's Slack or CRM directly. Send everything to a webhook in your own automation tool and route by site name, or have your team triage leads as part of the service.

The business decisions Anticode doesn't make for you

Client access

Do clients get a seat in your workspace, or send changes through you? Seats are shared with your own team, and a client as a member can publish. Many agencies keep clients out of the workspace and handle edits as part of a care plan.

Billing

Anticode bills the agency for its plan (see pricing). What you charge clients, and whether you itemise hosting, builds and edits, is your decision and your invoice. Builds are charged against a daily and weekly allowance by what they actually cost, and each build has a receipt, which helps when you price change requests.

Support

You're the first line. Clients email you, not Anticode. Decide your response times and what's included before the first site goes live.

Ownership

Everything in the workspace belongs to the agency's account. If a client leaves, the usual routes are an HTML or Next.js export, or a rebuild in their own account. Put this in your contract.

A sensible client contract clause set

• Who owns the domain (the client, always) and who owns the build account (the agency).
• What the monthly fee includes: hosting, a number of edits, form routing, a check of enquiries and analytics.
• What happens if the client leaves: an export of the site's code within an agreed time, and what it does and doesn't include.
• That the Privacy Policy and Terms Anticode writes for each site are a starting point the client must review, not legal advice.

What can go wrong

Three problems recur. Clients forward review links internally and comments arrive from people the brief never mentioned; make a fresh link per round and revoke old ones. Enquiries pile up in the agency's dashboard because nobody routed them to the client, or one client's channel receives another's because a connector was added to the whole workspace; set routing by site on launch day and send a test. And margins quietly erode when every "small change" is a full rebuild; agree in the contract what a change is, and use change requests in words for the small ones, which update the existing build.

How you know it's working

Launches don't stall on DNS, because you ask for access at kickoff. Each client's enquiries land somewhere they look. Your edits per client per month are predictable enough to price, and nobody on the client side has asked what the software is, or they've asked and the answer didn't matter.

Limits worth knowing

• White-label covers published sites only. The dashboard, review pages and sign-in remain Anticode's.
• No client billing inside Anticode. It doesn't invoice your clients or split costs by client.
• No client-only role. Anyone in the workspace is an owner, admin or member.
• One payment link per workspace. Buy buttons on every site open the same checkout, so clients who sell need their own account or a different setup.
• No transfers between accounts. Plan the exit route (export or rebuild) before you need it.

Questions people ask

Do client sites on the Agency plan show any Anticode branding?

No. The Agency plan is white-label: client sites carry no Anticode branding. Other paid plans remove the badge; free sites show a small Made with Anticode badge.

Can I use the Team plan for client work instead?

Yes, Team is a shared workspace with seats and no badge on paid sites. Agency adds its own allowance and seat count and full white-label for client sites. Compare them on the pricing page.

Can each client have their own domain?

Yes. Each site can be published to its own domain on a paid plan, verified by a CNAME or TXT record, with the certificate issued automatically.