StensonDigital.

7 April 2026 · Opinion

Five red flags to watch for in a Melbourne web designer's quote

Most Melbourne web designer quotes look professional. A few specific things on them tell you whether the project will actually deliver. Here's what to look for.

  • hiring a designer
  • working with a web designer
  • quotes
  • Melbourne

Most quotes from Melbourne web designers look professional. They’ve got a line-item breakdown, a total, a timeline, a deposit structure. They look like real business documents.

The trouble is that “looks professional” and “is going to deliver” aren’t the same thing. I’ve seen plenty of beautifully-formatted quotes turn into projects that went sideways, and plenty of scrappy-looking quotes turn into builds that absolutely delivered.

What actually separates the two is what’s on the quote. Five specific things, all of which are worth scanning for before you sign.

If you’re about to commit A$5,000–A$15,000 to a Melbourne web designer, this is the read-through I’d want before I committed.

Red flag 1: No mention of what happens after launch

Open the quote. Search for the word “launch”, “maintenance”, “support”, or “after”. If none of those appear, that’s the first red flag.

The reason this matters: a quote that’s silent on post-launch is a quote from someone who’s mentally modelling this as a project, not a relationship. The day the invoice gets paid is the day the relationship effectively ends. You become “support” — a category of work the designer doesn’t really want, doesn’t price for, and doesn’t have a process for.

This is the structural reason most Melbourne web designers “ghost” you in month four. It’s not malice. It’s that there was never anything in the contract that anticipated month four.

What you want to see instead: A clear, specific section about what happens after launch. Either an included grace period (e.g., “30 days of revisions included”) or an explicit ongoing retainer with a price and a scope. “We’re available for support afterwards” is not enough — that’s the phrase that turns into silence by month three.

The exact question to ask: “What does the quote include for the first six months after launch, and what’s the cost structure after that?” If the answer is vague, the project will be too.

Red flag 2: The platform isn’t named

A quote that says “we’ll build you a modern, responsive website” without specifying the underlying platform is a red flag.

Sometimes this means the designer hasn’t decided yet, which is fine — but if so, they should say “we’ll recommend a platform after our discovery call” or similar. Sometimes it means they default to WordPress with their preferred page builder and don’t want to flag that to you because they know it’s not the strongest answer for your situation.

The platform matters for everything that happens later. WordPress with a page builder is going to be slower than Astro, harder to maintain than Squarespace, and have specific ongoing costs (plugin licenses, hosting, security plugins) that Astro and Squarespace don’t. You can’t make an informed decision about a quote without knowing what’s being built.

What you want to see instead: A specific named platform with a one-sentence justification of why it’s the right fit. “Built on WordPress with the [theme name] theme — we’re picking this because of X, Y, Z” or “Built as a static site on Astro hosted on Cloudflare — we’re picking this for speed and low ongoing costs”.

The exact question to ask: “What platform are you building this on, and why is it the right fit for my situation specifically?” The “specifically” matters — generic justifications mean they pick the same platform for everyone.

Red flag 3: The number of pages is suspiciously round

This one’s subtle but it’s a real tell.

Quotes that say “10-page website” or “15-page website” without a list of what those pages actually are usually mean the designer is using “number of pages” as a billing unit rather than as a content plan. The actual question — what pages does your business need? — has been replaced with a price ladder.

The honest version is that there are exactly as many pages as your business needs and not more. For most small service businesses, that’s somewhere between 5 and 12 — Home, About, Services (or several Service pages), Contact, plus some combination of Case Studies, Blog, Method, and Tools. Not 10 because the package said 10. Not 8 because the package said 8.

What this red flag usually correlates with: quotes that include filler pages nobody will read (a “Testimonials” page when the testimonials should be on Home, an “Our Process” page when the process should be on Services) just to hit the package number.

What you want to see instead: A specific list of named pages, with a one-line description of what each one’s for. “Home (positioning + the three core services + lead capture), Services (deep-dive on each of the four service categories, including pricing), About (your story, the credentials, the team), Case studies index + 6 individual case study pages, Contact” — that kind of thing.

The exact question to ask: “What pages are we building, specifically, and why each one?”

Red flag 4: The timeline is suspiciously short

This is the opposite of what you might expect. “We can have it live in three weeks” is almost always a worse sign than “We’re looking at 8–10 weeks”.

