Show HN: Jelly – A simpler shared inbox for small teams

Original Article ↗ Hacker News Discussion ↗

Pricing and Value

  • Strong debate around the $29/month starter price.
  • Some see it as expensive for very small teams, hobby projects, and families, especially when stacked with other subscriptions.
  • Others emphasize it’s a flat team price (not per-seat), calling it cheap relative to employee salaries and typical SaaS alternatives.
  • Several suggest a cheaper “micro-team / duo” tier and special discounts; the team signals willingness to work with nonprofits and similar groups.
  • Concerns raised that “unlimited users” is risky; suggestion to introduce sensible caps (e.g., 1k–10k).

Product Philosophy & Positioning

  • Makers explicitly reject profit maximization and per-seat pricing, aiming to serve small teams that feel overcharged or underserved by bigger tools.
  • The product is framed as “does a few things well” vs. full-blown help desk platforms (Intercom, Zendesk, etc.).

Use Cases and Comparisons

  • Core pain: shared addresses handled via Google Groups, shared Gmail/Fastmail accounts, or filters/forwarding make it hard to see who owns a conversation, coordinate replies, and discuss internally.
  • Jelly’s value: assignment/“who has the ball,” inline discussion, activity views, and easy sharing of conversation URLs.
  • Some believe Google Workspace/O365 built-ins are “good enough,” especially when already paying per-seat.
  • Others compare to tools like Front, Missive, Chatwoot, Zammad, osticket; Jelly is praised for simplicity and pricing versus those.
  • Interest in family and household use (schools, medical, bills), but many feel $29/month is high for personal scenarios.

Technical Stack & Integrations

  • Built on a straightforward Rails + Postgres stack, deployed via Render with automated GitHub deploys.
  • Uses Postmark for inbound/outbound email.
  • Current workflow: forward mail from any provider into Jelly.
  • Higher-tier “Royal Jelly” offers IMAP-based sent-mail sync (e.g., back into Gmail); some want IMAP access on lower tiers for risk-free trials or mutt/desktop workflows.
  • Slack integration exists; potential future deeper provider integrations are hinted at.

Onboarding, Lock-in, and Reliability

  • Multiple commenters worry about adopting a shared inbox tool that might shut down or hike prices later, citing prior bad experiences.
  • Requests for clear data export paths and smooth fallback options; Jelly’s team stresses they’d help customers exit cleanly with their data.
  • Email deliverability is flagged as a concern after a verification email went to spam; the team treats this as serious and invites direct troubleshooting.

UX, Messaging, and Misc Feedback

  • Landing page and UI widely praised as clean, simple, and “decent.”
  • Some copy (“jam on email”) polarizes readers; others enjoy the playful tone and easter eggs.
  • Minor issues reported: CSS glitches, YouTube video requiring an account, and wording confusion on pricing explanation.