The Freelancer's Subcontracting Playbook: 2026 Edition
At some point most successful freelancers hit the same wall: more work than hours, and the AI-augmented version of that wall arrives faster than it used to. Hiring a subcontractor is the cleanest way through — and the messiest legally, if you do it without the right contracts. Here is the operational, tax, and IP playbook for 2026.
The Delivvo team· May 24, 2026 11 min read
Every successful freelancer eventually hits the same wall: more work than hours, and the obvious fix — turn some away — feels worse than the problem. AI tools have pulled that wall closer for a lot of people, because the same workflows that produce more output also produce more inbound. The decision a freelancer makes in front of that wall is one of the most consequential of the whole practice: hire a subcontractor, or stay solo.
This is the playbook for doing it carefully. Subcontracting is the moment a freelance practice begins turning into a one-person agency. It is also the moment most freelancers create their first real legal and tax exposure without quite realising it — because the same word, "freelancer," covers everyone in the chain, and the rules are not the same on every link.
What "subcontracting" actually means here
A useful first distinction. There are two things people loosely call hiring help.
The first is *delegating* — handing off a chunk of work to another independent freelancer who you pay directly, and who delivers their part of the project to you. Legally you are now a hiring party, with all the obligations that go with it.
The second is *referring* — passing a client to another freelancer entirely and stepping out of the engagement. That is a different transaction with different (mostly simpler) implications, and it is not the subject of this post.
This post is about the first. You are still the freelancer the client hired. You are still on the contract. You are now paying another person to deliver part of what you sold. Everything that follows assumes that shape.
When subcontracting makes sense (and when it does not)
The honest case for subcontracting is small, and the case against is larger than most freelancers admit.
The good reasons. A specific project needs a skill you do not have, and buying it in once is cheaper than developing it. A spike in workload is real but short-lived, and a subcontractor is the elastic capacity that lets you take the spike without dropping a client. A recurring slice of your work is well-defined, repeatable, and below your effective hourly rate — handing it off lifts your average earnings without changing your offer.
Keep reading
The bad reasons. You are tired and want fewer hours, but you have not changed what you charge. You want to "scale" because the word is in the air, without a concrete plan for what the bigger version of the business does that the small version cannot. You have a single big client whose work you cannot keep up with — that is a scope creep and pricing problem, not a staffing one.
The Freelancers Union's own framing of this is useful: independent contractors do generally have the right to subcontract, but once you start outsourcing work you "have become an agency," and that means real subcontractor agreements and a much more careful posture about quality, since the subcontractor's work will reflect on you (Freelancers Union, How to start subcontracting). The legal right to do it is the easy part; the operational reality is the work.
The classification trap nobody warns you about
This is the part that costs freelancers money, so it goes near the top.
When you hire a subcontractor, you are now the hiring party for that worker. US law makes a distinction between an independent contractor and an employee, and the consequences of getting it wrong fall on the hiring party — *you*, the freelancer who hired the subcontractor — not the subcontractor.
The Department of Labor's 2024 Final Rule on Employee or Independent Contractor Classification, effective March 11, 2024, returned the analysis to a six-factor "economic reality" test: opportunity for profit or loss based on managerial skill, the worker's and hiring party's investments, permanence of the relationship, the nature and degree of control, whether the work is integral to the hiring party's business, and the worker's skill and initiative (US Department of Labor, FLSA independent contractor classification FAQs). No single factor decides; the totality of the circumstances does.
For a freelancer hiring a subcontractor, two factors quietly cause most of the trouble. The first is *control*: if you tell the subcontractor when to work, what tools to use, how to do the job, and stop them from working for anyone else, you have drifted toward an employee relationship. The second is *permanence*: a subcontractor you have worked with full-time, exclusively, for two years looks very different from one you hire for a defined project.
The IRS uses a related but not identical test for federal tax purposes, and the rules can vary again at the state level — California's ABC test is the most-cited example of a stricter local rule. The practical takeaway is the same in every framework: pay a subcontractor on a project or deliverable basis, let them choose their own schedule and tools, do not stop them working with anyone else, and reduce the standing dependency. Get this right and the cost is small. Get it wrong and the back taxes, penalties, and reclassification liability fall on you.
Two freelancers collaborating on a project at a laptop in a bright workspace
The contract structure: master agreement plus SOW
The right legal shape for hiring a subcontractor is the same shape large agencies use, just smaller. It is two documents.
The first is a master services agreement — sometimes called an independent contractor agreement — that lives once and covers the standing terms: who the parties are, the confidentiality obligation, the intellectual property assignment, the indemnity language, the non-solicitation clause that stops the subcontractor approaching your clients to work with them directly, the basis on which the relationship can be ended, and the explicit statement that the subcontractor is not your employee. Bonsai's own guidance for freelance subcontractor agreements lays out the typical components — scope, payment, deadlines, confidentiality, IP, termination, dispute resolution (Bonsai, 10 tips for freelancers using subcontractor agreements).
The second is a statement of work (SOW) per project: what the subcontractor is doing this time, by when, for what fee, with what deliverable. The SOW is short and specific. The MSA is long and only signed once.
The two-document structure exists because the standing terms — IP, confidentiality, non-solicit — are too important to be re-negotiated every project, and the project terms are too specific to live in a permanent agreement. Drafting them separately, and signing the MSA before any work starts, is the single biggest piece of administrative hygiene in subcontracting.
If your subcontractor is in a different country than you, add a clear governing-law clause and think about how you will actually enforce the contract if you ever need to. The piece on non-US freelancers working with US clients is written from the other side of that situation, but it covers the same cross-border issues in reverse and is worth reading before you sign a foreign subcontractor.
The IP chain — the issue that bites everyone
Here is the issue that catches more freelancers than any other, because it is invisible until it is not.
Your client paid you for a deliverable. Your contract with the client almost certainly assigns the intellectual property in that deliverable to them. You then hired a subcontractor to make part of it. *Unless your subcontractor agreement also assigns the IP from the subcontractor to you*, you cannot pass to the client what the client paid for. The chain is broken.
US law makes this worse than it sounds. The "work made for hire" doctrine, which would automatically give the hiring party ownership, only applies to independent contractors in nine specific statutory categories *and* requires a written agreement saying it is work made for hire. Most freelance work — most software, most design, most strategy — falls outside those nine categories, which means "work for hire" language alone is not enough. The reliable mechanism is a present-tense, affirmative *assignment* of copyright in the subcontractor agreement: the subcontractor assigns to you all right, title, and interest in the deliverables, on the day the work is created.
The chain has to be unbroken. If you hire a subcontractor and the subcontractor hires their own helper, your subcontractor's agreement also needs to capture an IP assignment from that helper. Without it, the helper still owns their contribution, and your client is paying for a deliverable whose rights you cannot fully convey.
A line freelancers ask about: portfolio rights. It is reasonable to let a subcontractor display the work in their portfolio with your permission and the client's, but the default in the contract should be that they need that permission, not that they have it. Wording that requires the subcontractor to ask before sharing — which Bonsai's guidance specifically calls out — is the cleanest middle ground.
Tax: the 1099 and the cost layer you forgot
The tax side is procedural. If you pay a US subcontractor $600 or more during a calendar year for services, you generally must issue them a Form 1099-NEC reporting the payment, and file a copy with the IRS by the deadline (IRS, Form 1099-NEC and independent contractors). The threshold for 2026 has been raised to $2,000 going forward, but most subcontracting relationships will still cross any reasonable threshold.
The mechanics are simple. Collect a Form W-9 from the subcontractor *before* you pay them — not after — so you have their tax ID on file. At year-end, your accountant (or a 1099 service) issues the 1099-NEC. If the subcontractor is outside the US, you collect a W-8BEN instead, and 1099 reporting generally does not apply, though withholding rules sometimes do depending on the nature of the work.
The cost layer freelancers underestimate is everything else. Subcontracting adds time you previously did not spend: writing the brief, reviewing the work, managing the schedule, handling the payment, fixing whatever the subcontractor got wrong. Build that overhead into your rate from the start. A freelancer who hires a subcontractor at $40 an hour and continues to charge clients $80 an hour has often forgotten to price the supervision, and ends up earning less per *real* hour than before. The right way to price subcontracted work is by what the client gets, with your margin sized to cover your real time on the project — not by stacking hourly rates that lose money on management.
Disclosing to the client (or not)
This one depends on what your client contract says, and reading it before you subcontract is non-negotiable.
Many freelance contracts have an *anti-assignment* or *no-subcontracting* clause that requires the client's written consent before any work is delegated. Some have it as a flat prohibition. Some have nothing at all. The default rule for service contracts is that personal services cannot be subcontracted without consent — but the contract you signed governs, and a court will read it before any common-law default applies.
Read the contract. If consent is required, ask for it in writing before you bring a subcontractor in, and frame it the way it actually is: a specialist or capacity addition who will work under your direction, with you remaining the responsible party. Most clients agree without drama. The clients who say no are telling you something important about what they actually bought from you, and that is useful to know before you hire someone you cannot use.
Quietly subcontracting against a contract that forbade it is the version that ends careers. Discovery is usually accidental — a different email signature, a Slack handle the client did not recognise, a calendar invite from a third name. The cost of being caught is far higher than the cost of asking.
When subcontracting becomes a team
There is a point on this path where you stop being a freelancer who occasionally hires help and start being a small agency that employs people. The transition is gradual and easy to miss, and the indicators are practical: the same subcontractors working with you for years, full-time, exclusively, with you setting their hours and tools. At that point the right call is not to keep stretching the contractor structure — it is to formalise the relationship as employment in the jurisdiction where the worker sits, with all of the cost and obligation that brings.
The DOL's six-factor test is designed to catch exactly that drift, and the consequences of ignoring it are paid in back wages, payroll taxes, penalties, and (depending on the state) plaintiff-friendly remedies for the worker. The clean move when a subcontractor relationship has become permanent is to recognise it, and either restructure it to look truly independent again or to convert the worker to an employee with proper payroll. The half-measure — calling them a contractor while treating them like an employee — is the expensive option.
The financial half of this transition belongs alongside a quarterly view of your numbers; the same 13-week forecast in the cash-flow forecasting piece is what tells you whether your effective rate after subcontractor costs is actually rising or falling.
Delivvo gives a freelancer-turned-small-agency a branded client portal where the proposal, the contract, the SOW, the deliverables, and the invoice all live on one surface — so the work a subcontractor produces under your name still arrives at the client with the structure of a single, accountable practice. The legal chain holds because the operational chain is visible. See how it works →
The takeaway
Subcontracting is the inflection point at which a freelancer's practice either professionalises or develops a quiet legal liability. The professional version has a master agreement and a per-project SOW, a clean IP assignment in writing, a Form W-9 on file before any payment goes out, and a client contract that either permits the delegation or has been varied to allow it. The liability version is the same workflow without any of those documents.
The work of doing it correctly is not difficult, but it has to be done *before* the first project, not after the first problem. The freelancers who turn the transition into a real one-person agency get this right at the start. The ones who do not spend the next two years untangling chains of ownership, classification challenges, and the slow, expensive realisation that they built an agency without the agency's safety nets.
