How to choose a web developer in Perth

The right web developer for a Perth small or medium business is the one who can deliver a site your customers can understand and your team can run — not the one with the flashiest homepage or the cheapest number on a one-page PDF.

This is vendor selection: brief, inspect, question, compare. It is not a cost breakdown or a timeline explainer. If you are still unsure whether you need design, development, or both, start with web design vs web development.

Clarify the job before you shortlist

Agencies and freelancers look interchangeable until you write down the actual problem.

Be specific about the outcome:

• New site for a business that has outgrown a builder
• Redesign of a site that looks dated or fails to generate enquiries
• Platform move with the current look largely intact
• Ecommerce store, or a marketing site that happens to sell a few products
• Ongoing care for a site someone else built

Those are different scopes. A vendor who treats them as the same package is guessing. Write one paragraph on what “good” looks like in enquiries — not “a modern website” — plus who will update content. You need enough that two quotes share the same assumptions, not a 40-page spec.

What “Perth” should mean in the shortlist

Local can be useful. It is not a substitute for competence.

Useful local signals: they will meet on-site when needed, they understand WA details (service areas, click-and-collect, regional shipping), and they do not pretend every suburb needs a thin page. Our locations exist because we service those areas — not as a doorway trick.

Weak local signals: a river stock photo, a keyword in the title, and no process you can follow. Ask how discovery, feedback and launch work. Our process is written down for that reason; expect the same from anyone you hire. If you are in Subiaco, Osborne Park or Fremantle, say so. Service-area honesty beats a claimed CBD office.

A shortlist of five evaluation criteria

Score each vendor on these. A pretty proposal that fails two of them is a no.

1. They restate your problem

A good first reply repeats what you sell, who should enquire, and what is broken. If the reply is a generic capabilities deck, they have not read you.

2. Stack honesty

WordPress, Webflow, Shopify, WooCommerce and custom builds solve different jobs. Someone who “does all platforms” without a recommendation is selling hours. Someone who only ever sells one platform will force-fit it. You want a recommendation with a reason, plus a clear “we would not use X here because…”.

See Webflow vs WordPress when the CMS is the fork, and the ecommerce platform guide when selling products is the job. Do not let a vendor skip that conversation.

3. Design and build are both owned

Ask who does information architecture, who does visual design, who develops, and who writes or refines key pages. If the answer is “the junior after you sign”, budget risk accordingly. Combined custom website design is common; split teams can work if the handoff is specified.

4. SEO is treated as structure, not magic

You want titles, headings, sensible URLs, internal links and (for local service businesses) Google Business Profile alignment — not a promise of ranking first. Ethical vendors will not guarantee positions.

5. Aftercare is explicit

Launch is not the end of the site. Plugins, CMS versions, certificates and content drift. Ask what maintenance looks like, what is in a care plan, and what is quoted separately. “Call us if it breaks” is not a plan.

Questions worth asking in a first meeting

Use a subset. You are testing how they think, not running an interrogation.

• What would you not include in v1, and why?
• How do you handle content if our team is slow?
• Who is the day-to-day contact, and what is a realistic response time?
• Can we see a project of similar complexity — not only visual polish? (Start from work when you evaluate us.)
• How do you protect URLs and redirects if pages change?
• What do we own at handover (hosting, CMS, design files, credentials)?
• How do you test forms, mobile layouts and accessibility before go-live?
• If we disagree on homepage messaging, how is that resolved?

Listen for trade-offs. “It depends, here is how we would decide” is more trustworthy than “yes to everything”.

Red flags that should slow you down

None of these is automatically fatal, but a cluster of them is.

• A price before a scope. A round number with no assumptions is not a quote; it is bait.
• Unlimited pages / unlimited revisions. Unlimited is how quality and timeline both collapse.
• Guaranteed rankings or “we will get you on page one”. Search does not work like that.
• No staging environment. Editing live from day one is how you ship half-finished pages.
• You do not get credentials. If they keep the keys, you do not own the site.
• Template gallery as the entire design process. Templates can be a starting point. They are not a substitute for mapping your offers.
• Hostility toward your current site. A competent redesign keeps what already converts. Scorched-earth rebuilds are sometimes needed; they should be justified.
• Vague “AI-powered SEO” with no page-level plan. Tools are fine. A plan is better.

For trades, check quote friction and service areas — the tradies website guide is a briefing companion, not a substitute for a vendor who has thought about mobile calls.

How to compare quotes without fooling yourself

Line up three things, not one number:

1. Inclusions: unique templates, integrations, content writing, stock vs supplied photography, training, redirects, analytics.
2. Exclusions: what will be a variation. If it is not written, assume it is extra.
3. Assumptions: content readiness, stakeholder count, who supplies copy.

A cheaper quote that assumes copy next week is not cheaper if you will not deliver it. Ask for a written scope. If you cannot explain it to a colleague, do not sign it.

Freelancer, specialist or full-service studio

All three can be the right answer.

• Freelancer: strong when the job is small, you can project-manage, and the person is clearly senior in the skill you need.
• Specialist (UX-only, Shopify-only, SEO-only): strong when you already have the other pieces. Weak when nobody owns the joins.
• Full-service studio: strong when you want one throat to choke for design, build and launch. You still need to check that “full-service” is not “mediocre at everything”.

Why us states how we work: one page, one job; no fake urgency; platform honesty. Use that as a template for whoever you hire.

A simple selection sequence

1. Write the job paragraph and success measure.
2. Shortlist three vendors who have done similar complexity.
3. Have one conversation each with the questions above.
4. Compare written scopes, not slide decks.
5. Check handover and maintenance in the same document as the build.
6. Choose the proposal you could defend to a sceptical business partner.

If you want that conversation with us, request a quote with your current URL, what you sell, and what is failing today. We will tell you if we are a fit — and if the job is really a redesign, a new build, or a smaller intervention.