Hi,
I was reviewing how Supabase handles onboarding from sign-up to project creation, and I noticed something interesting.
It seems users need to go through organization setup and project configuration before they can actually experience the core value (like making their first query or API call).
In similar SaaS systems, this sometimes creates friction before users reach that first success moment, which can impact activation.
I’m curious — was this a deliberate tradeoff in the product design?
Thanks
AboJad is inquiring about the design choice in Supabase's onboarding process, where users must complete organization and project setup before accessing core features. They are curious if this was a deliberate design decision, as it might create friction before users reach their first success moment.