Insights · guide
How to set payment milestones for an XR project
Drafted with Insight · edited by The WE ARE VR team
design

Payment milestones should follow finished work, not the calendar.
I wrote this because XR projects often mix creative approval, software testing and event deadlines. A vague “50% next month” clause tells nobody what must be ready before money moves.
What's the problem?
XR work changes shape as soon as people try the first prototype. A client may discover that text is unreadable in a headset. A venue may have weak Wi-Fi. An AR effect may track poorly under the lighting at a Sandton launch.
If payments depend only on dates, both sides carry avoidable risk. The maker may complete substantial work without being paid. The commissioner may release money without seeing a usable result.
Calendar dates still belong in the schedule. They simply should not define completion on their own.
Another common mistake is naming a milestone without defining acceptance. “Prototype complete” sounds clear until one person expects polished art and another expects grey boxes (a classic meeting with no winner).
What's the solution?
Tie each payment to a specific deliverable that can be reviewed and approved. Write down what is included, who approves it, and how many working days they have to respond.
A simple four-part structure works for many small Johannesburg XR projects:
- Deposit and discovery: payment confirms the booking and starts research. The supplier delivers a confirmed brief, device list, technical approach, schedule and known venue constraints.
- Prototype: payment follows a working test of the main interaction. It may use rough visuals, but it must run on the agreed headset or phone.
- Approved build: payment follows the complete experience with final content, agreed fixes and testing on target devices.
- Final delivery: payment follows handover of files, build instructions, credentials, documentation and any agreed event support report.
For example, consider a WebAR exhibition commissioned for a Braamfontein venue. The contract might use 25% at booking and discovery, 25% after the tracked prototype works on the agreed Android and iPhone models, 35% after the full build is approved, and 15% after handover.
Those percentages are a starting point, not a rule. A project with costly 3D production may need a larger early payment. Hardware purchases should usually be paid before ordering, because the supplier should not finance ten headsets for a client.
Add one sentence for changes: work outside the approved brief needs a written change quote. Also state that delayed client feedback moves later dates. Otherwise, the supplier absorbs a delay they did not cause.
Keep approval evidence simple. An email saying “prototype approved” is enough if the contract names email as the approval channel.
What's next?
- Replace every date-only payment in your current quote with a named deliverable.
- Add one acceptance sentence to each milestone, including device and reviewer.
- Check that the final payment covers handover, support and outstanding project files.
Share your milestone structure with the Jozi XR community, or ask us where a difficult project should split.
The WE ARE VR team
