TL;DR
On this page
A UX designer invoice has six distinct line categories that should never be lumped together: the sprint or phase fee, research session passthrough, tools and subscriptions passthrough, the design system handoff tier, dev support hours during implementation, and additional revision rounds. Bundle them and the client cannot tell what they are paying for. Separate them and you capture revenue most beginners leave on the table. The single most under-charged line is the design system handoff tier; tokens plus components plus Storybook documentation can add 25-50 percent to project total but is often given away free in junior engagements. This piece is the 6-line invoice structure, the sprint billing pattern, the design system handoff tiers, and the worked example that ties it all together.
The general freelance invoice basics live in how to write a freelance invoice. This post is the UX-specific deep dive.
Why UX Invoices Need Different Lines Than Graphic Design Invoices
A graphic design invoice has 6 lines (design fee, revisions, licensing, source files, stock assets, rush). A UX design invoice has 6 lines but the categories are different because UX work involves research costs, design system handoff, and developer implementation support that graphic design doesn't.
| UX line | Whose money is it? | Tax treatment |
|---|---|---|
| Sprint / phase fee | Yours (revenue) | Reportable income |
| Research session passthrough | Client's (not yours) | Pass-through |
| Tools / subscriptions passthrough | Client's (not yours) | Pass-through |
| Design system handoff tier | Yours (revenue) | Reportable income |
| Dev support hours | Yours (revenue) | Reportable income |
| Additional revisions | Yours (revenue) | Reportable income |
Four revenue lines plus two pass-throughs.
The 6-Line UX Designer Invoice Structure
| Line item | Type | Example |
|---|---|---|
| Sprint / phase fee | Fixed | "Sprint 3 (Design + Prototype, 2 wks): $11,500" |
| Research session passthrough | Pass-through | "User testing (12 sessions): $1,440 (receipts attached)" |
| Tools / subscriptions passthrough | Pass-through | "Maze team license (1 mo): $99 (receipt attached)" |
| Design system handoff tier | Tiered | "Tokens + components handoff: +$3,500" |
| Dev support hours | Hourly | "Dev handoff support: 6 hrs at $185/hr = $1,110" |
| Revisions (additional rounds) | Variable | "Round 4 revisions: $620 (3 hrs at $185)" |
Per InvoiceZap's UI/UX design invoice template, this 6-line structure is now the dominant format for product UX work because it surfaces every distinct billable category cleanly.
Sprint-Based Billing (the Dominant 2026 Model)
For product UX work, bill per 1-2 week design sprint at a fixed sprint fee.
| Sprint | Duration | Activities | Fee range |
|---|---|---|---|
| Discovery | 2 weeks | Stakeholder + user interviews, audit | $6,000-$15,000 |
| Research | 2 weeks | User research, synthesis, insights | $8,000-$18,000 |
| IA + Wireframing | 2 weeks | Information architecture, lo-fi wireframes | $7,000-$14,000 |
| Visual Design | 2 weeks | Hi-fi designs, design system | $9,000-$18,000 |
| Prototype + Test | 2 weeks | Clickable prototype, usability testing | $7,000-$15,000 |
| Handoff | 1 week | Dev specs, asset export, support docs | $4,000-$10,000 |
Total for full 11-week engagement: $41K-$90K depending on tier and complexity.
Per general product UX engagement patterns, sprint billing aligns cash flow with effort and makes it easy to pause or extend at sprint boundaries without renegotiating the whole contract. Each sprint has clear scope and clear deliverables.
Phase-Based Billing (For Smaller Defined-Scope Engagements)
For smaller engagements under $30K, phase-based 25/25/25/25 billing is standard.
| Phase | % of total | Trigger |
|---|---|---|
| Contract signing | 25% | Contract signed; engagement begins |
| Wireframes approved | 25% | Client signs off on wireframes |
| Visual designs approved | 25% | Client signs off on hi-fi designs |
| Final handoff | 25% | Dev handoff complete |
Per UX Design Institute's design handoff guidance, phase-based billing tied to client approvals is the standard structure for fixed-scope UX engagements; it works well for smaller projects but breaks down on larger product UX work where the scope evolves through research findings.
Research Session Passthrough (Always At-Cost)
Research costs pass through at-cost with platform receipts and participant incentive logs attached. Components:
| Cost type | Typical range |
|---|---|
| Participant recruiting (B2C) | $40-$120/participant |
| Participant recruiting (B2B) | $200-$500/participant |
| Testing platform fee | $40-$200/session |
| Participant incentive (B2C) | $25-$100/participant |
| Participant incentive (B2B SME) | $200-$1,000/participant |
| Travel for in-person research | at-cost with receipts |
Sample research passthrough line
User research (12 sessions, April):
- UserInterviews recruiting fee (12 participants × $90 = $1,080) (receipt attached)
- Participant incentives (12 × $30 Amazon GC = $360) (incentive log attached) Subtotal: $1,440 (paid on Card 4421, passed through at cost)
Never mark up research passthrough. Per general UX freelance pricing guidance, marking up participants or testing platforms breaks client trust and is increasingly prohibited in modern UX contracts.
Tools / Subscriptions Passthrough
Project-specific tool licenses pass through at-cost. Examples: Maze ($99/mo team), UserTesting ($150-$500/mo project), Optimal Workshop ($109-$249/mo), Lookback ($25-$100/session), Dscout ($300+/mo).
Sample tools passthrough line
Tools subscription passthrough (April):
- Maze team license (1 month, project-specific): $99 (receipt attached)
- Optimal Workshop credits (treejack + first-click test): $159 (receipt attached) Subtotal: $258 (passed through at cost)
Tools you already own (Figma, FigJam, Notion) are NOT pass-through; they are part of your operating overhead and built into your sprint fee.
Design System Handoff Tiers (the Most Under-Charged Line)
| Tier | What client gets | Fee added |
|---|---|---|
| None | Final designs + asset export only | $0 |
| Tokens only | Color/type/spacing tokens organized in Figma | +$1,500 |
| Tokens + components | Above + reusable Figma components with variants/props | +$3,500 |
| Full system + Storybook | Above + published Storybook + docs site + design-token JSON | +$8,500 |
Per UXPin's design handoff guide and UX Studio's handoff guide, the design system handoff is what determines whether the engineering team can implement consistently or whether they re-create inconsistent design over and over.
pro tip
Don't include design system handoff in your base sprint fee. Most clients underestimate the value, and most junior UX designers under-price it. List the handoff tiers explicitly in the proposal and contract so the client elects what they need. The most common procurement-friendly tier is "Tokens + components" at +$3,500 because it gives the engineering team enough structure to implement consistently without the overhead of a full Storybook.
Dev Support Hours (Separate Line, Not Bundled)
Dev handoff support during implementation is billable hourly. Don't bundle it into the design fee.
Sample dev support line
Dev handoff support (April):
- Sync with engineering on token implementation (April 22): 1.5 hrs
- Spec clarifications + screenshots for engineering (April 24-26): 3 hrs
- Visual QA review on staging (April 28): 1.5 hrs Subtotal: 6 hrs at $185/hr = $1,110
Pre-disclose the dev support hourly rate in the contract. Pre-approve a budget cap (typical: 20-30 hours of dev support per engagement) so the client can plan against it.
Revisions
Three rounds with explicit purpose. Round 4+ is paid hourly.
| Round | Purpose | What counts |
|---|---|---|
| 1 | Concept / direction (after first design presentation) | Strategic shifts |
| 2 | Refinement (within-direction edits) | Layout, color, type adjustments |
| 3 | Polish (final pixel adjustments) | Micro-edits |
| 4+ | Paid round at $185/hr (1-hr minimum) | All client requests |
Worked Example: Sprint-Based UX Engagement Invoice (Sprint 3)
Hypothetical April 2026 invoice for a product UX engagement, Sprint 3 (Design + Prototype):
INVOICE #2026-0094
Issued: 2026-04-30
Due: 2026-05-15 (Net-15)
PO #: 2026-UX-0078
Bill to: Crafted Goods Inc.
Project: Mobile app redesign UX engagement, Sprint 3
SOW: dated Mar 15, 2026
Sprint 3 deliverables completed in April:
- Hi-fi designs (12 screens)
- Clickable prototype (Figma)
- Component library v1
- Mid-engagement design review (April 28)
Description Amount
-----------------------------------------------------------
Sprint 3 fee (Design + Prototype, 2 weeks) $11,500.00
Per Section 4 of SOW.
User research session passthrough (April) $1,440.00
UserInterviews recruiting (12 × $90): $1,080
Participant incentives (12 × $30): $360
Receipts + incentive log attached.
Tools subscription passthrough (April) $258.00
Maze team license (1 mo): $99
Optimal Workshop credits: $159
Receipts attached.
Design system handoff (Tokens + components) $3,500.00
Per Tier 3 election in proposal Section 9.
Delivered: Figma color/type/spacing tokens
+ 18 reusable components with variants.
Dev handoff support (April) $1,110.00
6 hrs at $185/hr (time log attached)
Round 3 polish revisions $0.00
Within scope (Round 3 included)
-----------------------------------------------------------
SUBTOTAL $17,808.00
Of which: Fees (revenue) $16,110.00
Of which: Pass-through (not revenue) $1,698.00
TOTAL DUE $17,808.00
Payment terms: Net-15. Late fee: 1.5%/mo.
Pay via ACH or wire to: [bank details]
Sprint 4 (Prototype + Test): scheduled May 5-19
Forecasted invoice: $9,500-$15,000 + research passthrough
Common UX Designer Invoice Mistakes
UX Designer Invoice Mistakes to Avoid
How This Connects to Your Other Documents
This invoice gets sent against the engagement defined in the UX proposal that shows process value. The sprint structure, design system handoff tier, and dev support cap should mirror the proposal exactly. For pricing benchmarks behind your sprint rates, see the 2026 UX Salary vs Freelance Rate Comparison.
For the parallel pattern in graphic design (source files + license tier), see graphic design invoice. For the parallel pattern in consulting (multi-fee model + value-based bonus), see consultant invoice (retainer/hourly/value).
For payment term strategy, see freelance payment terms. For chasing late payments, see how to deal with late paying clients.
Tools
The FreelanceDesk invoice builder handles the 6-line UX invoice structure with separate columns for sprint fee, research passthrough, tool passthrough, design system handoff tier, dev support hours, and revisions. It auto-attaches platform receipts and generates the fees-vs-pass-through subtotal split.
For invoicing app comparison, see best invoicing apps for freelancers in 2026.
References
- InvoiceZap - Professional UI/UX Design Invoice Template
- ClickUp - Invoice Template for User Experience Design Services
- Get Harvest - Invoice Template for UX Designers
- InvoiceOnline - UX/UI Designer Invoice Template
- TrulySmall - Free Designer Invoice Templates
- FreshBooks - Freelance Designer Invoice Templates
- Freel.ca - Free Freelance UI/UX Designer Contract Template Canada 2026
- UX Design Institute - How to Create a Design Handoff for Developers
- UX Studio - Battle-Tested Design Handoff Guide
- UXPin - Design Handoff Basics: What Do Developers Need from Designers
- Design Monks - How Much Does UI/UX Design Cost: Freelancer to Agency
- Visily - From Design to Dev: Why Smooth UI/UX Handoff Can Make or Break Your Product
- Medium - A Handoff Between UX Research and Design? Not So Much
- Behance - UI/UX Design Services Freelance Hire
- Upwork - Best Freelance UX Designers for Hire