Why Australian SMBs keep getting burned by web developers

Three structural problems in the Australian web development market explain almost every horror story, and once you see them you can avoid all three.

I have heard a version of the same story from twelve AU SMB owners in the last six months. Plumber in Sunshine West. Dental clinic in Hawthorn. Boutique liquor store in Adelaide. Family law firm in Canberra. Catering business in Brisbane. Each one paid somewhere between four and forty thousand dollars to a web developer who delivered something broken, late, or never. Each one assumed they had been unlucky. None of them had been unlucky. They had walked into the same three structural traps that every other operator walks into.

This post names the three traps, gives you the five questions that filter for them, and shows what a good engagement actually looks like on the other side.

Problem one: the freelancer-to-agency pipeline

Almost every web developer in Australia starts as a solo freelancer. The good ones get busy. The busy ones realise that doing the actual work is a constraint. The constraint becomes a business problem the moment they want more revenue than their own forty hours can produce.

The standard solution is to hire juniors and stop coding. The freelancer becomes a salesperson. The juniors become the builders. The clients still get pitched by the senior they originally hired. The actual work is now done by people who could not have won the work on their own.

This is the freelancer-to-agency pipeline. It is not a scam. It is a rational response to capacity constraints. It is also the single most common reason an AU SMB website turns out worse than the founder expected. The senior who quoted is not the senior who shipped. The senior who shipped is not the senior who answers your support email at month three.

The honest sign that you are in this trap: the proposal is signed by one name, the kickoff call introduces a second name, and the day-to-day work happens with a third name who you have never met. Two name swaps and you are on the freelancer-to-agency pipeline. Three name swaps and you are buying junior code at senior prices.

Problem two: the offshore arbitrage trap

Roughly forty percent of AU web development work is built by offshore developers, almost always in the Philippines, Vietnam, or India. The agencies do not advertise this because clients flinch. Clients flinch because every previous offshore project they have heard about went badly. Clients are right to flinch.

There is nothing wrong with offshore developers as a category. Plenty of excellent engineers in Manila, Hanoi, Belgrade and Buenos Aires. The problem is structural. The agency pitched a Sydney senior. The actual senior on the project is the local salesperson who does not write code. The code is written by a contractor four time zones away who has never seen your business, never visited your suburb, never talked to your customers. The communication overhead alone costs you fifteen percent of the project on average.

The arbitrage is straightforward. AU senior costs $160 an hour billed at $220. Offshore mid-level costs $25 an hour billed at $220. The gap between $25 and $220 is what makes the agency profitable. The cost is your project quality, which you will not detect until month four when the codebase starts buckling under the second feature request.

The honest sign that you are in this trap: the agency cannot tell you the first name of the engineer building your site. The standard dodge is "we have a team of senior developers" without naming any of them. A real senior team will introduce the actual human on the kickoff call.

Problem three: the WordPress installer pretending to be a developer

This is the most common one and the hardest to detect because the people doing it usually do not know they are doing it. A WordPress installer is someone who can install a theme, configure plugins, and customise a colour palette. That is genuinely useful work. It is not software engineering. The two get conflated because the buyer cannot tell the difference and the seller does not need to volunteer the distinction.

The WordPress installer can ship you a working site in two weeks. The site will be broken at month nine when WordPress core updates, the theme stops being maintained, the booking plugin you depend on changes its API, and the installer cannot fix any of it because they did not write any of the actual code in the first place. They installed someone else's code and now nobody is responsible for it.

The financial trap: WordPress installer pricing looks cheap. Three thousand dollars for a custom site sounds like a deal. The cost is the rebuild eighteen months later when the duct-taped plugin stack collapses under its own weight. That rebuild costs ten to fifteen thousand dollars. The lifetime cost is higher than hiring a real developer the first time.

The honest sign that you are in this trap: the developer's portfolio is full of beautiful screenshots but no live URLs. Or the live URLs all use the same WordPress theme. Or when you ask whether the code was written from scratch, the answer is some variation of "we used the best frameworks for the job" without naming the frameworks.

