How to Invoice as a UX Designer: Phases, Sprints, Retainers

UX projects are hard to invoice because much of the output is invisible to the person approving the payment. A finance manager sees "UX design, 40 hours, $6,000" and has no way to tell what was bought. An invoice line that names a deliverable the product team has already accepted gets paid. "Phase 2: checkout prototype, 12 screens, approved 3 March" is an example.

This guide shows how to structure invoices for the main UX engagement types, with a complete phase-billed project example, then the enterprise paperwork and the support-window problem that costs freelancers the most unpaid time.

What should a UX design invoice include?

Include the standard details: your business and the client's, an invoice number, issue and due dates, line items and the total. See how to write an invoice for those. Then add what product and finance teams look for:

• SOW reference and version. "Per SOW v2, signed 6 January" settles most scope arguments before they start.
• Phase or sprint name, with the approval date and the artefact approved (readout deck, Figma prototype, handoff file).
• PO number and cost centre for enterprise clients. Without them, accounts payable may return the invoice unpaid.
• Pass-through costs: participant incentives, recruiting fees, transcription and project-specific tool seats, each at cost with a receipt.
• Support or QA drawdown: hours used against the cap, and hours remaining.
• Payment terms that match the contract, for example Net 30 for enterprise.

Worked example: a checkout redesign billed by phase

Hypothetical example. A freelance UX designer signs SOW v2 with an online retailer to redesign checkout. The SOW has three phases with fixed fees, plus pass-through costs at cost and a capped support window:

The invoices that follow:

Invoice 2 is $450 in incentives plus a $240 panel fee. Invoice 4 is $2,000 plus 7 × $150 = $1,050. Every line points at something the client approved or can check: a signed SOW, a readout, a prototype, receipts and a time log. Nobody in finance has to ask the product team what the money was for.

Phase 1 is billed at signing because recruiting participants costs money and takes time, and a client who cancels after research starts would otherwise owe you for work with nothing invoiced. If a client cannot pay before work starts, an alternative is to split each phase into two payments, half at the start and half on approval.

How do you bill research incentives and tools?

Treat them as the client's costs that you pay on their behalf, not as part of your fee.

• Incentives: one line with the participant count and the amount each ("6 × $75"), at cost, with receipts. Agree in the SOW whether you or the client pays participants directly. Some enterprise clients pay incentives through their own research operations team.
• Recruiting and panel fees: at cost, with the receipt.
• Tool seats: a tool you use for all clients belongs in your rate. A seat bought for one project, such as a recording tool for one study, can be billed at cost for the months it was used.
• Travel for in-person workshops: at cost, or a day rate for travel time, as the SOW says.

If you add a handling markup to pass-through costs, state it in the SOW. A markup that first appears on an invoice is the kind finance teams query.

How do you stop post-handoff support from becoming unpaid work?

Write the support window into the SOW as a capped bucket, and show the drawdown on the invoice.

Developers will have questions after handoff, and answering them is part of good UX work. The problem is a "quick question" thread that runs for months. A bucket such as "up to 10 hours over 4 weeks, billed as used" gives the client a known maximum and gives you a point where the work ends. Log the questions as they come in. Invoice when the window closes, and show "7 of 10 hours used". When the window ends, offer a small retainer for ongoing support, or close the project.

The same logic applies to design-system maintenance and accessibility fixes found after launch. Each gets its own named bucket or its own SOW, never "a few more hours" added to the design phase. The scope creep guide covers how to raise it before you do the work.

What do enterprise clients need before they pay?

Large clients route invoices through procurement and accounts payable, so the paperwork matters as much as the work:

