What Clients Actually Notice About Your Website

A designer I know spent two days on the micro-interaction for a pricing toggle. Smooth easing, a tiny bounce, colour that shifted just so. It was lovely.

The client's feedback on launch day was one line: "The brochure link on the about page doesn't work."

Nothing about the toggle. They never mentioned it. They probably never noticed it.

That gap, between what we pour ourselves into and what actually registers on the other side, is worth taking seriously. Not because craft doesn't matter, but because if you know what clients notice, you can make sure the things they notice are the things you nailed.

So here's an honest list. Some of it stings a little.

They notice when something is broken. Immediately.

Clients are not looking at your site the way you are. They aren't evaluating the type scale. They're clicking around like a nervous customer, and the first thing that doesn't work is the thing they'll remember.

A dead link. A form that spins. A PDF that opens a 404. A video with a grey box where the player should be.

The cruel part is that one broken thing erases ten polished ones. You can have the best-built site in their industry, and if the "Download our guide" button fails on the day their sales lead demos it to a prospect, you built a broken site. That's the story that gets told.

Most of these failures are file failures, and most file failures come from the same place: something on the live site pointing at a link nobody controls. A Google Drive share. A Dropbox link someone tidied away. A freelancer's account that got closed. The site looks fine in the Webflow designer, and quietly breaks in the real world.

This is the problem Flowdrive exists to remove. Every file a client's visitors touch, hosted on something built to serve it, with a link that doesn't expire, change, or depend on anyone's personal account. Paste it into Webflow once and stop thinking about it.

They notice speed, but only when it's slow

Nobody ever emails to say "the site feels fast." They only email when it doesn't.

What clients experience as "slow" is rarely the whole page. It's usually one thing: a hero video that stutters, a gallery of uncompressed images, a 60MB catalogue that takes a full breath to start downloading. They won't diagnose it. They'll just say the site feels heavy, and that impression sticks to the whole build.

Agencies that avoid this keep the heavy stuff off Webflow's own assets and on hosting made for delivery. Big files load from somewhere built to serve big files, and the page itself stays light. Same for downloads. A visitor should click, and the file should simply arrive.

They notice whether they can find things themselves

There's a version of a client relationship where every small change goes through you. New PDF? Email the agency. Updated price list? Email the agency. Swap the team photo? You get the idea.

Clients tolerate this. They don't love it. Every one of those emails is a small reminder that they don't really have control of their own site, and that reminder compounds over a year.

The agencies clients rave about give them a place. Their files, organized by page or by type, where marketing can drop in a new resource and get a link without waiting on anyone. That's why Flowdrive organizes everything by client. Each client gets their own space, uploads what they need, and the agency stops being a bottleneck for a two-minute task.

The strange thing is that doing less for clients here makes them value you more. You're no longer the person they have to email to change a PDF. You're the person who set things up so they never have to.

They notice when something disappears

This one catches agencies off guard.

A client comes back after six months for phase two. They ask where the original case study files are, or the video from the launch campaign, or the hi-res version of the founder's headshot. And the answer, too often, is a pause, a search through three storage accounts, and an apologetic "let me find that."

Clients read that pause as carelessness with their stuff. Even if you find it, the moment where you didn't know where it was is what they'll keep.

Keeping live assets in one place that you control, with the client's name on it, means the answer to "where is…" is always a link, never a hunt.

They notice numbers, when you give them numbers

Here's something clients notice that you might not be showing them: proof.

"The resource section is doing well" is a feeling. "The onboarding guide has been downloaded 900 times since March and the two older whitepapers have had nine between them" is a fact, and it's one that leads to a conversation about what to build next.

Clients notice when an agency walks into a review with numbers on the actual things they built. Most agencies have site analytics. Far fewer can say what's happening to individual files. Flowdrive tracks requests per file, so every download, every embed, every play has a number next to it. It's a small thing that makes an agency look like it's paying attention, because it is.

They notice surprises on the invoice

Last one, and it's the one that ends relationships.

A client's site has a great month. A guide gets shared on LinkedIn. A product video gets embedded by a partner. Traffic jumps. The client is thrilled.

Then the hosting line on the invoice is three times what it was, because whatever was serving the files charges by bandwidth and the good month cost more. Now the agency is explaining why success is expensive, and no amount of design polish fixes that conversation.

Flowdrive charges by requests instead. A visitor opening a file counts once, whatever the file size, and repeat visits don't count at all. The hosting cost a client was quoted stays the cost they pay, including in the month everything goes right. It's a boring feature. It's also the reason nobody has that phone call.

What this means for how you build

None of this is an argument against craft. The pricing toggle should still be lovely. But if the list of things clients notice is broken things, slow things, whether they can help themselves, whether their stuff is safe, whether you can prove it works, and whether the bill makes sense, then the file layer of a site is doing a lot more work than most agencies give it credit for.

It's the layer that's invisible when it works and unforgivable when it doesn't.

Flowdrive is that layer, built for Webflow and no-code sites. Permanent links, organized by client, with per-file numbers and pricing that doesn't move with traffic. No code on your end. The free plan covers a good amount of requests a month, enough to move one client site over and take the file layer off your list of things that can go wrong.

Then go spend your two days on the toggle.

Try Flowdrive free →