Post Summary: We Recommended Against It and Built What She Wanted
A pest control outfit ran trucks in caution green, the shade you’d see on a hazmat crew, and the owner wanted it as the site’s dominant color at full width. Not as an accent. Everywhere.
Our first version used it sparingly, set against something darker. She turned it down flat. Rounds of discussion followed, with our argument being that a shade that intense wears on the eye and does more in small doses.
She stayed where she was, which is where this stops being ours to decide. The money is hers. We put our advice on record and told her we’d build the version she loved. She softened it slightly on her own, and what shipped sat nearer her instinct than ours.
That’s a disagreement rather than a power struggle. Each side said its piece, each was heard, and the one writing the check decided.
The Client Wanted Caution Green Everywhere
Early on, we worked with a pest control company. Caution green trucks. It was like a hazmat team showed up to every single job, and that green was so obnoxious. Boy, did she want it on the website.
Not accent colors. We’re talking main color, full width. The whole thing.
And we fought with her up, down, left, right.
Why We Recommended Accents Instead
The first design we came up with was much more reasonable. The green was there, accents, pops of color, balanced against a darker palette. Even against a black it would have been amazing. But she looked at it and said what every web designer eventually hears.
I don’t like it.
So we went back and forth. Back and forth. We told her straight, this is very bright, this is something that might be hard to look at. We know it’s your color, but we think accents would be better. She held her position. She wanted that green everywhere, and she was not shy about saying so.
We put up as much of a battle as we possibly could. Not because we wanted to win. Because we had the experience, and we knew what the screen was going to look like when she got her way. But there’s a line. Making the case is not the same as pushing you toward something more expensive, and this was never that.
Who Gets the Final Call on a Design
Here’s where we landed. We told her, look, you’re paying the money. We’ve documented the account of our recommendations and if you love it, that’s what we’ll do.
That’s the whole philosophy. If someone’s paying for something and they have strong opinions about it, they should get what they want. We’re not going to hold the site hostage over a color. We’re going to make our case, document it, and then build what the client asks for.
She relented a little on it. She wanted it all over the place and we were able to tone it down a little. It just wasn’t where we thought it should be.
And that’s fine.
Because that disagreement wasn’t a power struggle. It was just, look, we have the experience and this is the way we recommend. We said our piece. She said hers. We went back and forth until both sides had been heard. And at the end of the day, we yielded to what she wanted.
That’s what a healthy disagreement with your web designer should sound like. Two people who care about the project, honest about what they think, and the person paying gets the final say.
If pushing back has ever felt like something going wrong instead of something going right, that’s not a disagreement problem. That’s a relationship problem. And it doesn’t have to work that way.
Yeetish Question
What if I love something my web designer hates?
Then you should get it. We’ll tell you what we think, we’ll be direct about it, because that’s what you’re paying us for. But if you’ve heard the recommendation and you still love it, that’s your call. We document our side, we build what you want, and we move on. No grudge. No passive-aggressive “I told you so” down the road. It’s your business and your website. We’re here to make it as good as it can be, not to pressure you into our version of what that looks like.