The question agencies usually ask is about cost, but the better question is about shape. If the next twelve months hold a steady stream of build work, a developer on the team pays back the salary, learns your clients and your standards, and is there for the small changes that never justify a proposal. If the work arrives as one project, then nothing for six weeks, then two at once, a salary is paid through the gaps and the peaks still need help.
A white-label partner is paid per project and works under your name: your client deals with you, and the engineering happens behind the scenes. You keep the strategy, the design direction and the account. What you give up is daily control over who does the work, so the arrangement has to be written down before it starts: who the client sees, who owns the code and the accounts, how the price is fixed and what is handed over at the end.
Knowledge is the other trade-off. A hire keeps what they learn inside the agency. A partner keeps general know-how and gives you the project: the repository with its history, the hosting project, the CMS seats, the docs and a runbook. If the handover is a zip file and a password, the knowledge has left with the partner, and that is the risk to check before signing.
Many agencies end up with both: a small in-house team for the steady work and a partner for the peaks and the specialist projects, such as a web app, an integration or a Chrome extension. The two work best when the partner fits your process rather than asking you to fit theirs.