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

TL;DR: Tie every invoice line to a milestone or sprint your stakeholders already approved, separate research, prototyping, and handoff phases, and list expenses like participant incentives and tool licences as their own pass-through items.

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.

Hourly billing ($100-$200+ in tech hubs) suits ongoing embedded product work and ambiguous scopes. Fixed-sprint pricing (e.g., two-week discovery $8,000-$15,000) works when the scope and deliverables are well-defined. Monthly retainers ($5,000-$15,000+) suit embedded product design roles where you attend standups and ceremonies like a team member. Per-deliverable pricing (usability study $3,000, heuristic review $1,500) works for discrete research or audit projects.

Raise rates when you develop specialisation (healthcare UX, fintech compliance, accessibility), when you can demonstrate business outcomes from past work (conversion lifts, task-completion improvements), or when your calendar is booked two-plus months out. Senior UX consultants with 8+ years of experience and a track record of shipping products typically command $150-$250/hr or equivalent project rates.

Sample invoice line items

When to send the invoice

For milestone-based engagements, invoice at each milestone sign-off: after the research readout, after prototype approval, and after dev handoff. Tie the invoice to a specific deliverable the stakeholder already reviewed and approved -- this eliminates "what are we paying for?" questions.

On monthly retainers, invoice on the first business day of each month for the upcoming month's work. Include a brief summary of the previous month's output to reinforce value and justify renewal.

For enterprise clients on Net 30, submit the invoice within 48 hours of the milestone completion and include the PO number and project code. Ask finance for their AP submission deadline during onboarding -- missing the cut-off pushes you into the next payment cycle.

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.

Absorbing participant recruiting costs without billing them -- recruiting screeners, scheduling tools, and incentives add up quickly on a multi-round study; show them as pass-through expenses. Not separating design-system work from feature work -- if you spent 15 hours updating the component library and 25 hours on the checkout flow redesign, those are different budget lines for different stakeholders. Letting post-handoff Slack support bleed indefinitely -- define a support window (e.g., 2 weeks after handoff, up to 5 hours) in the contract and show the drawdown on the invoice.

FAQ

Should I charge for stakeholder workshops separately from design work? Yes. Workshops require preparation (agenda, exercises, Miro boards), facilitation time, and synthesis afterward. Billing them as a flat fee per session ($1,500-$3,000) or as a separate time block makes the effort visible and prevents stakeholders from treating prep work as free overhead.

How do I invoice when the project is paused by the client? Reference the pause clause in your contract. Issue an invoice for all work completed through the pause date. If your contract includes a re-engagement fee or calendar-hold charge for pauses longer than a set period, invoice that as well. Note the pause date and expected restart date on the invoice for record-keeping.

What is the best way to show hours on a retainer invoice? List total hours available, hours used (with a brief summary of what was worked on), and hours remaining. This transparency builds trust and helps the client decide whether to adjust the retainer size at renewal. If rollover is allowed, show the rollover balance too.

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.