Get three website quotes in Australia and you might see $3,000, $9,000 and $28,000 for what sounds like the same job. The quotes are not describing the same job and the difference is rarely explained. This guide is how to evaluate web designers, developers and agencies properly: the questions that expose thin processes, the ownership issues that cause the ugliest breakups and the single question that reveals more than any portfolio. Use it on everyone you talk to, including us.

The straight answer: choose the process, not just the portfolio

Anyone can show you attractive screenshots. What separates a good web designer from an expensive mistake is whether they can explain, in plain English, before you sign:

  • what the website needs to achieve for your business

  • who it needs to convince and what those people care about

  • what pages it needs and why

  • why the proposed platform makes sense for you, not just for them

  • how mobile has been designed, not just accommodated

  • how enquiries or sales will actually be generated and measured

  • exactly what is included in the quote and what is not

  • what you will own and control when the project ends

  • what happens after launch and what it costs

If they can walk you through all nine without flinching, you are probably talking to a professional. If the conversation keeps steering back to how it will look, keep interviewing.

Here is the order of evaluation this whole guide builds toward. Price is on the list. It is last on purpose.

1. Business understanding: do they get what you sell and who buys it?

2. Process: is there a real method between the sales call and the launch?

3. Portfolio: does the live work hold up, on mobile, today?

4. Scope: is everything included written down, with exclusions?

5. Ownership: domain, accounts, files, access, exit

6. Support: who answers when something breaks after launch?

7. Price: only comparable once the six layers above match

The web designer decision stack. Most bad hiring decisions come from starting at layer 7 and never reaching layer 1.

Work out what you actually need before comparing web designers

You do not need a technical brief. You need a page of honest answers: what the business does, who the primary customer is, the one job the website must do, your key services or products, what is wrong with the current site, the functionality you cannot live without, who is producing the content, what branding exists, a rough budget range and when you would like to launch. Writing this down before you contact anyone changes the entire dynamic and putting together a simple website brief first means every provider quotes against the same reality instead of their own assumptions.

Be specific about the goal. Increase enquiries, generate phone calls, take bookings, sell products, look credible enough to win bigger contracts, support recruitment. If the site's job is converting paid traffic, say so early and involve the team who will run your Google Ads before the sitemap is drawn, because why paid clicks land and leave without converting is usually decided at the design stage, not the campaign stage.

Separate essentials from nice to haves

This one habit prevents the classic mistake of comparing radically different scopes as if they were the same product.

Usually essential

Usually optional at launch

Contact form that works and notifies the right person

Complex animation

Online booking, if bookings run the business

Interactive calculators

Ecommerce, if you sell online

Advanced product filtering

A page per core service

Custom illustration

Genuine mobile optimisation

Extensive video production

CRM integration, where a CRM runs the pipeline

Customer portals

Multiple locations handled properly

Bespoke features nobody asked for

Essential items belong in every quote you request. Optional items can be phase two, priced separately, so they stop hiding inside inflated lump sums.

Freelancer, web designer, developer or agency?

The labels overlap more than the industry admits. Plenty of freelancers outperform agencies and plenty of agencies are one senior person plus subcontractors. What matters is matching the shape of the provider to the shape of your project.

Freelancer

Often the right call for smaller brochure sites, tightly scoped projects, lower budgets and businesses happy to coordinate copywriting or SEO separately. The advantages are real: direct communication with the person doing the work, lower overhead and often a strong specialist network. The risks are structural rather than personal: limited capacity, dependency on one human who takes holidays and gets sick, strategy and copy often sitting outside scope and ongoing support that depends entirely on their availability. None of that is a reason to avoid freelancers. It is a reason to ask how each of those situations gets handled before you need them handled.

Web design agency

Often suited to broader strategy, larger sites, ongoing marketing and businesses that want one accountable team covering strategy, UX, design, development, SEO, copy, analytics, paid media and maintenance. What to watch: higher prices, account manager layers between you and the people doing the work, delegation running deeper than the sales conversation implied and vague answers about who actually touches your project.

Developer

A strong developer is the right centre of gravity when the priority is custom functionality, integrations, technical systems or application behaviour. But development and design are different skills. Not every developer is a UX designer, a copywriter, an SEO strategist or a conversion specialist and the honest ones say so themselves. A trades business that needs a site to produce phone calls has a design and conversion problem before it has a technical one, which is why how we build websites for trade businesses starts with the enquiry path and works backwards to the technology.

