A Fourways brief with clear milestones from day one
The client was a small business in Fourways, Johannesburg, needing a new website and a practical way to manage payments with a freelance team spread across Gauteng and the coast. The brief was straightforward: keep the job moving, reduce payment risk, and make sure each stage had a clear approval point before any funds were released.
The project had a few firm constraints. The client wanted a simple public-facing site, mobile-friendly pages, and a launch date that would not slip too far because marketing material had already been printed. There was also a need to keep everyone aligned on scope, since the site included copy updates, image selection, form setup and a small content management handover. In short, no one wanted grey areas once work started.
- Client type: small business in Fourways
- Project type: website build with staged sign-off
- Payment method: escrow held until each milestone was confirmed
- Main concern: protect both buyer and supplier during delivery
How the escrow structure was set up for the build
We structured the work around three release points: planning, build completion, and final handover. Funds were held in escrow while the agreed tasks were completed, then released only after the buyer confirmed delivery at each stage. That gave the freelancer confidence that payment was secured, and gave the client assurance that money was not released early.
The payment flow was kept plain and practical. The parties agreed what counted as completion for each milestone, what documents or screenshots would count as proof, and how long the inspection window would run. This mattered because web projects often involve small changes near the end, and if those changes are not written down, they can drag on. A clear process saved time and cut down on back-and-forth.
- Stage 1: planning and content outline
- Stage 2: homepage and core page build
- Stage 3: revision, handover and release
- Inspection period: agreed before release at each step
What we supplied and why it worked for escrow deals
Our part was to guide the escrow process and keep the release conditions tight enough to be fair, but not so rigid that the work became awkward. We helped the client set out what would be checked on delivery, including page layout, contact form testing, navigation, file access and basic mobile display. The seller side also had clear instructions on what to submit for review, so there was less confusion when the project moved from one stage to the next.
The result was a cleaner handover. The buyer had a point of contact for questions about delivery and the seller had a route for release queries if anything needed confirmation. There was also space for evidence submission where needed, such as screenshots, links or signed approval notes. That is often the difference between a project that ends neatly and one that stalls over small issues. We kept the process practical, with no fuss.
- Delivery check support for each milestone
- Item condition review for completed digital work
- Release query support when approvals were pending
- Evidence submission help for fixes and sign-off
Timeline and project flow over four weeks
That timing suited the client because they needed enough room for review without letting the project drift. It also worked for the freelancer, who could plan around the release points and avoid doing a lot of extra work before the earlier stage was accepted. This is where escrow helps on web projects, especially when the job includes several moving parts and a few people need to approve the same deliverable.
- Week 1: scope agreement and escrow setup
- Week 2: first build delivered for review
- Week 3: revisions and testing
- Week 4: final sign-off and release
Results that made the handover easier
The buyer got a working website with a clean release trail and a clearer view of what had been paid for at each step. The seller got confidence that funds were being held properly and would be released once the agreed work was delivered. It was not flashy work, just a sensible process that kept the project moving without arguing over who owed what.
For a Fourways client dealing with a web project, that matters. Web work can fail at the edges, especially when the brief changes midstream or someone is waiting on content from a third party. With staged release, the parties had enough structure to settle issues before they became bigger problems. It also gave the client a process to follow if there was a delay, missing asset or scope difference. That kept the mood calmer all round.
- Clear approvals before payment release
- Reduced delay around late-stage changes
- Better record of what was delivered
- Cleaner communication between buyer and seller
Kept for the next deal
We would use the same model again for a similar Fourways project, especially where the work is split into stages and the buyer wants visible progress before full release. The key is to keep the milestone list short, define the inspection period at the start, and write down exactly what counts as completion. That keeps everyone honest and avoids wasteful disputes over minor details.
If we repeated the setup, we would also keep the delivery evidence simple and consistent, with one place for sign-off notes, screenshots and revision requests. That makes it easier to resolve wrong item support, missing accessories help, incomplete work review or scope difference help if any issue comes up. Before using any escrow provider, buyers and sellers should check that the provider is properly registered and that the terms are clear enough for both sides.
- Use short milestones with defined sign-off points
- Keep evidence and approvals in one place
- Agree the inspection period before work starts
- Check the provider is properly registered
Deal summary
| Project location | Fourways, Johannesburg |
|---|---|
| Project type | Website build with staged escrow release |
| Timeline | 4 weeks |
| Payment structure | Funds held until delivery confirmed |
| Main constraint | Tight launch timing and changing content inputs |
| Release method | Milestone sign-off before each payment release |





