Omentoo vs vanilla LLM, side by side.

## Feedback Summary ### 🔴 Blockers Costing You Revenue Right Now **SSO is a hard gate for upmarket deals.** Two separate signals — Acme Co (evaluating a Team plan) and Liam (already churned) — cite SSO as a non-negotiable. Liam explicitly said he'd come back if you ship it. If you're targeting teams with SOC2 requirements, this isn't a roadmap item, it's a prerequisite. **CSV import is broken for larger files.** Maria (paying, $89/mo, churn risk) and @kev_sales (Discord) both hit failures independently. Maria has 12,000 contacts stuck and is looking at HubSpot. This is an active retention issue, not a feature request. ### 🟡 High-Demand Features With Clear Signal **Linear integration** has unusually consistent demand across totally separate channels: Acme Co asked on a sales call, @sara.builds and two @bryan_indie mentions came from Discord, and — most urgently — Yumi is a trial user who said "if you have it I'll buy today." There's also a 404ing docs page implying this was planned or teased. That broken page is actively blocking a conversion. Fix or redirect it immediately, and treat the integration itself as high priority. **Mobile / PWA** came up from @helena_pm, an App Store reviewer (who docked 2 stars specifically for this), and likely represents a broader silent cohort. The ask is modest — a PWA would satisfy multiple people — and one user said they'd upgrade to 5 stars for it. **Audit logs** were requested by Acme Co alongside SSO. These tend to travel together for compliance-conscious buyers, so they're probably part of the same enterprise readiness package. ### 🟠 Onboarding & UX Friction **The product assumes a team; solo users feel excluded.** Devesh churned explicitly because the workspace setup pressured him to invite teammates he doesn't have, and per-seat pricing felt punishing. This is a positioning and UX issue as much as a pricing one — if you want to serve indie founders, the onboarding flow needs a "just me" path. **Basic navigation is failing trial users.** "How do I export a report?" and "where do I bulk-delete contacts?" (three users in one week) and "is there an API?" are all findability problems. These users aren't asking for new features — they're lost. A better in-app UI, clearer empty states, or a tightened help doc structure would reduce this load without any engineering work. **Notion overlap is causing uninformed signups and quick refunds.** Tomás refunded after four days because the product overlaps with Notion AI and lacks two-way Notion sync. He wasn't unhappy — he just didn't have enough information before buying. Clearer positioning on the landing page ("how we're different from Notion AI") could filter this out and improve conversion quality. ### 🟢 What's Working The core product is genuinely resonating. @vc_alex's tweet about catching a churn pattern in their support inbox is exactly the kind of word-of-mouth you want. The dashboard speed improvement landed well. Liam — who *churned* — still called the synthesis "actually better" than the competitor he switched to. Priya signed up with a real, motivated use case (200+ feature requests in a Notion doc). The retention risk here isn't product quality; it's missing infrastructure and rough edges blocking otherwise-happy users. --- ### Suggested Priority Order | Priority | Item | Why | |---|---|---| | 🔴 Immediate | Fix CSV import for files >5MB | Paying customer at churn risk | | 🔴 Immediate | Fix/redirect the Linear 404 doc | Blocking a trial conversion today | | 🔴 Short-term | SSO | Hard gate on enterprise deals; churned a customer | | 🟡 Short-term | Linear integration | Multi-channel demand, direct conversion signal | | 🟡 Short-term | Solo/single-user onboarding path | Pricing and UX misfit driving churn | | 🟠 Medium | PWA / mobile | App Store rating + multiple requests | | 🟠 Medium | Audit logs | Pairs with SSO for compliance buyers | | 🟠 Medium | Navigation & help docs | Reducing repetitive support load | | ⚪ Ongoing | Notion positioning on marketing site | Filtering low-fit signups |