Website projects can go wrong in surprising ways. Sometimes the problem is obvious, like your designer vanishing. More often, it's subtle: a designer who's technically competent but doesn't really understand your business, a timeline that quietly gets longer each month, or a finished site that doesn't actually do what you needed it to do. By the time you realise something's not working, you've often lost weeks or money. This guide walks you through nine warning signs to catch early, so you can address problems before they become costly.
The designer stops communicating regularly
One of the earliest warning signs is a designer who goes quiet. Perhaps they take days to answer emails. Maybe they only communicate when you chase them. A healthy project has regular check-ins, even if they're brief. You should know roughly what's happening and when to expect progress.
This matters because miscommunication breeds problems. You think they're building something, they think they're waiting for feedback. By the time you reconnect, expectations have drifted. A designer who communicates well from the start will maintain that rhythm throughout the project. If they're slow to respond now, they'll be slow later when you need fixes or adjustments.
If communication drops, flag it early. Ask directly: are they still on track? Do they need anything from you? Sometimes a designer is dealing with personal circumstances. Sometimes they're overcommitted. Either way, you need to know and adjust your timeline accordingly.
They never ask about your business or goals
A designer should ask questions. Lots of them. What does your business do? Who are your customers? What problem are you trying to solve with this site? What success looks like to you? If they jump straight to showing you designs without understanding your goals, that's a warning sign.
Design without strategy usually misses the mark. They might build something visually attractive that doesn't actually help you sell, book appointments, or achieve what matters to your business. A designer who takes time to understand your world makes better decisions about everything else, from navigation to messaging to what features matter most.
Listen for the quality of their questions. Generic questions like "what colours do you like" suggest they're thinking about aesthetics without business context. Smart questions like "how do customers typically find you" or "what would make this site a success for your business" suggest they're thinking strategically.
The scope keeps growing without discussion
Scope creep is normal in web projects. You start with five pages and realise you need seven. You add a contact form and then realise you also need a booking system. The danger is when this happens without anyone discussing it openly.
A designer should flag when scope expands. They should say something like: "I notice you want to add X and Y. That will extend the timeline by two weeks and costs extra. Do you want to proceed?" If instead changes just appear on invoices later, or the project drags on with no clear end, something's wrong.
Ask your designer to clarify scope early and document it in writing. What's included? What costs extra? How many rounds of revision do you get? If they resist putting this in writing, that's another warning sign. Clear scope protects both of you.
The timeline never has a real finish line
Related to scope creep is a timeline that keeps moving. The launch date was meant to be June, then it became July, then August. Each time, there's a reason: a technical problem, a delay in getting content, a third-party service being slow. Sometimes those reasons are valid. But if the finish line keeps moving and nobody's talking about why, that's a problem.
A good designer manages timeline risk. They'll tell you upfront what could cause delays and how much buffer they've built in. They'll update you if something's behind schedule and give you clear options: ship the original scope on the original timeline, or extend the timeline for more features, or reduce scope to keep the date.
If your designer can't tell you a realistic finish date, or that date keeps slipping without explanation, push back. Ask for a concrete plan to get to done. If they can't provide one, you may be working with someone who's overcommitted or isn't managing the project carefully.
You're doing the designer's job for them
You should not be gathering all the content, writing all the copy, sourcing all the images, and doing all the research for your site. A designer should guide you on what you need and help you get it. They might handle some of these tasks themselves. At minimum, they should provide clear requirements and deadlines.
If you're finding yourself drowning in tasks that feel like they should be the designer's responsibility, something's off. Either they haven't structured the project well, they're under-resourced, or they don't know how to manage clients. Whatever the reason, you're carrying their workload.
This often happens gradually. The designer asks for "copy whenever you have time", and you end up spending weeks writing. They need images "ideally by next month", and you're scrambling to source them. A clear project plan with assigned owners and deadlines prevents this.
The finished designs don't match what you discussed
You've had conversations about what you want. You've talked through goals and direction. Then the designer shows you designs that feel completely different from those conversations. The layout's wrong. The tone is off. The colours don't match what you discussed.
Sometimes this means the designer wasn't listening carefully. Sometimes it means they didn't take notes and misremembered. Either way, it's a sign the translation from conversation to design is breaking down. Large revisions at this stage often mean delays.
Good designers share sketches or wireframes early, while changes are cheap. They check in before doing polished designs. If you're seeing finished designs for the first time and they're way off course, the project has a communication problem.
No clear plan for what happens after launch
A website launch isn't an ending. You'll need updates. You might find bugs. You'll want to add new pages. Your designer should be clear about what happens next: do they offer support? How does that work? What does it cost? Is it included or extra?
Ambiguity here creates problems. You think they're supporting you indefinitely. They think the project ended at launch. Three months later you need a small fix and can't reach them. Or they tell you they need a certain fee to make simple changes, and you feel trapped.
Ask upfront: what's included after launch? How do you contact them if something breaks? What's the process for small updates versus big new features? Get this in writing. A designer who's clear about this usually treats you well afterwards.
They're vague about how the site will be built
A designer should be able to explain their technical approach. What platform will the site run on? How will it be hosted? Will it be easy to update yourself, or will you need them for every change? What happens if they're unavailable and you need to bring in another developer?
Vagueness here often indicates they haven't thought it through, or they're using a platform that locks you in to working with them. Either's a problem. A site should be built in a way that serves your business, not just their convenience.
Ask them to explain their technology choices and why those choices work for your specific needs. If they can't explain it clearly, that's a warning sign.
The contract or terms are missing or unclear
If you don't have a written agreement, that's already a warning sign. A contract doesn't have to be long or fancy, but it should cover what you're paying, what you're getting, what the timeline is, and what happens if either person needs to change course.
Without this, you have no protection if things go sideways. If the designer disappears, you don't know where the files are. If they want to charge extra for something, you can't point to what you agreed. If they hand over an unfinished site, there's no clear recourse.
Any professional designer should provide a written agreement. If they resist, that's a significant warning sign. You're about to hand over a chunk of money and multiple weeks of your time. You deserve clarity about what that means.
Frequently Asked Questions
What should I do if I spot one of these warning signs? Address it directly and promptly. Have a conversation with your designer and be specific about what you're noticing and why it concerns you. Many problems can be fixed with clear communication. If they're defensive or dismissive, that tells you something too.
Is it ever too late to address problems in a web project? It's harder the further along you are, but it's rarely too late. If you're early in the project, a difficult conversation can reset expectations and get things back on track. If you're near launch, you might need to accept that this project has problems and plan to fix them after launch.
Should I be worried if my designer misses one deadline but is otherwise communicating well? Minor delays happen in most projects. One late delivery isn't usually a sign of deeper problems, especially if they explain it and get back on track. Look for patterns instead. Is this the first delay, or the tenth?
What if I hired a very cheap designer and now things are going badly? You've learned an important lesson about value. Cheap often means under-resourced or inexperienced. Rather than throw more money at this project, focus on finishing it as well as possible and building a relationship with a better designer for the next phase.
Moving forward
Website projects succeed when everyone's clear about the goals, timeline, and expectations from the start. If you're seeing any of these warning signs, address them now. A conversation that feels uncomfortable today prevents much larger problems later. Learn more about how we approach web projects to see the kind of clarity and communication that should define your experience.
