If you want to finish your website project on time without losing your mind, you need to stop sending "I'll know it when I see it" emails. The secret to great website feedback is staying organized, being hyper-specific, and using a visual tool that lets you point and click instead of writing paragraphs. When you give feedback that is actionable and grounded in your business goals: rather than just your personal favorite color: the project moves faster, costs less, and actually helps you sell more.
We’ve all been there. You hire a designer, you’re excited, and then the first draft hits your inbox. You look at it and think, “Something feels off.” So you open a fresh email and start typing.
“Can we make the header more 'exciting'?” you ask. Or, “The font feels a bit too quiet.”
Three days later, you get a new version back. It’s still not right. Now you’re frustrated, the designer is confused, and you’re both buried in a 42-message email thread that has more attachments than a legal deposition. This is where website projects go to die.
Here is how you break that cycle and get the website you actually want.
Why email is the absolute worst way to give feedback
Email was built for letters, not for design. When you describe a change in an email, you are playing a game of visual telephone. You say “the button at the top,” but you mean the one on the right, and the designer thinks you mean the one in the navigation bar.
By the time you realize you’re talking about different things, you’ve wasted hours of billable time. Plus, emails get lost. Attachments get buried. Trying to find "that one comment about the logo size" from three weeks ago is a special kind of torture.
If you find yourself writing a sentence that starts with "On the page with the guy holding the hammer, about halfway down on the left side…", stop. There is a better way.
Rule #1: Be objective, not subjective
This is the hardest part for small business owners. Your website is your baby, and you have tastes. You might love the color neon green or hate the font Helvetica. But here is the cold, hard truth: Your website isn’t for you. It’s for your customers.
Instead of saying “I don’t like this blue,” try asking, “Does this blue help a plumber look trustworthy to a homeowner in Denton?”
When you frame feedback around business goals, the conversation changes.
- Bad feedback: “I think we need more pictures of trees.” (Subjective)
- Good feedback: “Our main service is outdoor landscaping, so we need the hero image to show a finished backyard project to build immediate credibility.” (Objective)
When you give "why" behind the "what," you’re not just a client barking orders; you’re a partner helping the designer solve a problem.
Rule #2: Batch your feedback
Don't send an email every time you have a random thought. If you send five emails in one afternoon, your designer is going to lose their place. They’ll start on change #1, but by the time they get to change #5, they realize it contradicts change #2.
Wait until you’ve looked at the whole page or the whole site. Write everything down. Sleep on it. Then, send it all at once. This allows the designer to see the "big picture" and make changes that actually work together.
The tools that make this easy
There's a whole category of tools built for exactly this: visual feedback platforms that let you click directly on a screenshot of your website and leave a pinned comment. No more "the thing at the top of the about page."
A few worth knowing about:
- PROOF (proofapp.io) : Built for freelance designers and small agencies. Your designer sends you a link, and you click anywhere on the website screenshot to leave a comment. No login required, captures desktop and mobile automatically.
- Markup.io : Similar concept, more established, geared toward bigger teams.
- BugHerd : Originally built for QA, also used for design feedback.
If your designer doesn't already use one of these, ask them to. Most will be relieved you suggested it. It saves them just as much time as it saves you.
Focus on the "User Journey"
When you’re reviewing a layout, don’t just look at the colors. Imagine you are a customer who just landed on the site after a long day of work. They’re tired, they’re in a hurry, and they have a problem they need fixed now.
Can they find your phone number in three seconds? Do they know exactly what you do before they have to scroll? Is the "Get a Quote" button obvious, or is it hiding?
Most "design" problems are actually "clarity" problems. If you feel like a page is "too busy," don't just tell the designer to "clean it up." Point out the specific elements that are distracting you from the main goal.
Stop asking your neighbor’s cousin for their opinion
This is the "Feedback Trap." You get a design, you’re 90% happy with it, but then you show it to your spouse, your neighbor, and your bowling league. Suddenly, you have fifteen different opinions from people who don't understand your business or your customers.
One person hates the logo. One person thinks there's too much white space. Now you’re confused, and you’re bringing that confusion back to your designer.
Unless the person you are asking is a target customer or a marketing expert, take their advice with a massive grain of salt. Too many cooks don’t just spoil the soup; they make the project take six months longer than it should.
What to do when you and your designer disagree
Designers aren't always right, but they (usually) have a reason for what they do. If they push back on a piece of feedback, ask them why.
If you say, "I want the text to be bigger," and they say, "I wouldn't recommend that," don't just get annoyed. Ask: "How does the current size help the user experience?"
They might tell you that making the text bigger ruins the mobile layout or breaks the visual hierarchy of the page. A good designer is like a good mechanic: you're paying them for their expertise, not just their hands. Listen to the "why" before you insist on the "what."
The "Final Approval" finish line
The most dangerous part of any project is the last 5%. This is where "scope creep" happens. You start thinking, “While we’re at it, maybe we should add a blog section and a live chat and a cat GIF.”
Don't do it.
Get the core site finished and launched. You can always add features later. It is much better to have a high-performing, simple site live today than a "perfect" complex site that is still stuck in development three months from now.
Reviewing a website shouldn't feel like a second full-time job. By moving away from the "Email Thread from Hell" and toward visual, objective feedback, you’ll actually enjoy the process. And your designer might actually enjoy working with you, too.
Need a web designer who uses tools like PROOF to keep your project on track? Get in touch with CFGroove.
