# Q2 Customer Feedback

Source: sales calls, support notes, product interviews, and pilot discussions
Period: 2026 Q2

## Feedback Items

1. "The AI answer is useful, but I do not know what source material it used."
2. "Our compliance team needs to see a trace of tool calls and file access before approving a pilot."
3. "The demo is strong when it turns a request into a task. Please make that the first thing users see."
4. "We want daily and weekly reports to run automatically, not only when someone asks in chat."
5. "The Outlook connector would be valuable if it can summarize customer emails and draft replies."
6. "We do not want every employee pasting company data into public SaaS tools."
7. "The Files page is useful, but users need clearer examples of what to upload."
8. "The task detail page helps reviewers understand what happened."
9. "The Skills concept is important. It means our team's best working methods can be reused."
10. "Skill publishing should require human approval. We do not want low-quality automations spreading."
11. "The interface has many pages. New users need a guided first workflow."
12. "Management will ask how this is different from ChatGPT Team or Copilot."
13. "The strongest value is repeatable knowledge work: weekly reports, customer feedback summaries, project risk reviews."
14. "We need a clear admin story: status, logs, provider configuration, connector health."
15. "Some users asked whether Beaver can run terminal commands. Security wants policy controls around that."
16. "The first pilot should avoid too many external integrations."
17. "We need to measure accepted tasks, revision rounds, and time saved."
18. "The model sometimes gives too much detail. Executive summaries should be shorter."
19. "Private deployment and per-user instance boundaries are important for enterprise buyers."
20. "The demo should show a failed or revised answer, because review is part of real work."

## Raw Themes Observed

- Trust and auditability
- Task lifecycle beyond chat
- Reusable skills and method capture
- Scheduled recurring work
- Private deployment and admin control
- Connector demand, especially email
- Need for simpler onboarding and clearer demo story