The month you say no: an overflow plan for agencies, before you need it
Set up overflow capacity before you need it. Run one small paid trial with a partner while your schedule is calm, agree on a handoff format (brief, design files, review rounds, QA checklist), and decide whether you want per-project pricing or a reserved monthly block. Then, when three projects land in the same week, you route one to a partner you have already tested instead of turning it down or hiring in a hurry.
Every agency has the month. Two retainer clients want a redesign at the same time, a new pitch comes through, and the developer you rely on has just given notice.
The options at that moment are all bad: turn work down, push deadlines, hire in a rush, or hand a client project to a stranger.
The fix is to make the decision a month earlier.
Why the panic option fails
A partner found under pressure gets no trial, no shared standards and a brief written in a hurry. Their first project for you is a live client project with no slack. If anything goes wrong, it goes wrong in front of your client.
None of that is the partner’s fault. It’s the setup.
Step one: a paid trial while things are calm
Pick something real but low-stakes: a landing page, a single template, an internal project, or a page for your own site. Pay for it. Then judge:
- Did they ask good questions before starting, or just start?
- Did the result match the design at every breakpoint, not just desktop?
- How did they handle feedback? Defensively, or by fixing it?
- Was the code clean enough that your team could maintain it?
- Did they meet the date they gave, without being chased?
One trial tells you more than any portfolio.
Step two: agree on the handoff
Most overflow problems are handoff problems. Write down, once:
- What a brief contains. Goals, audience, content status, references, constraints.
- What design files look like. Components, states, responsive frames. Our Figma handoff checklist is a starting point.
- How many review rounds and who gives feedback.
- The QA list before anything reaches your client: browsers, devices, accessibility basics, speed, forms, redirects.
- Where work lives. Your repository, your hosting, your accounts.
Step three: choose a capacity model
Per project. Fixed price and timeline for each piece of work. Good when overflow is occasional. For reference, our white label prices start at €950 for a landing page in three to five working days, €2,900 for a website in three to four weeks, €4,500 for a store in five to eight weeks and €1,800 for a brand identity in two to three weeks, each with 30 days of fixes after delivery.
Reserved capacity. A monthly block of team time that you direct across projects. Good when overflow is steady, and it means you never wait for a slot. Ours starts at €2,900 a month.
The full comparison with hiring is in white label or hiring a developer.
Step four: decide what you keep
Overflow works best when the agency keeps strategy, client relationship and creative direction, and the partner handles production. Splitting it the other way, with the partner talking to your client, is possible but needs a clear agreement about who says what.
Whichever you choose, the partner should be invisible unless you decide otherwise: full NDA, no credits in code or file metadata, your name on everything.
The calm-month checklist
- Shortlist two partners.
- Run a paid trial with one.
- Write the brief template and QA list.
- Agree on per-project or reserved capacity.
- Sign the NDA and IP terms before the first real project.
Then the month arrives, and it is just a busy month. If you want to run the trial with us, the details are on white label web design.
Common questions
What is a capacity retainer?
A fixed monthly block of a partner's team time, reserved for you, used across whatever projects you send. It suits agencies with steady overflow. Ours starts at €2,900 a month. Per-project pricing suits agencies whose overflow is occasional.
How many projects can a partner take at once?
Ask directly and be suspicious of 'unlimited'. A realistic answer for a small studio is two to three projects in parallel without quality dropping. That is our number.
Will my client know?
Not if the partner works properly under NDA: no credits in code or metadata, your branding on everything, communication through you unless you decide otherwise. Ask to see how a past white label delivery was handed over.
