How to choose an AU web developer who won't ghost you

Tim runs a plumbing business out of Sunshine West. Eight trucks, twenty-two staff, the kind of operator who knows every supplier by first name. Last year he paid a Melbourne web "agency" $11,400 to rebuild his site and wire up an online booking form.

He got a Figma mockup, three Slack messages, and then nothing.

The agency's website went offline at month four. The phone number rolled to a voicemail that was full. The "senior developer" Tim had been emailing turned out to be a contractor in Manila who'd been let go in February. By the time Tim called me, he was eleven months in, eleven grand down, and still running the same WordPress site he'd been trying to replace.

Tim's story is not unusual. I hear a version of it every second week. The numbers vary, the suburb changes, but the pattern is identical. AU small businesses lose somewhere between five and twenty thousand dollars a year to web developers who take the deposit and disappear, or who deliver something so broken it has to be rebuilt eighteen months later by someone else.

This post is the checklist I wish Tim had before he signed.

The real cost of a ghosted project

The deposit is not the worst part. The worst part is the eleven months you lose. Eleven months of your old site still running, eleven months of booking forms that don't work, eleven months of leads going to your better-organised competitor. By the time you cut your losses and start again, you've lost more in opportunity cost than you ever paid the original developer.

A ghosted project costs you the money, the time, and the second project. Most people who get burned once delay rebuilding for two to three years because they don't trust the next quote. That delay is where the real damage is.

So the goal is not to find a cheap developer. The goal is to never get ghosted in the first place.

Seven red flags that tell you to walk

These are the patterns I see across the operators who got burned. If two or more show up in your sales call, walk.

1. No fixed price. "It depends on scope" is fine for a discovery call. It is not fine for a proposal. A senior team should be able to price a defined scope before you sign anything. If they want you on a time-and-materials contract for a website rebuild, they're protecting themselves at your expense.

2. No portfolio of live sites. Mockups and case studies are easy to fake. Live URLs are not. Ask for three sites they built that are running right now. If they can only show you screenshots or archived links, the work was either never finished or was so bad the client took it down.

3. The senior who sold you is not the senior who builds. This is the most common one. A polished founder runs the sales call, the contract gets signed, and suddenly you're talking to a project manager who's "coordinating with the dev team." That dev team is offshore, junior, or both. The senior you trusted never touches your code.

4. No money-back clause. If the developer is confident, they'll back it. A small, clearly-worded refund clause for missed milestones is the cheapest insurance you can buy. Agencies that refuse one are telling you they expect to miss.

5. Vague timelines. "Six to twelve weeks" is not a timeline. It's a hedge. Real timelines have milestones with dates. "Design approval by week three, staging build by week six, production launch by week nine" is a timeline. Anything fuzzier is a future blame argument.

6. Offshore handoff after the sales call. Nothing wrong with offshore developers as a category. Plenty of excellent engineers in Manila, Hanoi, Belgrade. The problem is the bait-and-switch. If the proposal sounded like a Sydney senior was building your site, and the actual builder is a junior contractor on the other side of the world, you were sold a lie. Ask directly. Get the answer in writing.

7. Payment all upfront. Fifty percent upfront is standard. Some operators do thirty/forty/thirty across milestones, which I prefer. One hundred percent upfront is a leaving party. Don't fund someone's exit.

Five questions to ask in the first call

These five questions filter out almost every problem developer in one phone call. Ask them flat, take notes, and watch the body language.

"Can I see three live sites you built in the last twelve months?" You want recent and live. Not "we built this five years ago for a client who's since rebranded." Recent live work proves the team is currently functional, not running on past glory.

"Who specifically writes the code, and what's their name?" You want a first name and ideally a LinkedIn. If the answer is "our team" or "depends on the project," the answer is offshore juniors. A senior-only studio will name the human and put them on the kickoff call.

"What happens if you miss the deadline?" The answer should be specific and unflinching. Discount, refund, free month of work, something concrete. "We don't miss deadlines" is not an answer. It's a brag, and brags are usually lies.

"Walk me through your last delivery, week by week." You're not asking for confidential client info. You're asking for the rhythm of a real project. A senior who's actually shipped will describe it in detail. A salesperson who hasn't will get vague fast.

"What's your refund policy if I cancel in the first two weeks?" This one's the killer. Any developer who can't tell you their refund policy in plain English does not have one, which means your deposit is gone the moment it hits their account.

The senior-only model and why it costs more

I'll be direct because hedging on this would be dishonest. Voltari Digital is more expensive than the Fiverr quote, more expensive than the Geelong-based one-man-band, more expensive than the "Sydney agency" that's actually four juniors and a salesperson. We're not the cheapest option in the room.

We're not trying to be.

Senior-only means every line of code on your project is written by someone with ten years or more of production experience. No juniors learning on your build. No offshore handoff after the contract signs. The person who quotes the project is the person who ships it, or it's someone on a four-person team who's been doing this for over a decade.

That model costs more upfront because senior time costs more. It costs less overall because senior work doesn't need to be rebuilt at eighteen months. Most of the ghosted-developer rescue jobs I see are not rescues. They're rebuilds. The original work was so structurally bad that fixing it would cost more than starting again. That's the real price of cheap.

If you've been burned before, you already know this. You're not looking for the cheapest quote this time. You're looking for the quote you don't have to pay twice.

Where to go from here

If you want to see what a senior-only quote looks like, our Pilot tier is a fixed price launch package, fixed timeline, and a written money-back clause if we miss the milestone. No offshore handoff, no junior on your build, no surprise scope expansion.

You can see live work at /work, including ServoSimple which I built and run as a live AU SaaS, not as a portfolio piece. And if you want a quote before any call, send the scope to /contact and we'll price it in writing before we ever pick up the phone.

Tim's site is being rebuilt right now. By a senior, on a fixed price, with a deadline. Whatever you do next, make sure yours is too.