Provider

Often best for

Strength

Watch out for

Freelancer

Smaller, focused builds

Direct relationship

Capacity and dependency on one person

Agency

Strategy plus multidisciplinary work

Broader capability

Cost and team layers

Developer

Technical functionality

Strong engineering

May lack UX, copy and SEO depth

DIY platform

Very simple requirements

Low upfront cost

Your time, no strategy, scaling limits

How to review a web designer's portfolio properly

The wrong question is: do I like how these websites look? The better questions: is each site genuinely different, can you understand each business within seconds, are services easy to find, are calls to action obvious, does the copy sound specific to the business or could it be pasted onto any competitor, do the sites load reasonably fast and can the designer explain the problem each project solved? Design that photographs well and design that converts are different achievements. You are shopping for the second one.

Look at live websites, not screenshots only

Screenshots hide slow performance, broken mobile layouts, awkward navigation, painful forms, outdated content and accessibility problems. Open several real projects and use them like a customer would: find a service, fill a form, tap the phone number. While you are at it, run a quick accessibility check you can run on any site over a couple of their builds. Two minutes and you learn whether accessibility is something they practise or something they mention.

Review on mobile

Most Australian business sites now take the majority of their traffic on phones. On mobile, check the navigation, the hero, button sizes, forms, tap to call links, typography, spacing, sticky elements and the booking or checkout flow if there is one. A desktop screenshot tells you almost nothing about any of this and a portfolio full of desktop screenshots is itself a small red flag.

Look for variety

If every project has the same hero, layout, cards, animation and page sequence, the provider is probably working from a reusable design system or template. That is not automatically bad. Reusable systems can be efficient and reliable. The important question is whether they are transparent about it and whether the price you are quoted matches what is actually being reused versus designed. Which brings us to the most abused word in this industry.

Pay attention to the questions they ask you

This is the strongest selection signal available to a non technical buyer and it costs nothing to observe. A designer who plans to build something commercially useful has to understand your customers, services, competitors, goals, lead quality, current problems, sales process, traffic sources, analytics and advertising. So they will ask about those things. A designer who plans to decorate will ask what colours you like.

Discovery that predicts a good website

Discovery that predicts a pretty one

What happens after someone submits an enquiry? Who follows up and how fast?

What colours do you like?

Which service makes you the most margin and does the current site sell it?

Which websites do you like the look of?

Where do your best customers come from today?

How many pages do you want?

Colour and reference site questions matter eventually. They should not be the entire strategy.

What does custom website design actually mean?

Custom is the most loosely used word in web design quotes and the gap between what businesses imagine and what they receive is where most of the resentment in this industry lives. In practice, custom can mean four quite different things.

Level 1: template with content replacement

An existing template with your logo, colours, text and images swapped in. Genuinely useful for small budgets, simple sites and fast launches. It is not what most businesses picture when they hear fully custom design and it should not be priced as if it were.

Level 2: customised theme or framework

An established WordPress or Shopify theme, Webflow framework or component library, significantly adapted: new page structures, layouts, styling and components. This can be an excellent approach and a large share of good Australian small business websites are built exactly this way. The problem is not using a framework. The problem is pretending a lightly edited template was designed from scratch.

Level 3: bespoke UI and UX design

The team designs the sitemap, wireframes, page hierarchy, design system, layouts, components and responsive behaviour specifically around your business, then builds it, often still on an established CMS. This is the level most growing businesses actually mean when they say custom.

Level 4: custom software development

Configurators, portals, quoting systems, marketplaces, complex integrations, bespoke ecommerce logic. Real software engineering, priced like it. Most small business websites do not need this and a provider who steers every conversation here deserves scrutiny.

Level

Starting point

What gets customised

Appropriate for

Template

Existing layout

Brand and content swap

Small, simple, fast

Customised framework

Theme or component library

Structure, layouts, styling

Many Australian SME sites

Bespoke UI and UX

Your business requirements

Full page and component design

Growth focused businesses

Custom application

Custom architecture

Full software logic

Complex systems only

Questions to ask about custom

Ask directly: are you starting from an existing theme? Are layouts designed before development begins? Will I see wireframes and both desktop and mobile designs? Which parts use standard components and which are designed specifically for us? Are premium themes or frameworks involved and who holds those licences? Will I receive design or source files? None of these are gotcha questions. A professional answers them in two minutes and which platforms suit which kinds of business is a fair way to sanity check the platform half of their answer yourself.

