Getting StartedMarch 28, 20269 min readUpdated April 8, 2026

What to Expect When Working with a Web Designer (No Jargon Edition)

If you have never hired a web designer before, the whole thing can feel mysterious. Here is what actually happens — from the first conversation to launch day — explained in plain English.

Jump toThe five stages of a website project What you need to provide What a smooth project looks like A real-world before and after What you do not need to worry about FAQ

By Kootenay Made Digital · Updated April 8, 2026

The short version

The process has five clear stages — discovery, proposal, design, build, and launch — and most projects take two to four weeks.
The most useful thing you can do is have content ready early: logo, photos, service descriptions, contact info.
You do not need to know anything about code, hosting, or technical terms. That is exactly what you are paying for.
Good feedback is specific and consolidated. Scattered comments slow things down. Clear, batched input speeds them up.
After launch, you should be able to make basic updates yourself — no designer required for simple changes.

If you have never worked with a web designer before, the whole thing can feel a bit mysterious. What happens after you say yes? How long does it take? What do you need to provide? What if you do not know what you want?

Here is the full process, explained in plain English — no jargon, no tech speak, no acronyms. Just what actually happens from start to finish.

The short version: you bring the expertise about your business. A good designer brings the expertise about the digital side. Together, you build something you are proud to share. That is the whole partnership.

The Five Stages of a Website Project

Most small business website projects move through the same five stages. The pace varies — some projects run in two weeks, others take a month — but the shape is consistent.

Stage 1: The first conversation

Usually 30 minutes. A casual chat about your business, your customers, what is working, and what frustrates you about your current online presence. You do not need to have all the answers. That is the designer's job. The goal is to understand your business well enough to recommend the right approach — which is sometimes not a full website rebuild.

Stage 2: The proposal

A clear proposal with what will be built, how long it will take, and what it costs. No hidden fees, no vague “starting from” pricing. A real number you can budget around. You will also see a rough timeline and exactly what you need to provide. Want to know what a safe proposal looks like? Read how to spot a risky website quote.

Stage 3: Design

This is where it starts to look like something real. Usually the homepage gets designed first, because it sets the tone for the rest of the build. Love it? Keep going. Want changes? Adjust. Hate the direction entirely? Pivot. This stage is collaborative — your feedback genuinely shapes the outcome.

Stage 4: Build

Once design is approved, the site gets built for real. Mobile layouts, page speed, forms, SEO basics, image optimization, metadata. All the boring but important details most people never see. You do not need to understand any of it. When we say “fast,” we mean pages load in under a second. When we say “mobile-friendly,” we mean it looks right on a phone.

Stage 5: Review and launch

Before anything goes live, you review the whole site. Click through every page, read every word, test every button. Most projects include two to three rounds of revisions. Once you are happy, the switch gets flipped — domain connected, SSL certificate in place, and a quick walkthrough of how to make basic updates yourself.

What You Need to Provide

The most useful things to have ready before you start:

Your logo in a high-quality file (AI, EPS, SVG, or high-res PNG)
A few real photos of your business, team, or work
Your contact details — phone, email, address, and hours
A rough description of your main services
A sense of what pages the site needs

You do not need everything perfect. Just having these basics ready will visibly compress the timeline. The one thing that slows projects down more than anything else is missing content — not the design, not the build. The missing photos and half-finished bios.

The feedback principle that saves everyone time

“Can we make it pop more?” is not useful feedback. “This feels too formal for our business and the phone number needs to be higher on mobile” is useful feedback. Specific comments save days. Vague ones cost them.

What a Smooth Project Looks Like

A smooth project has a few consistent qualities:

Clear scope: everyone agrees on what is being built and what can wait.
Fast feedback: responses in one batch beat scattered messages over four days.
One decision-maker: too many cooks slow things down fast.
Realistic expectations: a simple five-page site launched cleanly beats a complicated build that drags for months.

Want to see the full timeline?

Our process page shows exactly how we work, what to expect at each stage, and how to make the project go smoothly.

Read the process →

A Real-World Before and After

Here is the difference a clear process makes in practice — same type of project, different experience.

Mini case — process made the difference

Before

A Kootenay business owner spends four months on a website project. No clear proposal, feedback happens via text in drips, content was never properly gathered, and the finished site has to be substantially reworked before launch. Frustration on both sides.

After

A Nelson business owner books a call, gets a clear proposal the next day, gathers content in week one, gives consolidated feedback twice, and has a live site in 22 days. Smooth, calm, and actually enjoyable.

Hypothetical composite based on patterns we see across Kootenay website projects. Process clarity is the biggest predictor of a project people are happy with.

What You Do Not Need to Worry About

You do not need to know anything about code, hosting, domains, DNS, SSL, SEO, responsive design, or any other acronym. That is literally what you are hiring someone for. Your job is to know your business and your customers. A good designer handles everything else.

A good web designer does not disappear after launch day either. They check in to make sure everything is smooth, and they are available if something needs adjusting. After that, you should be able to handle basic changes yourself — without needing to call someone every time you want to update your hours.

The best client-designer relationships work like any good partnership: clear communication, mutual respect, and a shared goal. You bring the expertise about your business. The designer brings the expertise about the digital side. Together, you build something you are proud to share.

If you are on the fence: the best first step is a 30-minute conversation. Most of the uncertainty about a website project clears up in that one call. No prep required — just show up and talk about your business.

Curious what a website should actually cost? Read What Should a Website Cost? so you can evaluate any quote with confidence. And if you are on the fence about whether you need a site at all, start with Do You Actually Need a Website in 2026?

Written by

Kootenay Made Digital

We build websites, local presence, and calm AI setups for Kootenay small businesses. No jargon, no agency fog, no surprise fees. Just clear work that makes you easier to find and easier to choose.

About Process

Frequently asked questions

What do I actually need to prepare before working with a web designer?

The most useful things to have ready: your logo in a high-quality file, a few real photos of your business or work, a rough idea of what pages the site needs, your contact details, and a description of your main services. You do not need everything perfect. Having these basics ready will visibly speed up the project.

How many revisions should I expect?

Most projects include two to three rounds of revisions, and that is industry standard. It is usually built into the price. A revision round is your chance to say what is working and what is not. Specific, consolidated feedback — not scattered text messages — keeps the project moving.

Do I need to understand code, hosting, or technical terms?

No. That is exactly what you are paying someone else to handle. Your job is to know your business and your customers. A good web designer translates technical decisions into plain choices you can make without a computer science degree.

What if I do not know what style or design I want?

That is completely normal. Most people do not walk in with a clear design vision, and they do not need to. A good discovery conversation will surface enough direction to start. You react to what you see and adjust from there. The design phase is collaborative — your feedback genuinely shapes the outcome.

What happens if I need changes after the site launches?

A good web designer will walk you through how to make basic updates yourself — changing hours, adding a photo, updating text. For more significant changes, ongoing support retainers exist for that purpose. You should never be stuck waiting on someone else for a simple change to your own website.