Three years earlier we made Zenedu a landing page. When they came back, the product had grown into a full platform — courses, subscriptions, payments, channels — running on an interface built for something much smaller. Every new feature made it harder to use, and the team spent more time explaining screens than building them.
We started with what the platform had become, not what the old screens said it was: twenty flows, one map, one language for naming things. Then a system before screens — tokens, components and rules, so both themes and dozens of states come from one source. And the messy states first: empty folders, failed payments, bulk moves, the places where products usually fall apart.
After twelve weeks the system was handed over, and Zenedu’s own team ships on it today. What began as a landing page became a long-term product partnership.
