What payment structure is normal for a New Zealand web project, and which arrangements should make you pause.
Payment terms tell you a lot about how a studio operates. Here is what is standard in New Zealand, and where the edges are.
The common structures
| Structure | How it works | Suits |
|---|---|---|
| 50 / 50 | Half on start, half on launch | Small projects under about six weeks |
| Thirds | Deposit, midpoint, launch | Medium projects where a midpoint milestone is meaningful |
| Milestone based | Payments tied to specific deliverables | Larger projects, apps, anything past two months |
A deposit is entirely normal and protects both sides. It confirms the booking and covers the studio's early work before anything visible exists.
What is reasonable
- A deposit between 30 and 50 percent for a fixed price project
- Final payment due on launch or shortly after, not months later
- Clear definition of what triggers each milestone
- A written variation process so changes do not become arguments
What should give you pause
- Full payment up front on a project of any size
- No written scope attached to the payment schedule
- Final payment tied to something outside your control
- Any suggestion that you do not get the code or files until some future condition is met
Late content and its effect on schedule
Most delays on web projects are content delays, not development delays. A fair contract acknowledges this in both directions: the studio commits to a timeline that assumes content arrives when agreed, and you accept that late content moves the launch date. Getting this in writing early prevents an awkward conversation later.