Questions to ask a web designer on your first call
Start with who is actually going to build it
The call is on your calendar in twenty minutes and the note app on your phone is still blank. Start with the first question, the one people forget because it feels obvious: who on the team will be doing the design and the build. Will that person be the one you talk to during the project?
Or does the work get passed to someone else once the sale is made? A studio that splits work across several people isn't automatically a problem. Not knowing who's assigned to your project is. If the answer stays vague, ask it a second way.
"When I have a question in week two, who answers?" A concrete name beats a company pronoun every time. Write the name down. You'll want it later, once the project is under way and you need to know exactly who to email.
This question matters more once you're weighing more than one option. DIY, freelancer, agency, and template each answer it differently, and the full picture of all four builder options is worth a read before you're deep into any one call.
Ask what the process looks like from start to finish
Get them to walk the whole project in order: discovery, design, revisions, build, review, launch. Listen for specifics, not polish. A real process has named stages and a rough sense of what happens inside each one. A designer who can describe their own steps has run this before.
A vague answer here is a preview of a vague project. If they can't lay out their own process out loud, you'll be inventing the structure together mid-build. You're the one paying for that improvisation, in delays and in frustration.
Ask one follow-up question too: what do they need from you, and by when. A designer who can name your homework knows where projects actually stall, because they've watched it happen before on someone else's project. Some common examples worth listening for:
- Website copy, ready before design starts
- Photos or a plan for stock images
- Login access to your current hosting or domain
- A short list of competitor sites you like or don't
Nail down how you'll hear from them, and on what schedule
Email, a shared document, a project tool, text messages - the channel matters less than agreeing on it now, before you're three weeks in and wondering why nobody's replied. Ask what a normal week of contact looks like on their end.
Ask what happens if you go quiet for a few days, and what happens if they do. Neither answer needs to be dramatic. You're just trying to learn the shape of the relationship before you're inside it.
Silence after money changes hands is a complaint that comes up again and again from people who've been burned before. Name it directly on the call. "If I don't hear from you for a stretch, is that normal, or should I be worried?" The answer matters less than how quickly and how comfortably it comes.
Some designers work solo and set expectations up front: a day or two turnaround, batched replies at set times. Others promise same-day contact and mean it. Neither shape is wrong. What matters is that the shape gets named before you're inside the project wondering which one you signed up for.
Separate what's included after launch from what costs extra
This question gets skipped because the call is about getting the site built, not about what happens once it's live. But launch day isn't the finish line. It's the start of a different phase, priced as its own line item, separate from the build itself.
Ask plainly: once the site goes live, what's included, and what starts costing money on top. Push for specifics instead of accepting a reassuring but empty answer. A few things worth naming out loud on the call:
- A small text or photo swap
- A new page added months later
- Plugin and security updates
- A contact form that suddenly stops working
What to expect once the project is done is a decision worth making early. It's a much easier decision once you've already asked this question on the first call, rather than discovering the answer by surprise well after launch.
Some designers bundle a short window of free fixes right after launch, then move to a paid arrangement. Others charge from day one for anything beyond the original build. Neither approach is wrong on its own. What matters is hearing which one you're getting before you need it.
Ask to see a sample contract before you commit to anything
You don't need to read every clause on the call itself. You need to confirm a contract exists, and you need to see it before any deposit moves. "Can you send me a sample agreement to look over?" is a completely ordinary ask.
How someone reacts to it tells you something real. A designer used to this question sends the document without friction. One who hedges, stalls, or claims contracts "aren't really necessary for something this size" has just told you something worth hearing before you go any further.
What the contract they show you should actually contain is worth knowing ahead of time, so you recognize what's missing rather than only what's there on the page in front of you.
Write your answers down right after the call, while the tone is still fresh in your memory. Note not just what was said but how comfortably it came out, since hesitation is its own kind of answer.
One call rarely settles everything on its own, and this list is one piece of the broader vetting process this call is part of. Putting words to what you actually want before you even dial in makes the whole call sharper, since a designer can only answer questions you've actually thought through ahead of time.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go