Gathering web design inspiration before briefing an agency — how do we avoid picking "pretty but useless" sites?

We made the exact same mistake. Before handing a list to our agency, we set these ground rules: 1) Completely banned inspiration from design award showcases. 2) Analyzed the conversion funnels of the top 5 competitors in our niche or adjacent B2B services. 3) Scrapped any site whose mobile form took more than three steps. Our inbound leads went up noticeably.

Honestly, an agency asking you for a mood board is often a sign they're taking the easy way out. You're not supposed to be the designer. A professional agency should analyze your industry, study your audience, and say "here is the structure that works for your demographic." If they leave everything to the client's visual taste, you just end up with a pretty picture.

B2B buyers are super busy and impatient people... While those fancy 3D animations are still loading, they'll just bounce to another vendor. btw clean, corporate sites with a visible phone number and a prominent "get a quote" button at the very top always drive the most revenue.

We spent 10,000 GBP last year on a gorgeous-looking site. Page load times ballooned to 4.8 seconds because of heavy animations. In two months, our form submission rate tanked from 2.2% to 0.8%. Once we stripped out all the bloat and went back to a clean design, load times dropped to 1.4s and quote requests literally doubled.

Don't send them pretty sites. Send them sites where you can request a quote with one thumb on mobile in under 10 seconds.

Award-winning design sites exist for one reason: so designers can record flashy portfolio clips. Whether the client actually closes deals or makes money is dead last on their priority list.

Always run your inspiration sites through speed test tools. Rule out any examples with bloated DOM sizes, 15 MB background videos, or scripts that lock up the main thread on mobile. If the agency tries to code those visual gimmicks 1:1, your technical SEO and search rankings will go straight into the trash.

I'll try it.

There's a common mistake people make when doing this. In legacy systems, the most expensive thing is unknown dependencies.

I was thinking the same thing. When we decide without measuring, we always end up in the same place.

This thread is archived.

Exactly, and not many people know this. Everyone rushing into web design inspiration gets stuck at the same point.

The real issue isn't the number, but what it's based on. That's all, sorry if I went on too long.

Thanks for writing this, that's the right way. Weekly written progress reports are much more useful than asking for dates.

If you have questions, write them; I'll answer as best I can.

I feel the same way. Taking notes for two weeks yields better results than a six-month estimate.

Of course, it varies if your situation is different.

I didn't know that. If it's your first time, start small; scaling comes later.

Hope this helps.

Thanks a lot, I'll try it today.

I agree.

There's one point I'm curious about. Everything goes well for the first three months; problems arise in the fourth.

This is my opinion, I'm not claiming it's absolute truth.