
UX Agency Contract Checklist: What to Include and Negotiate

925studios
AI Design Agency
UX Agency Contract Checklist: What to Include and Negotiate
Reviewed by Yusuf, Lead Designer at 925Studios
Most UX agency contracts are written to protect the agency, not the client. IP ownership, revision limits, termination clauses, and kill fees are where the real leverage sits, and most founders skim past them. A vague scope definition benefits the agency. A 90-day termination notice locks you in long after the relationship has stopped working. IP that transfers "upon full payment" sounds reasonable until the agency defines completion differently than you do. The 15 checklist items below cover every clause worth scrutinizing before you commit a five-figure engagement to paper. None of them require a lawyer to spot. All of them are negotiable with a professional agency that expects you to read the contract.
TL;DR:
Standard agency contracts favor the agency on IP, termination, and revision limits. Know what to push back on.
IP should transfer to you in writing upon full payment, not "by implication."
Kill fees of 10-25% of remaining contract value are standard and reasonable. Watch for agencies that structure them differently.
Two revision rounds per deliverable is the market norm. More than that should be documented and priced.
Push termination notice periods from 60-90 days down to 30 days for performance-related exits.
Quick Answer: A UX agency contract should include: clearly defined deliverables and scope, written IP transfer upon full payment, 2 revision rounds per deliverable, a 30-day termination clause for performance failures, a kill fee of 10-25% of remaining value for cancellation, liability capped at 3-6 months of fees, explicit data confidentiality terms, and unconditional access to all accounts and assets. These 8 categories cover the clauses most founders miss before signing.
Why does your UX agency contract matter more than most founders expect?