The five questions that filter out 90 percent of bad actors

Ask these in the first sales call. Take notes. Watch the body language.

One. Can I see three live sites you built in the last twelve months?

Live URLs, not screenshots. Built in the last year, not archived examples from 2019. If they show you three sites and one of them is yours-truly slow, half-broken, or running on a WordPress theme that is also being used by every other plumbing business in the country, you have learned something useful.

Two. Who specifically writes the code, what is their name, and will they be on the kickoff call?

A first name. Ideally a LinkedIn. The answer to whether the engineer is on the kickoff call should be yes. If the answer is "the project manager will introduce you to the team," you are looking at the freelancer-to-agency pipeline.

Three. Is any of the work offshored, and if so, how is that managed?

You want a direct answer. Offshore work is not automatically bad, but undisclosed offshore work is. A senior team will tell you exactly who builds what, what time zone they are in, and how communication is handled. An agency hiding offshore exposure will give you a three-paragraph non-answer.

Four. What happens if you miss the deadline?

The answer should be specific and unflinching. Discount, refund, free month of work, something concrete. "We do not miss deadlines" is a brag, and brags are usually lies.

Five. Walk me through your last delivery, week by week.

You are not asking for confidential client information. You are asking for the rhythm of a real project. A senior who has shipped will describe it in detail. A salesperson who has not will get vague fast. The vagueness is the answer.

What a good engagement actually looks like

If you have made it through the five questions and the developer is still in the running, here is what the next six weeks should look like.

Week one: paid discovery. A senior team will charge you between five hundred and two thousand dollars for a written discovery document that includes scope, architecture, risk areas, and a fixed price for delivery. They are charging because their senior time has a cost. You are paying because you want the discovery to be honest. The deliverable belongs to you whether you hire them for the build or not.

Week two to three: design and architecture. You see Figma files. You see a database schema. You see a deployment plan. None of it is final. All of it is real enough that you can imagine the site running.

Week four to five: build, in public. You should be seeing commits in a Git repository. You should be able to log into a staging environment and click around a half-built version of your site. If the developer says "we cannot show you anything yet, the build is not done," that is a warning sign. Modern development is incremental and visible.

Week six: launch. The site goes live on real infrastructure with real DNS, real SSL, real monitoring. The developer hands over admin access, documentation, and a thirty-day post-launch support window. You do not have to chase them to get this. They schedule it.

Months two to twelve: ongoing. A real engagement includes a defined maintenance arrangement. Hosting, security patches, minor changes, monitoring. The maintenance fee is transparent. The person who built your site is the person who maintains it.

If the engagement looks like this, you have hired the right person. If it does not, walk back through the five questions and find out which one you skipped.

The senior-only model and why it costs more

I will be direct because hedging would be dishonest. Voltari Digital is more expensive than the WordPress installer, more expensive than the offshore-leveraged agency, more expensive than the freelancer-to-agency pipeline. We are not the cheapest option in the AU market.

We are not trying to be.

Senior-only means every line of code on your project is written by someone with ten plus years of production experience. No juniors learning on your budget. No offshore handoff after the sales call. The person who quotes the project is the person who ships it. That model costs more upfront and less overall, because senior work does not need to be rebuilt at month eighteen.

You can see our pricing in plain English at /#pricing. You can see live work at /#work, including ServoSimple, which I built solo with AI assistance and which now runs in real AU petrol stations.

If you have just been burned and you want a second opinion before you hire anyone else, send the scope to /#contact. We will tell you honestly whether a custom build is the right answer or whether a smaller intervention will solve the problem. The second opinion is free.

What to do now

If you read this and recognised your own story in one of the three traps, your homework is not to find a new developer this week. Your homework is to write down what you actually wanted from the original project, what you got instead, and what the gap costs you per month right now. That document is the brief for the next conversation.

The good developers exist. They are not the cheapest. They are not the loudest. They are the ones who can answer the five questions in detail without getting defensive. Once you know to filter for them, the market gets smaller and your odds get better.