What Your Web Designer Needs From You (and When)

Every "the designer is taking forever" story has two sides, and the second one is told less often. A website project is not a hand-off; it's a collaboration where you — the person running a business — have homework. Not because designers are lazy, but because half the raw material a website is built from lives in your head, your files, and your schedule.

Hiring-thread compilations of small-business experiences describe projects stalling for weeks on a 40-photo request, or a request for page copy that arrives three weeks after the design was ready for it. None of these are scandals. They're just what happens when nobody tells the client the project has a client-shaped dependency in the middle of it.

Here's the full inventory of what your designer actually needs from you, and when.

The four inputs

Content. Words first, actually — most people expect it to be photos. Your designer needs the copy for every page: what you do, for whom, in what towns, with what prices or ranges, and the answers to the ten questions every customer asks on the phone. If professional copywriting is part of your package, you'll still need to supply the raw truth: your services in your words, spoken into a phone or typed badly — that's the material good copy is written from. If you're writing your own copy, know that this is the single most common timeline killer in small-business projects. Five pages of your own copy, written in the gaps of running a business, is not an evening's work.

Photos. Of your work, your team, your truck, your space, your finished jobs. Phone photos are usually fine — usable, even, when they're handled correctly. What's not fine is nothing: stock-photo websites are the graveyard of local-business credibility. Customers can tell a real crew from a paid actor, and studies of local search behavior consistently show people trust businesses that look real. If you have no photos, say so in week one — a photo shoot can be scheduled; a photo absence discovered in week four cannot.

Decisions. A short list of judgment calls only you can make: your hours, your service area, which services lead, what the phone number is on the contact page. These come in small batches at specific moments. The failure mode isn't getting them wrong — it's taking a week to answer each one. A decision delayed is a milestone delayed.

Feedback. At the design-review milestones, your designer sends you something and waits. The feedback that keeps a project on schedule is consolidated: one pass, all your comments, from everyone who needs to weigh in. The feedback that kills schedules is drip-feed — a comment Tuesday, a spouse's reaction Thursday, a reconsideration of the original comment the following week. The single most timeline-preserving habit available to a client: collect everything, then send it once.

When each thing is due

A well-run project gives you a schedule that looks something like this:

If you never received a schedule like this, ask for one. It's the same document as the designer's timeline, with your half of it filled in. What should a website timeline include covers what to ask for.

The three habits that make you the fast client

Reply the same day. Not with the answer — with acknowledgment. "Got it, thinking about it, will reply by Thursday" keeps the project's heartbeat going. Silence is the only reply that costs time.

Keep feedback in one place. Email threads, a shared document, a comment tool — anywhere as long as it's one anywhere. The alternative is decisions scattered across texts, calls, and two different email accounts, which is how "I thought you said" disputes are born.

Say when you don't know. "I don't know yet" is a fine answer on a discovery call. It is a fine answer mid-project too, as long as it comes with a date attached to when you will know. Designers can design around a pending decision. They can't design around a missing one that nobody flagged.

What you should expect from the other side

This is a collaboration, and the obligations run both ways. You're entitled to know what's needed and by when — in writing, with enough lead time to actually do it. A designer who springs a 40-photo request on you the night before the build starts, without ever mentioning it during scoping, has mismanaged their own project. The questions to ask a web designer before you sign include exactly this one: what do you need from me, and when?

You're also entitled to have your inexperience accommodated. If the contract assumes you know what a sitemap is, or what format photos should be in, that's the designer outsourcing their explanation work to you. Good designers explain the homework when they assign it.

The uncomfortable arithmetic

One number worth internalizing before you hire anyone: your time. If a DIY website builder looks free next to a professional build, run the real hours. A business-ready DIY site commonly consumes 40–80 hours of a business owner's time. If your hour is worth $95 — the rough billing rate of the trades — that's $3,800 to $7,600 of your own labor in the "free" option, before counting the speed and flexibility you give up. A designer who takes the content burden off your desk isn't saving you the money; they're buying back your hours.

Before you start

Three things to do the week before kickoff, which will make everything after it faster:

Do those three things and you're already the client designers put at the top of the queue.

Questions about what your project would need from you? We scope the client's workload before either of us signs anything. We answer every enquiry personally, within one business day.