Web development invoice template
You shipped the feature, squashed the bugs, and wrote exactly zero invoices you enjoyed. This template pre-fills the lines freelance developers bill most — hours, testing, deploy, support — so you can get back to the code.
What's pre-filled
| Line item | Qty | Rate |
|---|---|---|
| Development — [feature / project phase] (hours) | 20 | your rate |
| Responsive design & cross-browser testing | 1 | your rate |
| Deployment & launch support | 1 | your rate |
| Post-launch bug-fix window (30 days) | 1 | your rate |
| Notes: Source code delivered via private Git repository on payment. | ||
| Terms: Payment due within 14 days of invoice date. Work on subsequent milestones begins once payment clears. |
Rates are left blank on purpose — they're yours. Edit every line once it's open.
What to put on a web development invoice
- Hours against a named deliverable — “Development: checkout flow (20h)” survives a client's finance review; “dev work” doesn't.
- Testing as a visible line — cross-browser and responsive testing is real work; on the invoice it stops being assumed-free.
- Deployment and launch support — the go-live weekend has a price.
- A bounded bug-fix window — “30 days post-launch” converts “forever free support” into a defined deliverable.
- Where the code lives — note the repo handover in the invoice notes; it marks the moment delivery happened.
Invoicing tips for web developers
Bill by milestone, not at the end. Deposit → milestone → launch keeps your exposure to any one unpaid invoice small, and “next milestone starts when this invoice clears” — written in the terms — is the polite version of leverage that actually works.
Define the support window on the invoice. Every developer has a client who treats launch day as the start of a lifetime warranty. “Post-launch bug-fix window (30 days)” as a line item creates the expiry date in the client's own records.
Name the deliverable next to the hours. Finance departments approve “Checkout flow — 20 hours” without questions; they email you about “development services.” The five extra words are worth days of payment delay.
Frequently asked
Should freelance developers invoice hourly or fixed-price?
Both work — the invoice discipline is the same: tie the amount to a named deliverable or milestone. Hourly suits open-ended work; fixed-price suits well-specified projects with a deposit and milestone schedule.
How do developers handle clients who keep reporting bugs for free?
Put a bounded bug-fix window (e.g. 30 days post-launch) on the invoice as a line item. Inside the window it's covered; after it, fixes are new billable work by the client's own paperwork.
What payment terms are normal for freelance dev work?
Net 14 is common for freelancers (Net 30 favors large companies, not you). Add that the next milestone starts when payment clears — it makes late payment self-penalizing.
More free invoice templates
- PhotographySessions, editing, galleries & travel
- Graphic designLogos, branding, revisions & file handover
- Writing & copywritingArticles, per-word rates, briefs & kill fees
- ConsultingHourly strategy, workshops & reports
- TutoringSessions, materials & monthly billing
- VideographyDay rates, editing, licensing & delivery
- Cleaning servicesStandard cleans, deep-clean add-ons & supplies
← Billotter: the free, private, in-browser invoice generator