How a Small Team Ships Four Products at Once
- BY
- ROOT TEAM
- PUBLISHED
- JULY 20, 2026
- READING TIME
- 1 MIN READ
Four products in beta, one team, zero managers. This is the operating system we run. Shared principles, separate codebases, ruthless scope.
The most common question we get is how four products stay alive with one small team. The honest answer is most of the magic is subtraction, not addition.
Shared principles, separate products
Every product shares the same foundation. TypeScript end-to-end, the same design language, the same deploy pipeline. That means context switching between products costs hours, not days.
But each product has its own codebase and its own release cadence. A stalled idea never blocks a shipping one.
Scope is the feature
Each product does one job. Zyren schedules content, it doesn't edit videos. Lumex tracks portfolios, it doesn't trade them. When we feel tempted to expand, we ship the core tighter instead.
The result is maintenance stays cheap, and cheap maintenance is what lets a small team keep four things live at once.
Weekly rhythm
Monday. Pick the single most important thing per product. Wednesday. Internal demo or it didn't happen. Friday. Ship, write the changelog, go offline. Boring? Yes. Effective? Also yes.