Choosing a white label web development agency is a hiring decision with none of the usual signals. There is no CV, the portfolio belongs to other agencies by design, and the partner's job is to be invisible. So the selection has to run on questions, and on knowing which answers mean no.
We sit on the partner side of this arrangement for Web Tonic, where we have built 20 or more Webflow sites in a year under their name. These are the fourteen questions we would want an agency to ask us, grouped by what each one protects: your client, your margin, your schedule and your exit.
Questions that protect the client
1. Will you sign our NDA before we share client details?
The disqualifier is hesitation, or an insistence on the partner's own template instead of yours. Guides on both sides of this market agree: the NDA comes first, it should prohibit direct contact with your clients, and it should cover the existence of the white-label relationship itself, not only the project files. A partner who offers the NDA before you ask has done this before.
2. Who, by name, writes the code on our projects?
The disqualifier is "our team". You want a name, whether that person is an employee or a contractor, and who reviews their work. Of the seventeen providers we checked for a separate piece, fewer than half name anyone who touches a build. The ones that do tend to be the ones that stay.
3. What happens in week three if that person is unavailable?
The disqualifier is a pause. A real partner has a second developer who has seen the project, a shared staging site, and a written handover inside the team. A single freelancer presented as a studio has none of those, and the honest ones will tell you so.
4. Will your name appear anywhere the client can see?
The disqualifier is "no" without a list. Webflow resets form notification settings on a site transfer, but a site that stays in the agency's Workspace keeps them, and a partner's address in the notification list is the most common leak we see. The list the partner should be able to recite: form notifications, site and Workspace names, code comments, asset file names, Made in Webflow credits, the recorded walkthrough's branding and, if there is a repository, the commit author.
Questions that protect the margin
5. Is the quote tied to a written scope with a page count?
The disqualifier is a price without a scope. "Webflow site, $4,000" is a number, not a quote. A scope lists pages, templates, collections, integrations and the number of review rounds, and it defines what counts as a change request.
6. What is the change-request rate, in writing?
The disqualifier is "we'll work it out". Every project generates "can we also" requests, and the margin the agency planned on is decided by how they are handled. A rate per hour or per page, agreed up front, lets the agency quote the client the same day instead of absorbing the cost.
7. Does the quote include QA and the handover artefacts?
The disqualifier is finding out after launch. The seven artefacts a white-label build should end with are the design source, the site in the right Workspace, a CMS document, a page kit, a QA record, a tracking map and a recorded walkthrough. Ask whether they are in the quote. A partner that charges extra for the QA record is telling you QA is optional on its side.
8. Who pays for the Site plan and the Workspace?
The disqualifier is confusion. On Webflow, the Workspace plan sits with whoever builds, at $16 a month billed yearly for a Freelancer Workspace or $35 for an Agency Workspace, and the Site plan sits with whoever owns the live site, from $15 a month billed yearly for a site without a CMS and $25 with one. The contract should name the card for each, because Webflow's client-payments feature and its site-transfer feature produce different ownership outcomes.
| Provider type | What is published | Example |
|---|---|---|
| Template-package shops | Fixed per-project tiers | $1,499 to $4,699 per site for 5 to 15 template pages (White Label Agency) |
| Hours-per-day retainers | Monthly plans by daily hours | $729 to $2,157 a month for 1 to 6 hours a day (KrishaWeb) |
| Capacity retainers | Monthly plans, month to month | $1,299 to $9,999 a month (E2M, per directory listing) |
| Webflow-specialist studios | Nothing; quote per project | Always Fresh, Appsrow, Cheit Group, Octo |
A missing rate card is normal in this market. Use it to ask a sharper scope question, not as a red flag on its own.
Questions that protect the schedule
9. Which Workspace do you build in, and how does the transfer work?
The disqualifier is "we'll build in the client's account". That saves a transfer but gives the partner a seat the agency never approved and puts the partner's activity in the client's log. The clean pattern is staging in the partner's or agency's Workspace, then a transfer. Webflow lets Freelancer and Agency Workspaces transfer a site together with its paid plan and custom domains to a client's Workspace, with no downtime, once the client accepts. A partner should know that an Enterprise destination forces a downgrade to the free plan first, which takes a published site offline during the cutover.
10. How many review rounds are in the quote, and in what form?
The disqualifier is unlimited rounds. Unlimited sounds generous and means the schedule has no end. Two rounds, in one document, reviewed on one call with one person who can say yes, is the shape that holds.
11. What is your capacity next month, in sites?
The disqualifier is "whatever you need". Capacity is finite, and a partner who will not put a number on it is planning to subcontract your project onward. Ask what happens to your second site if a bigger client's rush job arrives.
Questions that protect the exit
12. Who owns the code, the design files and the CMS structure, and when?
The disqualifier is "as licensed" where you expected "assigned". The standard clause is that everything built for the project transfers to the agency as work for hire on final payment, with one fair exception: the partner's reusable base components stay theirs and you receive a licence to use them in the delivered site. Vague ownership language is fixable; a refusal to fix it is not.
13. Can we see the CMS document and QA record from a past project?
The disqualifier is a portfolio instead. Screenshots prove the partner can make a site look like a Figma file. The CMS document proves it can model content the client's marketing team will still understand in year two, and the QA record proves the testing happened. Names can be redacted; the structure cannot be faked after the fact.
14. What are the termination terms?
The disqualifier is reading them after signing. Month-to-month retainers with no minimums exist, and so do twelve-month commitments with a notice period. Neither is wrong, but a partner that buries the exit terms is a partner that expects you to need them.
The order to ask them in
Agencies tend to open with price. Open with questions one, two and twelve instead: the NDA, the named developer and the ownership clause. Those three are the ones a partner cannot improve on a second call, and they filter the list faster than any rate comparison. Price comes once the scope exists, because a scope is the only thing a price can be compared against.
The fourth question to ask early is the one about the Workspace, because the answer tells you whether the partner understands Webflow's transfer mechanics or has only ever built in a client's account. Our white-label service page describes how we answer each of the fourteen; the Web Tonic case study on this site is what the answers look like after a year.
