Borrowed Paper, Borrowed Risk: A Solo Designer's Guide to Subcontract Agreements
Photo: Lee Campbell leecampbell, CC0, via Wikimedia Commons
When a solo designer takes on work from a larger studio, the paperwork typically arrives already written. The prime has signed a master services agreement with an end client, and the terms of that agreement travel downhill — sometimes through an explicit flow-down clause, more often through a short email asking you to review the attached contract and return it signed.
That is the moment a straightforward freelance engagement quietly becomes something else. A designer who intended to sell a defined scope can find themselves warranting the prime's entire deliverable, accepting payment contingent on a client they will never meet, and granting rights considerably broader than the project requires.
None of this implies bad faith on anyone's part. It is simply what happens when a document drafted to protect a firm with in-house counsel and a risk manager is handed to a practice of one. The remedy is not a longer contract. It is a shorter one, written in plain language, that names the handful of terms determining whether the engagement is workable at all.
What follows is a working outline, not legal advice. Any agreement worth signing should be reviewed by an attorney licensed in your state.
Why Borrowed Paper Rarely Fits
Prime agreements are built for scale: multi-vendor coordination, indefinite delivery, warranties that run for years. A solo designer delivering a website refresh over eleven weeks does not need most of that machinery, but inheriting it costs real money in insurance premiums, legal review, and uninsured exposure. The practical move is not to redline the master agreement. It is to offer a one- or two-page subcontract rider that sits beneath it and speaks only to the terms that matter at your scale. Primes accept riders far more often than solo designers expect, provided the rider is short, legible, and does not reopen commercial questions already settled upstream.
Scope: Name the Deliverables and the Decision Rights
Vague scope is the most common source of unpaid rework in subcontract relationships. Specify deliverables by name, format, and count — three homepage concepts, one component library, two rounds of revision — and state plainly what is not included. Then address decision rights, because scope disputes are usually authority disputes in disguise. Who at the prime has approval authority? How many business days does a review cycle take? What happens when feedback arrives late? A single sentence establishing that schedule dates shift day-for-day with delayed feedback protects both parties and costs nothing to include.
Payment: Distinguish Pay-When-Paid from Pay-If-Paid
These two phrases sound interchangeable and are not. Under a pay-when-paid term, the prime commits to passing your fee along once the client pays, generally within a defined window. Under pay-if-paid, the client's payment becomes a condition precedent to any obligation — meaning you may never be paid if the end client stalls. Several states restrict or void pay-if-paid clauses in construction subcontracts, and the enforceability of similar language in design services varies. If you cannot avoid the term entirely, ask for a long-stop date: payment due regardless of client remittance after a fixed number of days. Also fix the invoicing cadence, the net terms, and whether the prime passes through any markup or fee.
Portfolio, Credit, and the Right to Show the Work
Confidentiality clauses drafted for enterprise clients frequently swallow portfolio rights by accident. Ask for an explicit carve-out permitting you to display the work after publication, with a reasonable embargo, and to describe your role accurately. Credit language belongs here too: a line in the project footer or a mention in the case study. If the end client requires approval before display, name the approver and a response deadline so silence does not become a permanent no.
Indemnity: Cap It, Define It, and Insure What Remains
Standard prime paper often asks the subcontractor to indemnify the prime against all claims arising from the work, without limit. For a solo practice, that is unbounded exposure against a document you did not draft. Ask for three things: mutual indemnity (each party covers its own negligence), a cap tied to fees paid under the subcontract, and an exclusion for consequential and indirect damages. Then check that your professional liability policy limit is at least equal to the cap you have accepted. If the cap exceeds your coverage, the cap is fiction.
Termination and the Exit File
Establish termination for convenience on both sides with a defined notice period, plus payment for work performed and expenses committed to that date. Add a sentence describing what happens to files: on final payment, you deliver source files and documentation in agreed formats, and the license transfers. Without that sentence, a terminated project can turn into a hostage negotiation over deliverables that were never contractually owed.
The Shape That Survives Review
Six short sections, numbered, in a document a project manager can read in four minutes. Attach it to the prime's contract rather than replacing it. Circulate it at the outset, before the first kickoff call, when everyone still has room to negotiate. Designers who present a tidy rider alongside a competitive fee typically find that the conversation is shorter and more collegial than they feared — and that the terms they inherit are finally their own.