After talking to Webflow power users, we found that many of them were already using “utility-based” frameworks like Client-First or MAST (similar to Tailwind, but built for Webflow by Webflow power users) and (in our CEO David’s words) “think in classes”. Our research told us that a) enabling more, better code reuse was an almost universal need across all customer segments, and b) our solution should, like Webflow’s other powerful capabilities, be rooted in the web platform.