What we recommend at Elev8d

There is nothing inherently wrong with templates or frameworks. We use component systems ourselves where they serve the project. The problem is paying bespoke design pricing without knowing you are receiving a modified template. Ask which level you are buying, get it written into the scope and check the price belongs to that level. Honest providers of all four levels exist. The trick is making sure the label, the work and the invoice all describe the same thing.

15 questions to ask before hiring a web designer

Print these. Ask all of them, on every discovery call and write down the answers. The answers matter, but so does how comfortably each one is answered.

1. Who will actually work on my website?

Separate the salesperson from the strategist, designer, developer, copywriter and project manager. You want names or at least roles and to know what is outsourced and where.

2. What is your design process?

You are listening for something like: discovery, sitemap, content, wireframes, design, development, QA, launch. Exact terminology differs and that is fine. What you do not want is a process that jumps from sales call to finished homepage design with nothing in between.

Discovery → sitemap → content → wireframes → design → development → QA → launch → training → maintenance

The stages of a healthy website project. Proposals that skip entire stages are quoting for a different, smaller job than you think you are buying.

3. Will the website be custom designed?

Then immediately ask what custom means in their process and map their answer to the four levels above.

4. Which platform do you recommend and why?

The answer should reference your needs, budget, ecommerce requirements, editing ability, integrations and growth plans, not simply we build everything in WordPress. Platform follows requirements. If WordPress is the recommendation, whether WordPress is still worth it in 2026 is a fair test of the reasoning and how WordPress, Webflow, Shopify and custom builds compare covers the trade at length.

5. Who provides the website copy?

Clarify whether copy is professionally written, edited from your drafts, entirely your responsibility or produced with AI assistance and how heavily. Copy is the most commonly unclaimed responsibility in website projects and unclaimed responsibilities become delays.

6. Is SEO included and what exactly does that mean?

SEO friendly by itself tells you almost nothing. Useful inclusions have names: keyword research, sitemap planning, URL structure, metadata, redirects, schema, technical SEO, Search Console setup, on page optimisation. If organic search matters to the business case, how organic search really works for Australian businesses will calibrate your expectations and it is worth having an SEO team involved before the sitemap is locked rather than bolted on after launch.

7. How is mobile handled?

Ask whether mobile is separately designed, considered during component design or simply adjusted after the desktop build. It will be responsive is the weakest possible answer to this question.

8. What accessibility standard do you design toward?

For Australian businesses, WCAG 2.2 AA is a useful benchmark to ask about. You are not testing whether they recite standards, you are testing whether accessibility exists in their process at all. What accessibility actually asks of an Australian business site covers why this question earns its place on the list.

9. How do you test before launch?

Look for mobile and desktop testing across browsers, forms, tracking, redirects, accessibility, speed, SEO settings, links and integrations. Compare their answer against everything worth testing before a site goes live. No formal QA process is a legitimate reason to walk away at any price.

10. What will I own after the project?

Design, copy, custom code, photography, source files, CMS account, domain, hosting account, licences. This question gets a whole section below, because it decides how expensive your worst day with this provider will be.

11. Will I have administrator access?

The answer should be an explicit yes or a specific reason with a path to access. Vague answers here become launch day surprises.

12. Who owns the domain and hosting account?

Your business should control its critical infrastructure rather than depending permanently on one supplier. More below.

13. What happens if we stop working together?

Can another developer take over? What gets handed over? How does hosting migrate? Are there exit fees? What happens to plugin and theme licences? Does our access survive? A provider who answers this comfortably is a provider you can probably trust while things are good, too.

14. What ongoing costs should I expect?

Hosting, maintenance, plugins, themes, apps, licences, domains, support, security, backups. Get the annual number, not just the monthly ones and compare it against what maintenance really costs after launch so you know whether the quote is realistic or a teaser.

15. What is not included in the quote?

Possibly the most revealing question of all. A professional answers with a list. An amateur answers with a pause.

How to compare website quotes without looking only at price

Website quotes differ by thousands, sometimes tens of thousands, because they are frequently not describing the same product. Before comparing dollars, compare what is inside: discovery, strategy, sitemap, number of designed templates, number of pages, copywriting, SEO, design depth, development, responsive design, forms, integrations, tracking, redirects, accessibility, QA, training, hosting, maintenance and post launch support. Two quotes only become comparable once those line up.

