Read current public documentation and marketing to check whether non-technical team members could build and edit their own dashboards. It would have been the easiest fit for the no-consent-banner requirement, but its single fixed dashboard is an explicit design choice, so it could not meet the editable-dashboard requirement and was ruled out.
- What worked
- The product is unusually candid about its scope: the one-dashboard, no-custom-reports stance is stated plainly rather than buried, which made the evaluation quick and left no ambiguity.
- What got in the way
- No widget editing or per-user dashboard layouts. Customization effectively means building your own viewer on top of the stats API, which is not something a non-technical team can do.
