Milestones, hourly rates and sprints
How a developer invoices usually mirrors how the project is scoped. For fixed-scope builds, milestone billing is the norm: split the total across stages such as discovery and setup, front-end build, back-end and integrations, then testing and launch, invoicing each as it is signed off. This protects both sides, because the client pays for demonstrable progress and you are never weeks deep in unpaid work. For maintenance, unclear scope or evolving requirements, hourly or day-rate billing with a logged breakdown of tickets and hours is cleaner and easier to justify. Teams working in sprints can bill per two-week sprint at a fixed capacity. The template supports all three, so a single invoice can carry a fixed milestone line for the core build alongside hourly lines for out-of-scope change requests.
Deposits, retainers and change requests
Most freelance developers take a deposit, often 30 to 50 percent, before writing code, with remaining milestones billed on completion. Once a site is live, recurring revenue usually comes from a monthly retainer covering a set number of support or development hours, security updates, backups and small changes, with anything above the included allowance billed at an overage rate. Change requests are the line item that keeps a project profitable: when a client asks for something outside the agreed spec, log it as a separate billable item rather than absorbing it. Spelling out on the invoice that work beyond the signed scope is billed hourly makes those conversations straightforward. For retainers, showing hours used against hours included each month keeps the relationship transparent and makes renewals easy.
Third-party costs, hosting and payment terms
A web invoice is rarely just labor. Hosting, domains, SSL certificates, premium plugins, API subscriptions and paid themes are recurring or one-off costs that should be listed as pass-through lines, either billed at cost or bundled into a managed-hosting fee so the client knows what they are paying for. Keeping these separate from development hours also makes annual renewals predictable. Payment terms matter for cash flow: net 14 or net 30 is typical, with a late fee or interest clause on overdue invoices, and it is worth noting that final code or deployment to the client's production environment happens once the invoice is settled. Because the template is free, customizable and exports to PDF or Word without any sign-up, you can keep separate presets for project milestones, monthly retainers and ad-hoc hourly support.