Skip to content

Agencies · Delivery models

White-label development · for digital agencies Contracts, code ownership and communication, without surprises

White-label development means a partner studio builds software that your agency delivers under its own brand. It works when four things are written down before the first commit: who owns the code and the accounts, what the end client may see, how the teams communicate, and who runs the software after launch.

Written by
Wael ChabchoubiFounder & Tech Lead
Published
Updated
Reading time
9 minLire en français

ANTASY IT (a.it) is a software studio in Sfax, Tunisia. We build for companies directly, and offer agencies white-label delivery. This guide is the checklist we would want an agency to hold any studio to, including us. It is not legal advice: use it to brief your lawyer, not to replace one.

How does white label differ from other ways of adding capacity?

In white label, the studio delivers finished work under the agency’s brand and carries most of the delivery risk, while the end client sees only the agency. A dedicated team or staff augmentation adds people the agency directs, and a freelancer suits small tasks. The real differences are who manages the work and who answers for it.

The table compares the four models agencies usually weigh, including when another model is the better choice.

White-label project, dedicated team, staff augmentation or freelancer: how they compare
CriterionWhite-label projectDedicated teamStaff augmentationFreelancer
Who manages the workThe studio, against an agreed scopeA lead on the studio side, with your prioritiesYou, day to dayYou
Who faces the end clientYour agencyYour agencyYour agencyUsually your agency
Usual billingFixed scope or milestonesMonthlyMonthly, per personHourly or daily
Delivery riskMostly the studio’sSharedYoursYours
Best whenThe scope is clear and you need a finished productWork flows steadily for monthsYour team lacks one skill for a whileA small, well-bounded task
Another model is better whenThe scope keeps moving: take a dedicated teamWork is irregular: buy projectsNobody can lead the extra peopleThe work is long or critical

Our own offer follows the same logic: white-label projects at a fixed scope or by milestones, and a dedicated team or individual developers by the month. The pricing page explains how each model is quoted.

What should a white-label agreement cover?

Ten headings, each worth a sentence or a page: confidentiality, ownership and transfer of the code, credits and branding, accounts and access, deliverables and acceptance, change requests, personal data, support after launch, exit and handover, and payment terms. Write them before the kick-off; adding them after the first invoice is much harder.

  1. Confidentiality. The studio keeps the end client’s name, data and documents confidential, and does not show the work anywhere without the agency’s written consent.
  2. Ownership and transfer of the code. Who owns the source code, when ownership transfers (often on full payment), and what stays with the studio: reusable libraries, internal tools, third-party components under their own licences.
  3. Credits and branding. No studio name in footers, page metadata, PDF templates, e-mails or admin screens, unless agreed otherwise.
  4. Accounts and access. In whose name the repository, domain, DNS, hosting, CDN, analytics, e-mail sending and app-store accounts are created, and who holds the admin rights.
  5. Deliverables and acceptance. What is delivered, on which environment, and the criteria that make a milestone accepted.
  6. Change requests. How a change is estimated, approved and billed, and who may ask for one.
  7. Personal data. Which personal data the studio processes for the end client, where it is hosted, and what happens to copies at the end. If the agency or the end client is in the European Union, the GDPR (opens in a new tab) governs this point.
  8. Support after launch. Who answers incidents, during which hours, and how support is billed.
  9. Exit and handover. What the agency receives if the collaboration ends: code, history, documentation, credentials, backups.
  10. Payment terms. Invoicing rhythm, currency and the bank details used for cross-border payments.

These are headings, not clauses. Your lawyer writes the clauses, under the law you choose; the headings make sure nothing important is missing from the brief.

Who should own the code, the domain and the hosting?

The agency or its client, never the studio by default. Domain, DNS, hosting, CDN and analytics accounts belong to whoever will still own the product in five years, with the studio invited as a user. Code ownership should transfer on payment, with the full repository history, not as a zip file sent at the end.

Takeovers show why. When we take over a site or an application built by someone else, the first question is always the same: who holds the domain, the DNS zone and the hosting account? When the answer is the client, a takeover is a technical task. When it is a former vendor, it becomes a negotiation, and the client waits.

Cloudflare deserves a line of its own. If the DNS zone sits in the studio’s Cloudflare account, the agency depends on the studio for every DNS change, every certificate and every cache purge. Put the zone in the agency’s or the client’s account and invite the studio as a member with the narrowest role that works.

How does a studio stay invisible to the end client?

By removing its name from everything the end client can see, not only from the footer. Credits hide in page metadata, PDF and e-mail templates, admin login screens, error pages, staging URLs and sender domains. A search for the studio’s name, domain and e-mail across the code and the rendered pages, before launch, catches most of them.

