An agency that has sold more work than its people can ship has three ways to add capacity: hire, assemble freelancers, or bring in a partner team. This post sets out how we size a white-label pod for a partner agency: the roles, the first weeks and the review before anything reaches your client.
It also shows how our partner rate card prices a pod, and ends with the cases where hiring is the better answer.
Can an agency grow without adding payroll?
Yes, when the work that is growing can be written down, handed over and reviewed. Payroll buys permanent capacity in fixed units of one person. A partner pod buys capacity by the month, sized to the queue you actually have, with notice periods in both directions. The agency keeps the client, the strategy and the margin.
- What it buys
- Help assembled from a freelancer marketplace
- Fits when
- The tasks are tiny, scattered one-offs
- What it buys
- Capacity by the month, sized to the queue you have
- Fits when
- The work can be written down, handed over and reviewed
- What it buys
- Permanent capacity, in fixed units of one person
- Fits when
- A lane is permanently full, or the work is your craft
What does not transfer is judgement about the client. If the extra work depends on knowledge that sits only in your account lead’s head, a pod will wait on that person, and the bottleneck moves rather than disappears. The sizing method below starts from that problem. The capacity and delivery page compares the three routes a partner can take.
White-label means the pod delivers under your agency’s brand. We do not approach the clients you introduce to us for direct business. That protection runs through the work and for 12 months after the last assignment for that client ends, and it is written into the agreement.
How we size a pod: four questions, in order
A pod is sized from the work in front of it, not from a headcount you name on the first call. We ask four questions before we propose anyone, and the proposal answers each one in writing, with the roles, the seniority and the monthly rate itemised.
- What is in the queue for the next 90 days? List the deliverables by discipline and by week: pages to build, campaigns to run, fixes to ship. A queue of one discipline needs a specialist, not a pod.
- Which roles does that queue need, and at what level? Every pod has a named lead. Engineering pods add engineers, QA and a delivery lead; design pods add UI, web or brand capacity behind a design lead.
- How many days a week per role? This is what moves the price. On our rate card the engineering pod’s driver is engineer count, and the design pod’s is designer days per week.
- Who approves on your side, and how often? We name one approver and fix the review points before work starts. A pod without a fast approver ships slower than a smaller pod with one.
If the answers point to one discipline at steady volume, we recommend a single dedicated specialist rather than a pod. Our rate card prices one person at 160 hours a month, reserved for your work.
The ramp: from brief to the first weekly report
The fastest ramps happen when the paperwork is done before there is a brief. Partners who join our bench sign the NDA and hold the rate card months ahead, so a new client becomes a staffing question rather than a contract negotiation. The table shows what happens at each stage and what you hold at the end of it.
| Stage | What happens | What you hold |
|---|---|---|
| Before a brief | NDA signed; rate card and capability pack on file | Prices you can quote in a pitch |
| Complete brief received | We confirm the date you will receive the proposal; you meet the proposed people | Named roles, seniority, monthly rate, notice terms |
| Start | Eligible engagements can typically start within two to three business days after scope, payment and required access are confirmed | A kickoff date and a named delivery lead |
| Week one | The pod joins your tools and stand-ups; for an engineering pod, the repository is live in your accounts | The onboarding plan: access, tools, first tasks, and the person on your side |
| End of week one | The first weekly report ships in your brand | A report you can forward to your client |
| End of month one | Role profiles, working agreement and handover rules are written down | A record of who owns what, and what happens if someone leaves |
In our partner engagements from July to September 2026, the size ranged from a single specialist to a pod of typically three people, and five in some cases. The time from signing to first delivery ranged from seven business days to four weeks; the whole project often runs longer. These are ranges from the Group CEO’s account of the quarter’s engagements, not averages.
How the work is reviewed before your client sees it
Capacity that ships unreviewed work only moves the bottleneck to your senior people. Before any delivery is released to you, three people check it: QA for function and accuracy, the delivery manager for scope and readiness, and a senior lead for quality and risk. Their sign-off sits with the delivery record.
Where the engagement includes it, the pod runs in a Prism workspace with your client’s name withheld: your requests, approvals, owned tasks and the weekly review, with each decision recorded alongside what we expect to change and by when. The write-up goes out in your templates, ready to forward.
How the partner rate card prices a pod
Pods are priced per month, per pod, against itemised roles. Partner agencies buy at the partner rates, which follow the ranges on our pricing page; volume terms are agreed under NDA. You set the retail price, and nothing in a report shows what you pay us.
- Engineering pod: a named technical lead, engineers, QA and a delivery lead in your tools; monthly, with a three-month minimum. Hosting and licence fees are outside the fee.
- Design pod: a named design lead with UI/UX, web and brand capacity; monthly, three-month minimum.
- Dedicated specialist: one person, priced monthly, for a single discipline at steady volume.
- Overflow project: one scoped brief at a fixed quote, with no ongoing commitment, for a single deadline.
Scaling up or down carries a notice period agreed before the start, in both directions. We say this plainly because “scale down any time” is not a promise anyone running senior teams can keep.
When hiring is the better answer
A pod is rented capacity, and renting is not always cheaper or wiser than owning. We tell agencies to hire, not partner, in four cases:
- The lane is permanently full. If a discipline has had more work than people for a year and the pipeline says it will continue, a salaried team will cost less and stay longer.
- The work is your agency’s craft. The discipline you are known for, and win pitches on, should be done by people you employ.
- Nobody can brief or approve. If your seniors have no time to write briefs or sign off work, a pod adds a queue. Fix the approval path first.
- The tasks are tiny and scattered. We do not take one-off micro-tasks; a freelancer marketplace serves that size better.
The warning signs that you need capacity before a deadline breaks are in the agency capacity problem nobody admits to. Before choosing any partner, including us, use the questions to ask before signing.
