Web development invoices usually mix more than one pricing model on the same document. There's often a chunk of hourly frontend work, a fixed fee for a defined deliverable like a responsive redesign, and — for clients who stick around after launch — a recurring hosting and maintenance retainer billed every month. Lumping all of that into one "development services" line makes it hard for a client to see what they're actually paying for, and makes it harder for you to spot when a retainer client's support requests have quietly grown beyond what the retainer covers. Separating hourly work, fixed-fee milestones, recurring hosting, and one-off bug fixes into their own line items keeps that visible on every invoice, not just in your own records. The template below starts with a common mix: billable frontend hours, a fixed-fee responsive build, a monthly hosting retainer, and a small block of support hours. Swap in your own project details and rates, add your client's information, and pick whichever look fits how you present your work — then download a PDF that's ready to send to the client or their accounts team, no separate invoicing software required.
Your Business Name
No. INV-001
Issued —
Due —
Bill To
Client Name
| Description | Qty | Rate | Amount |
|---|
Should I bill web development hourly or as a fixed project fee?
Hourly suits open-ended or research-heavy work where the scope can shift; a fixed fee suits well-defined deliverables like a responsive redesign with an agreed feature list. Many developers use both on the same invoice — hourly for exploratory work, fixed fee for the defined build.
How do I invoice for an ongoing hosting or maintenance retainer?
Bill it as its own recurring line item, separate from project work, ideally on a fixed monthly schedule the client can plan around. Keeping it distinct from one-off development charges makes it obvious at a glance which parts of the invoice repeat and which don't.
What if a client needs a bug fix outside the original scope?
Track it as billable support hours on the next invoice rather than absorbing it into the original project fee. If you offer a block of included support hours, note how many have been used so the client can see when they're approaching the limit.