What Good Communication Looks Like During a Website Build

When researchers compiled client complaints about web design companies, the results were lopsided in a way that surprises most business owners. The largest category wasn't design quality, technical skill, or even price. It was planning and service: non-responsive designers, missed deadlines, poor expectation management, and the phrase that appears over and over in complaint after complaint — "doesn't listen."

The technical work, it turns out, is table stakes. What separates a project you'd recommend from a project you'd warn people about is almost entirely about communication.

The problem is that most business owners have never been inside a well-run website project, so they don't know what normal looks like. Here's what healthy communication during a build actually looks like — so you can tell whether you're getting it, and so you can ask for it if you're not.

The baseline: what you should be able to expect

These aren't perks. This is the floor.

A reply to any question within one business day. Not an answer — a reply. "Good question, checking on the integration, back to you Thursday" is a same-day reply. Silence until Thursday is not. One business day is the standard because it's the standard of every other professional service you buy. If your accountant or attorney went dark for two weeks mid-engagement, you wouldn't wonder if you were being difficult.

Scheduled check-ins that actually happen. Weekly or milestone-based — either works if it's real. A check-in can be five minutes and an email: here's what moved, here's what's next, here's what we need from you. The magic isn't in the length; it's in the rhythm. Rhythm is what lets you relax. Projects with a rhythm rarely surprise anyone; projects without one are made entirely of surprises.

News delivered proactively, especially bad news. The slip, the integration that's fighting back, the stock photo that didn't clear — you should hear it from the designer before you notice it yourself. A designer who only communicates milestones and sunshine is managing you, not the project. If the first time you learn the project is late is because you asked, communication has already failed.

One place where things live. Decisions, files, feedback, the milestone list — one location, findable later. Not scattered across three email threads and a text exchange. When "what did we decide about the contact form" requires archaeology, the project is carrying a tax on every decision it makes.

What a communication plan looks like

If you're about to start a project, spend fifteen minutes at kickoff agreeing to the plan. Five questions:

That last one matters more than people expect. "Urgent" is where communication systems fail — the question that sits in the same inbox as everything else while the site is broken. Agree now what urgent means (site down, orders not arriving) and where it goes.

If your designer doesn't raise any of this at kickoff, you can. "Can we agree on a check-in schedule and where feedback lives?" is a question no competent designer will bristle at, and the way they respond to it is a preview of the next three months.

The client's side of the contract

Communication is bidirectional, and the complaints run both ways: designers' own frustration lists are topped by clients who go quiet for a week on a decision the project is blocked on, feedback that arrives in eleven installments, and scope that changes via a passing comment. Your side of the floor:

Reply to the things only you can answer. The project has a handful of moments where it stops and waits for you. Every one of those is a day on the calendar. Same-day acknowledgment — even "thinking, answer by Friday" — is the single most valuable communication habit a client can have.

Consolidate feedback. One pass, everything, from everyone. The drip-feed pattern — a comment today, a partner's reaction Thursday — is how schedules die. If more than one person will weigh in on the design, agree at kickoff who consolidates.

Ask questions when you have them. A question asked in week one is free. The same question asked in week four, after the thing you didn't understand has been built on top of, is expensive. There's a whole piece about being the client designers fight for — but the short version is that the clients who ask the "dumb" questions early get better websites.

The warning signs

How do you know communication has failed, rather than just been busy? The pattern is consistent:

One slow week isn't a pattern. A designer who tells you "we're heads-down on the build, expect a light week" is communicating — that's the healthy version of a quiet stretch. The unhealthy version is quiet with no explanation attached. Two consecutive missed check-ins without an explanation is the point where the standard advice is to stop waiting politely and put a dated, written ask in front of them. If that goes nowhere, you're not in a communication dip anymore — the mid-project ghosting playbook is the next piece to read.

Why this matters more than the design

Here's the thing that's easy to forget when you're comparing portfolios: you will spend more time communicating with your designer than looking at their work. The build is six to twelve weeks; the relationship — if it's any good — is years, because sites need updates, fixes, and changes as your business changes.

That's also why communication is the fairest test of a designer there is. Anyone can polish a portfolio. The way a designer communicates during the project — the responsiveness, the proactivity, the honesty about problems — is the same way they'll communicate when your site has an issue on a Saturday in year two. Choose on that.

Questions about how we run projects? We answer every enquiry personally, within one business day — including during yours.