Clients who see “Design services, $6,500” on an invoice ask three questions: What specifically are you billing for? Is this the full amount or a milestone? What’s the deadline for this payment? A web design invoice template that answers those questions before they’re asked gets paid in 2 days. One that leaves them guessing gets paid in 2 weeks, after 3 follow-up emails.
The problem isn’t sending an invoice. Most freelancers do that. The problem is sending a generic invoice that doesn’t account for how web design projects are actually structured: multi-phase work, milestone payments, deliverable dependencies, and a final payment that unlocks access to files and credentials. A generic invoice template treats all of that as “services rendered.” A web-design-specific template names each piece, answers the questions before they’re asked, and removes every friction point between “invoice sent” and “payment received.”
What a professional web design invoice includes (that a generic invoice misses)
Generic invoice templates were designed for simple transactions, one line item, one amount, one date. Web design projects don’t work that way. Here are the specific line items that belong on a web design invoice, and why each one matters:
Discovery and strategy session, Covers the kickoff call, requirements gathering, and any content audit. This is billable work. Naming it separately signals that your process starts before pixels, which builds client confidence.
UX wireframing, Specify the screen count and revision rounds. “UX wireframes, 6 screens, 2 revision rounds” is clearer than “wireframing.” It matches what’s in your proposal and prevents the client from assuming 12 screens were included.
Visual design, Comps, style guide, responsive layouts. Name the pages. “Homepage + 4 interior pages” is unambiguous; “visual design” is not.
Development, CMS setup, page build, form and integration setup. Separate development from design. Clients often don’t realize these are different work efforts, and naming them separately helps justify both line items.
Content integration, If you’re placing client-provided content (copy, images, PDFs), invoice for it. It’s real time. “Content integration, placing client-provided copy and images across 5 pages” is reasonable and clients rarely push back when it’s named clearly.
Testing and QA, Cross-browser testing, mobile responsiveness. This is non-negotiable work that many freelancers bury in “development.” Naming it separately shows professionalism and fills in the question “what did I pay for?”
Launch, Deployment, DNS setup, go-live support. Going live takes real time, and something almost always needs fixing in the first hour. Invoice for it.
Revision buffer, Track agreed revision rounds as their own line item. When a client hits round 3 of a “2 revision” project, you have a clear reference point for the overage conversation. “Revision rounds 1–2 included in scope above. Additional revision rounds: $X/round.”
The web design invoice template (copy-paste ready)
INVOICE
Invoice #: 001 Date: May 2, 2026 Due Date: June 1, 2026 Bill To: [Client name] / [Company] / [Address]
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Discovery and scoping session | 1 | $750 | $750 |
| UX wireframes, 6 screens, 2 revision rounds | 1 | $1,200 | $1,200 |
| Visual design, homepage + 4 interior pages | 1 | $2,500 | $2,500 |
| WordPress development + CMS setup | 1 | $1,800 | $1,800 |
| Mobile responsiveness and cross-browser QA | 1 | $400 | $400 |
| Launch and DNS migration support | 1 | $350 | $350 |
| Subtotal | $7,000 | ||
| Less: 50% deposit paid April 1, 2026 | -$3,500 | ||
| Balance due | $3,500 |
Payment due: June 1, 2026 Payment method: Bank transfer / [Waco3 payment link] Late fee: 1.5%/month on balances past due date.
Notes: Final files delivered via Google Drive within 24 hours of final payment. WordPress CMS login credentials delivered on payment confirmation.
Two things make this template more effective than a generic one: the due date is written as an actual calendar date (not “Net 30,” which requires the client to do math), and the notes section states exactly what they receive when payment clears. That second point removes the most common reason invoices sit unpaid, the client wants to know what they’re paying for before they send the money.
Write the actual due date on every invoice, not “Net 30” or “Due on receipt.” “June 1, 2026” is unambiguous. “Net 30” requires the client to do math and gives them a reason to stall.
The milestone invoice structure for larger projects
For projects over $5,000, break invoicing into milestones. One large invoice at the end creates payment anxiety. Three smaller invoices tied to project events are easier to approve and create natural checkpoints.
Invoice 1, 50% on project start: $3,500 Deposit to secure your time and begin discovery. This is the invoice that goes out immediately when the contract is signed, not after the kickoff call, not after wireframes are done. On signing, same day.
Invoice 2, 25% on design approval: $1,750 Sent when the client approves the final visual design comps. This milestone is clear and binary, approval happened or it didn’t. Never move to development without this payment.
Invoice 3, 25% on launch: $1,750 Due on go-live day or client approval to launch. Not “within 30 days of completion.” On launch. The client has every incentive to pay quickly, you’re holding the DNS.
Why milestone invoicing works: every payment is tied to a concrete event that the client participated in. There’s no ambiguity about what they’re paying for. Each payment unlocks the next phase, which makes the structure feel fair rather than arbitrary.
For milestone invoices, include a one-line reference at the top: “This invoice covers Milestone 2 of 3, design approval phase, as defined in the project proposal dated April 1, 2026.” That one line eliminates 90% of milestone payment questions.
What to write in the invoice delivery email
Most freelancers send invoices with no message, or with “Please find the attached invoice.” Both approaches miss an opportunity to set expectations and remove friction.
Here’s the template:
Hi [Name],
Invoice #001 for the [Project Name] redesign is attached, the balance due is $3,500, due by June 1, 2026.
The final site files and WordPress login credentials will be delivered within 24 hours of receipt of payment.
If you need the invoice addressed to a different billing contact or in a different format, just let me know, happy to send it that way.
[Your name]
Three things this email does: it states the amount and due date in the body (so they don’t have to open the attachment to get the key information), it specifies what they receive when they pay (which removes the “what am I paying for?” question), and it removes a common friction point upfront (billing contact issues are the second most common reason invoices get delayed).
Keep the invoice email short. The invoice itself has the detail. The email’s job is to make sure the right person sees the right number on the right date.
State the amount and due date in the body of the invoice email, not just in the attachment. The person approving payment often skims emails before opening attachments.
Sending invoices through Waco3 vs. sending a PDF
A PDF invoice and a Waco3 invoice contain the same information, but behave differently once sent. A PDF has no tracking, you don’t know if it was opened, forwarded to accounting, or sitting unread. A Waco3 invoice shows you when it was opened and by whom, which tells you when to follow up and when to stay quiet.
For one-time clients, a well-structured PDF works fine. For any client you’ll work with more than once, invoice software pays for itself in the first two follow-up conversations you don’t have to initiate manually.
Related: if you’re building the proposal before this invoice, How to Write a Freelance Proposal That Gets Accepted covers the structure that makes the invoice feel like a natural conclusion rather than a surprise.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