Create a quote comparison matrix

Put every proposal into the same grid. Ten minutes of typing has saved our clients five figure mistakes.

Item

Designer A

Designer B

Designer C

Discovery workshop

Included

No

Included

Sitemap

Included

Client supplies

Included

Custom design level

Bespoke UI

Template

Customised theme

Mobile designs

Included

Responsive only

Included

Copywriting

10 pages

No

Editing only

SEO foundations

Included

Basic metadata

Included

Redirects

Included

Extra

Included

GA4 and Search Console

Included

No

Extra

QA process

Documented

Not specified

Included

Training

Included

1 hour

Included

Hosting

Optional

Mandatory

Optional

Maintenance

Optional

Required

Optional

Ownership

Client after payment

Unclear

Client

Handover

Included

Unclear

Included

Ask for assumptions and exclusions

A clear quote states its assumptions: how many pages, how many revision rounds, who supplies copy and photography, how many ecommerce products, which custom features, which integrations, whether data migration and redirects are included, what hosting and licences cost and how much training is provided. Vague scope creates scope disputes and scope disputes are where client and designer relationships go to die.

Scope wording that protects both sides

Scope wording that guarantees an argument

Design and build 7 page templates: home, service, service child, about, contact, blog index, blog post. Two revision rounds per template.

Design and develop a modern professional website.

Client supplies copy for 5 pages by [date]; we write home and top 3 service pages. 301 redirects for the top 50 URLs included.

Includes copy and SEO.

Should you choose the cheapest web designer?

Not automatically. But also refuse the lazy agency logic that expensive automatically means better. A higher price may reflect genuine strategy, senior experience, design depth, development complexity, project management, copywriting, SEO and QA. Or it may reflect a nice office and a sales team. The only question that cuts through: what additional outcome, work or risk reduction does the higher quote actually buy? Calibrate against reality before the calls: how much a business website costs at each budget level sets the market ranges, the website costs businesses only discover later covers the line items that ambush budgets in year one and a realistic estimate of what your build should cost gives you a number to test every quote against.

Website ownership: sort this out before the project starts

Here is the section that saves businesses the most money and the most grief. Ownership is not one thing. A website involves a domain name, a hosting account, a CMS installation, design files, written copy, photography, custom code, theme and plugin licences, fonts, stock imagery, analytics accounts and third party integrations. Each can sit under a different ownership or licensing arrangement and the time to sort them out is before work starts, when everyone is friendly and nothing is leverage.

Domain

The domain should normally be registered under an account your business controls. Know the registrar, the account email, the renewal date, the recovery process and where DNS is managed. The domain is the one asset that cannot be rebuilt if it is lost: a website can be remade, but a domain held hostage takes your email, your rankings and your brand with it.

Hosting

Ask whether hosting sits in your name or theirs, whether the site can move later, whether backups can be exported, what happens to the website if you cancel their services and whether migration attracts a fee. Managed hosting through your agency is not inherently lock-in and it is often genuinely convenient. Inability to leave is lock-in. The test is not who manages it. The test is whether you can take the site and go.

CMS access

After launch you should know exactly who has administrator access, whether your access is restricted, why any restriction exists and how another provider would gain access if you switched. Some providers restrict admin to stop clients breaking things, which is defensible when it is explained and reversible. You should not discover after launch that you paid for a website you cannot administer or move.

Intellectual property

The part most businesses get backwards: paying the invoice does not automatically make you the owner of everything created. Australian government business guidance is direct about this. Absent a contract saying otherwise, a contractor generally owns the intellectual property they create and at best the law may imply a licence for you to use it. If you expect to own the design, code or content, that arrangement needs to be written into the agreement, not assumed from the payment. IP Australia's guidance covers the same ground from the other direction: IP rights are assets that can be assigned or licensed, which is exactly why the contract needs to say which of those two things is happening.

So ask, in writing: what happens to the custom design, custom code, written content, graphics and source files after final payment? Is ownership assigned to us or licensed to us and on what terms? For projects where IP ownership materially matters, a couple of hundred dollars of legal review before signing is the cheapest insurance in this entire process.

Third party licences

