Invoicing Solutions by Industry
Invoicing for web developers
Developers mix models inside one engagement: a deposit to start, milestones through the build, a retainer for maintenance, and pass-through hosting. Tying every payment to a deliverable keeps cash flowing and stops a stalled client from leaving finished work unpaid.
Tie every payment to a deliverable, not a date
Structure milestone invoices around checkpoints the client can see: deposit on signing, payment on design approval, payment on staging launch, balance on go-live. Common splits are 30/40/30 or 30/30/30/10. This protects cash flow on long builds and means a client who changes direction or runs out of budget cannot leave you unpaid for completed work. Reference the milestone explicitly on each invoice.
Collect the deposit before you write a line of code
Require 30% to 50% upfront for any project over a couple of thousand dollars, and consider full payment for very small jobs. A paid deposit filters out tire-kickers, secures your calendar, and keeps clients responsive. Treat the deposit as non-refundable for work begun and state your kill fee, the percentage owed if they cancel, in the contract.
Gate final handoff on payment and isolate pass-throughs
Invoice at the moment of delivery, before post-launch feedback opens a revision window, and transfer repository access, production credentials, and admin handoff only once the balance clears. List domains, hosting, and premium plugins or themes as their own line items at cost so clients never confuse your fee with third-party charges. Define revision limits in the contract to keep "one more tweak" from becoming free work.
Milestone billing patterns
| Split | When each payment lands | Good for |
|---|---|---|
| 50 / 50 | Deposit, then on completion | Small, well-scoped sites |
| 30 / 40 / 30 | Start, build, launch | Standard project builds |
| 30 / 30 / 30 / 10 | Start, design approval, dev, launch | Larger or longer projects |
| Retainer | Monthly, in advance | Ongoing maintenance and support |
Web developer invoicing FAQ
Should I ask for a deposit before starting?+
Yes. The standard is 30% to 50% upfront, and full payment for very small jobs. A deposit confirms commitment and protects your time. For larger builds, follow it with milestone payments rather than billing everything at the end.
What payment terms should a freelance developer use?+
Net 14 or Net 15 is a practical default for digital work, Net 30 for larger clients, and due on receipt for small fixes and deposits. Use explicit due dates and an online payment link to get paid faster.
How do I handle requests beyond the agreed scope?+
Define scope, revision count, and an out-of-scope process in the contract, then handle extras with a written change order that quotes the added cost before you do the work.