Here's something most people learn the hard way: the most expensive part of a web project often isn't the design. It's the redesign.
Revisions pile up when the designer is working from incomplete information. They fill in gaps with their best guess, show you the result, and hear "that's not what I meant." Then the cycle repeats. Each iteration costs hours, dollars, and goodwill on both sides.
The frustrating part is how preventable this is. A solid brief doesn't require technical skills or artistic sensibility. It requires honest answers to straightforward questions. Those answers matter whether you're working with a large firm or a cheap web designer — possibly even more so with the latter, since tighter budgets leave less room for course correction.
Here's a field guide to writing a brief that keeps your project on track.
Lead With Purpose, Not Preferences
If the first thing out of your mouth is "I like blue" or "I want it to look like Apple's site," you've already started on the wrong foot.
Aesthetic preferences are easy to express. They're also nearly meaningless without context. What matters is the role your website plays in your business. Is it meant to convert visitors into booked appointments? Help people find your physical location and operating hours? Present a catalog of services so prospects can self-qualify before calling?
A booking-focused site puts the scheduling tool front and center, with minimal competing elements. A directions-and-hours page prioritizes mobile performance because people are searching on the go. A service catalog organizes information with clear categories and filters.
Purpose drives structure. Structure drives design. When you reverse that order and start with surface-level preferences, you guarantee more revision rounds later.
Get Specific About Who Uses the Site
Designers need a clear picture of the end user. Vague descriptions like "potential customers" or "a general audience" don't provide enough material to work with.
Think about the last twenty people who contacted your business. How old were they? What questions did they ask? Did they call from a mobile phone or fill out a form on a laptop at their desk? Were they comparison shopping or ready to buy?
That kind of detail is gold for any designer. "Parents of school-aged children looking for after-school tutoring, browsing on phones between 3 and 6 PM" tells the designer everything about mobile priority, reading patterns, and call-to-action placement. A cheap web designer who receives this level of detail will deliver far more targeted work than one left to assume.
If you have website analytics, share relevant data. If you don't, share your own observations from customer interactions. Both beat silence.
Be Transparent About What You Can Spend
The budget question makes most clients squirm. But silence on the subject doesn't protect you — it misleads the designer.
Web development covers a vast range of complexity. A simple landing page and a multi-step checkout system with account management are not comparable projects. Without a budget benchmark, the designer doesn't know which world you live in. You risk getting a proposal that's either wildly ambitious or frustratingly basic.
Most professionals present a web design package at multiple complexity levels. When you share a real number or even a range, the designer can immediately tell you what's achievable. Maybe your goals fit neatly into a starter tier. Maybe they require phasing — launch with core pages now, add a blog or resource center in phase two.
This conversation is productive when it happens before anyone starts building. It becomes tense and adversarial when it surfaces after several rounds of work have already been completed.
Annotate Your Reference Sites
Sending links to websites you admire is easy. Explaining why you admire them is where most people stop trying.
A designer who receives five unexplained links has to guess what caught your attention. Was it the spacing? The color scheme? The way the navigation works? The tone of the copy? Every guess is a potential misfire.
Give each reference a sentence or two of explanation. "I like that their homepage has one headline and one button instead of ten competing elements." "The way they handle team photos — candid and casual, not stiff headshots." "Their pricing page uses expandable sections, which makes it feel less overwhelming."
Negative examples deserve the same treatment. If you find cookie-cutter layouts uninspiring, say so. If scrolling animations make you dizzy, the designer needs to hear that before they invest time building them.
A handful of annotated references prevents more wasted work than nearly any other brief component. One important caveat, however: never ask a designer to copy a competitor's site outright. That crosses ethical and legal lines. Use examples for direction, not duplication.
Solve the Content Problem Before It Becomes a Problem
Content is where well-planned projects quietly fall apart. The design gets approved on the assumption that text will be short and punchy. Then the actual copy arrives — long, dense, and nothing like the placeholder. The layout buckles. Back to the drawing board.
Prevent this by making content decisions before design begins. Decide who's responsible for writing. Many web design packages offer copywriting as an optional add-on, which can save considerable time and produce more consistent results. If you're writing it yourself, set a deadline that's realistic and treat it as non-negotiable.
Inventory everything: the number of pages, the available photography, the brand files. Send vector logos, official color hex codes, and licensed font files — not screenshots of your old website. The cleaner your asset delivery, the faster the designer can work.
And if your content isn't ready, communicate that upfront. Placeholder text is workable when the designer knows it's temporary and has a rough word count to plan around.
Define Boundaries in Writing
Scope creep starts with good intentions. After the initial design is approved, you think of one helpful addition. Then another. Each seems minor. Together they reshape the project timeline and budget.
Your brief should list what's included — the pages, the features, the integrations — and spell out how many revision rounds come with the project. Most designers cap review cycles at a set number. Rounds beyond that cost additional money. Knowing the limit encourages you to use each round intentionally.
Agree on how feedback will be delivered. A single consolidated document is far more efficient than a comment here, a phone call there, and a Slack message three days later. Many designers now formally request batched feedback to prevent fragmented communication from dragging out timelines.
Structure on both sides — scope and feedback — is what keeps a project moving in one direction.
Unify the Feedback Under One Name
The fastest way to waste revision rounds is to let multiple people deliver competing design notes. One person asks for brighter accent colors. Another insists on muted tones. The designer tries both, and you pay for both attempts.
Before the project begins, appoint a single decision-maker. Run the debates internally. Resolve disagreements among yourselves. Then send the designer one clean, consolidated set of notes.
This discipline saves more budget than most clients expect — especially when working with limited revision cycles and fixed-price agreements.
A Brief You Can Fill Out in Fifteen Minutes
If you need a starting framework, answer each item below before your first conversation with any designer.
State the single most important thing your site must accomplish for your business. Describe your typical visitor with demographic and behavioral specifics. List every page you expect to need, along with who provides the text, imagery, and brand materials.
Include three to five reference sites with brief annotations explaining what works for you, and one or two examples of what doesn't. Note any required functionality such as contact forms, appointment booking, or online payments.
Share your actual budget or a credible range. Set a deadline and explain what's driving it. Name one person who has final approval on all deliverables.
Matching goals to the right web design package is dramatically easier when a designer can review these answers before quoting.
The Bottom Line
Almost every frustrating revision cycle has the same root cause: something that was missing from the brief.
Gaps become assumptions. Assumptions get built into mockups. Mockups built on assumptions need to be fixed, and fixing them isn't free. The principle holds regardless of studio size or reputation — whether you've hired a celebrated agency or a cheap web designer.
The antidote is simple but requires discipline. Write the brief before the project starts. Be honest about what you can spend. Define the scope and put it in writing. Consolidate your feedback and deliver it through one channel to one person.
It's not the most exciting part of any web project. But it is the part that saves your money, protects your timeline, and preserves a healthy working relationship with the person crafting your site. That hour of preparation is always worth it.
Comments (0)