A surge is the few weeks when an agency has more due than its people can ship: a launch season, two big clients landing at once, a campaign that doubles in scope.
This post sets out how we staff a partner agency’s surge: what we triage first, who joins and for how long, and how the work comes back to your team when the peak is over. It also covers the surges a partner cannot fix.
First, decide whether it is a surge or a new normal
A surge has an end date. If the same overflow has appeared in each of the last three months, it is not a surge but a missing role, and it needs a standing answer rather than an emergency one. The test matters because the two are staffed and priced differently.
Look back at the last quarter and list the weeks your team worked late or moved a deadline. If they cluster around known events, you have peaks. If they are spread evenly, you have a capacity gap that a one-off brief will only postpone. The agency capacity problem nobody admits to covers how that gap builds up.
- 1Does the overflow have an end date?NoSame overflow three months running: a missing role
- 2Do the late weeks cluster around known events?NoSpread evenly: a gap a one-off brief only postpones
- 3Is there a brief, and time to hand it over?NoMove the date or narrow the deliverable
- 4Can the work leave one person’s head?NoFree that person's time rather than adding hands
- 5Does the client contract allow subcontracting?NoCheck before you plan around a partner, not after
- 6Is the bottleneck the work, not a decision or an approval?NoMore hands cannot speed it up: say so before adding any
Triage before anyone joins
Adding people to an unsorted queue makes a surge worse, because the new people spend the first week asking what matters. Before we staff anything, we sort the queue with you, in a working session with the person who owns the deadlines.
- List everything due in the surge window, by client, deliverable and date, including the work nobody has started.
- Sort it into three piles: quick wins, structural work, and things that should never have been promised on that date.
- Renegotiate the third pile first. A date moved now, with a reason, costs less than a date missed later.
- Decide what stays in-house: client-facing work, strategy and anything that depends on knowledge your team cannot write down in time.
- Write acceptance criteria for what goes out, so the people who join know when a piece is finished without asking.
Who joins, and for how long
The shape of the surge decides the shape of the help. A single deadline should not carry a monthly commitment, and a quarter of extra volume should not be bought one brief at a time. This is how we recommend matching them, using the engagement shapes on our rate card.
| Surge shape | What joins | Commitment |
|---|---|---|
| One deadline, one defined deliverable | A team scoped to that brief, with a named delivery lead | Overflow project at a fixed quote; no ongoing commitment |
| Several weeks of extra volume in one discipline | A dedicated specialist working in your tools | Monthly, with notice terms in the proposal |
| A season across several disciplines | A pod: a named lead, the roles the queue needs, QA and a delivery lead | Monthly, with a three-month minimum |
| A new client’s recurring work | A white-label retainer in your brand | Monthly, rescoped as the client’s needs move |
Whatever the shape, the people who join are named in the proposal, and capacity is confirmed there before you commit to your client. Once we have a complete brief, we confirm the date you will receive the proposal; eligible engagements can typically start within two to three business days after scope, payment and required access are confirmed.
We do not have a standard surge size, and we do not quote one. People are added only where the work can actually absorb them: some backlogs move faster with a second specialist, and others do not, because the bottleneck is a decision, a review or an approval that more hands cannot speed up. When adding people will not help, we say so before anyone is added.
How the work comes back to your team
The surge is only over when your team can carry the work again without calling us. That handover is planned at the start, not improvised in the last week, and the receiving person on your side is named before work begins. These are the items we hand back:
- Every agreed file, in your accounts: code in your repository, editable design files, documents and content.
- A written record of what was delivered, what is still open, and any known limitation with its owner.
- The decisions taken during the surge and why, so your team does not reopen them.
- Access transferred and confirmed working, and our access removed where it is no longer needed.
- A handover session with the person taking over, and reasonable answers to questions about the documentation afterwards.
On our side, applicable development work includes 30 days of corrective maintenance after production launch. A defect in our work reported within that period is ours to fix, even if the surge has ended.
When a surge partner is the wrong answer
Some surges cannot be solved by adding people from outside, and we would rather say so on the first call than staff them badly.
- The deadline is days away and there is no brief. Briefing a new team would take the time you do not have. Move the date or narrow the deliverable.
- The work lives in one person’s head. If only your lead knows what the client wants, help arrives faster as time freed for that person than as new hands.
- The client contract forbids subcontracting. Check before you plan around a partner, not after.
- It happens every month. Then it is a staffing question, and the capacity and delivery page sets out the standing options.
Written by
Shweta Agarwal
Chief Operating Officer, Vinove
Shweta runs the operating side of the group, holding delivery, process and accountability consistent across the group. Her focus is on the systems that let teams grow without losing the standard they started with.
LinkedIn →
