Stop losing money on
Ux Designer projects.
A missing contract turns a simple five-screen prototype into a never-ending cycle of unpaid Figma revisions. Without written boundaries, you are essentially giving away your specialized research and strategic thinking for free.
Pro Tip
Include a Phase-Gate Approval clause that requires a written sign-off on wireframes before you begin any high-fidelity UI work to prevent back-tracking.
Figma Seat and Tooling Costs
If the client expects to collaborate in real-time, the contract must specify who pays for the professional Figma seats or specialized user testing platform subscriptions.
Indefinite Prototype Hosting
Maintaining interactive prototypes on services like Framer or Axure can incur ongoing costs that should not fall on the designer after the project ends.
The Infinite Iteration Trap
UX work is subjective by nature; without a capped number of revision cycles, a client can demand endless variations under the guise of user-centricity.
Built from real freelance projects
This template is based on real-world scenarios across freelance projects where unclear scope, missing payment terms, and revision creep led to lost revenue. It is designed to protect your time, define expectations, and ensure you get paid.
What is a Ux Designer contract?
A UX Designer contract template is a legally binding agreement that defines the scope of user experience work, including research, wireframing, and prototyping. It protects designers by setting clear limits on revisions, defining ownership of design files, and establishing a payment schedule tied to project milestones to prevent scope creep.
Quick Summary
A professional UX Designer contract is essential for managing complex digital projects. It outlines specific deliverables like journey maps, wireframes, and prototypes while protecting the designer from scope creep and unpaid revisions. Key components include intellectual property transfer clauses, Figma seat cost responsibilities, and milestone-based payment schedules. By using a specialized template, UX professionals can ensure they are compensated for both strategic research and visual design. This document serves as a roadmap for the collaboration, clarifying how feedback is handled and how the final developer handoff will occur to avoid post-project disputes.
Why Ux Designers need a clear contract
UX design is an iterative process that can easily spiral out of control because clients often confuse high-fidelity visuals with the entire scope of work. A specific contract defines the difference between a minor UI tweak and a structural change to the user flow. It protects you from the technical debt of a project that grows in complexity as the client discovers new business requirements mid-sprint. Without a formal agreement, you risk losing dozens of hours to stakeholder feedback loops that were never factored into your initial quote. A contract ensures you are paid for the discovery, the research, and the testing phases, not just the final exported assets. It establishes you as a consultant rather than a pixel-pusher, setting clear expectations for tool access, user testing recruitment, and final handoff protocols.
Do you need an invoice or a contract?
Invoices help you get paid, but they do not define scope, revisions, or ownership. For most projects, professionals use both a contract and an invoice to protect their work and cash flow. MicroFreelanceHub bundles both into a single link.
Real-world scenario
A freelance UX designer agreed to a flat fee for a mobile app redesign. The initial agreement was verbal, focusing on the checkout flow. Three weeks in, the client decided to pivot the entire business model from B2C to B2B. This change required a complete overhaul of the information architecture and the creation of an administrative backend that was never discussed. Because there was no signed contract defining the specific screens or a change-order process, the designer felt pressured to complete the extra work to secure the final payment. They ended up working 60 hours extra for zero additional dollars. If they had a contract, the pivot would have triggered a new project estimation or an hourly overage rate, saving the designer thousands of dollars in lost billable time.
🛡️ What this contract covers:
- ✓User Persona documentation and journey maps
- ✓Low-fidelity wireframes for core user flows
- ✓Interactive high-fidelity prototypes in Figma or Penpot
- ✓Comprehensive UI Style Guide or Design System documentation
- ✓User research summary reports and usability testing findings
- ✓Developer handoff files including CSS specs and asset exports
Pricing & Payment Strategy
UX designers should secure a 50 percent upfront deposit before starting discovery work. Use milestone-based payments tied to specific phases like Research Completion, Wireframe Approval, and Final Handoff. Avoid flat rates for long-term projects; instead, include a clause for an hourly rate to cover meetings and ad-hoc developer support. Always include a 15 percent late fee to ensure your cash flow remains steady while the client reviews your work.
Best practices for Ux Designers
Define Revision Boundaries
Explicitly state that you provide two rounds of revisions per milestone and that further changes incur an hourly fee.
IP Transfer on Final Payment
Specify that the client only owns the Figma source files and intellectual property once the final invoice is paid in full.
Specify Handoff Format
State exactly how files will be delivered, such as a Figma link or exported SVG files, to avoid post-project tech support.
Statement of Work
REF: 2026-0011. Covered Provisions
This agreement officially documents the following parameters:
- User Persona documentation and journey maps
- Low-fidelity wireframes for core user flows
- Interactive high-fidelity prototypes in Figma or Penpot
- Comprehensive UI Style Guide or Design System documentation
- User research summary reports and usability testing findings
- Developer handoff files including CSS specs and asset exports
Exclusions (Out of Scope)
- × Requesting a full marketing landing page design when the scope only covered the product dashboard.
- × Asking for the design of five additional edge-case user flows that were not part of the initial sitemap.
- × Demanding the designer attend daily developer stand-ups for three weeks beyond the scheduled handoff date.
Legal Disclaimer: MicroFreelanceHub is a software workflow tool, not a law firm. The templates and information provided on this website are for general informational purposes only and do not constitute legal advice.
Frequently Asked Questions
Do I need to include a kill fee in my UX contract?
Yes, a kill fee ensures you are compensated for work completed if the project is cancelled during the research or wireframing phases.
Should I give the client access to my Figma source files immediately?
No, your contract should state that full edit access and ownership transfer only happen after the final payment is received.
How do I handle user testing participants in the contract?
Specify that the client is responsible for any third-party costs related to recruiting users or providing incentives for testing sessions.