What I Learned Subcontracting Work to Another Freelancer for the First Time

An engagement grew past what I could reasonably handle solo, so I brought in another freelancer to handle a defined slice of the work. Their technical output was fine — that part I'd actually prepared for, checking references and reviewing past work. What I hadn't prepared for were the problems that had nothing to do with their skill.

What actually went wrong

• The client wanted to communicate directly with the subcontractor on a few occasions, which I hadn't set a clear policy on, and it created confusion about who owned what decision.
• I'd priced the subcontracted work at a margin that looked fine on paper but didn't account for the time I'd spend reviewing and integrating their output, which ate most of the margin.
• I hadn't been explicit enough about my own quality bar and house style, so the first deliverable needed more revision than it should have, costing both of us time.

Subcontracting doesn't remove your workload, it changes its shape — from doing the work to managing the work, and I'd budgeted for the first and gotten the second.

What I'd do differently

Set an explicit communication boundary with the client upfront — I handle all client-facing communication, the subcontractor works through me, full stop, stated before work begins rather than improvised when it comes up. Price the review and integration overhead as its own line item rather than assuming it's covered inside the margin. And front-load the style and quality-bar conversation with the subcontractor far more than felt necessary at the time — what felt like excessive hand-holding in the moment was actually the cheapest way to avoid rework later.