MimirMimir
GuideSecurityContactSign in
All analyses
Combinely logo

What Combinely users actually want

Mimir analyzed 9 public sources — app reviews, Reddit threads, forum posts — and surfaced 18 patterns with 6 actionable recommendations.

0
sources analyzed
0
signals extracted
0
themes discovered
0
recommendations

Top recommendation

AI-generated, ranked by impact and evidence strength

#1 recommendation

Build enterprise security tier with SSO, RBAC, and customer-managed encryption keys

High impactLarge effort

Rationale

Enterprise controls are blocking high-value customer adoption. The evidence shows a direct gap between current capabilities (SOC 2 Type II, basic encryption) and enterprise requirements (SSO, granular access controls, key management). Firms evaluating AI for tax review operate under strict compliance mandates and need these controls before they can commit.

This is not a nice-to-have — it's an adoption gate. Without SSO and role-based access control, you cannot land multi-partner firms where access governance is non-negotiable. Without customer-managed encryption keys, you cannot serve regulated industries where data sovereignty determines vendor eligibility. The product already has strong foundational security (SOC 2, AES-256, penetration testing), but lacks the operational controls that enterprise buyers require to sign contracts.

If you don't build this, you cap revenue at small firm adoption and miss expansion into the firms that would pay 3-5x for multi-seat deployments. The alternative is watching competitors offer these controls as table stakes and win the deals you cannot close.

More recommendations

5 additional recommendations generated from the same analysis

Extend post-termination data export window from 30 days to 12 months with self-service retrievalMedium impact · Small effort

The 30-day data export window creates lock-in perception and undermines the trust messaging around customer data ownership. Customers handling sensitive tax data need confidence they can retrieve their information on their timeline, not yours. A 30-day window forces rushed migrations and suggests the product is designed to trap data rather than empower customers.

Create subprocessor change notification system with 30-day advance notice and data flow audit logMedium impact · Small effort

Customer data flows through 15 subprocessors with no clear notification mechanism when that list changes. For tax firms operating under compliance mandates, subprocessor changes can trigger re-approval workflows, vendor risk assessments, and client notifications. A living document approach without proactive alerts creates compliance risk that customers discover only when audited.

Clarify Usage Data collection scope with customer-facing dashboard and opt-out controls for non-essential telemetryHigh impact · Medium effort

The Terms of Service grant broad rights to collect and analyze Usage Data derived from customer data, but this contradicts the privacy-first marketing message. Customers who adopt based on the promise that their data is never used for training will feel deceived when they discover the product collects derived insights for product development. This is a trust time bomb.

Redesign billing dispute resolution process with itemized usage reporting and 90-day dispute windowMedium impact · Small effort

The current 30-day billing dispute window creates tight timelines for customers managing per-seat subscriptions across multi-partner firms. Combined with non-refundable advance billing and auto-renewal defaults, this structure maximizes Combinely revenue at the cost of customer trust. Customers who feel trapped by billing terms churn faster and warn peers, especially in relationship-driven industries like accounting.

Build error severity scoring into AI review output to differentiate critical tax errors from formatting inconsistenciesHigh impact · Medium effort

AI review catches 75 percent of common errors, but without severity scoring, reviewers must evaluate every flagged item with equal urgency. This undermines the efficiency claim — if managers still need to triage every flag, review time savings are limited by noise. The value proposition is reducing manager review time by 50 percent, but that requires prioritizing what matters, not just flagging everything.

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.

Critical
12x
Moderate
8x

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.

High impactLow effort

PRDs, briefs, emails — on demand.

Generate documents that reference your actual research, not generic templates.

/prd/brief/email

Paste, upload, or connect.

Transcripts, CSVs, PDFs, screenshots, Slack, URLs.

.txt.csv.pdfSlackURL

This analysis used public data only. Imagine what Mimir finds with your customer interviews and product analytics.

Try with your data
Mimir logoMimir

Where product thinking happens.

Product

  • Guide
  • Templates
  • Compare
  • Analysis
  • Blog

Company

  • Security
  • Terms
  • Privacy
© 2026 MimirContact