Skip to main content

Ever Async — MVP scope

The product thesis (from the founding LinkedIn post): good async communication is not writing more — it's giving people enough context to respond without a ten-message discovery process.

Scope calls​

  1. One platform first: Slack. Slack + Discord + WhatsApp is three MVPs, not one. Discord ships real — signed interactions, /async, buttons and full egress — but without a Gateway client, so message classification runs on Slack only. Discord delivers ordinary messages over a websocket, never by webhook, and that connection is its own project.
  2. Three connectors: GitHub + Jira + Ever Gauzy. They cover "the PR" and "my last task" — the canonical examples.
  3. Cut entirely for now: WhatsApp/Teams/Telegram channels, the "ChatGPT/Claude personal prompting coach" idea (different product), auto-posting on the author's behalf (nudges suggest, humans post), dashboards beyond the basic admin app.

MVP features​

  1. Per-channel opt-in Slack app — reads only channels it's invited to; no retention beyond the processing window. Trust is the adoption gate.
  2. Low-context detection — deterministic heuristics (naked greeting, artifact-without-link, contentless help plea) + optional LLM for the ambiguous middle, gated by sensitivity.
  3. Private nudge, never public — after a grace window (default 150s) with no self-correction, the author gets an ephemeral message with reasons + a suggested rewrite. The single most important design decision: a bot that corrects people publicly gets uninstalled in a week.
  4. Auto-context enrichment — "the PR" / "my last task" resolved via connectors (author + recency), posted as a thread card when confidence clears the policy threshold; below it, nothing public happens.
  5. Context cards for pasted links — (post-MVP polish; native unfurls partially cover this) — our differentiator is resolving missing links.
  6. Team communication charter — the workspace's own rules, cited by every nudge; editable; defaults to the three founding rules.
  7. /async slash command — status/on/off/sensitivity/delay/charter/ digest, per conversation.
  8. Weekly digest — messages observed, nudges sent, context attached; the manager's reason to keep it installed.

Riskiest assumption​

People tolerate an AI commenting on their communication at all, even privately. Mitigations: conservative-by-default sensitivity (precision over recall), grace window with self-correction cancel, charter framing ("your team's rules"), and the nudge always saving the author time (one-click-able rewrite) rather than assigning homework.

Direction after MVP​

Tools for async work, starting from communication: someone does something → Ever Async prepares the context (or the artifact) → the next person continues without a synchronous round-trip. Example: a file lands in a channel → AI reviews it → posts what's needed so the async collaborator starts warm.