A web designer decides how your website should look and work for the people using it. They turn your business goals into page layouts, navigation, content hierarchy and visual details, then work with a developer or a website-building platform to make those decisions real. For a Perth business, the useful question is not whether someone calls themselves a designer. It is what they will actually deliver.
The job starts before a page is drawn
A good designer does not open a design tool and start choosing colours. First, they need to know who will visit the site, what those people need, and what you want them to do. A plumber might need emergency callers to find a phone number immediately. A clinic might need patients to understand services, locations and booking options without calling reception.
That early work can include a discovery session, a review of your current site, a look at competitor sites and a page plan. You should come away with a clear view of the site’s purpose and scope. If the first conversation is only about fonts and a hero image, the real decisions are still waiting.
What a web designer actually produces
Site structure and user journeys
The designer maps the pages and their relationships: where the services sit, how visitors move from a general page to a specific answer, and what happens when they are ready to enquire. This often becomes a sitemap and a set of simple wireframes. A wireframe is the skeleton of a page, not a finished visual. It lets you agree on content order and calls to action before anyone argues about shade of blue.
Visual designs and a reusable system
Once the structure works, the designer applies typography, spacing, imagery and colour. The output may be a set of page designs or a reusable library of headings, buttons, cards and form styles. The second approach matters as a site grows. New service pages should look like they belong to the same business, even if they are built months later.
A designer should also show how important layouts behave on a phone. Shrinking a desktop mock-up is not mobile design. Menus, forms and contact buttons need to make sense when someone is standing on a job site with one hand free.
Specifications and handover
Someone has to turn the approved design into a working website. The designer may supply the source files, image selections, layout rules and notes on interactions for a developer. On a smaller project, the same person may build the pages in WordPress or another platform. Ask which handover files you receive, who can edit them later and whether the build is included in the quoted scope.
Designer, developer and copywriter: who does what?
The lines overlap, but the responsibilities are different. The designer shapes the experience and presentation. A developer builds and tests the functionality, from templates and forms to integrations and more complex features. A copywriter works out what each page should say. Search specialists may guide the topics and page structure so the finished site answers real searches.
One person can cover more than one role. Plenty of capable independent designers can build an excellent small business site too. The danger is assuming that a job title guarantees every skill. If your quote says “website design”, check whether it also includes the build, written content, mobile testing, basic search setup and launch support. Those are separate pieces of work unless the scope says otherwise.
What the process should look like
Most projects move through discovery, page planning, design, build, testing and launch. The stages may overlap, but each should have a clear decision point. You approve the site structure before detailed design. You review the design before it is built across every page. You test the working site before it goes live.
Ask how feedback is collected and how many revision rounds are included. One consolidated set of comments is usually easier to action than a string of individual requests from different people. You should also know who is supplying photos, logos, service information and legal text, and when each item is due. A designer cannot finish a page whose main message has not been agreed.
During testing, try the site as a customer would. Can you find the service you need? Does the enquiry form submit? Is the phone number easy to tap? Ask someone outside the project to try it on their own phone. Familiarity hides awkward paths.
What to ask for in the brief and the handover
Before signing, ask for a list of deliverables rather than a general promise of a “modern website”. It might name the sitemap, wireframes, designs for key page types, mobile layouts, the working build, form testing and training. It should also identify the platform and say who will maintain it after launch.
Check whether the final handover includes admin access, any editable design files, image licences and a short guide to changing routine content. Some businesses need only the ability to update opening hours and team profiles. Others will add service pages regularly. The handover should fit the way you plan to use the site, not just the day it launches.
For a fuller view of how these stages fit together, see our website design and development service. It shows why design decisions and build decisions belong in the same conversation.
Frequently asked questions
Will the designer write all the words on my site?
Not necessarily. Some designers offer copywriting, while others need you to supply approved text. Ask who owns the writing and editing before the design starts, because the amount and shape of the copy affect every layout.
Do I need to supply professional photographs?
Real photographs help visitors recognise the people and work behind your business, but a professional shoot is not always required. Discuss what images you already own, whether they are suitable for web use, and who will source any replacements.
How many design concepts should I expect?
There is no universal number. A focused process may present one well-reasoned direction and revise it with your feedback; another may show alternatives. What matters is whether the quote explains the concept and revision scope before work begins.
Can I give feedback once the site is built?
Yes, but late changes to an approved layout may take more work than changes to a wireframe. Agree on review points during planning and design, then use the built-site review to catch practical issues rather than restart the visual direction.
Make the scope visible
When you can name the decisions, files and working pages you will receive, you can judge a proposal properly. If you are planning a new Perth business site, book a discovery call. Bring the outcome you need and the questions your current site leaves unanswered. We can help turn that into a buildable brief.