Some components are nobody's to hand over. WordPress plugins, Shopify apps, stock photography, commercial fonts, premium themes and third party software are typically used under licences rather than owned and government guidance on contractor IP makes the same distinction for a provider's pre existing tools of trade: they stay with the provider, licensed for your use. Clarify who holds each licence, what it costs to renew, who is responsible for renewing, whether it survives the end of the agency relationship and what would need replacing if you left. Demanding ownership of things that cannot be owned wastes goodwill; knowing your licence position costs nothing.

Component of your website

Typical arrangement

What to confirm

Domain name

Registered to an owner

Your business's account, not theirs

Hosting

Account based

Whose name and portability

CMS installation

Access controlled

Your administrator access

Written copy

Own or licensed

What the contract assigns

Custom design and code

Own or licensed

Assigned or licensed, in writing

Theme and plugins

Licensed

Licence holder, renewal cost, survival on exit

Stock images and fonts

Licensed

Licence scope covers your use

Analytics and Search Console

Access roles

Business holds admin and owner roles

That table is the ownership map of a typical business website: a few things you should own, several you licence and accounts where what matters is the access role. Businesses that understand which is which never get held hostage.

What should be included in a website handover?

At minimum, depending on the project: CMS administrator access, hosting details, confirmation of domain and DNS access, analytics access, Search Console, Tag Manager, third party integration credentials, a list of licences and renewal dates, backup information, design or source files where the contract provides for them, documentation, training, maintenance instructions and an emergency contact process. Two of these deserve special mention because they are so routinely botched: setting up Search Console with your business as the verified owner rather than only the agency and getting GA4 configured under the business's own account so your data history survives any change of supplier.

Ask for the handover to arrive as a simple asset register. One page and it converts a fuzzy relationship into an auditable one:

Asset

Platform

Owner

Admin access

Renewal

Domain

Registrar

Business

Yes

Annual

Hosting

Provider

Business or agency

Yes

Monthly

Website CMS

WordPress

Business

Administrator

N/A

GA4

Google

Business

Administrator

N/A

Search Console

Google

Business

Verified owner

N/A

Plugin licences

Various

Confirm

Confirm

Annual

Add a row for every licence and integration your build uses. Pair the register with a backup and recovery plan worth the name, because a handover without backups is a handover of risk.

What should a web design contract cover?

General information, not legal advice. A clear agreement typically addresses: the parties, scope, deliverables, each side's responsibilities, timeline, approvals, revision rounds, payment schedule, variations, intellectual property, third party licences, hosting, ongoing costs, delays, termination, handover, confidentiality and a dispute process. Australian government guidance on engaging contractors consistently recommends documenting exactly these matters in writing rather than relying on friendly understandings, because friendly understandings do not survive disagreements.

Scope and deliverables

Avoid professional five page website as a scope. Prefer named page templates, listed functionality, listed integrations, content responsibilities, SEO work items, tracking setup, launch work and training. Everything the salesperson promised verbally belongs in this section, in writing. If it is not in the scope, it is not in the project.

Payment schedule

Common structures: deposit plus milestone plus completion, staged monthly payments or deposit plus design approval plus launch. No structure is universally best. What matters is knowing when payments are due, what milestone triggers each one, whether anything is refundable and what happens to money and work if the project pauses. Payments tied to defined milestones protect both sides; payments tied to calendar dates while the project drifts protect nobody.

Variations

The agreement should explain what happens when pages are added, functionality changes, content arrives late, integrations expand or revision limits are exceeded.

Termination and exit

Understand how either party can terminate, what fees fall due, who gets partially completed work, which files are handed over, when access is removed, how hosting transitions and where IP rights land at termination. Reading the exit clauses before signing is the contractual version of checking where the fire exits are: you hope to never use them and you check anyway.

Unfair contract terms

This article will not analyse anyone's contract legally and neither should a web agency. But it is worth knowing the backdrop: Australian Consumer Law contains protections against unfair terms in standard form consumer and qualifying small business contracts and since 9 November 2023, proposing, using or relying on prohibited unfair terms can attract penalties. The ACCC's compliance and enforcement priorities for 2026 to 27, announced in February 2026, specifically flag unfair contract terms with a focus on harmful cancellation practices: automatic renewals, early termination fees and clauses that stop you cancelling. Which is worth pausing on, because auto renewing maintenance agreements and punishing exit fees are exactly the mechanics some website suppliers rely on. For a significant project, have unfamiliar or heavily one sided terms professionally reviewed before signing. It costs less than one month of a maintenance contract you cannot escape.

Web designer red flags to watch for

Fifteen of them, earned the hard way by businesses that came to us afterwards.

