Industry example
Website design invoice
Web projects sprawl if the invoice doesn't mirror the scope. Break fees into phases clients recognise: discovery, design, build, launch. They pay faster when each line maps to something they saw in the proposal.
Or jump straight to the Invoice Generator.
Line items clients expect
Discovery and sitemap work is billable, not "free planning." Wireframes and homepage design usually sit as separate lines so change requests don't eat the build budget silently.
Build and responsive layout is often the largest line. CMS setup, copy population, and launch QA deserve their own rows if they were in the SOW.
Deposits and milestones
50% before design starts, 25% at design approval, 25% at launch is a common split. Invoice each milestone when it hits, not when the whole site goes live six weeks later.
What to put in the notes
Hosting is client-owned unless you resell it. Revision rounds capped per phase. Third-party plugin licenses billed at cost if that was agreed.
Fieldline Web
Invoice INV-3310
| Item | Qty | Rate | Amount |
|---|---|---|---|
| Discovery & sitemap | 1 | $340 | $340 |
| Homepage + inner page designs | 1 | $2,800 | $2,800 |
| Build & responsive layout | 1 | $3,600 | $3,600 |
| Testing & launch | 1 | $425 | $425 |
| Total | $7,165 | ||
Common questions
- Should hosting be on the invoice?
- Only if you bill it. Many designers invoice the build and let the client pay hosting directly to the provider.
- How do I bill hourly overruns?
- Add lines for additional hours at your stated rate, or reference the change-order doc number in the notes.
- Retainer vs project invoice?
- Retainer: same amount monthly for maintenance. Project: one invoice series tied to milestones. Don't mix them on one doc without labelling clearly.