The brief
Flowdrive lets Webflow teams host videos and files on their own domain, without surprise bandwidth bills or a patchwork of Vimeo, S3 and CDN accounts.
The audience is designers and agencies. They don’t want to read about CDNs; they want to know the video will load and the client won’t call them about it.
The goal
Make a technical product feel simple and trustworthy in the first screen, then answer the real objections (cost, speed, where data lives) further down, in the order people actually think of them.
Decisions on the first screen
Every element above the fold has one job.
- serif = calm
Hosting is stressful, so the type isn’t. A large editorial serif makes a developer tool feel friendly and premium.
- one button, one promise
A single orange call to action. No competing “Book a demo”: the product is self-serve, so the page is too.
- answer the first worry
The EU data note sits right under the button, because “where does my data live?” is the first question agencies ask.
- proof, fast
Customer logos come straight after, before any feature talk.
Showing the problem instead of explaining it
The section after the hero is where most visitors decide if this is for them.
- their words, not ours
The headline quotes the client’s complaint. Designers recognise themselves before they read a single feature.
- the mess, drawn
“Before” is a literal tangle of tools and a red $$$$ tag. One glance says “this is your stack today”.
- the fix, tidy
“After” uses the same layout so the eye compares row by row. Six neat tiles replace the tangle.
Desktop and phone
The headline and the button keep their weight on a small screen; the layout re-stacks rather than shrinks.
What I learned
On a technical product the copy is the design. Once the headline was right, the layout got simpler, not busier.
Next time
I’d test a shorter version of the hero subheading and track which objection section people scroll back to, to reorder the page around real behaviour.