1. They promise Google rankings

We'll get you to number one should trigger questions, not excitement. No web designer controls Google's rankings and the ones who claim to are telling you something about their honesty in general.

2. They recommend a platform before understanding the business

Every business should use WordPress and Shopify is always better are the same mistake in different directions. Platform follows requirements.

3. They cannot explain what custom means

Ask directly, then map the answer to the four levels earlier in this guide. Evasion here predicts evasion everywhere.

4. The proposal is one paragraph

If the project costs thousands and the scope is design and develop a modern professional website, the ambiguity is not laziness, it is dangerous. Every undefined item is a future dispute.

5. Ownership is unclear

Especially the domain, the website itself, code, content and accounts. Unclear now means contested later.

6. You cannot access your own accounts

Domain, GA4, Search Console, ad accounts, CMS. If you are asking for access to your own business assets and getting excuses, believe the excuses.

7. They refuse to explain ongoing costs

Hosting, licences, maintenance, apps, subscriptions. You should know the full annual picture before signing, not discover it invoice by invoice.

8. Their only discovery question is which websites do you like

Inspiration is not strategy. A mood board is not a plan for generating enquiries.

9. Every portfolio website looks identical

Not automatically bad, as covered earlier. But ask why and listen for whether the answer is a transparent system or a disguised template mill.

10. No mobile examples or testing process

For a modern business site this is close to disqualifying. Most of your customers will only ever see the mobile version.

11. SEO means we'll install Yoast

An SEO plugin is a tool, not a strategy. If organic traffic matters to your business case, this answer alone should end the conversation.

12. No redirect plan for a redesign

If URLs change without redirects, rankings and traffic built over years can be damaged in a day. Anyone rebuilding an existing site should speak fluently about redesigning without losing your search rankings. Silence on redirects is a flag with a siren attached.

13. No backup or rollback plan for launch

Especially when replacing a working business website. What happens if launch night goes wrong should have a rehearsed answer.

14. They disappear when you ask about handover

A good supplier is comfortable explaining how you would leave, because they do not plan to give you a reason to.

15. Pressure to sign immediately

Fake discounts, artificial deadlines, price only valid today, urgency before scope has even been discussed. Quality providers have pipelines, not pressure tactics.

Question

Good sign

Warning sign

Who owns the domain?

The business

The designer only

Is scope detailed?

Clear deliverables

Professional website

What does custom mean?

Explained clearly

Avoids the question

Who does the work?

Named roles

Unclear outsourcing

Is mobile tested?

Defined process

It will be responsive

Is SEO included?

Specific inclusions

SEO ready, unspecified

Are ongoing costs listed?

Transparent annual picture

Discovered later

Can you leave?

Clear handover process

Locked platform or accounts

Are revisions defined?

Counted per template

Unlimited or vague

Is QA documented?

Yes, with a checklist

No formal process

Are redirects included?

Yes on redesigns

Not mentioned

Is ownership in writing?

In the contract

Verbal assurance

How much should reviews matter?

Reviews help you assess communication, timelines, support, reliability and how problems got resolved. They are weak evidence when reduced to a star rating and a count. Look for detail: the project stayed organised, feedback was handled well, scope remained clear, support continued after launch, the business saw actual results. Those themes describe how a provider behaves under normal friction, which is what you are really buying.

And one question beats another dozen five star reviews: ask the designer what happens when a client is unhappy. Everyone has had an unhappy client. The ones who pretend otherwise or blame every one of them, are answering a different question than the one you asked.

Do you need a local web designer?

Not necessarily. Great websites are built remotely every day and a brilliant provider two states away beats a mediocre one two suburbs away. Local makes sense when it adds something specific: face to face workshops for a complex project, genuine local market understanding, photography or content work that needs someone onsite or simply a preference for local accountability where you can sit across a table from the people responsible.

For our own clients, being Melbourne based matters most at the strategy end: a Carlton café, a Dandenong manufacturer and a Toorak financial firm are competing in genuinely different local markets and understanding those markets shapes the site. It matters much less for the build itself, which is why we work with clients around Australia. The same logic applies to specialised sectors: a Sydney law firm is often better served by websites for professional services firms built by a team who understands compliance and referral dynamics than by whoever happens to be closest.

How to shortlist web designers

Step 1. Choose 3 to 4 providers, not 12. Beyond four, you are not comparing, you are procrastinating.

