I can usually tell in the first meeting how a website project is going to go, and it has nothing to do with the budget or how big the business is. It comes down to whether the owner showed up prepared. The ones who arrive with a clear goal, their real content, and a couple of example sites they like tend to launch on time and close to budget. The ones who don't tend to stall. And a stalled project always costs more than a moving one.
Hiring a web designer is not the first step. Getting ready to hire one is. The prep is not complicated and none of it requires you to be technical, but almost nobody does it, and the gap between a client who did and a client who didn't gets measured in weeks and dollars. Here is what to have in hand before you start calling designers.
What do you want the site to actually do?
Start here, because every other decision hangs off it. "I need a website" is not a goal. "I need the site to get more people to call for a quote" is. So is "I need to take bookings without playing phone tag" or "I need to sell a dozen products online." A site built to get calls is a different machine than a site built to take bookings, which is different again from a store.
You do not need to know how to build any of it. You need to know what the one job is. When a designer asks what success looks like six months after launch, you should have an answer that is not "it looks nice." Pin the primary goal, add a secondary one if you have it, and let the rest stay negotiable. A good designer will pull this out of you anyway, which is a process I have written about in why discovery comes first. The more of it you bring yourself, the faster and cheaper that part goes.
What content do you need to gather?
Content is almost always what holds a project up. Have your words and your pictures ready before you start, or at least the raw facts to build them from. There are three pieces:
Real copy, or the raw facts. A designer can write or polish your words, but they cannot invent your service list, your prices, your hours, or your story. Even rough bullet points and a brain-dump beat an empty page. Photos of your actual work, not stock. This is the big one. A roofer's real roofs, a baker's real cakes, your actual dining room. Stock photos of someone else's business read as fake, and every visitor can feel it. Your logo and brand files. The logo in a proper file, your colours if you have them set, any fonts. If all you have is the logo screenshotted off your old site, say so early, because rebuilding it from scratch costs time.
Do you know who controls your domain and hosting?
Before launch day, someone has to log in to the place your domain and hosting live. If that someone is a web guy you lost touch with in 2019, find out now, not the week you go live. Your domain name (the yourbusiness.com part) is registered somewhere, and your site files sit on a host. Pointing the domain at a new site means editing DNS records, and that needs the login.
I have watched launches stall for two weeks because nobody could remember who set up the domain. Track down the accounts, or at the very least the email address they are attached to and who holds the password. Ideally both are registered under your own business email, not a former developer's personal account. If a past developer controls everything, that is worth knowing before you sign with someone new. It is also one of the things I would check before you even pick a designer, which ties into how to choose a web designer in the first place.
Who is the one person making the calls?
Pick a single decision-maker. Projects with one clear point person move. Projects run by committee crawl. When four people weigh in and nobody has final say, every choice takes a week and half of them get reversed the week after. Design by committee is where scope creep lives.
Choose one person who can approve copy, sign off on a design direction, and answer a question within a day or two. Everyone else can have input, but one person owns the decision. If that person is you, block out the time honestly. A designer waiting on your feedback is a project standing still, and you are usually paying for the calendar either way.
What helps a designer quote your project accurately?
Three things: a budget range, any hard deadline, and two or three example sites you like. You do not have to open with a number, but you should know your own ceiling, and you should tell the designer about any date that cannot move (a grand opening, a season, a trade show). A vague timeline with a secret hard deadline underneath is how projects blow up in the last week.
The example sites do more work than people expect. Send two or three you like, and one line each on why: "I like how fast this one feels," "this booking flow is exactly what I want," "these photos are the vibe." That tells a designer more about your taste and your target than a page of description. If you are not sure what a project like yours should cost before you set that range, I laid out honest numbers in what a website costs in Ontario.
| Have this ready | Why it matters |
|---|---|
| The one job the site must do | Every design and build decision hangs off it; without it you are guessing |
| Real copy, or the raw facts | A designer can polish words but cannot invent your services, prices, or story |
| Photos of your actual work | Stock photos read as fake; real ones build trust and sell the work |
| Logo and brand files | Rebuilding a logo from a screenshot wastes time and money |
| 2-3 example sites you like | Shows the designer your taste and what "done right" looks like to you |
| Domain and hosting logins | Launch day needs them; a lost account stalls the whole project |
| One decision-maker | Committees cause delays and reversals; one owner keeps it moving |
| Budget range and any hard deadline | Lets a designer scope honestly and tell you what fits |
What happens if you show up unprepared?
Nothing dramatic, which is the trap. The work simply slows down. The designer builds what they can, then waits on your copy, then waits on your logo, then waits on a decision nobody is empowered to make. Every gap in your prep becomes a gap in the schedule, and gaps in the schedule are where budgets quietly climb. Scope creep sneaks in because a project with no fixed goal has no natural finish line.
The fix is boring and it works. Make a few decisions and gather a few files before the meter starts running. Do it, and the build is faster, the quote is more accurate, and the finished site actually does the job you hired it for. Skip it, and you pay for the delay one way or another.
If you are getting ready to commission a site and want a straight read on what you actually need before you start, get in touch. I would rather help you show up prepared than watch a good project stall over a missing logo file.