A while ago, we introduced @Beew Studio V2.0.
We redesigned the studio and introduced our Design Subscription.
But that was only the first part.
Now we're rebuilding what happens behind Beew, too.
We're building Beew Hive, our own platform for running projects, collaborating with clients, and connecting the workflows behind the studio.
Alongside it, we’re rebuilding the technical foundation of Beew:
→ a new public website
→ a structured content system
→ Beew Hive (Client portal)
→ internal workflows & automations
→ a shared design system across everything
This time, I’m going to build it in public.
Sharing the product decisions, design explorations, technical choices, mistakes, and everything we learn along the way.
Next chapter of Beew V2.0 ↓
A while ago, we introduced @Beew Studio V2.0.
We redesigned the studio and introduced our Design Subscription.
But that was only the first part.
Now we're rebuilding what happens behind Beew, too.
We're building Beew Hive, our own platform for running projects, collaborating with clients, and connecting the workflows behind the studio.
Alongside it, we’re rebuilding the technical foundation of Beew:
→ a new public website
→ a structured content system
→ Beew Hive (Client portal)
→ internal workflows & automations
→ a shared design system across everything
This time, I’m going to build it in public.
Sharing the product decisions, design explorations, technical choices, mistakes, and everything we learn along the way.
Next chapter of Beew V2.0 ↓