Web agencies: absorbing workload peaks on a white-label basis, without hiring

Three projects signed in the same month, then a lull: this is everyday life for many agencies. On a white-label basis, a web agency absorbs these peaks without hiring, provided the collaboration is properly framed. Models, day-to-day operation, clauses to include, profitability calculation and a start-up checklist: here is the guide.

The problem: an erratic order book

An agency sells projects, not regular hours. Signatures arrive in clusters, go-live dates overlap, and the same team has to keep up maintenance on the sites already delivered. The result: weeks at 130% workload, followed by quiet weeks.

Hiring for a peak: a bet of several months

Hiring seems the natural answer. But the timetable does not match that of a peak:

• Notice period: under the Syntec collective agreement, an engineer or cadre who resigns owes three months’ notice. [2] The developer you recruit today often arrives in a quarter’s time.
• Probation period: the French Labour Code limits it to four months for cadres, renewable once if an extended sector-wide agreement provides for it, up to a limit of eight months. [1] During that time, the commitment remains fragile on both sides.
• Ramping up: after that, they still have to learn your conventions, your tools and your clients.

When the peak is over, the fixed cost remains. And a hiring mistake is expensive in supervision time, delays and team morale, even if that cost is hard to quantify.

The usual answers and their limits

White label in practice

What it is

On a white-label basis, a partner provides developers who work under your agency’s name, in your tools and according to your conventions, bound by a confidentiality agreement (NDA). Your client sees your agency, your deliverables and your contacts. The partner does not approach them and does not sign your deliverables.

For the agency, it is extra production capacity that can be activated within a few days, with no fixed cost, and scaled back when the peak passes.

What it is not: legal opacity

White label means commercial discretion, not legal concealment. Three points frame it:

• Personal data: if the partner has access to your client’s personal data (the customer database of an e-commerce site, forms), it becomes a sub-processor. Article 28 of the GDPR then requires the prior written authorisation, specific or general, of the controller, that is, your client. [3] In practice, the “subprocessors” clause in the contract with your client must provide for it.
• Contract with your client: many contracts prohibit subcontracting without consent. Re-read them before starting production.
• Act of 31 December 1975: its article 3 requires each subcontractor to be accepted by the project owner. [9] Whether it applies to IT services and to a subcontractor established outside France should be checked with your legal counsel.

Three models for three situations

At iones, these three models rely on our dedicated developers (remote time-and-materials), on web development projects handled end to end, and on the application maintenance of the sites you have delivered, which frees your team for new projects. On that last point, our guide Outsourcing your application maintenance details the scope, the risks and the steps.

How it works day to day

Onboarding: the first week

• Day 1: accounts created (Git repository, ticket manager, messaging, acceptance environments), individual NDAs signed.
• Day 1–2: presentation of your conventions: code style, repository structure, branching strategy, definition of “done”.
• Day 2–3: local environment set-up, reading through the project, first simple ticket in pairs.
• Day 4–5: first real tickets, systematic review by your lead or the partner’s lead.
• End of week 1: alignment meeting, list of open questions, adjustment of the rules.

Tools: yours

The developers work in your tools: your GitLab or GitHub, your Jira or Redmine, your Slack or Teams, with named accounts that you can revoke at any time. No parallel repository, no copy of the code elsewhere. Give read-only access to production, or none at all, unless there is a justified need.

Rituals

• a 15-minute daily meeting, shared or staggered depending on your organisation;
• sprint planning and a demo per sprint;
• a monthly meeting with the partner’s lead: upcoming workload, quality, rotation of people.

The iones team, based in Tunis, works in French on hours aligned with yours: the same time as France in winter, one hour’s difference in summer, as Tunisia does not observe daylight saving time.

Quality

Quality cannot be delegated without rules. Require a code review on every merge request, automated tests in the CI and static analysis. With the arrival of AI assistants, this matters even more: generated code can pass the tests and still be wrong, as we explain in our article Offshore in 2026: with AI, the senior developer matters more than ever.

Communication with your client

Decide this before you start: either the developers stay behind the scenes and only your project manager speaks to the client, or they take part in some technical meetings as members of your team, with an email address and a signature in your name. Both work; ambiguity does not.

Contracting without nasty surprises

If the partner also takes over maintenance of the sites you have delivered, the clauses specific to that type of contract (scope, service levels, security updates, reversibility) are detailed in our guide to the application maintenance contract.

Profitability calculation: an illustrative example

The figures below are fictitious. They represent neither your rates nor iones’: replace them with your own.

Assumptions: a project sold at 40 days at €600 excl. VAT, i.e. €24,000 excl. VAT. Fully loaded internal cost of one project manager day: €350.

The formula to keep:

Marge = Prix vendu
        - (jours × tarif du partenaire)
        - (jours de pilotage × coût interne)
        - provision de reprise

And the ceiling not to exceed: maximum partner rate = (selling price − management − provision − target margin) ÷ number of days. If the partner requires more management than planned, or if the rework provision is consistently used up, your margin melts away: this is the real quality indicator for a partner.

Common mistakes

• Looking for the lowest rate. A cheaper partner who needs twice as much management and rework costs more.
• Starting with the most critical project. Start with a controlled scope to settle the rules.
• Forgetting onboarding. Without written conventions, each developer applies their own.
• Not reviewing the code. The review is your quality assurance, especially with AI-generated code.
• Signing without re-reading the client contract. Subcontracting clause, GDPR: check before, not after.
• Changing partner at every peak. All the value comes from the accumulated knowledge of your clients.

Start-up checklist

• [ ] Peak identified: volume in days, dates, skills.
• [ ] Model chosen: one-off reinforcement, dedicated team or agency extension.
• [ ] Client contract re-read: subcontracting clause, personal data.
• [ ] Partner contract: NDA, assignment of rights, non-solicitation, reversibility, article 28, work organisation.
• [ ] Vigilance documents collected.
• [ ] Written conventions: style, branches, definition of “done”.
• [ ] Named accounts created, minimum rights.
• [ ] Rituals set: daily, sprint, monthly meeting.
• [ ] Rule for communication with the client decided.
• [ ] Indicators tracked: management days, rework rate, reopened tickets.

Frequently asked questions

Getting through the next peak without hiring

A workload peak is not a hiring problem: it is a temporary capacity problem. White label answers it, provided you choose the right model, welcome the partner like a member of the team, review the code and sign a complete contract. Calculate your margin on total cost and track your management days: they will tell you very quickly whether the partner is the right one.

To go further, find out how to sell credible AI offers and deliver them on a white-label basis, see our dedicated developers offer, or contact us to talk about your next peak: reply within 48 to 72 hours, no commitment, under NDA.