Zearn

The initial Webflow build for Zearn had to be designed with expansion in mind, even when the immediate scope was limited. The fact that the same architecture supported a full Enterprise redesign and major content expansion a year later validated that approach entirely.

Zearn's growth eventually required capabilities — multi-editor workflows, advanced CMS structures, higher publish limits — that the standard tier couldn't support. Recognizing that threshold early and recommending the upgrade was the right call for the client's trajectory.

Working with Zearn across multiple years and two site iterations built a level of context about their content workflows and team needs that informed every decision. That depth of understanding is impossible to replicate on a single project.

On large education platforms, a page that's hard to replicate becomes a bottleneck that the content team hits repeatedly. Designing every template with the assumption that it will be duplicated dozens of times changes the decisions you make at every level.