Look at count.co for a Figma-like approach to databases.
We were using it at work (transitioning to Metabase); it's great for exploring and debugging and prototyping but it ends up too much of a tangled spaghetti mess for anything long-term. Would not recommend for user-/other-company-departments-facing reports or dashboards.
That's super interesting!
With Kavla I want to lean into the exploring/debugging phase for analytics. "Embrace the mess", in a way.
My vision is that there will be an "export to dbt" button when you're ready to standardize a dashboard.
What made you pick count? Was spaghetti the major reason you left count, or something else?