Let's talk about the challenges that every website designer and developer has faced at one time or another: those “pain in the arse” clients who constantly try to override your creative process, push for shortcuts, or ignore the boundaries you’ve set.
Welcome to another episode of Websites Made Simple with me, Holly Christie!
I’m getting honest about what it feels like when a project just isn’t sitting right—when your heart drops at another problematic email and you start questioning your own approach, especially as everyone else seems to be breezing through perfect testimonials and happy launches.
I’ll share my practical strategies for protecting your boundaries, saying a firm “no” to unethical requests (like copying someone else’s design), and managing difficult clients who want you to queue-jump or abandon your process.
You’ll hear some real stories from my own experience, including how to handle disagreements over design decisions, document your advice, and know when it’s time to offboard a client altogether.
If you’ve ever lost sleep over a challenging project or wondered how to keep your business running smoothly without sacrificing your sanity, this episode is especially for you.
Listen in and let’s talk about how to thrive as a web designer, even when you’re dealing with the trickiest clients.
00:00 Dealing with Overbearing Clients
04:36 Client Feedback During Design Process
07:23 Client Boundaries and Collaboration
10:15 "Importance of Client Communication"
13:40 Avoid Problem Clients' Retainers
Mentioned in this episode:
If a client is asking you to queue jump, then it's
Speaker:a pretty big red flag. If you break your
Speaker:boundaries, first of all, you'll just feel terrible about the whole project.
Speaker:It's not you, it's those clients.
Speaker:You know that feeling you get where your heart drops when you receive the email
Speaker:from the client and they made some suggestions for the website
Speaker:design, or when you feel everything's
Speaker:kind of not going as well and you're not sure why.
Speaker:We're here to talk about this today.
Speaker:Hi, and welcome to another episode of Websites Made Simple. This is
Speaker:Holly Christie hosting the podcast to help you website
Speaker:designers and developers have a much better
Speaker:web design career. Because, trust me, it doesn't matter how well
Speaker:it starts off, at some point we'll hit that bump on the road.
Speaker:And today we're talking about what happens when the
Speaker:clients decide that they are going to overrule you during the
Speaker:website design process. Because we've all been there,
Speaker:we've all heard the, oh, just make it look like this, or that doesn't feel
Speaker:quite right, or I have a friend who has mocked
Speaker:up this or that, and it is so
Speaker:incredibly frustrating. But it can also feel quite
Speaker:alienating, particularly if we're in those spaces where we're seeing other people
Speaker:produce project after project, testimonial after testimonial,
Speaker:and it looks like everything is going amazingly
Speaker:for them and you're there with your sleepless nights, hanging on by
Speaker:your fingernails, thinking, what am I doing wrong? It's not you, it's
Speaker:those clients. Anyway, let's crack straight into it.
Speaker:So when you have a client who tries to override the
Speaker:project for whatever way or reason that they
Speaker:are doing it, and as said in the intro, this could be
Speaker:that they want to lead the design, which
Speaker:is always a bit of an iffy thing, but sometimes they want to
Speaker:do that. It could be that they've seen something on someone else's
Speaker:website. Whatever it is, the first, first thing that you
Speaker:need to do is work out
Speaker:if what they're trying to override this design. And this
Speaker:process about actually aligns with how you work as
Speaker:well. So what I mean by that is I have a really
Speaker:strong we do not rip off other people's work
Speaker:policy. So every design someone gets from my
Speaker:websites is created for them. And
Speaker:I, whilst we'll all use inspiration of previous designs or
Speaker:other designs or something like that, if someone says to me, could you copy
Speaker:this design? It is an out and out. No, no, I cannot. It doesn't
Speaker:align with my work. If a Client repeatedly comes up with that
Speaker:saying, I just want it to look like this. We want an exact copy of
Speaker:this. That is the point where we need to off board that client
Speaker:and to say to them, this isn't working out. This
Speaker:isn't how I work. I have this covered in
Speaker:my terms and conditions. It says, you know, we will not copy other people's work.
Speaker:If you don't have your terms and conditions sorted out, I can
Speaker:help you out with that. Just go along to websitesmadesimple.co.uk
Speaker:and my website Designer's Contract pack, which is my best selling
Speaker:product for a reason. It has editable contracts
Speaker:for terms of service contracts, everything and anything you need for
Speaker:running your web design business, it is here in the Web Designers contract package.
Speaker:Either refer to your own terms of service or get these whipped up very
Speaker:quickly and explain it is immoral and you would be ripping off
Speaker:someone else's work. Someone's already been paid for that. You also do not
Speaker:want to end up in a lawsuit because when your client says copy
Speaker:this, you don't know who owns the copyright to that work. So it's an out
Speaker:and out. No. And usually I will say to someone,
Speaker:well, I could produce something similar to that, but it would be produced
Speaker:for you, so it wouldn't be an exact copy. We don't do that
Speaker:at this Demanding Life or Websites Made simple either. That's
Speaker:the first thing. If they're just saying I would like something like this,
Speaker:find out what it is they like about it and then you can use that
Speaker:to inform the design. And if you are
Speaker:not sure or not very tight on your design process again,
Speaker:hop over to the website and I've got loads of resources there
Speaker:which will help you kind of really nail your web design process as well.
Speaker:But you should be having points during the website design
Speaker:where your clients do get to check in and they get to give you feedback
Speaker:on the website. Do not go and build an entire
Speaker:website and then show it to them at the end. Make sure that they do
Speaker:have this back and forth on the way through. It will make it much easier
Speaker:for you. But it does need to be a controlled back and forth. It can't
Speaker:be that they can just drop a message anytime you do need set times that
Speaker:you speak to a each other around them.
Speaker:So the next thing is if it's just that they have a set idea of
Speaker:design and it's not really the way that
Speaker:you design, but you also know that the website's not going to be
Speaker:signed off without this part of the design being in
Speaker:there, then sometimes you just
Speaker:gotta get on with it and do it. You know, the client is the one
Speaker:who has to live with it, not you. If it's just a
Speaker:really crappy design. Like I had a client who they were really lovely
Speaker:and we've got a great working relationship and I do still manage their website and
Speaker:everything, but they very much wanted to lead the design. And it wasn't
Speaker:a design that I particularly wanted to put my name to, but the
Speaker:only way we were going to get this website project over the line was if
Speaker:I did build it out this way. So that's what I did. And
Speaker:I just removed the site credits. So it doesn't tell you who built the website
Speaker:there. It's not on my portfolio. The client loves it.
Speaker:That's the most important thing there. As I say, the first thing work
Speaker:out is it moral issue. If it is, don't do it. And
Speaker:if it isn't, then kind of put up and shut up, build it
Speaker:and move on. Something really important when a
Speaker:client is overriding, because they don't always just override in
Speaker:the design areas, they can try and override in
Speaker:other areas of the contract as well. So the first thing is
Speaker:really do not break your boundaries around timescales and
Speaker:around payments. You have those boundaries there for a reason.
Speaker:We have the boundaries of the timescales so that we know that we can
Speaker:deliver the project in its entirety within that time
Speaker:and still be able to do the other things that we need to do within
Speaker:our businesses. And that could be the marketing, it could be looking at
Speaker:other projects. I am always working on more than one project at a time, so
Speaker:I can't necessarily, necessarily rush something and I can't queue jump
Speaker:a project. And if a client is asking you to
Speaker:queue jump, then it's a pretty big red flag.
Speaker:And one of the things you'll find is if you break your boundaries, first
Speaker:of all, you'll just feel terrible about the whole project. It just won't sit
Speaker:right with you. But also, the client will most
Speaker:likely be trying to get you to break other boundaries around stuff
Speaker:as well. So. So really stick to your guns. I have some
Speaker:terminology that I use for clients and I often say to
Speaker:them, I want us to have a really good working relationship. In fact, that
Speaker:is like one of the first things at the beginning of my terms of service.
Speaker:I want us to have a really good relationship. And the way that I can
Speaker:ensure that we do that is if we stick to the process that
Speaker:I've mapped out. I'VE been a web designer for a long time
Speaker:and I know that this is going to give a really meaningful experience
Speaker:for you and that's it. And if they push back on that,
Speaker:it's up to you. Whether you reply, you've said your part and it's time
Speaker:just to move on, or it's time if they keep pushing
Speaker:back, it might be worth considering whether they are the right client for you.
Speaker:And I know that it can be really frightening offloading clients
Speaker:or choosing not to work with someone, especially because sometimes
Speaker:work can feel quite sporadic. But it is never worth
Speaker:working with clients who keep you up at night. Clients who try to
Speaker:break boundaries around payment. No,
Speaker:it's just that's a flat out no for me because if
Speaker:they've engaged you and they've chosen to prioritise their
Speaker:website build, then whatever comes up next isn't
Speaker:your problem. There are a couple of things where obviously if there was a
Speaker:family bereavement, you might want to flex your
Speaker:payment terms for them. But really, to be
Speaker:careful with this one, I sometimes
Speaker:offer clients payment plans if I know that they would maybe
Speaker:struggle to come up with the payment at the time. Again, you can find the
Speaker:payment plan template in the website designer's contract pack
Speaker:and it's a binding document. It says what everyone's going
Speaker:to set up to do. And sometimes I've even had clients
Speaker:who had an unexpected issue and we said,
Speaker:okay, well let's extend the payment plan and make the payments as small,
Speaker:smaller amount until it's paid off. But remember, just as much
Speaker:as they need to organize their business finances, you need
Speaker:to organize yours. And you can't do that if you are flexing on those
Speaker:payment terms. So work out what works for you and
Speaker:then be watertight with your boundaries around them.
Speaker:So if you push back with clients, particularly when it's design work,
Speaker:but with kind of anything that comes up within the project, make sure you
Speaker:explain your thinking to them because often if it's
Speaker:like a flat out, nope, we're not doing that, bye. That's where
Speaker:people like developers can get a really bad reputation where
Speaker:people say my developer's been ghosting me or I
Speaker:can't get an answer for them. And often they've actually had the answer from the
Speaker:developer. The answer's been no and there's been
Speaker:no like explanation around that no.
Speaker:So the client doesn't really understand a computer and then they think, oh, the
Speaker:devs just, you know, kind of ghosting me. And it's not the case at all.
Speaker:I always like to explain why I am doing something and why I'm not
Speaker:going to be doing something as well. And it makes for a much better
Speaker:relationship with the clients. Because if you think information is power
Speaker:and if we give the client that information,
Speaker:it gives them the power there to understand.
Speaker:When they understand, they usually always end up
Speaker:having a really good relationship with the person who's explaining it to them as well.
Speaker:And I often find that if I am saying no to a client about something
Speaker:and I give my explanation as to why, they accept it really well, and we
Speaker:can move forward really well if they go against your advice,
Speaker:make sure you put it in writing, even if it's
Speaker:just an email outlining the conversation.
Speaker:I've spoken before on the podcast about tricky clients that I've had
Speaker:and there was one particular tricky client who
Speaker:I built her website for her and all
Speaker:was well. And we got to the point of first draft and I
Speaker:repeatedly said to her, I really think you should have individual service
Speaker:pages. And she kept saying no, she wanted all the services
Speaker:on one page. And I said to her, what about if we
Speaker:even just bundled these services and, you know, just had a couple of pages and
Speaker:we put these ones together and these ones together. And she said no.
Speaker:So I came back to her with an email and I said,
Speaker:I just wanted to reiterate the importance of having
Speaker:individual service pages. It will really help with your SEO, it will help
Speaker:with the customer user experience, all of this. She came back,
Speaker:she said no, she just wanted it on one page. So
Speaker:after the website was launched a little while later, she was
Speaker:getting inquiries, but she wasn't getting the kind of inquiries that she
Speaker:wanted and they were falling down at the invoicing stage. And she consulted an
Speaker:SEO company and the first thing that they said was, you need
Speaker:individual service pages. So she then came back to me and said,
Speaker:you didn't do the job properly, you didn't do the build properly. And
Speaker:I said to her, but I did, and I put it in writing that I
Speaker:advised this for you. And she said to me,
Speaker:oh, well, I thought it would be a better user experience to have all the
Speaker:services on one page. And so I came back and I said, I'm an
Speaker:award winning website designer who specifically won an award in user
Speaker:experience and user journeys. Why did you think I'd advise you wrongly?
Speaker:And she argued just a little bit. And I was able to provide the
Speaker:evidence that I had recommended repeatedly that she had these
Speaker:individual pages. So it wasn't an easy experience. And
Speaker:luckily the website had been built and Finished. So I didn't need to worry about
Speaker:off boarding her. But it was real
Speaker:vital information in an experience about saying always, always put it
Speaker:in writing. If you are clashing a little bit on
Speaker:the way forward with the clients,
Speaker:these clients as well, like I was saying about this particular
Speaker:one, didn't stay on on retainer afterwards. And the one thing I would
Speaker:say is if you have a clash with clients during
Speaker:the website build where they're trying to override you,
Speaker:they are not the clients you want to keep on a retainer. I know that
Speaker:the hard work is in getting the client on board in the first place.
Speaker:I get it. I really, really get it. I promise I did. And then you
Speaker:have them and you, they spend the money with you and you know, you build
Speaker:this great website. And so the easiest thing in the world is to say, stay
Speaker:with me, I'll manage a website. It's regular money, that's great.
Speaker:But if you have had issues with them during the build process, I promise you
Speaker:it is not worth it. The easiest way is just to not offer them a
Speaker:retainer. They can stay on for hosting and maintenance
Speaker:or they can stay on for maintenance only and self host it. And there have
Speaker:been a couple of times where I haven't offered that option because the
Speaker:relationship with the client feels like it just hasn't been there.
Speaker:And so at the end say, you know, please let me know what you'd like
Speaker:to do with hosting if you already have hosting set up, or I can recommend
Speaker:and set you up with your own hosting and instructions on how
Speaker:to maintain the website will be provided in your website user
Speaker:manual. Or if you'd rather have a professional maintain it for you, I can
Speaker:recommend a couple of people who are great at this and those people will
Speaker:have a different working relationship with your clients. So you don't need to worry about
Speaker:off boarding someone who's been a bit of a nightmare. And if
Speaker:not, just set them up with their hosting and go on their way. And if
Speaker:they do come back and say, oh, well, I see that you offboard this.
Speaker:It is okay to say it's been great building your website for you.
Speaker:I'm pleased with the results, but I didn't feel like our working experience was that
Speaker:great. And I want you to have a really good working experience with someone and
Speaker:therefore I recommend this person. Usually people just don't push back with
Speaker:that. So that is me for this
Speaker:session. I hope you have liked this episode. It feels very
Speaker:honest. We all have had these experiences. I
Speaker:would to love, love to hear from you. I would love to hear your experiences,
Speaker:so do drop over to websitesmadesimple.co.uk
Speaker:and let me know your horror stories of
Speaker:when a client has overridden you. That's all for now. See you
Speaker:next.