Web projects pay best when they're billed by milestone — and the invoice should make the milestone unmistakable. This one arrives mid-project: milestone two of three, QA, and launch deployment.
Hosting setup and launch deployment1$350.00$350.00
Subtotal$4,750.00
Total due$4,750.00
Notes
Staging is live for your review — content freeze starts Monday.
Terms
Net 14 by card. Final milestone invoiced at launch.
Pay $4,750.00
Secure card payment by Stripe
Free to download — no signup.
The anatomy
What belongs on the invoice
On the document
Which milestone this is — "Milestone 2 of 3" beats a bare description
What the milestone contains: build, migration, QA, deployment
A staging or deliverable link in the notes, so approval is one click away
Hourly support or post-launch work separated from fixed-fee build lines
What triggers the final invoice — usually launch or handover
Hosting, licenses, and other pass-through costs as their own lines
Common line items
Milestone 2 of 3 — CMS build and content migration
Responsive QA — phones, tablets, desktop
Hosting setup and launch deployment
Post-launch support — 5 hours
Performance pass — Core Web Vitals
Plugin and license costs, at cost
Rates are yours to set — the generator does the math.
01
Bill by milestone, not at launch
A deposit, one or two mid-project milestones, and a final payment at launch keeps cash arriving while the work is fresh. One big invoice at the end finances the whole project yourself.
02
Separate the build from the upkeep
Maintenance, hosting management, and support belong on their own recurring invoice, not buried in the build. Clients understand a build that ends and a service that continues.
03
Don't let client content stall your invoice
Bill the milestone when your work is delivered, even if their content isn't. Terms like "Milestone billed on delivery of development work" keep someone else's delay off your cash flow.
General invoicing guidance, reviewed July 16, 2026 — not tax or legal advice. Rules vary by location and trade; confirm current requirements with the relevant authority or a qualified adviser.
FAQ
Questions, answered
How should I structure payments for a website project?
A common shape: 30 to 50% deposit, a milestone payment mid-build, and the balance at launch. Each invoice names its milestone so the paper trail matches the project plan.
How do I bill ongoing maintenance?
As a separate flat monthly invoice — care plans are easier to understand than surprise hourly bills. During beta, duplicate the previous invoice and send it manually on the same date each month; automatic scheduling is not active yet.
What if the client delays launch?
Invoice on your delivery, not their go-live. If the site is built and waiting on their content, the milestone is done. Your terms can say exactly that, and this template's example does.
Fixed price or hourly for development?
Fixed for well-scoped builds, hourly for ongoing or ambiguous work — and both on one invoice is normal: fixed milestone lines plus an hourly support line, like the example here.