In general I'd always lean toward a standard reporting tool for a few reasons: 1. Error-prone-People make mistakes building dashboards: a wrong aggregation or join, and the numbers just aren't reliable anymore. Standard tools at least enforce some baseline of modeling and validation. 2. Maintenance- burden Self-built dashboards need active upkeep. When data sources or requirements change, they break quietly, and nobody notices until someone questions the numbers. 3. Bus factor -The biggest risk: the person who built it leaves or is out, and now there's a system nobody understands or wants to touch. Standard tools have a known structure and ecosystem of docs/support, so onboarding a successor is much easier. That said, I use both - self-built dashboards only when I hit specific limitations in reporting tools, usually around visualizations. For me that's an ad-hoc data request, not a long-term replacement. I wouldn't currently recommend it as a substitute for a standard BI tool in a business workflow, mainly because governance, security roles, and sharing are usually missing or have to be built from scratch in custom solutions.

@Tariq Belgharouadi Just as a heads up, Google Sheets nodes tend to hit rate limits pretty quickly once a workflow scales up. It's worked fine for smaller/simpler setups, but anything with higher volume or frequency runs into throttling issues fast.

Amazing 💯

Both together 💯