Start with what your website must do. Then ask each provider to explain the work, who'll do it and how you'll know it's finished. Compare live evidence, matching scope, full costs and the rights you keep. Pick the proposal that meets your essentials and has a delivery process you can check.
Follow a selection process you can check
Treat choosing a web designer as an evidence check. Five steps keep it honest:
Set a budget range early, even though prices only compare once the scope matches. A strong score or a lovely design can't fix an unclear exit or a missing business function. Our small business website guide covers the wider build journey.
Define the job before requesting quotes
Write one page that every provider receives. Keep it short and factual:
Business and customer: [who you serve]
Main website task: [enquiry, booking, sale or other]
Essential functions: [requirements]
Current assets and problems: [facts]
Content and approvals: [owners and dates]
Budget and preferred launch: [amount and timing]
Unresolved dependencies: [questions to investigate]
Separate requirements from solutions. "Customers can request a quote with photos" is a requirement. A particular plugin is only one way to meet it. A common mistake is writing the solution into the brief before anyone has looked at the problem.
Make your essentials specific to your business. Booking might be essential for a clinic and irrelevant for a builder. Advanced filtering matters for a big catalogue. A five page site rarely needs it. Our guide on how to plan a small business website helps you prepare the brief.
Check your own readiness
Name the decision maker and the people who supply content, approvals and product data. Add whoever controls access to your other systems. Agree review windows and who can approve a change. No provider can credibly promise a launch date without knowing you can supply those inputs.
Sometimes the right first purchase isn't a build. If the current site already does its main job, a repair or better content may be enough. If you're deciding how much to change, our redesign checklist covers the wider scope.
If a critical integration or data move can't be quoted yet, pay for a small discovery phase first. Agree its deliverables and rights. That way another provider can use the findings.
Choose the provider arrangement
The label on the door tells you less than the people doing the work. Each arrangement can suit the right job:
These categories overlap. A freelancer can have a strong network. An agency can rely on one person. So ask who will work on your project and which roles are reserved. Then ask what happens if someone becomes unavailable.
A DIY or hosted builder can suit a simple site the business can run itself. Count the owner's time honestly, check the platform's limits and know where you'd get help. A developer team suits custom functions and integrations. Confirm who owns the user experience, the copy and the commercial requirements.
Check the portfolio and its evidence
Review a small, relevant sample of live work, using the same method for each provider. Include a project with comparable functions as well as one from your industry. Record what each project actually proves:
Project and date: [URL and delivery date]
Supplier contribution: [work actually completed]
Current maintainer: [who changed it since]
Relevant customer task: [what you inspected]
Outcome evidence: [metric, period and source]
Limitations: [other changes and missing data]
Reference permission: [approved contact route]
Inspect the navigation, content and mobile layouts. Then try the keyboard, zoom and forms. Complete the customer task on a phone and a desktop, in realistic conditions. Don't send false enquiries to businesses that haven't agreed to a test.
Treat outcome claims with care. Ask for the baseline and the dates. Then ask how the metric was defined and where the numbers came from. More enquiries after a redesign may also reflect more ad spend, a busy season or a new offer.
Confidentiality can limit what a supplier shows. A permissioned anonymous case or a live demonstration can still help. A logo in a portfolio may stand for a small part of a bigger project.
A live fault deserves a question before an accusation. Someone else may have changed the site after handover. An attractive site can't prove code quality, security or genuine results on its own. Ask to see the editing and handover experience as well.
Ask what happens after the enquiry
A good provider asks about your customers and the services that earn you money. They'll also ask about demand, lead quality and sales follow up. Questions about colours and sites you like are fine design inputs. The worry is a proposal that never connects them to how you make money.
Ask what happens after an enquiry, booking or order. Then ask who handles it:
If ads will send people to the site, involve whoever runs them early. They should see the offer, landing page and measurement plan before the scope locks. That might be your own team or an outside agency such as Elev8d's Google Ads team. Our guide to ads that get clicks but no leads shows why a clear task matters.
For organic search, settle content and migration needs early. A designer needn't own every marketing service. Each handoff between roles still needs an owner.
Understand the four levels of custom work
"Custom" means different things to different providers. Start with the difference that matters most:
Most proposals sit somewhere on these four levels:
Level | What you're buying | Evidence to request |
|---|---|---|
Template with new content | Your content in an existing layout | Template, licence and edit limits |
Adapted theme or components | A proven base with new layouts | The reused base and the changes |
Bespoke design and user experience | Structure and design built for you | Requirements, designs and tests |
Custom software | Logic such as a customer portal | Architecture, tests and upkeep |
These levels describe different work. They aren't ranks of quality or fixed price bands. A project can mix them. Bespoke design doesn't mean rewriting the content management system (CMS). A well adapted system can meet the requirement for less.
An original looking interface doesn't prove the software underneath is custom. Ask where AI is used in the project and what human review follows. Check which of your information goes into outside tools. Get permission, confidentiality terms and a record of third party assets in writing.
Also ask what you'll actually receive:
wireframes or page plans
mobile and interaction states
source files, where the contract provides them
premium licences and who holds them
A different design method is fine if it gives you clear review and acceptance evidence. Polished design files alone don't prove professionalism.
Ask these 15 questions before you sign
Ask every provider the same 15 questions. Then ask for evidence to back each answer. Written evidence can be a scoped process, a redacted example or a demonstration. A rehearsed pitch doesn't prove this team has done the same work.
The first eight questions
1. Who will actually work on the website?
Named roles, the lead, subcontracted work and cover
2. What is the design and delivery process?
Milestones, reviews, inputs, tests and change handling
3. What does custom mean in this proposal?
The reused base, the design work and any custom logic
4. Which platform fits the requirements?
Reasons tied to editing, commerce, integrations and upkeep
5. Who supplies and approves the copy?
Page scope, drafts, editing, AI use and due dates
6. What exactly is included in SEO?
Structure, metadata, redirects, technical checks and access
7. How is mobile designed and tested?
Layouts, interaction states, devices and full tasks
8. What accessibility target is included?
Standard and level, scope, test method and fixes
The platform comparison tool helps structure the platform discussion. Our platform comparison guide covers the trade offs in detail. If WordPress is on the table, our guide on whether WordPress is still worth it covers that choice.
For copy, agree who writes, who edits and who approves each page. Our guide to writing website copy covers the writer's process.
Separate the SEO foundations built at launch from ongoing content and optimisation. Installing a plugin isn't the scope. Google says no one can guarantee a top ranking on Google. It also suggests bringing SEO in early when you redesign. Our guide to SEO for small business covers the wider organic strategy.
WCAG 2.2 AA is a sensible accessibility target to discuss. It still needs a defined scope and evaluation. A tool score, a nice palette or an "accessible" label can't verify it. W3C's Easy Checks give a first look, and W3C says they aren't definitive.
The tool is a guided manual self review. It isn't a scan or a conformance certificate. Our guide to website accessibility in Australia covers the standards and legal context.
The remaining seven questions
9. How will the finished site be tested?
Customer tasks, errors, devices, integrations and tracking
10. What rights will the business receive?
New work, existing material, licences and files
11. What admin access will we have?
Roles, restrictions, recovery and an editing demo
12. Who controls the domain and hosting?
Registrant details, recovery access, billing and renewals
13. What happens if the relationship ends?
Handover scope, exports, support, fees and licences
14. What ongoing costs and duties remain?
Renewals, required services, optional care and owner tasks
15. What is excluded or assumed?
Omissions, limits, dependencies and change approval
Don't ask for a provider's master server or other clients' data. Ask for the rights, roles and continuity your own site needs. A hosted platform or managed service may offer a practical equivalent to a server login.
Ask to see a sample handover register and an anonymised test report. These show how the provider works. The signed scope for your project is still the commitment that counts.
For security, use named accounts with the right permissions. During selection, share only what the review needs. Google's same guidance suggests read access only to Search Console for an audit. Keep passwords, keys and recovery codes out of ordinary documents.
Compare equivalent quotes and full costs
Line up the same scope before you compare prices. Mark each item Included, Excluded, Client supplies or Unresolved, with the quantity beside it. A tick without a quantity is weak evidence. A common mistake is comparing headline prices before the scopes match.
Separate template counts from published page counts. Then spell out volumes where they matter, such as products, redirects and revision rounds. Don't accept "top 50 redirects" without an inventory of what happens to every other useful URL.
Vague wording | Testable scope |
|---|---|
A modern seven page website | The seven pages, reusable templates and who fills each |
Copy and SEO included | Who writes each page, the review steps and SEO deliverables |
Two revision rounds | What a round covers and how new requests are handled |
CRM integration | The system, fields, error handling, tests and support |
Redirects included | A URL inventory with a tested decision for each |
CRM integration included
Name the CRM, fields, error handling, test evidence, operator and support scope
That's example wording, not a contract clause. Price only means something once the scope matches. Here's an example comparison, in AUD excluding GST. These aren't our quotes or market rates:
Cost item | Provider A | Provider B |
|---|---|---|
Initial build quote | $7,500 | $9,500 |
Copy to match scope | $1,800 | ✓ Included |
Migration to match scope | $900 | ✓ Included |
Training to match scope | $300 | ✓ Included |
Ongoing service, 24 months | $100 × 24 = $2,400 | $125 × 24 = $3,000 |
Comparable initial cost | $10,500 | $9,500 |
Total over 24 months | $12,900 | $12,500 |
Provider A's lower headline ends up $400 dearer over the period once the missing work is added. That doesn't prove B is the better supplier. Check equivalence, quality and the essentials first. The initial cost and the ongoing amount already make the total. Don't add the subtotal again.
Count your own staff time and content production too. So do payment fees and renewals. Keep cash invoices separate from any value you put on internal time. Don't mix currencies, GST bases or support scopes without explaining the adjustment.
Our guide to website costs gives the full budget picture. The website cost estimator gives a starting scenario, not a quote.
Agree rights, access and ownership
"You own everything" is too broad on its own. Owning your website covers four separate things. There are rights in the work created and permission to use licensed material. Then there's control of the accounts and the practical ability to run or move the site.
The map shows who controls what. It's an example, so match it to your real contract.
Register the domain correctly
For a com.au domain, the business should be the registrant, the holder named on the licence. The domain regulator, auDA, lets someone register it for you with your explicit written permission, using your details. Those details decide who holds the licence. A domain is a licence for a set term. It isn't ownership of the name or brand.
Confirm who gets renewal alerts and who manages DNS, the records that point the domain at your site. A common mistake is letting a developer register the domain under their own details.
Settle intellectual property and licences
By default, a contractor generally keeps the IP they create. Business Queensland says a business must expressly provide for ownership in the agreement. IP Australia also advises a written contract that says who owns the IP. So specify which new work is assigned or licensed, when and for what uses.
Contractors often keep their own tools and license them to you. Third party themes, plugins, images and fonts stay licensed too. Paying for a build doesn't transfer ownership of WordPress, Shopify or a supplier's own software. Check the supplier can grant the rights it promises, including any subcontractor's work.
Record each item before signing:
Asset or service | Record before signing |
|---|---|
Domain and DNS | Registrant, registrar, admin, recovery and renewal owner |
Hosting or hosted platform | Account rights, operator, billing and continuity |
CMS and routine edits | Roles, training and a demonstrated editing route |
New design, code and copy | Assignment or licence, timing, scope and files |
Third party components | Licence holder, permitted use, renewal and exit terms |
Measurement and integrations | Business access, identifiers and authorised users |
Item: [code, design, copy, image or software]
Creator or supplier: [name]
Arrangement: [assignment or licence]
Permitted use: [scope]
Effective date or condition: [agreed event]
Renewal and transfer: [cost and restrictions]
Evidence: [contract or licence reference]
That's a procurement record. It isn't a legal finding or a standard contract. Get advice on any material rights question.
With agency managed hosting, you may not get the master server account. You still need a usable route to your own site, data and agreed rights. Our hosting guide covers hosting responsibilities and exit questions.
Specify the handover before work starts
Agree the handover list at the start and keep it current through the build. Track each action with an owner:
Confirm domain and DNS control
Provide editing access
Confirm hosting or platform rights
Hand over files and documents
Transfer measurement access
Document licences and integrations
Demonstrate recovery
Train staff and hand over support
Then have your own editor log in and change a routine item. Ask them to find the documentation and show where an enquiry lands. A folder of instructions is less useful if the intended operator can't use it. Record the date and any open issue, and don't mark handover done because a link was sent.
For measurement, our Search Console guide covers business access to search data. Our GA4 guide covers analytics. Our guide to backing up your website explains what a usable backup includes.
Keep the project recoverable
Ask for progress documentation during a significant build. Then a stalled project stays recoverable. The agreement should cover partial and paid work. Licences and transition help belong in it too. Don't assume access or rights transfer automatically on termination.
Clarify subcontractors, absence cover and access recovery before the build starts. Confirm how confidential inputs are handled, including any use of AI tools. Exits then come in two kinds:
Changing developer on Shopify can be simple without moving platform. Moving a working site elsewhere is a separate project. Webflow's code export, for example, leaves out hosted CMS content, Ecommerce and form processing.
Protect backups and new customer records during a transition. Revoke old access only after the new party confirms everything works. Don't cancel hosting or remove the only recovery contact first. Agree how the old provider deletes retained copies and personal information. Our guide to transferring a website to a new developer covers the detail.
Agree the contract and acceptance tests
A clear agreement covers these, in plain language:
the contracting entity and the named scope
client and supplier responsibilities
dates, dependencies and review points
payment and how changes get approved
IP, licences and confidentiality
support, termination and disputes
Write verbal promises down to reduce confusion. That doesn't make unwritten promises meaningless. The ACCC notes a contract can exist without a written document.
Approving the design isn't accepting the whole website. For each important function, agree the expected result and the test conditions. Then agree the evidence and who signs it off:
Requirement: [business task]
Conditions: [device, role and test setup]
Expected outcome: [observable result]
Evidence: [record or approved demonstration]
Defect and severity: [if the test fails]
Owner and retest: [person and date]
Acceptance decision: [approved or unresolved]
Typical items look like this:
Acceptance item | Observable evidence |
|---|---|
Enquiry or booking | A test reaches the right system, person and reply route |
Checkout, if relevant | Paid and failed tests, orders and stock work in test mode |
Client editing | Your editor completes routine tasks without a developer |
Accessible customer path | Agreed keyboard and assistive technology tasks pass |
Migration | Old URLs and assets reach their agreed destinations |
Measurement | Agreed outcomes record once, with privacy handled |
Define how defects get reported, retested and classified. A minor cosmetic issue and a lost order need different decisions. A subjective "looks good" sign off can't prove the site works. Our enquiry form design guide covers forms.
Keep a defect fixing period separate from maintenance and new features. Agree what it covers, without assuming a standard warranty length. Statutory rights may still apply.
Tie payments to deliverables
No deposit percentage or milestone structure is right for everyone. Tie each payment to a deliverable you can understand. Then cover taxes, cancellation and what happens during a pause.
Confirm the contracting entity before you pay. If payment details change, call the supplier on a number you already know. The ACSC's small business guide recommends exactly that, plus a formal process for payment changes.
Check for unfair terms
Unfair contract term protections apply to relevant standard form contracts. They cover small businesses with fewer than 100 employees or turnover under $10 million. That applies to contracts made, renewed or varied since 9 November 2023. Only courts make the final call on whether a term is unfair.
The ACCC's 2026 to 2027 priorities include harmful cancellation practices, such as automatic renewals and early termination fees. That's an enforcement focus. It doesn't ban every renewal. Review unclear, one sided or significant terms before you sign.
Investigate warning signs and references
Treat each warning sign as a prompt for evidence. The first eight concern scope and rights:
Ranking promises
Ask for realistic scope, evidence and limits
Platform chosen before discovery
Ask for reasons tied to your requirements
Custom is undefined
Identify the reused base and the bespoke work
A vague proposal
Request quantities, deliverables and acceptance tests
Unclear rights
Agree assignment, licences and access in writing
No usable account access
Settle business roles and recovery arrangements
Hidden ongoing costs
Request a full renewal and duties schedule
Discovery covers looks only
Discuss customers, tasks, content and follow up
The next eight concern delivery and pressure:
Portfolio sites all look alike
Ask what's reused and whether it fits your scope
No mobile evidence or test method
Request representative task and device checks
SEO means one plugin
List the actual search work and its limits
No URL plan for a redesign
Inventory the site and agree URL decisions
No launch recovery plan
Define restoration and protection of new records
Handover avoided
Specify deliverables, access, training and exit
Pressure to sign today
Ask for written terms and time to review them
Bank details changed by email
Verify on a known number before paying
Tell an open question from a refusal before you react:
A small supplier can run a sound process with simple documents. A template isn't automatically bad. A real capacity limit isn't fake urgency. What matters is whether each material requirement gets resolved.
Mapping redirects can't guarantee every ranking holds either. Keep relevant pages and content, test the migration and monitor the results. Our migration checklist covers the process.
Use reviews and location sensibly
Reviews are useful for specific delivery evidence, such as communication and how scope changes were handled. A star average isn't a technical assessment. Ask for a reference relevant to the proposed work. Find out what the referee actually experienced, without asking for confidential customer data.
Ask how a difficult project was handled. Look for a coherent explanation and evidence it was resolved. Public reviews are a selective sample. One bad review proves little either way.
Local collaboration helps with workshops, photography and onsite knowledge. Remote teams can deliver well too. Compare communication and time zone overlap. Onsite needs and support cover matter as well.
A Melbourne address isn't proof of better work for every Australian business. Industry pages help with sector needs, such as web design for trades and professional services websites.
Build a shortlist and settle the essentials
Three or four suitable providers is a manageable start. That's a practical number, not a statistical rule. Send each the same honest brief. Don't hide a requirement to test them. Mark uncertainties and ask each one to explain their assumptions.
Settle the critical requirements before you score anything. Record Pass, Fail or Unresolved for each, with evidence:
An unresolved answer isn't a pass. A discount can't fix a failed critical requirement. If no proposal fits, revise the scope or timing. Or buy paid discovery for the uncertain part, or keep looking. Don't just pick the middle price.
Before deciding, send each provider the same clarification request:
Please confirm [missing requirement] and the evidence that it's included.
What will you deliver, who is responsible and how will we accept it?
Please also confirm the full initial and ongoing cost and our rights and access.
Explain the handover process if the engagement ends.
Record any assumptions or exclusions in the revised proposal.
Use the scorecard after the essentials pass
Score only after the essentials pass. These ten categories and weights are our editorial starting point, not research findings. Adjust the weights to your business before you see any proposal. Then apply the same method to every provider.
Here are example scores for two imaginary providers:
Category | Weight | A score | B score |
|---|---|---|---|
Business understanding | 20% | 4 | 5 |
Process and strategy | 15% | 4 | 5 |
Live portfolio quality | 10% | 4 | 4 |
Mobile and UX thinking | 10% | 4 | 4 |
SEO and technical foundations | 10% | 4 | 4 |
Scope clarity | 10% | 4 | 4 |
Ownership and handover | 10% | 4 | 1 |
Communication | 5% | 4 | 5 |
Ongoing support | 5% | 4 | 4 |
Price against value | 5% | 3 | 5 |
Score 1 for a documented weak fit and 3 for an adequate one. Score 5 for a strong, evidenced fit, and use 2 and 4 in between. Missing information stays Unresolved. It never gets a made up zero, an average or a hopeful score. Record why you chose each number.
In this example, B's proposal leaves the domain and hosting with the agency. That's the 1 for ownership and handover. It fails an essential. B can't be chosen until that's fixed, even though it scores 83 against A's 79.
Choose Provider B because 83 beats 79
Resolve B's rights and access issue first, then compare the remaining evidence
A isn't appointed automatically either. It still has to pass its own essentials and contract check.
Watch for false precision. Change the weights a little and see whether the order holds. Lift ownership and handover to 20% and drop business understanding to 10%. B then falls to 75. A stays at 79.
The scorecard structures the discussion. It doesn't certify a supplier or guarantee a good website.
Check the timeline and dependencies
Our web design page quotes 4 to 8 weeks for its website packages. Our landing pages are quoted at about a week. That's our own service expectation, not an industry benchmark. Scope changes it, and so does how quickly content and feedback come back.
Phases often overlap. Ask what you supply at each stage and which approval releases the next:
A simple site can move faster than an integration heavy build. A small page count can still hide difficult functions.
Ask for the earliest credible start date and who owns each dependency. Ask what happens when your input runs late. For stores, include payment and shipping setup. Include external system access, licence purchases and data migration too. Separate calendar time from the provider's production hours.
Agree a variation process before anything changes. Each request should record:
the reason for the change
the scope impact
the price and timeline
who decides
Fixing an agreed defect shouldn't attract a change fee.
Before launch, name who handles updates and backups. Customer messages and incidents too. Turning down a care plan is fine, as long as someone can run the site. Agree an observation period after launch and an escalation contact. Our guide to website maintenance costs covers the ongoing side.
What we recommend at Elev8d
Write the brief, check live evidence and settle the essentials before you score anyone. Then put scope, rights, acceptance and the exit in writing. Don't get taken for a ride by a polished pitch or a ranking promise.
Here's how we answer the same 15 questions. Hold us to the same standard, and confirm the specifics in your own proposal:
Who works on it: You deal directly with the designers and developers building your site. Our own team designs and builds.
Process: We plan and wireframe first, then design and build. Testing, launch and handover follow.
Custom work: Key pages start as wireframes planned around how your customers buy. Any reused components should be named in your scope.
Platform: It follows your requirements. We recommend WordPress for most business sites and Shopify for online stores. Custom builds use React, Next.js or Laravel.
Copy: If your copy isn't ready, we can help write it from a conversation about your business. Copy is quoted per project. Some of our specials include it, so ask when you enquire.
SEO: Clean structure, proper markup and permanent (301) redirect mapping for the pages that bring in visitors. Ongoing work is separate, through our SEO team.
Mobile: Mobile first builds, tested on phones, tablets and browsers.
Accessibility: Our review covers colour contrast, image descriptions, keyboard use and form labels. A formal standard such as WCAG 2.2 AA gets scoped at the start.
Testing: We test on phones, tablets and browsers before launch. Forms, speed and tracking get checked too.
Rights: You own your site, your code and your hosting. Third party themes, plugins and fonts stay under their own licences.
Access: You get an easy to use CMS, with training at handover.
Domain and hosting: Both are in your name from day one.
Exit: There's no lock in contract. Your accounts stay in your name. You keep the handover notes and training. A Shopify store stays on Shopify unless you rebuild it elsewhere.
Ongoing costs: Hosting, domain and any care plan sit outside the build price. They're set out before you sign.
Exclusions: Paid licences, extra pages and third party fees sit outside the build.
Our web design service page sets out the packages.
Our free audit is a short, prioritised read on what to fix first.
Frequently asked questions
How do I choose the best web designer?
Match each proposal to your requirements. Then check the evidence, the scope and the rights you'd keep. Delivery and full cost come next. There's no universal best provider.
Should I hire a freelancer or an agency?
Compare capability, availability and responsibility. The label alone tells you little.
How many quotes should I get?
Three or four is manageable. Consistent inputs and a suitable shortlist matter more than the count.
How can I tell what custom includes?
Ask for the reused base, the specific design or software work and the files you'll receive. The four levels above help you compare.
Should I own my website?
Separate the questions. Ask about rights in new work and licensed parts. Then ask about account control and continuity.
Can a developer register my domain?
Yes, with your explicit written permission and your business's details. Keep control and recovery access in the business.
Should SEO be included in a website build?
The launch foundations should be. Ongoing SEO is separate work. No one can promise rankings.
Should I have administrator access?
Agree the roles and recovery you need to edit and transfer the site. Any restrictions should be explained.
Do I need a local web designer?
Choose local when workshops or onsite work add value. Otherwise, check how remote delivery and support work.
How long should a website build take?
Scope and dependencies set the schedule, along with availability and review time. A quoted range needs its conditions.
What if the provider stops responding?
Use the agreed escalation, access and partial work terms. Get advice for a contract dispute.
What costs continue after launch?
Hosting, domains and licences continue. So do maintenance and any support plan. Confirm which are required and which are optional.
Next steps
Write the brief
Use the brief template above and send the same version to every provider.
Match the proposals
Line up scope, exclusions and two year costs before comparing prices.
Close the critical gaps
Send the clarification request and record Pass, Fail or Unresolved for each essential.
Arrange a scoped review
If you'd like a second opinion on a proposal, ask us for a scoped review.