Step 2. Send all of them the same written brief. Identical inputs are the only way to get comparable outputs.

Step 3. Have a discovery call with each and score the questions they ask you as much as the answers they give.

Step 4. Review live portfolio work, on your phone, like a customer.

Step 5. Put every proposal into the same comparison matrix from earlier in this guide.

Step 6. Clarify ownership, access and recurring costs in writing.

Step 7. Ask questions about every gap. How the gaps get handled is a preview of the project.

Step 8. Choose on understanding, process, quality, communication, commercial fit, scope, then price. Not price alone.

Web designer comparison scorecard

Score each shortlisted provider from 1 to 5 in every category, multiply by the weight and total it. The weights are the point: price is deliberately the smallest category, because a cheap website that fails its commercial job is the most expensive kind.

Category

Weight

Understanding of your business

20%

Process and strategy

15%

Portfolio quality, live and on mobile

10%

Mobile and UX thinking

10%

SEO and technical foundations

10%

Scope clarity

10%

Ownership and handover

10%

Communication

5%

Ongoing support

5%

Price against value

5%

If two providers finish close, the tiebreakers are the human ones: who explained things without jargon, who answered the exit question comfortably and who asked the discovery question that made you stop and think.

Common mistakes businesses make when hiring a web designer

Choosing by homepage aesthetics alone

You are buying a commercial asset, not artwork. Pretty and profitable overlap less than the industry pretends.

Choosing the cheapest quote without matching scope

The cheapest quote is often the smallest scope wearing a friendly number.

Choosing the most expensive quote assuming it is better

Price is a claim, not evidence. Make the expensive quote justify its gap line by line.

Not checking live portfolio sites

Screenshots are marketing. Live sites are proof.

Never testing the portfolio on mobile

Where most of your customers will actually be and where weak builds fall apart first.

Failing to define the website goal

A site with no defined job will do no job in particular, beautifully.

Assuming custom means custom

Ask which of the four levels you are buying and check the price matches.

Ignoring copy and content responsibility

Unowned copy is the single most common cause of website projects running months late.

Ignoring SEO until after launch

URL structure, page hierarchy and content decisions are SEO decisions. Retrofitting costs more than including.

Forgetting redirects during redesigns

Years of rankings can be damaged in one unredirected launch.

Not discussing ongoing costs

The purchase price is the entry fee. The annual running cost is the membership.

Letting the agency own every account

Convenient right up until the relationship changes. Access roles are cheap to set up correctly on day one.

Assuming IP ownership without reading the contract

The default position under Australian law generally favours the creator, not the payer. The contract is where that changes or does not.

Not planning handover

A handover register takes an hour to complete and removes the single biggest source of exit friction.

Signing a vague proposal because the salesperson was convincing

Charm is not scope. The document you sign is the project you get.

Our honest take: a good web designer should make it easy for you to leave

A healthy agency relationship should never depend on technical captivity. If the website is good and the service stays valuable, clients stay because they want to, not because the domain is trapped, the CMS is inaccessible, the hosting cannot move, the agency owns every account, the files were never provided or leaving means rebuilding from zero. Lock-in is not customer retention. It is the business model of providers who do not expect their work to survive comparison.

A clean handover process is not evidence that an agency expects you to leave. It is evidence that they respect that the website exists to serve your business, with the ownership and licensing of each piece agreed in writing rather than assumed. That is the standard we hold how we scope and build websites at Elev8d to and it is the standard this entire article hands you the tools to demand from anyone, us included. Should things ever change, the checklist for relaunching an existing website shows how much smoother that day is when the assets were yours all along.

FAQs

How do I choose a good web designer?

Evaluate in this order: their understanding of your business, their process, live portfolio work on mobile, written scope, ownership and handover arrangements, ongoing support, then price. The decision stack at the top of this article exists because most people run it backwards.

What should I ask before hiring a web designer?

The 15 questions in this guide. If you only ask three: who will actually do the work, what exactly is excluded from the quote and what happens if we stop working together.

How many web design quotes should I get?

Three to four, from the same written brief. Fewer gives you no comparison; more gives you noise.

Should I hire a freelancer or a web design agency?

Match the provider shape to the project shape. Tight scope and direct collaboration suit freelancers; broader strategy, bigger builds and multi skill work suit agencies. Neither label guarantees quality.

How do I compare website design quotes?