A Series A funding round stalled when investors discovered a founder's contractor had never signed an IP assignment agreement (StartupBos, 2024). The design work the company had been showing in pitch decks was, legally, not theirs. This is not a rare edge case. IP, termination, and account access disputes are the three most common sources of agency conflict, and all three originate in contract language most founders never scrutinize because the agency presented it as standard.
Standard does not mean fair. It means the agency's lawyer wrote it for the agency's benefit. Every clause in a professional services agreement was put there intentionally, and most are negotiable. The agencies that push back hard on contract questions are the ones worth avoiding. A confident, experienced studio expects you to read the contract and ask questions before signing.
Across the engagements we run at 925Studios, founders who ask clear contract questions upfront consistently have smoother projects. The questions force both sides to align on scope, IP, and exit conditions before work starts, which prevents the disputes that derail projects mid-delivery.
If you are still deciding which agency to hire, this hiring checklist covers the 15 questions to ask before you sign with anyone.
What should your UX agency contract checklist cover?
Work through the contract section by section against the following categories. Flag anything that does not match what was discussed verbally and ask for written clarification before signing.
Category 1: Scope and Deliverables
1. Every deliverable is named and described specifically. Vague language like "design work" or "UX improvements" protects the agency, not you. The contract should name each deliverable (wireframes, prototype, design system documentation, handoff files), the format (Figma, PDF, HTML), and who owns sign-off on completion. Anything not in the scope document is not included in the price.
2. Out-of-scope work has a defined process. Changes happen. The contract should describe exactly what triggers a change order: new features, pivot in product direction, additional screens. Change orders should require written agreement from both sides before additional work starts. Verbal approvals are not enforceable.
3. Timeline milestones are tied to deliverables, not calendar dates alone. A calendar date for delivery is meaningless if the agency's delivery depends on your timely feedback. Good contracts include mutual dependencies: the agency delivers by date X, assuming the client provides feedback within Y business days of each review.
Category 2: Intellectual Property
4. IP transfer is written and explicit. IP does not transfer "by implication." It transfers by written, signed conveyance in the contract. The clause should state that all custom deliverables created under this agreement become the client's property upon full payment. Watch for language that says "license to use" rather than "ownership transfers." A license means the agency retains the underlying rights. According to legal experts at LegalGPS (2024), this is the most common IP dispute in creative services agreements, and it originates from language founders do not notice until the relationship ends.
5. Pre-existing agency tools and frameworks are carved out correctly. Agencies sometimes build on proprietary design frameworks, component libraries, or internal tools they own before your engagement. That is normal. The contract should clearly distinguish between what is custom to you (and transfers to you) and what is the agency's pre-existing IP that you are licensed to use during the engagement. The license terms for that pre-existing material should survive the contract end.
6. Third-party assets are clearly documented. If the agency uses stock photography, icon libraries, or licensed fonts in your deliverables, the contract should specify which licenses are included, who holds them, and what rights transfer to you. A design that includes a font licensed only to the agency means you cannot legally use it in production without purchasing your own license.
Not sure what to look for in an agency's portfolio before any of this reaches contract stage? This decision framework for hiring a SaaS UX agency covers evaluation criteria before you negotiate anything.
Category 3: Revision Rounds and Change Management
7. Revision rounds are numbered and defined per deliverable. Two revision rounds per major deliverable is the market standard. "Unlimited revisions" in the contract language either means the scope is vague or you will be managing a strained relationship where the agency eventually pushes back informally. Push for a clear number (two to three rounds), a definition of what counts as a revision versus a change request, and an hourly rate for work beyond that limit.
8. Feedback deadlines are mutual. The agency has delivery deadlines. You should have feedback deadlines too. Contracts that only specify agency delivery dates but not client response windows create conflicts when projects stall because the client was slow to review. A professional contract specifies feedback windows (five to seven business days is typical) and states that delayed feedback extends the project timeline accordingly.
Category 4: Payment Terms and Kill Fees
9. Payment milestones are tied to deliverable acceptance, not calendar dates. A schedule that bills you on the 1st of each month regardless of delivery progress is an agency-favorable arrangement. Better contracts tie payment to milestone completion: 30% on kickoff, 40% on approved wireframes, 30% on final delivery. Milestone-based payment gives you leverage if delivery stalls.
10. Kill fees are fair and clearly structured. If you cancel mid-project, a kill fee compensates the agency for work completed and for the opportunity cost of turning down other work. A standard kill fee structure: you pay for all completed work at the agreed rate plus 10-25% of the remaining contract value. Watch for kill fees that exceed the value of completed work or that trigger even when the cancellation is due to the agency's performance failure.
At 925Studios, our contracts include kill fee clauses that apply only to client-initiated cancellations and are waived entirely if the cancellation is triggered by missed agency deliverables. That distinction protects both sides.
Category 5: Termination and Exit
11. Notice period is realistic. Agency contracts often include 60-90 day notice periods for termination. This is longer than necessary for most startup engagements and creates a lock-in period that protects the agency's revenue more than it serves your project. Push for 30-day notice for standard termination and immediate termination with cause for material breach (missed deadlines, delivered work that does not match the agreed scope).
12. Exit handoff is defined. What happens to your files, accounts, and materials when the contract ends? The contract should specify: all project files are delivered in their native format within X business days of project completion or termination, all agency access to your tools and accounts is revoked upon project end, and a transition document is provided if requested. This prevents the common situation where an agency holds your files hostage during a dispute.
Category 6: Confidentiality and Data Protection
13. Confidentiality terms are mutual and specific. The agency should not share your product roadmap, user research data, unreleased designs, or business information with any third party. NDA terms should specify: what is covered (all non-public product and business information), how long the obligation lasts (two to three years post-project is standard), and what happens in case of a breach (dispute resolution mechanism, not just "you can sue us").
14. Data handling complies with applicable law. If the agency will access any user data, analytics data, or systems that contain personal information, the contract should include a data processing addendum that specifies how data is handled, stored, and deleted at project end. For products in regulated markets (fintech, healthtech), this clause is not optional.
Category 7: Liability and Dispute Resolution
15. Liability cap is proportional to the contract value. Agency contracts typically include a liability cap limiting the agency's financial responsibility in case of errors or omissions. A cap at one month's retainer is agency-favorable and genuinely insufficient for a six-month engagement. Negotiate for a liability cap of at least three to six months of fees, or the full contract value for engagements under six months (LegalGPS, 2024). Also check that the dispute resolution clause specifies the governing law and jurisdiction, and confirm it is yours, not the agency's.
What mistakes do founders make when signing design agency contracts?

