Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Leaders and teams rolling it out.
Leaders and teams rolling it out
36 sources. Accounts from departments and data teams, including client consultants and leaders deciding a company rollout.
Individual users
23 sources. Accounts from individual data engineers and analysts, including developers testing their own data.
All users
59 sources. All reviewed accounts, combining individual trials with team pilots. Their conclusions differ.
59 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual userOne person using it for their own work23 sources
Emphasizes Semantic views, wrong answers, and keeping dashboards
- Small team2 to 10 people sharing it2 sources, counted here
Emphasizes Replacing hand-built chat apps, and topic-specific semantic views
- DepartmentA department, or a named company's team30 sources, counted here
Emphasizes Fast setup, cost, and where business users should ask
- IT & leadershipIT and business leaders deciding the rollout3 sources, counted here
Emphasizes Semantic views only, and CoWork against Claude over MCP
- Organization-wideCompany-wide rollout1 sources, counted here
Emphasizes Managing CoWork grants as code across a company
What changes with scale. Individual builders talk most about semantic views and wrong answers. Team accounts shift to how fast an agent goes live, what it costs, and whether business users should ask in CoWork or in Claude, ChatGPT, or Teams. At company scale, Xero's request to manage Snowflake Intelligence grants in Terraform is the one public account.