You hired a web designer three weeks ago and they just sent you a mockup. It looks... fine? Maybe? You're staring at it trying to figure out if this is what good web design looks like or if you're about to waste thousands of dollars on something that won't work. The problem is that you're not a designer, and you have no framework for evaluating whether what you're seeing is actually going to help your business. You can tell if you like the colors, but you can't tell if it's going to convert visitors into customers. And that's a terrifying position to be in when you're writing checks.
Here's the thing most web designers won't tell you: looking good and working well are not the same thing. A designer can show you something beautiful that makes you feel excited and impressed, and it can still be completely useless for your business. The reverse is also true—some of the highest-converting websites look almost boring because they're built around clarity and user behavior rather than visual impact. So when you're trying to evaluate your designer's work, your gut reaction to the aesthetics is actually one of the least reliable indicators you have.
The first thing to look at is whether your designer is asking you the right questions. Before they ever show you a single design mockup, they should have spent significant time understanding your business, your customers, and what you're trying to accomplish. If they jumped straight into asking about color preferences and showing you inspiration boards, that's a red flag. Good designers are solving business problems, not just making things pretty. They should be asking who your customers are, what makes them choose you over competitors, what actions you want people to take on your site, and what's currently not working. If those conversations never happened, the work they're doing is decorative, not strategic.
When you do see design work, the question isn't whether you like it—it's whether it makes sense for your customers. Can someone who's never heard of your business land on the homepage and immediately understand what you do and why they should care? Is the most important action on each page obvious and easy to take? Does the design guide someone's eye to the right places in the right order? Your designer should be able to explain every major design decision in terms of user behavior and business goals, not just aesthetic preference. If they can't tell you why something is the way it is beyond "it looks good" or "it's modern," they're not doing strategy.
Pay attention to how your designer handles your feedback. This is counterintuitive, but a good designer will push back on some of your requests. Not in a defensive way, but in a way that shows they understand your goals better than you understand design. If you say you want the logo bigger and they immediately make it bigger, they're an order-taker, not a problem-solver. If they ask why you want it bigger and then explain how making it smaller might actually make your brand feel more premium and trustworthy, that's someone thinking strategically. You should feel like you're collaborating with someone who has expertise you don't have, not like you're directing someone to execute your vision.
Timeline matters more than most people realize. A good designer isn't fast or slow—they're appropriately paced. If someone promises you a custom website in a week, they're either using templates and lying about it, or they're skipping all the strategy and research that makes a website actually work. But if months are going by with no clear progress and vague explanations, that's also a problem. You should have a clear timeline with specific milestones, and your designer should be communicating proactively about where things stand. Silence followed by a big reveal is a sign of inexperience or disorganization.
The technical questions are harder to evaluate if you're not technical yourself, but there are some basics you can check. Ask your designer about page speed, mobile responsiveness, and SEO fundamentals. You don't need to understand the details, but you should hear confident, specific answers. If they seem annoyed by the questions or dismissive about technical performance, that's a problem. A website that looks great but loads slowly or breaks on phones or can't be found on Google is a failed project, and a good designer knows that. They should be thinking about these things without you having to bring them up.
Ultimately, the best indicator is whether your designer is solving your actual problem. You didn't hire them to make something pretty—you hired them because your current website isn't generating enough leads, or it's making your business look less credible than it is, or it's confusing potential customers. Everything they do should be in service of fixing that specific problem. If you can't see the connection between what they're designing and the business outcome you need, ask them to explain it. If they can't, or if the explanation feels like hand-waving, then either they don't understand your business or they're not actually doing the work you're paying for.
You don't need to become a design expert to evaluate whether your designer is doing good work. You just need to pay attention to whether they're thinking like a business partner or like a visual decorator. The right designer will make you feel like they understand your business, will push back when your ideas conflict with what actually works, will communicate clearly about process and progress, and will be able to explain every decision in terms of outcomes rather than aesthetics. If you're seeing those things, trust the process even when you're not sure about a color choice. And if you're not seeing those things, it doesn't matter how good the mockups look—you're probably not getting what you paid for.