The short version
Web projects end late for the same reason they get invoiced badly: nobody wrote down where they stop. Pages, rounds and exclusions on the invoice are what turn an open-ended build into a finished one you can bill for.
What goes on a web designer invoice
Six things, in the order they belong on the page. The invoice generator opens a web designer / developer document with the lines already in place, so most of this is checking rather than typing.
- Bill discovery as its own stage. Wireframes and structure are work that happens before any design does. Priced separately, they also give you a paid exit if the project stalls.
- Show the page count. Five pages at a rate reads as five pages. A single build figure invites the sixth page to arrive for free.
- Name the revision rounds. Per stage, not per project, and priced beyond the included number.
- Say what is excluded. Content writing, photography, third-party licenses and migration. What is not on the invoice is what the client assumes is included.
- Separate build from ongoing support. Hosting, maintenance and support are a recurring product, not a line inside a one-off build.
- Stage the payments. A deposit, a payment at design sign-off, a balance at launch. A build billed once at the end is billed after you have lost your leverage.
The lines a web designer invoice usually carries
These are the lines the generator opens with when you pick Web designer / developer. The figures are a starting point to type over rather than a going rate: this site runs no pricing survey, and the number on your invoice should be the one you charge.
| Line | What it covers | Qty | Opens at |
|---|---|---|---|
| Discovery and wireframes | Agree what the site has to do and lay out each page in outline before any visual design starts. | 1 | $700 |
| Page design (per page) | Design each page to the agreed direction, in the states it needs, ready to build. | 5 | $320 |
| Development and build | Build the pages so they work on a phone as well as a desktop, and connect any forms. | 1 | $2,400 |
| CMS setup and training | Set the site up so you can edit it yourself, with a walkthrough of how to make changes. | 1 | $450 |
Add, rename, reorder or delete any line, and set tax per line where it applies. Priced as they open, that comes to $5,150 before tax.
A worked web designer invoice, filled in
This is the same job as the table above, written out the way it would leave your phone. Every figure on it is a starting point rather than a going rate, and the tax line is shown at ten per cent purely so the arithmetic is visible: set your own rate, or none, per line.
INVOICE
Bill to
Your client name
Client address
Work carried out at
Job address
Job or order reference
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Discovery and wireframes | 1 | $700 | $700 |
| Page design (per page) | 5 | $320 | $1,600 |
| Development and build | 1 | $2,400 | $2,400 |
| CMS setup and training | 1 | $450 | $450 |
| Subtotal | $5,150 |
| Tax at 10% | $515 |
| Total due | $5,665 |
Late payment. State your own rate and when it starts, so it is agreed before the due date rather than argued after it.
Subtotal $5,150, tax $515, total $5,665. The parts worth copying are the structure rather than the numbers: the job reference next to the client, every line separately priced with its count showing, the tax on its own line, and terms that name a number of days instead of saying on receipt.
Pages, rounds and exclusions: the three lines that end a project
Almost every web project that runs long runs long for one of three reasons: more pages appeared, more rounds happened, or something everyone assumed was included was not.
All three are solved on the invoice. Show the page count with a per-page rate so a sixth page is arithmetic rather than a negotiation. Name the rounds per stage. And list the exclusions explicitly, because a client reading an invoice with no mention of content writing will reasonably assume you are writing the content.
None of this is about being difficult. It is about the project having an edge, which is the only way it can be finished and paid for.
Sign-off on staging, and the build that never closes
A build without a formal sign-off does not end. It fades, with small requests arriving for months while the final invoice sits unpaid.
Tie a payment to sign-off on staging. Send the link, get approval recorded, invoice the milestone. The approval is what converts "nearly done" into a stage that has completed and can be billed.
Anything after that is either a defect, which you fix, or a change, which is a new line. Having a signed reference point is what lets you tell the two apart without it being a matter of opinion.
Hosting, support and who owns the code
Two questions arrive after launch, usually together: who keeps the site running, and what happens if the client leaves.
Bill hosting and maintenance as a recurring invoice with what it covers named: uptime, updates, backups, a number of support hours. Rolled into the build fee it becomes an obligation with no revenue attached to it.
On ownership, decide and write it down. Whether the client receives the code, whether third-party licenses transfer, and whether your support access ends. Silence here means the answer gets decided during a dispute rather than before one.
Hourly, fixed price or per unit: how web designers price the work
Web work is priced per project with stages, because the client is buying a working site and the risk sits in the middle of the build rather than at either end. Hourly billing survives for maintenance and for genuinely unknown work.
| Model | Where it wins | What it quietly costs you |
|---|---|---|
| Project fee, staged | New sites, rebuilds, anything with a defined scope | Scope creep arrives as small requests, so the change process has to exist first |
| Day rate | Agency overflow, integrations, development inside someone else project | You carry no upside from the outcome, only the hours |
| Monthly care plan | Hosting, updates, backups, small changes and support | Small changes is unlimited unless it says how many hours a month it covers |
Stage the payments against things the client can see: discovery approved, design approved, build complete, launch. It is the only structure where a project that stalls at the client end has already paid for the work that was done before it stalled.
Working out what to charge
This guide is about what goes on the document, not what the number should be, and nobody should hand you a rate for your own market. What the site can do is the arithmetic: the freelance rate calculator works back from what you need to earn, the service price calculator prices a service against your costs, and the profit margin calculator checks what is left once the job is done.
Writing it on your phone, in five steps
Most web designers write the invoice standing next to the work rather than at a desk a week later, and the week later version is the one that gets details wrong. The generator is built for the first case.
- Open it with your trade already chosen. The web designer / developer invoice loads with discovery and wireframes and the rest of the lines already on the page.
- Put the client and the job reference in first. It is the part you will not remember accurately in three days, and on agent, landlord or contractor work it is the reason the invoice gets paid at all.
- Edit the lines rather than starting from empty. Change the quantities and the rates, delete what you did not do, add what you did. Keeping the descriptions means the wording stays consistent from one job to the next.
- Set the terms to 14 days and add a payment link. A due date that is an actual date gets chased. A link and a QR code means it can be settled before you have packed up.
- Send it before you leave. The clock on your terms starts when the invoice arrives, not when the work finished, so every day it sits unsent is a day added to getting paid.
Getting paid once it is sent
Put a due date and your terms on the document, because an invoice without them is hard to chase. Add a payment link and a QR so settling up is a tap rather than a transfer somebody has to set up. When part of it lands, the receipt maker records it as a part payment and prints the balance still due. If the due date passes, the late fee calculator works out what your own terms allow and writes the chasing letter to go with it.
Five dates decide whether a web designer gets paid on time, and four of them are set before the work starts.
Mistakes that cost web designers money
- No page count on the invoice. The sixth page arrives assuming it was always included.
- Exclusions unlisted. Anything not mentioned is assumed to be in scope, especially content.
- Support folded into the build fee. An ongoing obligation with no ongoing revenue.
- No sign-off milestone. The project fades instead of finishing, with the final invoice unpaid.
- Silence on code ownership. It gets decided during a dispute rather than before one.
Web designer / developer invoice questions
How do I invoice for web design?
Bill discovery as its own stage, show the page count with a per-page rate, name the revision rounds, list what is excluded, keep ongoing support separate and stage the payments. The generator opens a web design invoice with discovery, page design, build and CMS setup already listed.
Should I charge a deposit for a website build?
Most do, and staging the payments across deposit, design sign-off and launch is the more useful structure. Each stage is tied to something the client has received, which is what makes it easy to approve.
How do I handle extra pages?
Put a per-page rate on the invoice from the start. Then an additional page is arithmetic the client can see rather than a negotiation about whether it was always included.
What should I exclude on a web design invoice?
Anything you are not doing: content writing, photography, third-party licenses, data migration, ongoing hosting. What is not mentioned is what the client assumes is covered.
How do I bill hosting and maintenance?
As a recurring invoice separate from the build, naming what it covers such as updates, backups and a number of support hours. Inside the build fee it is an obligation with no revenue behind it.
Who owns the website code after final payment?
Whatever the agreement says, which is why it belongs on the document. State whether the code transfers, whether third-party licenses move with it, and what happens to your access.
When should I send the final invoice?
At launch or at sign-off on staging, tied to an approval you have recorded. A build with no sign-off point tends not to end, and the final invoice waits with it.
Free web designer invoice template
The free web designer invoice template opens with the lines above already priced, in any of 200 designs, and exports a print-ready PDF with no signup and nothing saved to a server. If you would rather edit a file offline, there are 72 Word templates, 72 Excel templates with the totals already calculating, and 72 fillable PDFs.
Invoicing guides for related trades
The same billing questions come up next door. These four guides cover the trades closest to web designers, and each one sits alongside its own free template.
Every trade has one: see all 46 invoicing guides, or go straight to the 46 free invoice templates they describe.
Everything on this site, set up for web designers
The whole toolkit, with the reason each one matters to web designers rather than in general. The five marked links open with web designer / developer already selected.
Make the document
Five of these arrive with web designer / developer already selected, so the first line reads discovery and wireframes rather than nothing.
- Invoice Generatoropens set to this trade. The web designer invoice this guide describes, priced and ready to edit.
- Quote Generatoropens set to this trade. Quote first: always, with stages, rounds and exclusions. Converts to the invoice without retyping.
- Receipt MakerRecords a deposit or a stage payment and shows the balance still due.
- Recurring InvoicesFor web designers billing the same client on the same day every month.
- Purchase OrderBill against a client purchase order, or raise one for a supplier of your own.
- Work OrderBrief a second freelancer with the scope and the deadline in writing.
- Cost Estimatoropens set to this trade. Build the job up from materials, labor and margin before you quote it.
Templates and files to send on
The same web designer lines, in whatever file the client accounts team wants.
- Web designer / developer invoice templateThe template this guide is written about, with the web designer lines already on it.
- 200 invoice designsopens set to this trade. Put those lines in any of 200 designs and keep the one you like.
- 72 Word templatesEdit offline, or send a file a client can fill in themselves.
- 72 Excel templatesThe totals calculate themselves, which matters on a long line list.
- 72 fillable PDFsType into the fields and print, with nothing to install.
- Google Docs templatesCopy to your own Drive and edit from a phone.
- Google Sheets templatesSame totals, shared with whoever does your books.
- Blank invoice templatesA plain document for the commission that does not fit a standard shape.
- Quote templatesA priced quote on paper, for a client who wants the figure before the work.
- Estimate templatesA ballpark that is explicitly not a fixed price, before the brief is settled.
- Receipt templatesProof of payment for a client who needs it for their own records.
- Work order templatesThe scope, the site and the authorisation, before anybody drives out.
Work out the number first
This guide is about the document. These are for deciding what goes on it.
- Freelance Rate CalculatorWork back from what you need to earn a year to the rate a web designer has to charge.
- Service Price CalculatorPrice a service against your own costs rather than against what somebody else charges.
- Profit Margin CalculatorCheck what is actually left on a web designer job once materials and time are paid for.
- Break-Even CalculatorWork out how many projects a month cover your costs before anything is profit.
- Discount CalculatorSee what a discount actually costs you before you offer it.
- Sales Tax CalculatorAdd or strip tax on a figure before it goes on the invoice.
Get it paid without the awkward email
Terms of 14 days is the shape this guide assumes. Deposit: deposit on signing, then stage payments.
- Payment links and QR codesA link and a scannable code on the invoice, so paying is a tap.
- Late fee calculatoropens set to this trade. Works out what your own terms allow and writes the chasing letter.
- Payment terms guideWhich terms actually get invoices paid, and the exact wording to use.
- Deposit invoicesWhen to ask, how much, and how the final invoice shows the balance.
- Chasing an unpaid invoiceThe reminder, the call, the overdue notice, then what comes after.
- Progress billingBilling a long job in stages so you are not funding it yourself.
- Invoice numberingA numbering system that never repeats and never skips.
- Change ordersPricing extra work in a way the customer has already agreed to.
Read next
- All 46 invoicing guidesThe same guide, written for every other trade on the site.
- 46 trade invoice templatesEvery trade, each opening with its own lines already priced.
- Invoicing glossaryPlain definitions of the words on an invoice, a quote and a job.
- The blogLonger pieces on quoting, billing, tax and getting paid.
- All 24 toolsEverything on the site in one list, including the ones not named here.