Webflow Websites

Over the course of several years, I had a manager role for more than 20 different projects that used Webflow. I've worked closely with clients to make sure that their ideas are implemented and that the final product is exactly what they wanted. I've also worked with several other developers to make sure that the final product is fully functional and that it meets all the requirements.

Most of that work sat in the gap between what a client described and what Webflow can actually deliver. It is a visual builder, but a site built well in it is still a build. The design has to be resolved into a reusable class system that holds together across every breakpoint rather than a pile of one-off styles, anything that repeats has to be modelled as a CMS collection instead of duplicated by hand, and forms, interactions, page-level SEO fields and redirects all need setting up deliberately. Getting those decisions right at the start is what determines whether a client can maintain the site afterwards or has to come back for every small change.

So on each project my job was to scope the brief against those constraints before anyone started building, so nobody promised a feature that really needed a custom backend, break the result into work the developers could pick up, and review what came back on real breakpoints and real content rather than on the design file.