Invoice template for web developers
Developer invoices should mirror how the project was actually scoped — milestone-based for fixed-bid builds, hourly for maintenance and support, or a mix of both. For a fixed-bid site build, list each milestone as its own line (discovery & design, front-end build, backend/API integration, QA & launch) so a partial-progress invoice is self-explanatory. For ongoing maintenance or support retainers, list the billing period and hours included, plus overage hours at your standard rate as a separate line. Always call out third-party costs you're passing through — hosting, domain renewal, premium plugins/licenses, API/SaaS fees — as their own line items rather than folding them into your dev rate, since clients often want to see (and later manage) those costs separately. If you require a deposit before starting, note it as a credit/deduction line on the final invoice so the total reconciles cleanly against what's still owed.
Suggested line items
| Description | Qty | Rate |
|---|---|---|
| Discovery & technical scoping | 1 | $400.00 |
| Front-end build (React/Vue components) | 24 | $85.00 |
| Backend API integration | 12 | $95.00 |
| QA, cross-browser testing & launch | 1 | $350.00 |
| Hosting & domain setup (pass-through) | 1 | $60.00 |
Opens the invoice generator pre-filled with these line items — nothing is saved until you download or share.
INVOICE
Your Business
INV-2026-041
From
Your Business
you@example.com
Bill to
Client Name
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Discovery & technical scoping | 1 | $400.00 | $400.00 |
| Front-end build (React/Vue components) | 24 | $85.00 | $2,040.00 |
| Backend API integration | 12 | $95.00 | $1,140.00 |
| QA, cross-browser testing & launch | 1 | $350.00 | $350.00 |
| Hosting & domain setup (pass-through) | 1 | $60.00 | $60.00 |
Frequently asked questions
How should I invoice a fixed-bid web project?
Break the fixed bid into milestones — discovery, front-end, backend/integration, QA & launch — and invoice against each milestone as it's completed rather than one lump sum at the end. It gives the client visibility into progress and keeps your cash flow moving through a multi-week build.
How do I invoice for ongoing site maintenance?
List the billing period and the hours or scope included in the retainer (e.g. 'April 2026 maintenance — up to 5 hours'), then add any overage hours as a separate line at your hourly rate. That keeps recurring invoices consistent and easy to audit month to month.
Should hosting and third-party fees be on my invoice?
If you're passing through hosting, domain, plugin licenses, or SaaS/API costs on the client's behalf, list them as their own line items rather than bundling them into your development rate — clients generally want to see (and later take over) those recurring costs separately from your labor.