Put them in the same matrix and compare inclusions before dollars: discovery, design level, copy, SEO, redirects, tracking, QA, training, hosting, maintenance, ownership, handover. Quotes only become comparable once scope matches.

What does custom website design actually mean?

One of four levels: a template with content swapped, a customised theme or framework, bespoke UI and UX design or genuine custom software. Ask which level you are buying and check the price belongs to it.

Should my business own the website after it is built?

Your business should control the critical assets: domain, hosting arrangements it can move, administrator access and clearly agreed rights over design, code and content. Some components, like plugins and stock images, are licensed rather than owned by anyone you hire.

Who should own my domain name?

Your business, in an account you control, with the registrar, login recovery and renewal details known to you. This is the least negotiable item in the entire process.

Should I have admin access to my website?

Yes or a specific explained reason with a path to it. Discovering post launch that you cannot administer the site you paid for is a failure of the engagement, not a technicality.

What should be included in a web design contract?

Parties, scope, deliverables, responsibilities, timeline, revisions, payment schedule, variations, IP, licences, hosting, ongoing costs, termination, handover and disputes. Vague scope is the most common and most expensive omission.

Does a web designer own the copyright to my website?

Under Australian law, a contractor generally owns the IP they create unless the contract provides otherwise, which is exactly why the agreement should deal with ownership expressly. Get legal advice where it materially matters to your business.

What should happen when I stop working with my web designer?

A documented handover: access transferred, files provided as agreed, licences clarified, hosting migration path confirmed and any fees known in advance. Ask about all of it before you sign, not after you decide to leave.

Should SEO be included in website design?

The foundations should be: URL structure, page hierarchy, metadata, redirects on redesigns and analytics. Ongoing SEO is a separate engagement, but a site built without the foundations starts the race barefoot.

What are the biggest web designer red flags?

Guaranteed rankings, one paragraph proposals, unclear ownership, no access to your own accounts, no redirect plan on a redesign and pressure to sign before scope is discussed.

Do I need a local web designer or can I hire remotely?

Remote works well. Choose local when workshops, local market knowledge, onsite content work or face to face accountability genuinely add value to your project.

How do I know whether a website is really custom designed?

Ask to see the wireframes and design files from a past project and ask which parts of your build start from existing components. Genuine bespoke design leaves a paper trail; template work does not.

What ongoing website costs should I ask about?

Hosting, maintenance, plugin and theme licences, apps, domain renewals, support arrangements, security and backups. Ask for the expected annual total, in writing.

How much should a business website cost?

Australian small business websites commonly run from a few thousand dollars for template work to $15,000 to $40,000 and beyond for bespoke design and complex functionality. The number only means something next to its scope, which is the argument of this whole article.

Next steps: pick your path

Path 1: you are comparing proposals right now. Build the comparison matrix, run every proposal through the scorecard and ask each provider the exit question. Two hours of structure will do more for this decision than another week of gut feel.

Path 2: you are not ready to brief anyone yet. Start with the one page brief and the essentials list, then read our complete guide to getting a business website built properly so you walk into every conversation knowing how the process should run. Sharpening the brief is free; fixing the wrong build is not. And while you are preparing, forms that people finish instead of abandoning is worth a read, because the enquiry path is the part of the site that pays for everything else.

Path 3: you want us in the comparison. Good. Bring us your shortlist and your hardest questions and put us through every test in this article: the 15 questions, the ownership map, the exit question. If we are the right fit, the answers will show it and if we are not, you will have lost nothing but half an hour.

Sources and further reading

Business Queensland: IP created by contractors and consultants , the default ownership position, express contract provisions and the tools of trade licensing distinction.

Business.gov.au: intellectual property , plain English overview of IP types, including copyright over designs, writing and computer programs.

IP Australia: understanding IP , the national IP office's guidance on identifying and managing intellectual property assets.

ACCC: contracts and unfair contract terms , standard form contracts and the unfair terms protections carrying penalties since 9 November 2023.

ACCC compliance and enforcement priorities 2026-27 , including the focus on unfair contract terms and harmful cancellation practices such as automatic renewals and early termination fees.

General information only. Rules vary by situation, particularly around advertising claims, privacy, reviews and consumer law. If you're unsure about compliance, get professional advice.

AK
Written by

Ajay K.

Ajay K is the founder of Elev8d. A psychology grad turned marketer, he writes plain English guides on SEO, ads and web design. Reader, adrenaline seeker & self confessed introverted extrovert.