On our direct projects we do the opposite, openly: the Mohamed Damak et Cie website carries a “Développé par AIT” credit that links to us, and our own product Made in Tunisia shows “Réalisé par” followed by our logo. That is exactly the kind of line a white-label delivery must not contain, and in a real codebase it can sit in more places than the footer:

  • Footer credits and “powered by” lines
  • Author and generator meta tags, Open Graph site names, web app manifest
  • PDF templates: invoices, quotes, reports, delivery notes
  • Transactional e-mails: sender domain, footer, reply-to address
  • Admin panel: login page, logo, favicon, page titles
  • Error and maintenance pages
  • Staging and preview URLs on the studio’s domain
  • Package metadata, README files and comments shipped to the browser
  • Third-party accounts (maps, analytics, error tracking) registered to the studio

How should the agency and the studio communicate?

Through the agency’s channels, at the agency’s rhythm. The studio works in the agency’s chat, tracker and repository, joins client calls only when invited and under the agency’s banner, and writes release notes the agency can forward unchanged. From Tunisia, the working day matches Paris and Berlin in winter and runs one hour behind in summer.

Tunisia has stayed on UTC+1 all year since it abandoned daylight saving time in 2009 (opens in a new tab). Our office hours are Monday to Friday, 9:00 to 18:00 local time, and we work in English and French. For a European agency, that is a shared working day, not an overnight hand-off.

A sample week

The rhythm we propose to an agency, adapted to its own rituals:

  1. Monday: planning with the agency’s project manager; the week’s priorities written in the agency’s tracker.
  2. Every day: a short written update in the agency’s channel: done, next, blocked.
  3. Midweek: a demo on staging, at a URL under the agency’s domain, behind a password and marked noindex.
  4. Thursday: questions for the end client batched and sent to the agency, never to the client directly.
  5. Friday: a release or a release candidate, with notes written in the agency’s voice.

The days matter less than the principle: the agency always knows more than the end client, and never learns news from them.

Who runs the software after launch?

Decide it before launch, in writing. Either the studio keeps operating the software (hosting, updates, monitoring and backups) under accounts the agency or the client owns, or it hands everything over with a documented package. Both work. What fails is the unspoken middle, where everyone assumes someone else will renew the certificate.

Operating what we build is our default with direct clients, through our DevOps and hosting service. For an agency, the same work can run under the agency’s accounts, or end with a handover. Either way, the handover package below should exist from the first release, not be assembled in a hurry at the end.

What a handover package contains

  • The repository with its full history, not an archive
  • A README a new developer can follow to run the project locally
  • The list of environment variables without their values, and the secrets passed through a password manager
  • An infrastructure note: servers, ports, process manager, reverse proxy, CDN rules
  • The DNS records and where each one points
  • Backup location, schedule and the date of the last restore test
  • Dependency versions and known upgrade work
  • Every third-party account and who owns it

Which pitfalls should an agency plan for?

Six are worth planning for: credits left in templates, accounts opened in the studio’s name, staging sites indexed by search engines, e-mails sent from the studio’s domain, licences bought by the studio, and support after launch that nobody priced. Each takes minutes to prevent at kick-off and days to untangle once the end client notices.

  • Indexed staging. A preview site on a public URL without a password and without noindex ends up in search results, sometimes under the studio’s domain. Our direct clients’ apps can run on our own subdomains when they choose it; in white label, staging belongs on the agency’s domain, behind authentication.
  • E-mails from the wrong domain. Password resets and notifications must leave from the agency’s or the client’s domain, with its SPF and DKIM records, not through the studio’s mail server.
  • Licences. Paid themes, fonts, plugins and APIs should be bought in the client’s or the agency’s name, or transferred at handover.
  • Unpriced support. A launch without a support agreement turns every bug report into a negotiation.
  • Silent dependencies. An analytics, error-tracking or maps account owned by the studio breaks the day the collaboration ends.
  • Credits. See the checklist above: the footer is only the first place to look.

If you are comparing partners, our page on nearshore development in Tunisia covers time zones, languages and how to check a studio’s production work. The process page shows how a project runs from discovery to operations, the agencies hub lists every way we work with agencies, and the glossary defines the terms used here.

FAQ

Questions readers ask

How can an agency test a white-label studio before a large project?

Start with a small, real piece of work with a clear scope: a module, a page with a form, or a round of fixes on an existing app. Judge the code delivered in your repository, the questions asked before starting, the release notes and how surprises are reported, not only whether the deadline was met.

Can the end client take the code in-house later?

Yes, if the agreement transfers ownership of the code and requires a handover package: repository with history, documentation, environment variables and infrastructure notes. Without those two clauses, the code may exist yet be impossible to run without the studio. Write them before the project starts, not when it ends.

Should the studio ever talk to the end client?

Only when the agency decides it, and under the agency’s banner. Some agencies invite the studio’s lead to technical meetings with an agency e-mail address; others keep every exchange in-house. Either works, provided the rule is written down and the studio never contacts the end client on its own initiative.

Sources

Sources and references

External facts in this guide come from these documents. Examples from our projects are first-hand.

  1. Tunisia abandons daylight saving time in 2009 (opens in a new tab)timeanddate.com
  2. Regulation (EU) 2016/679, General Data Protection Regulation (GDPR) (opens in a new tab)EUR-Lex, Publications Office of the European Union

Looking for a studio that stays behind you?

Tell us about the project and how your agency works; we adapt to your tools and your rhythm.