White label Webflow development is an arrangement where an outside team builds a Webflow site that your agency sells, presents and supports under its own name. The client signs with you. The partner builds. Nobody on the client side needs to know who wrote the classes.
We have run this arrangement from the partner side for Web Tonic since 2025: 20 or more Webflow sites in twelve months, two to three weeks each, the largest a CMS with over 1,200 items. This guide is what we would tell an agency owner before the first project, including the parts that only matter in month three.
What a white-label partner does, and what the agency keeps
The split is cleaner than most agencies expect, because the work divides along a line clients never see.
| Work | Partner | Agency |
|---|---|---|
| Discovery, positioning, page map | Advises on CMS implications | Owns it |
| Design in Figma | Builds from it, or designs when asked | Owns it, or reviews the partner's |
| Webflow build, interactions, responsiveness | Owns it | Reviews on staging |
| CMS collections and content model | Owns it | Signs off the field list |
| Content entry and migration | Owns it when scoped | Supplies the content |
| QA across browsers and widths | Owns it, delivers a checklist | Spot-checks |
| Tracking, forms, integrations | Wires them | Supplies the accounts |
| Client calls and emails | Never, unless the agency asks | Owns it |
| Invoice, margin, contract | None | Owns it |
| Post-launch edits | On a retainer, under the agency's name | Decides what gets done |
The partner's job ends at a site your client's marketing team can run. The agency's job is everything the client can see, plus the judgement calls about scope. The arrangement breaks when either side crosses that line: a partner who emails the client directly, or an agency that forwards the client's Slack thread and expects the partner to decode it.
How Webflow's workspace rules shape the whole thing
White-label on Webflow is simpler than on WordPress for one reason: Webflow has built-in mechanics for exactly this handoff. They also decide how your contract should be written.
Workspace plans. As of October 2026, Webflow's Freelancer Workspace costs $16 a month billed yearly and includes 10 staging sites, one free client seat per site, client payments and free guest access in client Workspaces. The Agency Workspace costs $35 a month billed yearly and adds unlimited staging sites, three free client seats per site, site-level roles and publishing permissions. The partner builds on staging sites in its own Workspace; the plan it is on decides what happens at handover.
Site plans. The site itself needs its own plan to go live on a custom domain. Webflow's current site plans start at $15 a month for Basic and $25 a month for Premium, which adds the CMS, both billed yearly. Someone pays for this per site, and the contract should say who.
Transferring a finished site. Webflow's help centre is explicit: only Freelancer and Agency Workspaces can transfer a site with an active paid Site plan to a client's Workspace, and the client's Workspace must not be an Enterprise Workspace. The client accepts by email, and the site moves with its plan and connected custom domains, with no downtime. The partner, or the agency, then gets credit back for unused time on the plan. The client has to re-authenticate any third-party apps connected to the site, so the tracking and form integrations need a second look after the move.
The Enterprise trap. If the destination is an Enterprise Workspace, or the source Workspace is on a Starter, Core, Growth or Enterprise plan, the site must first be downgraded to the free Starter plan. Webflow warns that this causes downtime on a published site. For an enterprise client that means the handover is a planned cutover, not a button.
Staying on after handover. Once the client owns the site, they can add the partner or the agency back as a Workspace guest, free, as long as the guest holds a Freelancer or Agency plan. That is how a retainer keeps working without anyone holding the client's billing.
Client payments. The alternative to transferring is to keep the site in the agency's Workspace and bill the client's card for the Site plan through Webflow's client payments feature. The site never moves, the agency keeps control, and the client is not a member of the Workspace. This suits agencies that sell ongoing management; it suits badly when the client wants to own their asset outright, which is most B2B clients.
The seven handover artefacts
A white-label build is finished when these seven things exist, not when the site is published. We hand all seven to Web Tonic on every project, and the ones agencies most often skip are numbers four, six and seven.
- The design source. The Figma file with the components the build used, or the partner's own design system if it designed the site. Ownership transfers to the agency.
- The site, in the right Workspace. On the agency's staging site or transferred to the client's Workspace, with the Site plan on the agreed card. The partner holds no admin role once the project closes.
- The CMS model document. Every collection, every field, what it renders, which fields are required and why. A page on the agency's wiki, or a PDF the client's marketing lead can read in ten minutes.
- The page kit. A list of the reusable sections and which combinations make a new campaign page. Without it, the client's first new landing page becomes a ticket back to you.
- The QA record. Which browsers and widths were tested, what was fixed, what was deliberately left. Agencies that forward a QA record spend less time on "is this a bug" calls.
- The tracking map. Every form, event and integration: where it fires, where it lands, which account owns it. This is what the client has to re-authorise after a transfer, so it doubles as the post-transfer checklist.
- The walkthrough. A short recorded screen share under the agency's brand, plus a written editing guide. Clients ship their first page faster with a video than with a document, and they call less.
How partners price white-label Webflow work
There are three models in use, and the right one depends on how steady your pipeline is.
| Model | How it works | Fits when | Watch for |
|---|---|---|---|
| Per project | A fixed quote per site from a written scope | Pipeline is lumpy; two sites one month, none the next | Change requests priced one by one; scope must be written |
| Monthly capacity | A retainer buys a number of days or sites per month | Three or more builds a month, or a steady edit load | Paying for unused days in a quiet month |
| Hourly overflow | A rate card, billed on time used | Occasional overflow, rescue work, odd integrations | Hard to resell at a margin without an estimate per task |
Published numbers are rare, which is itself a signal. E2M, one of the larger white-label shops, lists month-to-month plans from $1,299 to $9,999 a month with an NDA and a non-solicitation clause on every engagement. Clickx publishes a per-project model with no contracts or minimums and says it scrubs identifying metadata from files. Most Webflow-specific partners, including us, scope per project and do not publish a rate card, because a four-page site and a 1,200-item CMS migration are not the same job.
Two things decide whether the margin holds. First, whether the partner's quote includes QA and the seven artefacts, or whether those arrive as extras. Second, how change requests are handled: a partner that prices every "small change" separately will eat the margin the agency planned on, and a partner that absorbs them all will cut corners somewhere you cannot see.
Confidentiality, metadata and the places the partner leaks
An NDA covers what people say. It does not cover what a site says about itself. Before any white-label handover, someone has to check these.
- Form notification emails. Webflow resets them on transfer, but on a client-payments site they stay. A partner's address in the notification list is the most common leak we see.
- Site name and Workspace name. Both appear in the Dashboard the client logs into.
- Code comments and class names. A partner's name in a custom code embed, or a class prefix that matches its studio, survives every transfer.
- Asset file names. Exported Figma assets carry the exporter's naming. Rename before upload.
- Made in Webflow and Creator Credits. Webflow requires removing a site from Made in Webflow and clearing its Creator Credits before transfer. Agree in the contract that the partner will not showcase the site under its own name.
- Loom and screenshot branding. The walkthrough video is recorded on the partner's account unless the contract says otherwise.
- Git and build tooling. If the site uses custom code deployed from a repository, the commit author is visible to anyone who gets access.
Agreeing a visibility level up front saves this list. We run three with partner agencies: silent, where none of the above carries our name; co-delivery, where we join calls as the agency's development team; and credited, where the agency is happy to name us. Most B2B agencies choose silent for the first project and co-delivery once the client has met the team.
Four traps that look like good deals
The partner who is really one person. A single freelancer presented as a studio has no cover for illness, holidays or a second client's emergency. Ask who else touches the build, and what happens in week three if the lead developer is unavailable.
The quote without a page count. "Webflow site, $X" is not a scope. A scope lists pages, templates, collections, integrations and the number of review rounds. Everything outside it is a change request, and the quote should say what those cost.
The partner that wants the client's Workspace from day one. Building directly in the client's Workspace saves a transfer but gives the partner a seat the agency did not approve, and makes the agency's role visible in the activity log. Build on staging, transfer at the end.
The retainer with no definition of a day. Capacity retainers work when "a day" is defined as hours, deliverables or tickets. Undefined, the agency and the partner will disagree about it by the second month.
A 30-day plan for the first white-label project
The first project is the audition, for both sides. Run it like this.
Days 1 to 5: scope and contract. Written scope with page count, templates and integrations. Contract covers IP ownership, visibility level, NDA, non-solicitation, who pays the Site plan, and the change-request rate. Agree on the seven artefacts by name.
Days 6 to 15: build on staging. The partner builds in its own Workspace on a staging site. The agency reviews at the end of each week, in one call, with one person who can say yes or no. Feedback goes in one document, not in Slack threads.
Days 16 to 22: QA and content. The partner runs QA across widths and browsers and delivers the record. Content entry or migration happens here, with the CMS document written alongside it.
Days 23 to 27: handover. Transfer to the client's Workspace, or set up client payments. The client re-authorises apps against the tracking map. The walkthrough is recorded under the agency's brand.
Days 28 to 30: review. Agency and partner go through what slipped, what the client asked for that was not in scope, and what the second project's quote should include. The decision at the end of day 30 is whether this is a one-off or a bench.
If you would rather see how this looks from the partner's side before you choose one, the Web Tonic case study on this site is the twelve-month version of the plan above, and our white-label service page explains how we scope it.
