That holds whether you're a business replacing a tired website or an agency with more work than people. The country and the hourly rate get most of the attention. The brief, the ownership and the exit decide whether it works.
Outsourced projects go wrong around the code, not in it
Most developers, offshore or local, can build what's in the brief. The trouble starts in the gaps around it:
- The brief says "a modern, mobile-friendly website", so every quote prices a different job.
- Nobody on your side has the time or the background to answer questions, approve designs and test what's delivered.
- The hosting, code repository and domain sit in the developer's accounts, so you can't leave without their help.
- The contract covers launch day, but not what happens after it, or if the work ends early.
A cheaper or dearer team doesn't fix any of these. They're fixed before anyone is hired.
Three ways to outsource web development
| Option | Suits | Watch for |
|---|---|---|
| Offshore team or marketplace freelancer, such as Upwork or Toptal | Clearly specified builds and repeatable tasks, with someone on your side to manage them | You vet the developer, write the brief and check the work yourself. Time zones slow every question down |
| Local agency | Large builds that need designers, developers and a project manager every day | The people who pitch aren't always the people who build. Ask who runs your project day to day |
| Independent senior developer or consultant | Takeovers, most builds and ongoing care, with one accountable person | One person's capacity. Ask who they bring in for bigger jobs, and who stays accountable for that work |
There's a second choice inside the first: buy a project, or buy people. A project has a fixed scope and price, and suits a rebuild or a migration where the requirements are known up front. Staff augmentation, where outside developers join your team by the hour or the month, suits a product that keeps changing, but your business carries the management, the priorities and the quality control. If nobody in your business can do that, a fixed-price project with a clear brief is the safer buy.
Write the brief before you shop for a team
A developer quoting on a vague brief is guessing, and the cheapest guess usually describes the least work. A brief that teams can quote on covers why you're building the site, who it's for, what it has to do, what's out of scope, a budget range, a date, and how you'll decide. The website brief and agency selection page has the full checklist.
Still working out what the new site needs? That's a scoping job, not a build job. Website redesign scoping turns it into a reverse brief and a technical specification that any team, local or offshore, can quote on.
Eight things to settle before anyone writes code
- Every account in your name. The code repository, hosting, domain, DNS, CMS admin, analytics and any paid licences. The developer gets access. Your business holds the keys.
- Ownership of the work, in writing. IP Australia says IP created by a contractor is the contractor's property unless the contract says otherwise. Have your lawyer put an assignment of the code, designs and content into the contract, covering anything subcontractors produce too.
- The named people. Who will design, build and test your project, and who you'll speak to each week. Not the sales team.
- Milestones you can test. Pay against working, accepted deliverables, and agree what "accepted" means up front: browsers and devices, page speed, content loaded, documentation handed over.
- How changes are handled. Who can ask for a change, how it's priced and who approves it. This is where most budget arguments start.
- Working hours. The Philippines is two to three hours behind Melbourne, depending on daylight saving, India four and a half to five and a half, and Eastern Europe seven to nine. Agree which hours overlap, who answers questions in them, and how quickly.
- Personal data. If the Privacy Act covers your business (generally organisations with an annual turnover of more than $3 million, plus some smaller ones), giving an overseas developer access to customer data is usually a disclosure under Australian Privacy Principle 8. You must take reasonable steps to make sure they handle it properly, and you can be held accountable if they don't. Wherever you can, give them test data, not your live CRM.
- The exit. What gets handed over at launch or if the work ends early: the source code, credentials, documentation, and help moving to the next team.
If you're an agency outsourcing overflow
Agencies outsource for a different reason: they've won more work than the team can carry, and the client must never notice. The eight points above still apply, with two more. The developer works under your brand, in your tools and your process, and never contacts your client unless you ask. And you need a number before you quote the client, so you know your margin.
An offshore team can cost less per hour on a build that's fully specified. It's the work around the build that's harder from another time zone: a client who changes their mind, a deadline in Australian business hours, a producer who needs an answer before the client meeting. That's where a local senior person earns the rate. White label web design and development covers how I work with agencies.
What I've seen from both sides
I spent ten years agency side, six of them as a senior digital producer and then digital production lead. As production lead at a Melbourne agency, I set up the ClickUp workspace and the deployment pipeline for a production team that grew from 3 to 9, running more than 20 client projects at once. Every change went through a request and a review before it was deployed. That discipline is what makes outside developers safe to use, wherever they sit.
In my last in-house role, as Head of Digital at a large residential home builder, I sourced and mentored specialists through Upwork to turn architectural PDF floorplans into interactive, branded SVGs. The specialists did the specialist work. The brief, the review and the standard stayed with us.
Where I fit
I'm an independent digital consultant in Melbourne, working with businesses and agencies across Australia. On an outsourced web project I can:
- Scope it, so every team quotes on the same job, with website redesign scoping.
- Choose the team with website brief and agency selection: the brief, shortlist, scoring and contract review.
- Manage it from your side as part-time digital leadership, whoever does the build.
- Build it. I design and build on most platforms, such as WordPress, Craft CMS and Shopify. For larger builds I lead Keal Collective, a group of vetted people I work with, and I stay accountable for their work. If I'm running your selection, Keal Collective only bids if you invite it.
- Look after it after launch with website maintenance and hosting.
You deal with me from the first call to the finished work.
I don't publish prices, because the job decides them. It starts with a free 20-minute call. When the scope is clear, I can usually send a ballpark by email afterwards. If the work means learning your internal systems, such as a CRM or ERP integration, it starts with paid scoping, credited against the build. Nothing starts until you've agreed the price.
Tell me what you're outsourcing and what's already been decided, and I'll tell you what to settle first.
