What questions should I ask a web designer before hiring them? Ask what they will build and why, who does the work, what you will own at the end and what happens when plans change. Then pin down content and support. You should leave a discovery call with fewer assumptions than you brought in, not just a confident sales pitch.
Take this checklist to the meeting. You need the answers before you sign, even if you do not read every question aloud.
Start with the job the website needs to do
- What will you need to learn about my customers before you design anything? A designer should ask who needs the site, what those people need to know, and what action they should take. If the conversation jumps straight to colours and page layouts, bring it back to the business goal.
- How will you decide which pages we need? Ask them to explain how services, locations and customer questions shape the page plan. A Perth electrician with several service areas needs a different structure from a retailer selling products nationally. The page list should follow the job, not a standard package template.
- What would success look like after launch, and how would we measure it? Leads, bookings and qualified enquiries are more useful answers than “a modern look”. Ask how they plan to track contact forms and phone clicks, and which parts of that setup are in their scope.
Ask who is responsible for each part of the build
- Who will actually design and build my site? You may meet the founder and work with a different designer, developer or subcontractor. That is fine if you know who owns the work, who reviews it and whom you contact when something breaks.
- Who writes the copy and supplies the images? A site with finished layouts but empty pages is not ready to launch. Ask whether the quote includes planning and writing the words, editing your draft, uploading supplied material or none of those. The answer should be explicit for every page.
- How will the site work on a phone and with a keyboard? Ask for mobile layouts, readable type and a practical accessibility check, including forms and navigation. You do not need a technical lecture. You need to hear how they test the site before it goes live.
- What is included in the handover? Ask about your login, training, instructions for routine changes, and access to the domain and hosting accounts. A handover should let you operate your own site, even if you choose to keep the designer for support.
Put the uncomfortable questions on the table
- What is not included in the proposal? A clear answer might mention copy, photography, subscriptions or data entry. You are not trying to catch anyone out. You are trying to compare the full job rather than two totals that cover different work.
- What happens if I disagree with a design direction? Ask when you get to review the structure and visuals, how feedback is collected and how many rounds are included. It is easier to change direction at an agreed checkpoint than after every page is built.
- If the project stalls, what happens next? Ask what the designer needs from you, how they flag a delay and who adjusts the plan. A sensible schedule has named decisions and room for feedback. A launch date alone is not a project process.
- Which parts of the site and its accounts will I control? Ask for a plain explanation of access and ownership for the domain, hosting, content, design assets and any software licences. Ask what happens if you stop using the designer. Get the agreed answer into the proposal rather than relying on a conversation.
- What support can I expect once the site is live? Find out who handles faults, whether updates are included, and how you request help. A week of bug fixes and an ongoing support arrangement are different promises. Ask which one is on offer.
Listen to the answers, not just the promises
You are looking for a designer who can explain the trade-offs in your project without making every choice sound inevitable. They may challenge a page you thought you needed, or ask for better photos before proposing a design. That is useful. Someone who agrees to everything before learning about your customers has given you very little to judge.
Ask them to put the scope, responsibilities and decision points in writing. You can then compare proposals on the same basis. A short, specific explanation is more useful than a glossy presentation that avoids what happens on a difficult Tuesday.
Frequently asked questions
Should I send my questions before the meeting?
Yes, particularly if you have a complicated booking process or several service lines. It gives the designer time to bring the right person and a considered answer.
Is it a warning sign if the designer cannot answer immediately?
Not always. A careful “I need to check” is better than an invented certainty. Ask when they will come back to you and make the answer part of the written scope.
Can I ask for the proposed team members to join the call?
Yes. If a developer or copywriter will be doing substantial work, meeting them can clarify responsibilities and how feedback will move through the team.
What should I take away from a first conversation?
A clear next step, the information the designer needs from you and a timeline for a proposal. You do not need to commit on the call. Take the written scope away and read it.
Take the checklist into the room
Do not sign because the meeting went well. Sign when the written scope answers the hard questions. Planning a new site in Perth? Book a discovery call and bring your list.