• Vendor onboarding: expect a supplier form, bank details and sometimes proof of insurance before the first invoice can be paid. Ask in week one.
• W-9 (US): businesses usually ask for one before paying a contractor. The IRS says that for tax years after 2025, Form 1099-NEC is filed for nonemployee compensation of $2,000 or more. Payments made by card or through a payment network go on Form 1099-K instead (IRS: Instructions for Forms 1099-MISC and 1099-NEC, accessed October 2026).
• PO number on every invoice, and invoices sent to the AP address rather than to your product contact.
• Budget timing: ask when their quarter or financial year closes. An invoice that arrives after the budget is locked can wait until the next period.

Sales tax on design services depends on the state. Check your state's guidance before adding tax. For the payment terms themselves, see invoice payment terms. The late fee glossary entry explains late fees if your contract includes one.

How should retainers and embedded roles be invoiced?

Bill the month in advance, on the first business day, for an agreed capacity, such as "8 days in May". Then add an unpriced summary of the previous month: what shipped, which meetings and workshops you ran, and days used against capacity. Say in the contract whether unused days roll over and what extra days cost, and bill extra days as a separate line on the next invoice. The retainer agreements guide covers rollover rules, and the retainer invoice template has a layout.

When is phase billing the wrong fit?

• Staff augmentation through an agency or talent platform. The agency invoices the client and pays you, often from your timesheets. Your invoice goes to the agency, on their terms.
• Open-ended QA or "help us when needed" work. Hourly billing with a monthly cap is fairer to both sides than guessing a fixed fee. See hourly vs fixed-price invoicing.
• Very small jobs. A one-day heuristic review needs one invoice with one line, not a phase plan.

Invoicing UX projects with InvoiceQuickly

Type or say "Invoice Northwind Retail phase 2 design, checkout prototype 12 screens, approved 3 March, $9,000, PO 4500123", and InvoiceQuickly drafts the client and line into an editable invoice that you review before saving. For the workflow above:

• Estimates (Pro): send the SOW price as an estimate. The client accepts it in their portal and you convert it to an invoice.
• Phase invoices: create one invoice per phase, as in the example. Milestone-based invoicing explains the approach, and the milestone invoice template shows a layout.
• PO numbers: there is no dedicated PO field. Put the PO number in the line description or the invoice notes.
• Pass-through costs: add them as ordinary lines at cost. Each invoice takes one tax rate, so if only some lines are taxable, invoice them separately.
• Payment (Pro): email the invoice with the PDF attached, add a payment link from your own Stripe or PayPal account, and turn on scheduled reminders. Record bank transfers yourself; payments are tracked on every plan.
• Time and bookkeeping (Pro): track support hours with the timer or manual entries, assign a project, and select unbilled entries to create a draft invoice. New PDFs copy your saved tax ID. Pro's CSV export moves invoice data into your bookkeeping.

The Free plan covers 5 invoices, 5 clients and 3 AI drafts. Pro is $9/month for unlimited invoices, estimates, email delivery and payment links. See pricing or start free. Templates: freelance invoice and web design invoice. More on invoicing for freelancers and on the InvoiceQuickly blog.

Frequently asked questions

Should UX designers charge hourly or by project?

By project or phase when the deliverables are clear: research, a prototype, a handoff. Hourly, with a cap, when the scope is open, such as design QA or support. Retainers suit embedded work where you attend team rituals and the output changes from week to week.

When should I send the first invoice on a UX project?

At signing, for at least the first phase or a deposit. Research and recruiting start costs immediately. After that, invoice when each phase is approved, so every invoice matches a decision the client already made.

How do I invoice user research participant incentives?

As a separate pass-through line at cost: "Participant incentives, 6 × $75", with receipts attached. Agree in the SOW whether you or the client pays participants, and state any handling fee there rather than adding it on the invoice.

How do I bill for support after design handoff?

Sell it as a capped bucket, for example up to 10 hours over 4 weeks at your hourly rate, billed as used. Log each request, invoice when the window closes, and show hours used against the cap.

What should I put on an invoice for an enterprise client?

The PO number, the SOW reference, the phase and its approval date, the cost centre if they gave you one, and their payment terms. Send it to the accounts payable address, and have a W-9 on file before the first invoice.