A real Melbourne small business website — done properly, with discovery, real copy, real photography, actual structure designed around how customers find you — takes 6–10 weeks. Sometimes longer if there’s heavy custom functionality. The 3-week version means one of two things:

  1. The designer is using a template and dropping your logo + colours on it, without actually doing the work of figuring out what your specific business needs.
  2. The designer is overbooked and is going to rush the build, with the corner-cutting showing up in the result.

Neither is what you want. The shorter timeline isn’t a feature — it’s a warning that the depth of work being done is shallower than your business deserves.

What I’ve seen the most: 3-week builds that end up requiring 6 months of post-launch fixes because the foundation was wrong. The “fast” build was actually the slow one once you counted the cleanup time.

What you want to see instead: A 6–10 week timeline with specific milestones. Week 1–2: discovery and content audit. Week 3–4: copy and structure. Week 5–6: design. Week 7–8: build. Week 9–10: review, polish, launch. Some variation on that, broken down so you can see what’s happening when.

The exact question to ask: “Why is the timeline what it is? What happens in each phase?” If the answer is vague, the build will be too.

Red flag 5: The deposit is more than 50%

The deposit structure tells you about the designer’s cashflow situation more than anything else.

A healthy, established designer typically asks for a 30–50% deposit, with progress payments tied to specific milestones (e.g., 30% on signing, 40% on design approval, 30% on launch). The designer has enough cashflow to absorb the gap between starting work and getting paid in full.

A designer asking for 70%+ up front, or for the full amount on signing, is telling you (without meaning to) that their cashflow is tight enough that they need most of the project paid before they start. This isn’t always a disaster — some legitimate small designers run lean. But it does mean two things you should know:

  1. If the project goes sideways (their personal life intervenes, they take on too many other projects, they lose interest after the first weeks), you’ve paid most of the money for the least complete version of the work.
  2. The designer has less skin in the game at the back end of the project, which is exactly the period where most designers’ focus drifts.

I personally take 50% on signing and 50% on launch, with a no-questions refund of any unused portion if I haven’t started building. That’s not unique — most established Melbourne designers operate similarly. The 70%+ up-front structure is a flag.

What you want to see instead: A 30–50% deposit, with the remainder either due at launch or staged across milestones.

The exact question to ask: “What’s the payment structure, and what happens if the project doesn’t progress?” The answer about what happens if it doesn’t progress is the more telling part.

The colour-coded summary

Run your quote through these five. Count the flags.

  • Zero flags: You’re talking to someone who runs this professionally. Proceed with reasonable confidence.
  • One flag: Worth asking the question once. If the answer is sensible, fine.
  • Two flags: Get a second quote from someone else before committing. The pattern of issues is concerning enough that you should compare.
  • Three or more: Don’t sign. Get more quotes. This designer might still be perfectly good — but the quote itself is telling you the project will be friction-heavy, and you should know that before committing A$8,000.

The point of this isn’t to be paranoid about Melbourne designers. Most of them are honest, well-meaning, and want their work to succeed. The quote red flags above usually aren’t malicious — they’re just signs that the structure of the project isn’t built to deliver the result you want, even when everyone involved has good intentions.

You don’t need a perfect designer. You need a designer whose business model produces the outcome you’re paying for. The quote is the first artefact of their business model. It tells you a lot. For the wider picture on how to hire well, what to expect from a healthy project, and what good ongoing support looks like, the complete guide to working with a Melbourne web designer is the broader reference.


If you’d like a second pair of eyes on a quote you’re considering, book a 15-minute call — I’m happy to read it on the call and tell you straight what I’d want to know more about. No pitch, no commission, just an honest read. I’d rather you go with the right Melbourne designer than the wrong one.

Or if you’re at the earlier stage of thinking about whether your current site needs replacing in the first place, run the free audit and you’ll see in 30 seconds whether you’re in tune-up or rebuild territory.

The full picture

The complete guide to working with a Melbourne web designer

This post covers one specific angle. The complete guide on working with a designer is the long-form reference if you want the whole picture.

Read the guide

Written by Elliot Stenson. If you spot something off in this post — outdated fact, wrong assumption, or a counter-argument I should have addressed — email me and I'll update it.

Keep reading

If this landed

Want to talk through your own site?

Fifteen minutes, no pressure, no sales pitch. I'll walk through what's working on your current site, what isn't, and what to do about it.