How to Invoice as a UX Designer: Rates, Terms and Templates

UX work spans discovery, research synthesis, IA, prototyping, and handoff. Invoices should tie to milestones your stakeholders already approved—otherwise “UX” looks like a black box. When you bill workshops or travel, separate them from Figma file delivery so finance can allocate cost centres.

Accessibility audits, usability tests, and design QA after dev are distinct phases—blur them and you absorb unpaid time. Design-system maintenance (tokens, components, documentation) is often sold as a retainer; if you fold it into “product design hours,” product and marketing will both assume it is free forever. OKR or KPI workshops that look like meetings still consume prep and synthesis—bill the working sessions and the readout separately when pricing discovery-heavy quarters.

Typical rates

Contract hourly ($100–$200+ in many tech hubs) or fixed sprints (e.g. two-week discovery). Embedded product contracts may use monthly billing. Participant incentives and recruiting should be expense lines with receipts. Nielsen Norman Group UX research topics give clients an external anchor on why structured research is not “just asking users.” Workshop facilitation can be flat per day plus materials; synthesis readouts can be fixed per study—mixing them into one hourly bucket obscures value. Design QA after dev launch should be scoped as buckets of hours or timeboxed sprints—otherwise engineering Slack becomes an infinite invoice leak. Competitive benchmarking and heuristic reviews can be fixed-price mini-deliverables—great for filling a slow week without open-ended hourly fear from the client. Stakeholder workshops that run long still bill against the sold block unless you explicitly gift the overage.

Payment terms

Deposit before kickoff workshops, milestone after research readout or prototype sign-off, final before dev handoff package per agreement. Enterprise: Net 30 with PO. Late fees where permitted—mirror your MSA. See invoice payment terms. PO burn-down clients need remaining budget noted in your cover email even when the PDF is clean—finance lives in spreadsheets.

What to include

Client, product or initiative name, sprint or phase description, hours × rate or fixed fee, workshop counts, expenses, tool licences if rebilled, subtotal, tax, total, due date. Reference SoW version in notes. Use how to write an invoice for standard fields and consistent invoice numbering across parallel workstreams. Research participant counts and incentive totals should be visible when legal reviews the bill—even if incentives are a pass-through, transparency matters. Figma or FigJam links belong in internal records; the PDF can stay clean with a short “deliverables per link shared [date]” note when procurement forbids URLs.

Common mistakes

Billing “UX—40 hrs” with no milestone mapping. Eating recruiter fees for user tests. Unlimited post-handoff questions not scoped. Invoicing after quarter close when procurement already locked the budget. Handoff files delivered without a sign-off email—attach or reference the approval thread in internal records. Localisation and content design assumed included when only English wireframes were priced. Engineering “quick favours” after handoff—if you bill them, label them T&M discovery or support bucket so PMs do not think design debt is free forever.

Template link

The freelance invoice template fits milestone-based UX engagements alongside expense rows.

---

Join early access to align invoices with research readouts and sprint demos.