What to put together before you meet a web designer

The page and feature list, written down before anybody quotes it

The calendar notification is sitting on your screen: a first call with a web designer, Thursday, 10 a.m. Before it arrives, write out a rough list, even if it's messy. What pages does the site need - home, about, services, contact, maybe a blog? What does it need to do beyond display information: a booking calendar, a quote request form, a way to take payment?

A designer can ask these questions live on the call, but every one you've already answered for yourself is a question the meeting doesn't have to spend time on. That leaves more room for the parts only a real conversation can actually surface.

You don't need final answers. A rough list in a notes app, six or eight bullet points, gets you most of the way there. Even a wrong guess is more useful to a designer than a blank page, because a wrong guess still tells them something about how you're picturing the site.

Logo files, photographs, and who holds the originals

Track down your logo file before the meeting, in whatever format you actually have it. Even a low-resolution version pulled off an old business card tells a designer something useful. If you don't have a usable file at all, say so early, since it changes what the first phase of work looks like.

Same with photographs. Do you have real photos of your shop, your team, your product, or is the plan to use stock imagery instead? Knowing the honest answer before the call saves a round trip later in the project.

If someone else designed your current logo, find out who, and whether the original files still exist anywhere. That one question alone heads off a scramble weeks into the build. It's also worth noting any brand colors or fonts you already use on business cards or signage, even loosely, since those become a starting point rather than a blank guess.

What you already have written and what still has to be written

Gather anything you've already written about your business: an old brochure, a bio from a directory listing, even a rough email you once sent a customer explaining what you do. None of it needs to be polished. It's raw material a designer or a writer can shape into something usable.

Then be honest with yourself about what doesn't exist yet. An About page, service descriptions, a list of frequently asked questions - if none of that is written anywhere, say so plainly rather than assuming it will appear on its own partway through the build.

A short paragraph on who you serve and what makes you different is worth writing before the call too. It doesn't need polish. It just needs to exist somewhere other than in your head.

The domain, the current site, and who controls those accounts

Find your domain registrar login before the meeting, if you already have one. If you're not sure who registered your domain or where that account lives, say that too. It's a common gap, and naming it early beats pretending otherwise.

If you already have a website, note who hosts it and who currently has admin access to it. A designer will need this information eventually. Bringing it to the first meeting instead of the third one saves a full week of back-and-forth email later.

If a previous designer or a relative set any of this up years ago, jot down whatever you remember, even fragments. A half-remembered username is still a faster starting point than none at all.

Two or three sites you like, and what you like about each

Before the meeting, spend twenty minutes finding two or three websites - in your industry or outside it - that you genuinely like. Then write down why, specifically. Not "it looks clean," but which part exactly: the color choices, the photography, how the navigation is laid out, how a competitor describes what they actually do.

Specific examples do more work in a first conversation than any adjective you could reach for on your own. A designer can look at a site you point to and immediately understand something that would otherwise take ten minutes to describe out loud.

This works in reverse too. A site you actively dislike, and a sentence on why, tells a designer just as much as one you admire. Both narrow the range fast.

The date you are working to and the number you are working to

Say your real timeline out loud, even if it's flexible. A launch tied to a specific event is different from a soft goal of sometime this year, and a designer plans differently around each one.

Same with budget. Saying the number out loud is its own small hurdle worth clearing early, because a vague answer here tends to produce a vague quote in return.

Bringing a rough list like this to a first meeting doesn't make you look like you've done someone else's homework. It's the fastest way to get a specific answer instead of a generic pitch.

What to ask once you are in the room is the natural next step once you've walked in with something in hand. Putting words to what you are picturing helps with the pages and features list above, if translating a mental picture into plain language is the part that keeps stalling you.

The wider hiring decision this meeting belongs to still has to happen regardless of how ready you show up on the day. What a solid first meeting produces, ideally, is the start of what the meeting should eventually produce in writing - a real scope, not just a friendly conversation.

More from the blog

All posts