The most expensive mistake is assuming "standard" terms are non-negotiable. Every professional agency expects contract questions. An agency that tells you the contract is non-negotiable is giving you important information about how the relationship will go.
The second mistake is signing without confirming account access. Founders have found themselves unable to access their own analytics, ad accounts, and design files because the contract did not specify that access was unconditional. Confirm in writing that access to all accounts, tools, and materials is yours regardless of payment status, with any payment disputes handled separately through the dispute resolution clause.
Our honest take: most contract disputes with design agencies come from scope ambiguity, not bad intent. An agency that is vague about deliverables is usually not trying to cheat you. They just wrote a contract that protects their flexibility. That flexibility comes at your expense. Specificity in the contract benefits both sides because it removes the ambiguity that causes disputes mid-project.
The third mistake is not documenting verbal agreements. If a scope, timeline, or payment agreement was made in a call or email, it needs to be reflected in the written contract or in a written amendment. "But we agreed on the call" is not a legal argument in a dispute.
What are your next steps before signing a UX agency contract?
Work through the 15 checklist items above before you sign. Flag anything that does not match what was discussed and ask for a written amendment. For engagements over $15,000, a one-hour review with a commercial contracts lawyer costs $150-$400 and is worth every cent. Most disputes that founders describe as "the agency screwed me" were actually contract disputes that a 30-minute read would have prevented.
Once the contract is signed, save a copy where your team can access it, set a calendar reminder for the termination notice date (so you can exit cleanly if the project is not going well without missing the notice window), and document all verbal scope changes in writing immediately after they happen.
If you want to understand what a well-structured agency onboarding looks like before the contract is even relevant, this guide covers what to expect in the first 30 days with a UX agency.
Frequently Asked Questions

What should be in a UX agency contract?
A UX agency contract should include: a specific deliverables list with formats and acceptance criteria, written IP transfer to the client upon full payment, numbered revision rounds per deliverable, a kill fee structure (10-25% of remaining contract value for client-initiated cancellation), a 30-day termination notice clause with immediate exit for material breach, a liability cap of at least 3-6 months of fees, mutual confidentiality terms, and defined access to all accounts and assets at project end.
Who owns the design work after a UX agency project?
The client should own all custom deliverables upon full payment. This ownership must be stated explicitly in the contract as a written IP assignment, not implied. If the agency used pre-existing frameworks, templates, or proprietary tools, those remain the agency's property, but you should have a license to use them in your product. Any stock assets, licensed fonts, or third-party components should be documented separately with their license terms.
What is a kill fee in a design agency contract?
A kill fee is the payment you owe the agency if you cancel the project mid-engagement. It compensates the agency for work completed and for opportunity cost (turning down other work to take yours). A standard kill fee is: payment for all completed work at the agreed rate, plus 10-25% of the remaining contract value. A fair contract also specifies that the kill fee does not apply if the cancellation is triggered by the agency's failure to deliver as agreed.
How many revision rounds should I negotiate in a design contract?
Two revision rounds per major deliverable is the market standard for most design engagements. Three rounds is reasonable for complex deliverables like a full design system or multi-page product redesign. Beyond that, additional revisions should be billed at an agreed hourly rate. The key distinction in the contract is what counts as a revision (minor changes to an approved direction) versus a change request (a new direction or new scope), which should be handled as a change order at a separate cost.
What notice period should I negotiate for ending a design agency contract?
Push for 30 days notice for standard termination, down from the 60-90 days that agencies often include as default. Also negotiate an immediate termination with cause provision for material breach, defined as: missed deliverable deadlines by more than 10 business days, deliverables that do not match agreed scope after the revision process, or breach of confidentiality. A 30-day notice period is fair to both sides and gives the agency enough time to wrap up work in progress without locking you in.
Should I hire a lawyer to review a design agency contract?
For engagements over $15,000, a commercial contracts lawyer reviewing for one hour at $150-$400 is worth the cost. For smaller engagements, working through the checklist above and asking the agency to amend specific clauses in writing is usually sufficient. The clauses that trip up founders most (IP assignment language, termination notice, liability caps) are not complex legal concepts. They are specific phrases that mean something different from how they sound at first read.
What happens to my files and accounts when a design agency contract ends?
The contract should specify: all native design files (Figma, Sketch, source files) are delivered within a set number of business days of project completion or termination; all agency access to your tools, accounts, and platforms is revoked; and a transition document is provided if requested. If the contract does not include an exit handoff clause, add one as an amendment before signing. Never assume the agency will hand over files voluntarily after a difficult project ends without a contractual obligation to do so.
What are the red flags in a design agency contract?
Watch for: IP language that says "license to use" instead of "ownership transfers on full payment," termination notice periods exceeding 60 days with no performance-related exit clause, kill fees that apply even when cancellation is due to the agency's failure, liability caps limited to one month of fees on a six-month engagement, vague deliverable descriptions that give the agency discretion over what "completion" means, and no account access clause confirming access to your own tools is unconditional and not contingent on payment status.
Tired of managing three vendors for design, motion, and brand? 925Studios is one creative partner across every visible surface of your product.
If you're building a product and want a team that covers product design, motion, and founder video under one roof, talk to 925Studios. We work with SaaS, fintech, healthtech, web3, and AI founders.
See our work or book a free 30-minute call.
Follow us on Instagram and YouTube for design breakdowns and case studies.

