INVOICE
- Invoice number
- INV-0001
- Invoice date
- Sep 1, 2026
- Due date
- Oct 1, 2026
Bill to
| Description | Qty | Price | Tax | Amount |
|---|---|---|---|---|
| — | 1 | $0.00 | — | $0.00 |
- Subtotal
- $0.00
- Total
- $0.00
Milestones, sprints, hosting and maintenance — billed on one document your client's finance team can process.
| Description | Qty | Price | Tax | Amount |
|---|---|---|---|---|
| — | 1 | $0.00 | — | $0.00 |
Development work is usually billed one of three ways: hourly against a tracked log, per sprint at a fixed rate, or against milestones tied to deliverables. Milestone billing is the friendliest to clients because it maps spend to visible progress, and the friendliest to you because it front-loads cash.
Whichever you use, the invoice line should reference something the client can verify — a sprint number, a milestone name from the statement of work, or a date range from your time log.
The one-off build is the visible revenue; the recurring lines are the ones that quietly go unbilled for months.
Bill change requests as their own lines, referencing the request, rather than absorbing them into the milestone. It costs nothing to be explicit, and it produces a paper trail showing exactly why the project cost more than the original quote.