Why We Started Saying No to "Just Make It Look Like [Competitor]"

I run a small WordPress studio — webmaster.co.ua, 18 years, 235+ projects. "Can you just make our site look like [competitor]'s" is one of the most common briefs we get. For years we said yes without pushing back. Now we treat it as a request that needs a follow-up question before any work starts.

"Looks like" almost never means "looks like." Dig one layer deeper and the actual request is usually about an outcome, not an aesthetic — the competitor ranks higher, gets more calls, seems more established. Copying the visual style doesn't touch any of that. We've shipped visually similar sites that solved nothing, because the client's real problem was never on the surface.

Competitor sites are optimized for a business you can't see. A competitor's homepage might be built around a sales team that handles all real conversion by phone, or a brand budget the client doesn't have, or a completely different customer acquisition channel. Copying the layout without knowing what it's actually built to support means importing someone else's strategy without any of the context that makes it work.

Asking "what specifically about it do you want" filters signal from noise fast. Sometimes the honest answer is "the color scheme feels more professional." That's a real, small, actionable note. Sometimes it's "they seem more trustworthy" — which is a positioning and content problem no layout change will fix. Same brief, completely different scope, and you only find out which one you're dealing with by asking.

Benchmarking is useful. Copying is a shortcut to someone else's mistakes, too. We still pull competitor sites for reference constantly — it's a legitimate, fast way to calibrate expectations. The difference is treating them as one data point among several, not as the brief itself.

If "make it look like theirs" is a request you take at face value, it's worth pausing on — it's rarely actually about the look, and building for the wrong problem is slower than asking one more question up front.