Dardo
ENESPT
ENESPT

White-label web design and development for agencies

White-label web development means a studio builds the websites your agency sells, under your agency's name. Dardo does it for design and marketing agencies that need build capacity: we work from your Figma files inside your tools, keep our name off the work, test each build before your team sees it and assign the copyright to your agency in writing.

By Dardo editorial team8 min read
Get a proposalMessage us on WhatsApp
Dardo / Editorial illustration
On this page

What our white-label web development includes

A white-label engagement covers the build and everything that must happen before your team shows it to a client. Each project's proposal marks what's in scope.

  • Front-end build from your Figma files, or design and build when your designers are fully booked
  • Astro, Next.js, Webflow or Framer; WordPress sites you already run, maintained after an audit
  • Work in your repository, Webflow Workspace or Framer project, with staging on your accounts
  • A written QA report before your review
  • Handover notes and editor training under your agency's name
  • Maintenance of launched sites, billed to your agency

Builds meet the standards of our web development service. Platform trade-offs are on our Webflow development and Astro development pages, and our website maintenance plans can run behind your brand after launch.

Is white-label development right for your agency?

It fits an agency that wins and designs the work, owns the client relationship and has a project lead, but has sold more builds than its developers can take on. It's the wrong model in these cases:

  • You're commissioning your own company's website: hire us directly for custom web design.
  • You need many developers on many builds at once. We're a team of three; a larger outsourcing firm fits better.
  • It's a logged-in product with users and data: scope it as web app development, white-label or not.
  • Nobody on your side can review the work or make client decisions. White-label adds a relay, and the relay needs an owner.

How we keep your agency's name on the work

Nothing we deliver mentions Dardo. We sign your NDA before we see client files, and the agreement can include a non-solicitation clause covering your clients.

  • No credits in footers, meta tags, code comments, package names or file names
  • Commits under names and email addresses you assign, in your GitHub or GitLab organization
  • Staging and preview links on your domains or hosting accounts
  • White-label work stays out of our portfolio unless you agree in writing

Slack Connect marks every external person's profile photo with their organization's Slack icon, so we use it only in channels between your team and ours. If your clients join your workspace as guests, we can join client channels the same way.

Who talks to your client?

You decide per project, and the proposal records it. There are two set-ups: we stay behind your team, with every client message going through your project lead, or we join calls as your developers, introduced under your agency's name. Either way, we don't contact your client outside the channels you set up, and we never quote, invoice or pitch them.

Who talks to your client?
ResponsibilityYour agencyDardo
Client relationship, sales and billingOwns itNot involved
DesignOwns it, or delegates it in writingBuilds from it, or designs under your art direction
Build and stagingReviews and approvesBuilds and deploys to your staging
QAFinal review against what the client expectsFull check and written report before your review
Client feedbackCollects and prioritizesEstimates changes, then makes the approved ones
Hosting, domains and accountsHeld by you or your clientInvited as a user
Support after launchFirst contact for the clientFixes and maintenance behind you

From your Figma file to a tested build

Fidelity starts with a file review before the build: we check components, variables and auto layout, list missing states (hover, focus, error, empty, long text) and ask questions as Figma comments on the frame concerned. Dev Mode needs a Full or Dev seat, and every member or guest on a paid Figma plan has a seat, so plan one for us in the team that owns the file.

We flag accessibility problems while they're cheap to fix. WCAG 2.2 Level AA asks for pointer targets of at least 24 by 24 CSS pixels and focus that sticky headers don't completely hide; we propose fixes in the file rather than quietly changing your design in code. Every build gets these checks before your review:

  • Current Chrome, Safari, Firefox and Edge at each agreed breakpoint
  • Keyboard and screen reader passes with VoiceOver and NVDA
  • Test submissions that confirm each form reaches its inbox or CRM
  • Metadata, structured data, redirects, analytics events and Lighthouse results

A full WCAG conformance report is a separate scope: our web accessibility audit.

Who owns the code? IP assignment and payment terms

Your agency does, through a signed copyright assignment written into our agreement. A work-for-hire clause alone may not be enough: the US Copyright Office explains that commissioned work is made for hire only if it falls into one of nine categories and both parties sign an agreement saying so. Website code doesn't clearly fit those categories, so our agreement also assigns copyright in writing, as the Copyright Act requires for a transfer of copyright. You then pass ownership to your client under your own contract.

Open-source libraries keep their licenses, and fonts, plugins and platform plans are licensed in your name or your client's, never ours. On Webflow we build in your Agency or Freelancer Workspace; at launch you can transfer the site to your client's Workspace with its Site plan and custom domains.

We invoice your agency, never your client, in stages you can mirror in your own billing. Have your lawyer review the agreement; this page isn't legal advice.

Working hours from Bogotá

Bogotá keeps UTC−5 all year, so a Colombian working day overlaps most of a US one. From the first Sunday in November to the second Sunday in March, Bogotá's clock matches New York's; during US daylight saving time, Bogotá is one hour behind New York and level with Chicago. Los Angeles is two or three hours behind Bogotá.

Before the build we agree an overlap window, a standing check-in and response times for blockers. Our page on working with a Colombian studio from the US covers contracts, payments and communication in more detail.

What moves the price of a white-label build?

Each project gets a written quote with its scope, assumptions and exclusions, so you can add your margin and resell it. There's no per-page rate; these factors move the number most:

  • How complete the Figma files are: every state and breakpoint, or desktop frames only
  • Platform: a Webflow or Framer site, or an Astro or Next.js build with a headless CMS
  • Unique templates, languages and integrations such as a CRM, booking or payments
  • Client-facing time: none, or calls and demos as part of your team
  • Timing: a planned slot, or overflow against a client date that's already fixed

Our pricing page lists Dardo's published starting prices and the budget ranges we use to scope projects.

Questions before you choose

Will our client know that Dardo built their site?

Not from us or from the work. Nothing we deliver carries our name, we sign your NDA, and white-label projects stay out of our portfolio unless you agree in writing. If your client later asks who built the site, what to tell them is your decision.

Which platforms do you build on?

New builds go on Astro, Next.js, Webflow or Framer, chosen per project by who edits the site, what it connects to and where it's hosted. On WordPress we take over maintenance and fixes of sites your agency already runs, after an audit. If a client is set on another platform, say so in the brief and we'll confirm fit before quoting.

Can you design as well, or only build from our Figma files?

Both. We usually build from your Figma files, but when your designers are fully booked we can design under your art direction, in your Figma team. The proposal says who makes each design decision, so your creative director keeps the final say.

How do change requests from our client work?

They reach us through your project lead. We estimate each change against the agreed scope before starting, so you decide whether to absorb it, bill your client or move it to a later phase. Fixing problems found in QA is part of the build; new templates, integrations or features are quoted separately.

Can you maintain the sites after launch under our brand?

Yes. Our maintenance plans can run behind your agency: monitoring, tested updates, backups, small changes and a monthly report written under your name for you to forward or rework. Alerts go to the contacts you choose, and response times are written into each plan.

Can we see white-label work you've done?

White-label projects stay under each agency's NDA and out of our portfolio, the same rule that protects yours. Judge our builds by the projects published under our own name, such as Janus Observatory, ten 3D worlds that still work without WebGL, or Hyper's scroll-driven product story. A small first project is a sensible way to test the fit.

From the blog

Sources & further reading

Sources behind this page, with further detail from the original publishers.

From one partner project to a written proposal

Send one project's Figma link, platform, deadline and how you want us to handle your client. We reply with a scoped quote and the agreement terms, NDA included.