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.
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.
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.
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.
Previous: Project selection and optionality
Next: Boundaries and burnout
Comments
Sign in to comment.