What Notion users actually want
Mimir analyzed 15 public sources — app reviews, Reddit threads, forum posts — and surfaced 10 patterns with 6 actionable recommendations.
Top recommendation
AI-generated, ranked by impact and evidence strength
Add full audit trail with change explanations for every Custom Agent action
Rationale
A power user explicitly demanded that agents never modify content silently and must state why changes were made, what changed, and propose the updated version. The intensity of this requirement (repeated multiple times in Spanish) signals hard-learned pain from opaque AI behavior. This friction point directly undermines the workflow automation value Custom Agents promise. If users fear invisible modifications, they will avoid delegating high-stakes tasks to agents, capping engagement depth.
Theme 1 shows enterprises already require full audit trails for compliance, but the current implementation may not surface sufficient context at the moment of change. Users need inline explanations (not just logs) showing reasoning before execution. This addresses both the trust erosion in Theme 5 and the enterprise transparency requirements in Theme 1.
If you don't build this, Custom Agents remain confined to low-risk workflows. The 100 percent migration to agent-driven work reported in Theme 0 will stall once teams hit tasks requiring reversibility confidence or collaborative review. The gap between 'every run is logged' and 'I understand why this happened before I see the result' is the difference between adoption and abandonment for complex workflows.
More recommendations
5 additional recommendations generated from the same analysis
Private Slack channel support is explicitly noted as coming soon, signaling Notion recognizes this blocks high-value workflow automation for security-conscious teams. Many enterprises (62 percent of Fortune 100 per Theme 2) discuss sensitive topics in private channels—customer negotiations, financial data, personnel decisions. Without this, Custom Agents cannot automate the highest-leverage work, forcing teams to keep critical workflows in external tools and undermining the consolidation promise.
Users can view Google Calendar and iCloud events alongside Notion database items, but cannot import calendar events into databases or sync changes bidirectionally. This limitation breaks the single source of truth narrative in Theme 2—teams still manage calendars in parallel tools instead of consolidating into Notion. The absence of this feature when integration is heavily positioned suggests implicit user need.
Custom Agents are free until May 2026, after which pricing shifts to a workspace add-on based on Notion credits that reset monthly without rollover. This creates budget unpredictability for teams with variable automation needs—a team that builds ten agents for a product launch may consume credits unevenly, wasting budget in slow months and facing overages during peaks. The absence of rollover punishes efficient usage and forces monthly re-budgeting conversations.
A power user manually simulating database features (SQL files, integrity validation, concurrency control) within Notion explicitly acknowledged the system cannot execute SQL or validate real database integrity. While the user accepted these limitations for prototyping, the need to work around missing database primitives reveals a ceiling on complexity for technical teams. Theme 0 shows Custom Agents already integrate with Linear, GitHub, Figma, HubSpot, Ramp, and Stripe—adding database connectors would unlock engineering and data team workflows currently impossible in Notion.
Notion Calendar and mobile apps support phones, but optimized tablet experiences are still in development. For users who work across multiple devices (desk to couch to travel), incomplete tablet support fragments the unified workspace promise. Product managers often review roadmaps on iPads during offsites, founders sketch strategy on tablets in meetings, and engineering leads triage issues on Android tablets during incident response. If the experience degrades on tablets, users keep separate tools for mobile-first contexts.
The full product behind this analysis
Mimir doesn't just analyze — it's a complete product management workflow from feedback to shipped feature.
Themes emerge from the noise.
Ranked by severity and frequency, with the original quotes inline so you can judge for yourself.
Talk to your research.
Ask questions, get answers grounded in what your users actually said.
What's the top churn signal?
Onboarding confusion appears in 12 of 16 sources. Users describe “not knowing where to start” [Interview #3, NPS]
A prioritized backlog, not a wall of sticky notes.
Ranked by impact and effort, with the reasoning you can actually defend in a roadmap review.
PRDs, briefs, emails — on demand.
Generate documents that reference your actual research, not generic templates.
Paste, upload, or connect.
Transcripts, CSVs, PDFs, screenshots, Slack, URLs.
This analysis used public data only. Imagine what Mimir finds with your customer interviews and product analytics.
Try with your data