Game lens: When you subcontract, effort and judgment become partly hidden. Incentives, briefs, and review loops determine whether quality holds or quietly drifts.
Game-theory pearl: Delegation fails less from bad people than from missing information and mispriced ambiguity.
Go deeper: Onboarding, Delivery, and Retaining Clients Use now: Subcontractor Brief + QA Checklist
What changes when you stop doing all the work
Hidden assumptions become expensive. You now need to define outcome, deliverables, definition of done, constraints, quality standard, dependencies, communication rules, and who reviews what before anything reaches the client.
The client still bought your judgment. If a collaborator sees only a task, they cannot reliably apply that judgment. Your job becomes designing enough context, incentives, and review structure that quality does not depend on mind reading.
Brief for judgment, not only tasks
A weak brief says what to do. A strong brief says what matters.
- client context and business objective
- exact deliverable
- definition of done
- acceptable and unacceptable examples
- known risks and constraints
- deadline, review sequence, and ownership boundaries
The brief should also say what not to optimize for. If speed matters less than accuracy, say that. If brand tone matters more than novelty, say that. If the client hates surprises, define the escalation rule.
Copyable subcontractor brief
Fill this in for every delegated deliverable. If you cannot complete a line, that gap is usually where the rework will come from.
Project: [client / project name]
Deliverable: [exactly what you hand back, format, length or size]
Why it matters: [the client's business goal in one or two sentences]
Audience and context: [who will use it, what they already have]
Definition of done:
- [criterion 1, checkable]
- [criterion 2, checkable]
- [criterion 3, checkable]
Good example: [link] Not like this: [link + why]
Constraints: [brand rules, tools, accessibility, legal or data limits]
Do not optimize for: [e.g. speed over accuracy, novelty over brand tone]
Owner of each decision: [you / subcontractor / client]
Deadline for first draft: [date + time zone]
Your self-check before handoff: [the 3 to 5 items to confirm]
Escalate to me if: [blocker, scope question, anything client-facing]
Fee and payment: [fixed fee or rate, revision rounds included, payment date]QA is part of production
Quality control should happen in layers:
- self-check by the subcontractor
- internal review by you
- only then client-facing delivery
If the first time you inspect the work is when the client sees it, you already accepted too much risk. QA time is not overhead to hide. It is part of production and should be included in margin.
A simple review rubric
Sort every issue you find into one of three groups before you send feedback. It keeps reviews fast and stops personal taste from turning into endless revisions.
- Must fix: fails the definition of done, is factually wrong, breaks a client constraint, or would embarrass you in front of the client. The work does not ship until these are fixed.
- Should fix: meets the brief but misses the standard you would hold yourself to. Fix in this round if time allows; otherwise add it to the brief for next time.
- Preference: a different choice, not a better one. Mention it once, then let it go unless the client has asked for it.
After each project, turn every repeated must-fix into a line in the brief or the subcontractor's self-check. That is how quality stops depending on your review alone. The subcontractor brief and QA checklist gives you a starting set of checks to adapt.
Incentives matter
- Paying only for speed often buys sloppy work.
- Vague ownership creates duplicated effort or dropped tasks.
- Underpricing the management layer hides briefing and QA labor.
- Overloading the dependable collaborator creates a new bottleneck.
- Unlimited revisions quietly punish the most conscientious person in the system.
Good incentives do not need to be complicated. Pay fairly, define quality, cap revision ambiguity, give fast feedback, and reward people who surface risk early instead of hiding it until review.
Start with narrow delegation
Do not delegate the most ambiguous, highest-stakes piece first. Start with one bounded deliverable, one deadline, and one clear review cycle. Then review what broke, what the brief missed, what can become a reusable QA rule, and whether the margin still works.
A good first delegation candidate is repeatable, visible, low to medium stakes, and easy to inspect. A bad first candidate requires deep client politics, undefined taste, or hidden context only you understand.
When not to subcontract yet
- Your own process is still improvised.
- The offer is too custom every time.
- You do not know what “good” looks like in a repeatable way.
- Your margin is too thin to absorb briefing and QA time.
- You need help because you are overcommitted, not because the work is ready to delegate.
If the real problem is that you said yes to too much, fix the intake first. The project selection guide shows how to score new work against your capacity before it lands on the calendar.
Put the subcontractor agreement in writing
A short written agreement protects you, the subcontractor, and the client. Use the same structure you would use with a client: a statement of work for the deliverable, plus terms that cover the points below. The guide to freelance contract clauses explains each one in more depth.
- Scope, deadline, and revision rounds, matching what you promised the client, with a buffer for your own review.
- Ownership of the work. If your client contract assigns rights to the client, you need the subcontractor to assign the same rights to you first, or you cannot pass them on.
- Confidentiality and data access, including which client systems they can use and what happens to files when the job ends.
- Client contact. Whether they may talk to the client directly, and whether they may solicit the client for their own work.
- AI tool use, if your client contract restricts it. The briefing on AI use clauses in client work covers what to check and pass down.
- Payment terms: fee, invoice date, and whether payment depends on the client paying you.
In the U.S., ask each subcontractor for a Form W-9 before you pay them. For payments made in 2026, you generally need to file Form 1099-NEC for each non-employee you pay $2,000 or more for services in the course of your business, up from $600 for earlier years (IRS instructions for Forms 1099-MISC and 1099-NEC). The 1099-K and 1099-NEC briefing covers the threshold change in more detail. In every country, how much you control a subcontractor's hours and methods can affect whether they count as self-employed, so check local rules if one person starts working for you close to full time.
The margin check
- Estimate subcontractor production cost.
- Add your briefing, review, communication, and rework buffer.
- Add client communication and project management time.
- Check whether the remaining margin still beats doing the work yourself.
- If not, raise price, narrow scope, or do not delegate this piece.
Worked example: is this delegation worth it?
This is a hypothetical example. A freelance web designer quotes a client $8,000 for a site build and plans to hand the front-end development to a subcontractor at $100 an hour for 35 hours, or $3,500.
- The designer's own hours: 4 for briefing, 6 for review, 6 for client communication and project management, and 4 as a rework buffer. That is 20 hours.
- Money left after the subcontractor: $8,000 − $3,500 = $4,500. Per hour of the designer's time: $4,500 ÷ 20 = $225.
- Doing it all themselves would take about 30 hours of development plus the same 6 hours of client work, so 36 hours: $8,000 ÷ 36 ≈ $222 an hour.
The hourly result is about the same, but delegating frees 16 hours for sales or another project, so it is worth doing. Now suppose the brief was weak and review turns up problems that take the designer 8 more hours to sort out: 28 hours in total, and $4,500 ÷ 28 ≈ $161 an hour. A weak brief and late QA turned a good delegation into a worse deal than doing the work alone.
Give feedback that improves the next round
- Give feedback within one working day, while the context is fresh for both of you.
- Point to the line in the brief or rubric that the issue relates to. If no line covers it, the brief needs updating, not the person.
- Say what good looks like, not only what is wrong.
- Thank people for raising risks early, even when the news is bad. That is the behavior you most want repeated.
- Keep a short note per collaborator of what they do well, so you give the next project to the right person instead of the most available one.
Reliable delegation is part of the same system that keeps clients coming back. The delivery and retention pillar shows how review windows, weekly updates, and change control fit around it.
FAQ
Is it OK for freelancers to subcontract work?
Usually yes, as long as your client contract allows it and you stay responsible for the result. Check for a clause on subcontracting or assignment before you hire help, since some contracts require the client's written consent. If the client expects you personally to do the work, ask before delegating any of it.
How much should I mark up subcontractor work?
There is no standard markup. Work out the subcontractor's cost, add your own briefing, review, and project management hours at your floor rate, and add a rework buffer. If the client fee does not cover all three with margin left over, raise the price, narrow the scope, or do that piece yourself.
Should I tell clients I use subcontractors?
Being open is usually safer than hiding it, and some contracts require it. You do not need to list every collaborator, but say that you work with a small team, that you review all work before delivery, and that you remain the single point of contact and accountability.
Do I pay subcontractors before the client pays me?
Decide this before work starts and put it in writing. Paying on your own schedule, regardless of when the client pays, builds trust and attracts better collaborators, but you need the cash buffer to do it. If you will only pay after the client pays, say so up front and give a latest payment date.
Previous: Project selection and optionality
Next: Boundaries and burnout

Comments
Sign in to comment.