Missive vs Zero

Multi account

1. switcherConnect several accounts across providers — Gmail, Microsoft 365, IMAP — and work them from one place

   weight 3 · round to Missive
   Missive~partialclaimed4/10

   Evidence only touches this obliquely: contacts management explicitly 'syncs with Office 365 and Google' (missive-docs-23), and shared/team inboxes are documented (missive-docs-32, missive-docs-28), implying multi-account consolidation, but there is no explicit documentation in the pack of connecting Gmail, Microsoft 365, and generic IMAP accounts as email sources worked from one unified inbox. Missing for 10: explicit account-connection docs for Gmail/O365/IMAP email (not just contacts sync), and confirmation that all provider types can be combined in one inbox view.

   • [claimed-docs] “Manage your contacts in shared or private address books. ✓ Syncs with Office 365 and Googl”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other’s toes.”

   proof ↗⚑ flag

   Zero!disputedcontradicted4/10

   Zero's marketing repeatedly claims a 'Unified Inbox' connecting Gmail, Outlook, 'and more,' but the only hands-on/community description of the actual product (zero-comm-1) says it 'works on top of Gmail' and is in public beta, suggesting multi-provider (Microsoft 365, IMAP) support isn't yet realized in practice — no IMAP mention anywhere in the pack. Missing for 10: explicit IMAP support, confirmed working Microsoft 365/Outlook connection, and independent verification that multiple accounts can be worked from one place simultaneously.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Portability

1. switcherMy mail stays reachable over open protocols and standard formats — IMAP/JMAP/SMTP access and standards-based export — so no client can lock me in

   weight 2 · round drawn
   Missive—none0/10

   The evidence pack contains no mention of IMAP, JMAP, or SMTP access for user mailboxes, nor any standards-based export functionality; all connectivity evidence is about REST API, webhooks, and MCP integrations for AI/automation, not about open mail protocol interoperability or data portability for switchers.

   ⚑ flag

   Zero—none0/10

   Evidence shows Zero connects to providers like Gmail/Outlook and offers self-hosting and an MCP server for AI actions, but nothing in the pack mentions IMAP/JMAP/SMTP protocol access or standards-based mail export for portability — the core of this switcher story is unaddressed.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [claimed-docs] “Self-hosting capabilities”

   proof ↗⚑ flag

2. switcherSelf-host the email app and keep the mail pipeline under my own control

   weight 1 · round to Zero
   Missive—none0/10

   Missive is a cloud-hosted SaaS collaboration/email platform with no documented self-hosting option; community evidence confirms mail data routes through Missive's own servers (missive-comm-1), and no docs mention on-premise or self-hosted deployment.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

   Zero✓fullprobed7/10

   Zero is explicitly open-source and self-hostable, with GitHub docs stating 'Self-Hosting Freedom – Run your own email app with ease' and a probe confirming a real, keyless-cloneable source tree with docker-compose files for self-hosting the full mail pipeline (DB, prod services). This gives a switcher genuine control over their own instance rather than relying on a hosted SaaS. Missing for 10: detailed self-hosting setup/migration docs (e.g. IMAP/SMTP backend specifics), independent hands-on reports of a completed self-hosted deployment, and confirmation of full mailbox portability beyond Gmail/Outlook OAuth integration.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Self-hosting capabilities”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Zero
   Missive—none0/10

   Direct probes show no llms.txt, no docs.md, and no OpenAPI spec exposed at expected locations (all 404), and no evidence of agent-oriented documentation formats being offered elsewhere; while Missive has an MCP server (a different axis), there's no proof an agent can be pointed at llms.txt or similar agent-readable docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   The repo ships an AGENT.md (agent-configuration doc) and a detailed MCP.md describing the MCP server's tool surface, both of which are exactly the kind of machine/agent-oriented documentation an AI agent could be pointed at; this was confirmed by a hands-on probe of the actual repo tree. However there is no evidence of a dedicated llms.txt file or any explicit guidance framing these docs as an 'agent-readable spec' in the llms.txt convention. Missing for 10: an actual llms.txt file, first-party statement that docs are structured for LLM consumption, and independent confirmation an agent successfully parsed these docs.

   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Missive
   Missive~partialprobed3/10

   Missive exposes a REST API, webhooks, and a documented MCP server that let external systems and AI agents trigger actions without using the UI, which could be scripted from CI/automation pipelines. However there is no evidence of an official CLI, headless mode, Docker/container deployment, or CI-specific documentation/examples for running Missive itself in automated pipelines. Missing for 10: dedicated CLI or headless execution mode, CI/CD integration guides, and independent confirmation of automation-in-CI use cases.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “API & MCP access”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Missive
   Missive✓fullclaimed8/10

   Missive documents a clear custom-MCP flow: users add a 'Custom MCP' server with a URL and auth, and 'connect any MCP-compatible server to Missive's AI Copilot' to let the assistant use internal APIs, databases, or custom tooling, alongside pre-built MCP integrations (Notion, Linear, Attio, Lindy.ai). Missing for 10: independent/hands-on verification of the custom MCP connection flow beyond vendor docs, and more detail on tool invocation limits or reliability.

   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “Add "Custom MCP" and enter a name and your server URL. Choose an authentication method and click Add”
   • [claimed-docs] “Missive ships with ready-to-use MCP integrations for Notion, Linear, and Attio, plus AI automation platforms like Lindy.ai.”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”
   • [claimed-docs] “Connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprietary data, or homegrown too…”
   • [claimed-docs] “Extend capabilities beyond Missive's built-in MCP integrations”
   • [claimed-docs] “Missive ships with ready-to-use MCP integrations for Notion, Linear, and Attio, plus AI automation platforms like Lindy.ai. The assistant ru…”

   proof ↗⚑ flag

   Zero—none0/10

   All evidence describes Zero exposing its own email/label/compose tools via an official 'ZeroMCP' server for other AI agents to consume — i.e., Zero acting as an MCP server/provider, not as a client that plugs in external MCP servers to use their tools. There is no documentation of Zero itself connecting to third-party MCP servers to extend its own toolset.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Missive
   Missive✓fullprobed9/10

   Missive explicitly documents an official MCP server that lets external AI apps (Claude, ChatGPT, Cursor) connect and act on conversations, contacts, calendar, and drafts with configurable permissions, and a dedicated docs page for the MCP server is confirmed to exist via probe. Missing for 10: independent/hands-on third-party confirmation that external agents successfully connect and operate via this server.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”
   • [claimed-docs] “API & MCP access”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a documented, named 'Zero MCP' server (MCP.md) exposing concrete tools (email CRUD, labels, AI compose, mailbox Q&A, web search) with an authentication method (Better Auth session token, OAuth coming soon), confirmed by an independent runtime probe finding the file in the actual repo. Missing for 10: independent hands-on verification that a third-party agent successfully connects and uses the server end-to-end, and OAuth is still unimplemented.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Missive—none0/10

   Missive is an email/collaboration app offering REST API, webhooks, and MCP integrations, but no evidence anywhere in the pack mentions an official CLI tool for interacting with Missive. Probes for docs/openapi manifests return 404s, and no CLI-related changelog or docs entries exist.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”
   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero's evidence shows an MCP server (ZeroMCP) and self-hosting via docker-compose, plus a pnpm-based dev script for Drizzle Studio, but no official CLI tool for AI-native interaction with the product itself is documented anywhere in the pack.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Missive✓fullprobed8/10

   Missive documents a REST API, webhooks, UI integrations, and custom channels for developers (missive-docs-31/39/15), plus an official MCP server exposing conversations, contacts, calendar, and drafts to AI apps like Claude/ChatGPT/Cursor (missive-docs-1/20, missive-probe-4). This gives AI-native users a documented, programmatic way to drive the product beyond the UI. Missing for 10: a discoverable OpenAPI/swagger spec or llms.txt (all probed and 404'd) and independent third-party corroboration of API robustness.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”
   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”
   • [claimed-docs] “API & MCP access”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a documented MCP server (ZeroMCP) exposing a public, structured API for emails, labels, AI compose, mailbox Q&A, and web search, with authentication documented via Better Auth session tokens (OAuth coming soon), corroborated by a runtime probe confirming the real MCP.md and AGENT.md files in the repo. missing for 10: independent third-party usage/testing of the MCP API beyond first-party docs and a single runtime probe, and full OAuth support (currently listed as coming soon).

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Missive
   Missive~partialclaimed5/10

   Missive's MCP integration explicitly notes external AI apps connect "with the permissions you choose" (missive-docs-20) and custom MCP setup lets you "choose an authentication method" (missive-docs-17), implying some scoped access control for agents. However, there's no documentation of granular API-key scopes, role-based permission tiers, or a dedicated credential-issuance UI for least-privilege agent access. Missing for 10: explicit scoped API key/token generation flow, documented permission levels/roles for agents, and independent confirmation that scoping is enforced in practice.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Add "Custom MCP" and enter a name and your server URL. Choose an authentication method and click Add”
   • [claimed-docs] “API & MCP access”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”

   proof ↗⚑ flag

   Zero—none0/10

   Zero's MCP server documents authentication via a Better Auth session token (or future OAuth), but there is no evidence of scoped or least-privilege credential issuance, permission granularity, or agent-specific token scoping — auth appears to be a single session-level token granting full account access. Missing for 10: any documentation of scopes/permissions models, per-agent credential minting, or restricted-access tokens for agents.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Zero
   Missive—none0/10

   Missive documents a REST API, webhooks, custom channels, and MCP integrations for developers, but no evidence anywhere mentions official client SDKs (e.g. language libraries) for building against Missive; probes even show 404s for OpenAPI/spec files that would typically back SDK generation.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”

   proof ↗⚑ flag

   Zero~partialprobed5/10

   Zero doesn't publish a traditional language SDK, but it does document an official 'ZeroMCP' server (MCP.md) with concrete tool endpoints (email CRUD, labels, AI compose, mailbox Q&A) plus AGENT.md agent-configuration docs, giving AI-native developers a documented, official programmatic interface to build against, corroborated by a runtime probe confirming these files exist in the live repo. Missing for 10: an actual client SDK/library (Python/JS package), auth beyond a session token (OAuth marked 'coming soon'), and independent third-party developer usage reports.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [github] “🚀 Developer-Friendly – Built with extensibility and integrations in mind.”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Missive
   Missive~partialclaimed4/10

   Missive's developer tools page explicitly lists webhooks alongside REST API and custom channels, confirming the capability exists, but there is no detail on event types, subscription setup, payload format, or independent corroboration of webhook usage. Missing for 10: documented list of subscribable event types, webhook setup/config instructions, security/signing details, and third-party confirmation of reliability.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence covers Zero's MCP server (tool-calling actions like search, compose, label management) but nowhere mentions webhooks, event subscriptions, or push notifications for external systems to react to inbox events.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Zero
   Missive~partialclaimed5/10

   Missive's AI assistant can summarize inboxes, draft replies, and triage conversations against connected data (CRM, docs) via MCP, and can compose/reply/translate with AI, which counts as AI-generated insights/suggestions from data. However, evidence is mostly marketing copy without hands-on demonstration of proactive 'insights' (e.g., analytics-driven suggestions) and no independent corroboration of quality or accuracy. missing for 10: independent/hands-on verification of insight quality, concrete examples of proactive analytics-style insights beyond summarization/drafting, and detail on how suggestions are surfaced in UI.

   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”

   proof ↗⚑ flag

   Zero✓fullprobed7/10

   Zero documents AI features that generate insights from mailbox data: composing emails with AI assistance, answering questions about mailbox content and specific threads, and summarizing/chatting with inbox content, corroborated by founder description of AI-powered summarization and chat-with-inbox in community coverage. missing for 10: independent hands-on verification of insight quality/accuracy and no broader third-party review confirming these AI features work reliably in practice.

   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Missive
   Missive~partialclaimed7/10

   Missive documents rule-based workflow automation (up to 1000 rules) and long-running AI assistant sessions that operate in the background with a session tab showing progress ('no longer need babysitting'), plus agent-driven triage of conversations against a CRM before a human looks at them — evidence of autonomous background automation. However, there's no independent/hands-on confirmation of reliability or scope of autonomy, and details on triggers/scheduling for rules are thin. Missing for 10: independent corroboration of autonomous execution reliability, deeper documentation on rule triggers/scheduling and failure handling.

   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “The session tab now shows what the assistant is up to, and a conversation links back to the sessions attached to it.”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows an MCP server exposing on-demand email tools (search, compose, label, delete) that an AI client can call interactively, but nothing shows Zero itself scheduling or running autonomous background automations/triggers/workflows without a user or agent actively invoking them.

   ⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Zero
   Missive✓fullclaimed7/10

   Missive documents a built-in AI Assistant/Copilot that can compose, reply, translate, triage conversations against CRM data, and run extended 'sessions' with a visible status tab, plus access internal tools via MCP — all delegatable from within the product (missive-docs-49, missive-docs-34, missive-docs-22, missive-docs-16, missive-docs-52). Missing for 10: independent/hands-on evidence of actual task delegation outcomes and more detail on assistant capabilities/limits beyond first-party changelog blurbs.

   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “Give your AI assistant access to your own tools and internal systems, directly from Missive.”
   • [claimed-docs] “The session tab now shows what the assistant is up to, and a conversation links back to the sessions attached to it.”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a built-in AI assistant that can compose emails, answer questions about threads/mailbox, and perform web search (Perplexity), confirmed both in docs (MCP.md) and independent community description of it as an 'AI-powered email client' that summarizes, drafts, and lets users chat with their inbox. Missing for 10: broader independent hands-on verification beyond a single HN comment, and clearer distinction between MCP-exposed tools vs. in-app assistant UX.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Missive✓fullclaimed7/10

   Missive's AI Assistant/Copilot and MCP integration let users issue natural-language requests (e.g., 'Ask Claude to summarize your inbox and draft replies,' 'compose, reply, and translate messages with AI') and let external AI apps act on conversations, contacts, calendar, and drafts through natural language via Claude/ChatGPT/Cursor. The command bar also supports quick text-based commands for actions like snoozing. Missing for 10: independent/hands-on user validation of natural-language accuracy and no detailed listing of all supported natural-language actions beyond marketing copy.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Ask how a feature works, how to set up a rule, or where a setting lives. The answer comes straight from the Missive documentation instead of…”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”

   proof ↗⚑ flag

   Zero✓fullcommunity7/10

   Zero's founder describes it as an AI-powered email client where users can chat with their inbox, ask questions about threads, and have AI draft replies, and the MCP docs confirm natural-language driven actions (compose, search, ask questions, web search) — this directly matches AI-native NL command operation. Missing for 10: independent hands-on verification of the actual chat UI/NL command interface beyond founder claims and MCP protocol docs.

   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [claimed-docs] “Compose emails with AI assistance”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Missive—none0/10

   Missive documents a REST API and developer tools, but there is no evidence of an interactive API reference or runnable examples; explicit probes for openapi/swagger specs all returned 404s, indicating no interactive API explorer exists.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is an email client with an MCP server and docs (MCP.md, ROADMAP.md), but there is no evidence of an interactive API reference (e.g., Swagger/OpenAPI explorer, Postman collection, or runnable code sandbox) for AI-native users to explore and execute example calls.

   ⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Missive—none0/10

   Probes for OpenAPI/Swagger spec files at standard locations all returned 404, and no evidence pack item mentions a downloadable machine-readable API spec despite Missive having a REST API and developer docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Missive—none0/10

   No evidence of any sandbox, staging, or test environment offered by Missive; all MCP/API access documented operates directly against live conversations, contacts, calendars, and drafts (missive-probe-rt-2), with no mention of a non-production mode for testing.

   ⚑ flag

   Zero—none0/10

   Zero is an AI email client whose evidence covers MCP tools for real mailbox operations (send/delete/label emails) and self-hosting, but nothing describes a sandbox, test/staging mode, or mock data environment isolated from production email accounts.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Missive—none0/10

   There is a REST API and MCP integrations documented, but no evidence of API versioning scheme or any documented deprecation policy; probes for openapi/spec files all 404. missing for 10: versioning scheme documentation, explicit deprecation/backward-compatibility policy, changelog of breaking API changes.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence describes Zero's MCP server capabilities and self-hosting, but no documentation anywhere mentions API versioning, version numbers, or a deprecation policy for its MCP/API surface. missing for 10: any mention of API versioning scheme, changelog/deprecation policy, or backward-compatibility guarantees.

   ⚑ flag

Agent workflows

1. ai-native userAn external agent — Claude, ChatGPT, or my own — can read, triage, draft, and send my email end to end through a documented connection

   weight 2 · round to Zero
   Missive~partialprobed6/10

   Missive documents an official MCP server (missive-probe-4) that lets external AI apps like Claude, ChatGPT, or Cursor connect and act on conversations, contacts, calendar, and drafts with configurable permissions (missive-docs-1, missive-docs-20), including summarizing inboxes, drafting replies, and triaging conversations against a CRM (missive-docs-21, missive-docs-22). However, explicit end-to-end 'send' capability via the agent is not directly documented, and there is no independent/hands-on corroboration of the full read-triage-draft-send loop working in practice. Missing for 10: explicit documentation of agent-initiated sending (not just drafting), and third-party/hands-on verification of the full workflow.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”
   • [claimed-docs] “Connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprietary data, or homegrown too…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero documents an official MCP server (MCP.md, verified by probe) enabling agents like Claude to read threads, ask questions about mailbox content, compose with AI assistance, and create/send drafts and new emails, plus manage labels — covering triage, drafting, and sending end to end via Better Auth session token auth. missing for 10: no hands-on third-party report of an external agent (Claude/ChatGPT) actually completing a full read-triage-send workflow, and OAuth support is still 'coming soon' rather than shipped.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Ai assistant

1. ai-native userAsk an assistant questions across my whole inbox and calendar — who said what, what's outstanding — and get grounded answers

   weight 2 · round drawn
   Missive~partialclaimed6/10

   Missive's AI Assistant/MCP integration lets external AI apps (Claude, ChatGPT, Cursor) act on conversations, contacts, calendar, and drafts, and docs explicitly mention asking Claude to summarize the inbox and draft replies — directly supporting cross-inbox Q&A grounded in Missive data. However, evidence doesn't demonstrate calendar-specific querying depth or explicit 'what's outstanding' style aggregate reasoning across the whole inbox, and there's no independent/hands-on validation of answer groundedness or accuracy. Missing for 10: concrete examples of calendar-integrated Q&A, evidence of multi-conversation aggregate answers, and independent corroboration of answer quality/groundedness.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Zero's MCP server explicitly supports asking questions about mailbox content and specific email threads, plus AI compose, search, and labels, and community commentary confirms an AI-powered 'chat with your inbox' experience. However, evidence doesn't show cross-inbox/whole-calendar synthesis, calendar integration, or 'who said what / what's outstanding' style grounded multi-thread reasoning — the documented Q&A appears scoped to mailbox/thread level rather than full inbox+calendar grounding. missing for 10: calendar integration/awareness, evidence of synthesizing across the entire inbox (not just single threads), independent hands-on verification of grounded multi-source answers.

   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Ai drafting

1. ai-native userAI drafts replies in my own voice and tone — ready to review and send, not generic boilerplate

   weight 3 · round to Zero
   Missive~partialclaimed4/10

   Missive documents AI compose/reply features ("Quickly compose, reply, and translate messages with AI directly in Missive" and "Ask Claude to summarize your inbox and draft replies") confirming AI drafting exists, but there is no evidence describing tone/voice personalization or that drafts are tuned to the user's own writing style versus generic boilerplate. Missing for 10: evidence of voice/tone learning or personalization, hands-on examples showing draft quality matches user's style, independent corroboration of draft usefulness.

   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”

   proof ↗⚑ flag

   Zero~partialcommunity5/10

   Zero's MCP docs and founder description confirm AI drafts replies ('Compose emails with AI assistance', 'drafts replies') as a core feature, but no evidence describes voice/tone personalization or learning the user's writing style. Missing for 10: documentation of voice/tone matching or personalization mechanism, and independent hands-on verification that drafts read as the user's own voice rather than generic AI text.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Ai triage

1. ai-native userAI triages my inbox for me — auto-labeling, categorizing, and surfacing what needs attention — with behavior I can steer and audit

   weight 3 · round drawn
   Missive~partialclaimed6/10

   Missive's AI Assistant/MCP integration explicitly supports agent-driven triage ('Let an agent triage new conversations against your CRM before you look at them'), inbox summarization, and rule-based automation (up to 1000 rules), and provides audit trails via action logs and a session tab showing assistant activity, plus permission-scoped access for steering behavior. However, there's no explicit mention of automatic labeling/categorization as a distinct AI feature (only manual rules), and no independent/hands-on evidence confirming triage quality works as advertised. Missing for 10: explicit auto-labeling/categorization feature description, hands-on validation of triage accuracy, and clearer UI for reviewing/adjusting AI triage decisions beyond session logs.

   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “The session tab now shows what the assistant is up to, and a conversation links back to the sessions attached to it.”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Every action within Missive is logged, so you know who did what, and when.”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Up to 1000 rules”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Community and docs evidence show Zero markets itself as an AI-powered inbox that auto-categorizes emails, and its MCP server exposes tools to modify/create labels, filter/search by label, and answer questions about threads/mailbox content, giving a steerable interface for AI actions. However, there's no explicit documentation of automatic prioritization/surfacing of 'what needs attention' or an audit log of AI triage decisions beyond the generic MCP action list. Missing for 10: dedicated 'needs attention' surfacing/prioritization feature, explicit audit trail or history of AI-taken triage actions, and independent hands-on verification of auto-labeling accuracy.

   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Create new custom labels with custom colors”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Zero
   Missive~partialclaimed3/10

   Missive documents rule-based automation ('Up to 1000 rules') and API/MCP access that could act across many items, plus a bulk auto-archive list feature, but there is no direct evidence of a bulk-select/bulk-action UI or bulk API endpoint for acting on many conversations/contacts at once. Missing for 10: explicit bulk-action UI documentation, bulk API/webhook examples, and independent confirmation of scale-limits for automation across many items.

   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Picking Everyone in a shared account's Auto-archive list covers anyone who joins your organization later, instead of adding each person by h…”
   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”

   proof ↗⚑ flag

   Zero~partialprobed5/10

   Zero's MCP server exposes email actions like 'Bulk delete emails' and 'Bulk archive emails' explicitly labeled as bulk operations, plus label/search operations that could apply across many items. However, evidence does not specify limits, batch size, or confirm bulk semantics beyond these two named actions, nor is there hands-on confirmation of bulk behavior at scale. missing for 10: independent/hands-on verification of bulk operations at scale, documentation of batch limits or performance, evidence of bulk operations beyond delete/archive (e.g., bulk label/move/send).

   • [claimed-docs] “Bulk delete emails - Bulk archive emails”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Missive
   Missive~partialclaimed5/10

   Missive confirms a native Rules feature ("Automate your workflows", "Up to 1000 rules", and documentation referencing 'how to set up a rule') that lets users define automation triggered by events, plus webhooks/API for event-driven actions. However, the evidence pack lacks concrete documentation of what trigger events or actions rules support, no hands-on examples of rule configuration, and no independent corroboration of automation depth or reliability. missing for 10: detailed rule trigger/action catalog, hands-on walkthrough of rule creation, independent user validation of automation reliability.

   • [claimed-docs] “Ask how a feature works, how to set up a rule, or where a setting lives. The answer comes straight from the Missive documentation instead of…”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero as an AI email client with MCP tool actions (search, compose, label, etc.) but no documented rule-based automation engine that triggers actions on events (e.g., 'when email arrives from X, do Y'). All actions appear to be user- or agent-invoked rather than event-triggered automation. Missing for full credit: any documented trigger/condition/action rules engine or scheduled/event-based automation feature.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Missive—none0/10

   Missive documents an AI Assistant, MCP integrations, and an event-triggered 'rules' automation engine (up to 1000 rules) for workflows, but nothing in the evidence describes scheduling recurring/cron-style jobs or timed recurring AI workflows — rules appear to be trigger-based, not time-scheduled. missing for 10: any mention of a scheduler, cron-like recurrence, or time-based recurring job configuration for AI/assistant workflows.

   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is an AI email client with MCP tools for email actions (labels, search, compose, AI Q&A) but no evidence of scheduling recurring jobs or workflows/automation triggers.

   ⚑ flag

Calendar

1. power-userSee my calendar, respond to invites, and create events without leaving the email client

   weight 2 · round to Missive
   Missive~partialclaimed2/10

   The only calendar-related evidence is indirect: MCP changelog entries note that external AI apps can 'act on your conversations, contacts, calendar, and drafts,' implying Missive holds calendar data, but there is no documentation of an in-app calendar view, RSVP/invite response flow, or event-creation UI comparable to inbox features. Missing for 10: dedicated calendar panel/view docs, invite accept/decline UI, and event creation flow evidence — only an AI-assistant-access mention exists.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. power-userShare my availability or insert bookable meeting times directly into an email

   weight 1 · round drawn
   Missive—none0/10

   The evidence pack shows Missive's MCP integration can 'act on... calendar' generally, but there is no mention of any feature to share availability, generate scheduling links, or insert bookable meeting times into an email — a distinct capability from generic calendar access.

   ⚑ flag

   Zero—none0/10

   Zero is an email client with AI/MCP features for composing, searching, and managing emails, but no evidence in the pack mentions calendar integration, availability sharing, or inserting bookable meeting times into emails.

   ⚑ flag

Sending

1. power-userSee whether and when recipients opened my email

   weight 1 · round drawn
   Missive—none0/10

   No evidence in the pack mentions read receipts, email open tracking, or notifications about recipient opens/views; the pack covers collaboration, MCP/AI integrations, and admin features but nothing about tracking email opens.

   ⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions read receipts, open tracking, or notifications about when recipients open emails; the MCP/docs only cover sending, drafting, labeling, and searching emails.

   ⚑ flag

2. power-userSchedule an email to send later and undo a send within a grace window

   weight 2 · round drawn
   Missive—none0/10

   No evidence in the pack mentions scheduled sending or an undo-send grace window; the pack covers MCP integrations, collaboration features, snoozing, and canned responses but nothing about send scheduling or send-delay/undo functionality.

   ⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions scheduled send or undo-send functionality; MCP docs list send/draft/delete but nothing about delayed sending or a grace-window recall.

   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts”

   proof ↗⚑ flag

Templates

1. power-userInsert saved snippets or templates — with variables and attachments — instead of retyping the same reply

   weight 2 · round to Missive
   Missive✓fullclaimed8/10

   Missive's canned responses/templates feature explicitly supports saving reusable replies, inserting them via keystrokes/command bar, sharing across teams, and customizing with a variables templating engine (recipient name, etc.), directly matching the story; MCP/API docs also confirm drafts resolve template variables like {{ user.name }}. missing for 10: explicit first-party documentation confirming attachments can be bundled/saved within a canned response/template, and independent hands-on corroboration of the templating workflow.

   • [claimed-docs] “Canned responses (or templates) are pre-written replies to common questions. Instead of typing the same answer repeatedly, you write it once…”
   • [claimed-docs] “You can easily customize your responses or templates with dynamic content like your recipient's name by using our variables templating engin…”
   • [claimed-docs] “Drafts created outside the composer, by the assistant, by a rule, or through the API and MCP server, now resolve {{ user.name }} and {{ user…”
   • [claimed-docs] “Drafts created outside the composer, by the assistant, by a rule, or through the API and MCP server, now resolve {{ user.name }} and {{ user…”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence pack item mentions saved snippets, canned responses, or templates with variables/attachments; the docs describe AI-assisted composing, MCP tools, labels, and self-hosting but nothing about a snippet/template insertion feature.

   ⚑ flag

Offline

1. power-userRead, search, and write email offline, with changes syncing when I reconnect

   weight 2 · round drawn
   Missive—none0/10

   No evidence in the pack addresses offline mode, local caching of email data, offline search, or sync-on-reconnect behavior; all citations concern MCP/AI integrations, team collaboration, and pricing features unrelated to offline reliability.

   ⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions offline mode, local caching, or sync-on-reconnect; Zero appears to be a web-based email client requiring live connection to providers/AI services, with no offline-capability documentation.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Zero
   Missive~partialprobed4/10

   Missive documents a REST API, webhooks, and an MCP server that can act on conversations, contacts, calendar, and drafts (missive-docs-15, missive-docs-31, missive-docs-45, missive-probe-4), suggesting broad but not explicitly complete UI/API parity — there is no vendor claim of 1:1 feature parity, and the OpenAPI spec could not be located via standard probes (missive-probe-3), making it hard to verify full API surface coverage against UI capabilities like snoozing, canned responses, or command-bar search (missive-docs-supp-1/3/4) which are not mentioned as API-exposed. Missing for 10: an explicit vendor statement of full UI/API parity, a discoverable OpenAPI/schema reference, and evidence that UI-only features (snoozing, canned responses, command bar actions) are also API-accessible.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Drafts created outside the composer, by the assistant, by a rule, or through the API and MCP server, now resolve {{ user.name }} and {{ user…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”
   • [claimed-docs] “Snoozing temporarily hides a conversation until a specific time, then brings it back to your Inbox. Use it to defer emails you can't deal wi…”
   • [claimed-docs] “Canned responses (or templates) are pre-written replies to common questions. Instead of typing the same answer repeatedly, you write it once…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Zero's MCP server exposes many core email actions (search, send, draft, delete, labels, AI compose, thread Q&A) that mirror UI functionality, giving strong API-parity for mail operations. However missing for 10: no evidence of API parity for UI-specific settings like customizable keyboard shortcuts, UI theming/customization, unified inbox provider management, or account/connection setup via API — these remain UI-only per docs, and there's no independent confirmation the MCP surface is fully comprehensive versus a curated subset.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Customizable keyboard shortcuts”
   • [github] “Customizable UI & Features – Tailor your email experience the way you want it.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Missive—none0/10

   The evidence pack shows a REST API, webhooks, and MCP integrations for connecting external tools, but nothing documents a bulk data-export feature or open-format (mbox/CSV/JSON) export enabling a user to fully extract their mail, contacts, and conversation history and leave the platform. Probes for docs/API artifacts (llms.txt, openapi) also 404, further indicating no dedicated export-and-leave capability is documented.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero is self-hostable, open-source, and doesn't sell user data, plus a Drizzle Studio DB viewer for self-hosters, but there is no documented data-export feature (e.g., mbox/EML export, takeout tool) letting a user extract all their mail data in an open format and leave the service.

   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Zero
   Missive—none0/10

   Missive is a closed-source commercial email/collaboration SaaS; no evidence anywhere in the pack of an open-source license or public source repository, and probes for typical openness indicators (llms.txt, docs.md, openapi) all 404. No indication source code is available under any license.

   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero's source is publicly hosted on GitHub (Mail-0/Zero) with a full contributing guide, self-hosting instructions, and a verified runtime probe confirming a real, clonable source tree with Docker configs for self-hosting — consistent with an open-source project freely readable by AI-native users. Missing for 10: explicit citation of the license file/name (e.g. MIT/AGPL) to confirm licensing terms.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Zero
   Missive—none0/10

   Missive is a cloud-hosted SaaS collaboration/email product; evidence shows data routes through Missive's own servers (missive-comm-1) and no docs mention any self-hosting/on-prem deployment option anywhere in the extensive feature/pricing/docs pack.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Multiple GitHub and docs citations explicitly advertise 'Self-Hosting Freedom' and describe running your own email app, and a runtime probe confirms a real self-hostable source tree with docker-compose files for self-hosting deployment. Missing for 10: independent hands-on report of a completed self-host deployment beyond the repo/docker-compose evidence, and more detailed self-host setup documentation.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “⚙️ **Self-Hosting Freedom** – Run your own email app with ease.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “Self-hosting capabilities”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Zero
   Missive—none0/10

   No evidence in the pack mentions data residency, region selection, or geographic storage location controls; features like IP restrictions and SSO relate to access control, not data storage location. Missing for 10: any mention of regional data hosting options, residency guarantees, or storage location configuration.

   ⚑ flag

   Zero~partialclaimed5/10

   Zero's self-hosting capability (own infra, own database via docker-compose) lets a user effectively choose where their data lives, and it claims not to track/collect/sell data, but there is no explicit region/residency selection feature or documented multi-region hosted offering. missing for 10: explicit region/residency selection UI or hosted multi-region options, documentation on data locality guarantees for the hosted SaaS version, independent confirmation of self-host deployment satisfying residency requirements.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “⚙️ **Self-Hosting Freedom** – Run your own email app with ease.”
   • [claimed-docs] “Self-hosting capabilities”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Zero does not track, collect, or sell your data in any way.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Zero
   Missive—none0/10

   No evidence in the pack addresses any AI-training opt-out, data-usage policy for AI model training, or privacy controls specific to preventing training on user data. The pack covers MCP integrations, AI assistant features, and collaboration tools, but nothing about training data exclusion or a documented privacy commitment on this axis.

   ⚑ flag

   Zero~partialclaimed5/10

   Zero states it does not track, collect, or sell user data, and self-hosting is available which would let users fully control data flow, implying no AI training on user data. However, there is no explicit statement or policy about AI-model training exclusion (e.g., no clause addressing whether email content sent to AI features like compose/summarize is used for model training). missing for 10: explicit AI-training opt-out/data-use policy, third-party AI provider data-handling terms, independent verification of the no-training claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Zero
   Missive—none0/10

   No evidence describes any data retention or deletion controls (e.g., configurable retention periods, right-to-delete, data purge options) for Missive or its AI/MCP features; the only related community note concerns data routing through servers via TLS, not retention/deletion policy.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

   Zero~partialclaimed5/10

   Zero claims a no-tracking/no-sell data policy and supports self-hosting (giving users full control over their own data and deletion since they own the infrastructure), plus MCP tools include explicit 'delete emails' actions. However, there's no documented data retention policy, no explicit account/data deletion workflow or export tooling described, and no independent verification of the no-tracking claim. missing for 10: documented retention/export/deletion policy for hosted use, independent audit of data practices, explicit account-deletion or right-to-be-forgotten flow.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Bulk delete emails - Bulk archive emails”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to Zero
   Missive—none0/10

   No evidence pack item addresses telemetry/usage-tracking opt-out settings, privacy controls, or data-collection disclosures for Missive; the closest related content (comm-1) merely notes emails route through Missive's servers, which is unrelated to telemetry opt-out. This is an applicable axis for a SaaS product but no supporting evidence exists.

   ⚑ flag

   Zero~partialprobed5/10

   Zero's GitHub page states it 'does not track, collect, or sell your data in any way,' and self-hosting support (Docker compose files, self-hosting docs) lets AI-native users run their own instance with no vendor telemetry at all. However there is no explicit telemetry settings/opt-out toggle documented, no privacy policy detail, and no independent verification of the no-tracking claim. Missing for 10: explicit telemetry opt-out control/setting, detailed privacy policy, and independent/hands-on confirmation of the no-tracking claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Protection

1. switcherUse aliases or masked addresses so sign-ups and strangers never learn my real address

   weight 1 · round drawn
   Missive—none0/10

   No evidence anywhere in the pack of email aliasing, masked/burner address generation, or similar identity-protection features for switchers; Missive is an email client/collaboration tool, and evidence covers team inboxes, MCP/AI integrations, and SSO, none of which address address masking.

   ⚑ flag

   Zero—none0/10

   Zero is an AI-powered unified email client with labels, search, and MCP integrations, but nothing in the evidence pack describes email alias generation or masked/burner address creation to hide a user's real address from sign-ups or strangers.

   ⚑ flag

2. switcherThe client protects me from senders' tracking — blocking read pixels by default — and is transparent about what it does with my mail data

   weight 2 · round to Zero
   Missive—none0/10

   No evidence pack item mentions tracking-pixel blocking, image-loading proxying, or a documented privacy policy explaining what Missive does with mail data. The only related community evidence shows a user learning mail routes through Missive's servers and declining ('Thanks, but I pass'), which does not demonstrate a pixel-blocking feature or proactive transparency documentation.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

   Zero~partialclaimed3/10

   Only a general privacy claim ('Zero does not track, collect, or sell your data in any way') is evidenced, with no mention of read-pixel/tracking-pixel blocking specifically or a detailed data-handling policy. missing for 10: explicit read-receipt/tracking-pixel blocking feature, documentation of default-on behavior, a privacy policy detailing mail data handling, and independent confirmation of the no-tracking claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”

   proof ↗⚑ flag

Migration

1. switcherImport my complete mail history and contacts from my old provider or client

   weight 1 · round drawn
   Missive—none0/10

   No evidence in the pack discusses importing mail history or contacts from another provider/client (e.g., Gmail/Outlook migration, IMAP sync, contact import tools). Evidence covers AI/MCP features, collaboration, search filters, and pricing but nothing about onboarding migration or historical data import.

   ⚑ flag

   Zero—none0/10

   Zero connects to providers like Gmail/Outlook for unified inbox access, but no evidence describes any import/migration tool for bulk historical mail or contacts from an old provider/client — no mention of mbox/EML import, contact list import, or migration wizard.

   ⚑ flag

Search

1. power-userSearch is fast and precise — operators, filters, and ranked results across my full mail history

   weight 2 · round to Zero
   Missive~partialclaimed3/10

   Evidence confirms Missive has search filters (Type: Internal/External, Date range) and a command-bar search that can query across messages, contacts, or a specific label, but there is no documentation of search operators (from:, subject:, boolean, etc.), relevance ranking, or explicit assurance of full-history indexing/performance at scale. Missing for 10: documented search operator syntax, ranked-results behavior, evidence of speed/precision across large mail archives, and independent corroboration of search quality.

   • [claimed-docs] “The Type (Internal / External) and Date range filters in search no longer stay greyed out until you enter a search term.”
   • [claimed-docs] “The Type (Internal / External) and Date range filters in search no longer stay greyed out until you enter a search”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”

   proof ↗⚑ flag

   Zero~partialcommunity4/10

   Evidence shows a basic 'search emails with custom queries' and 'filter by labels' capability via the MCP server, but there is no documentation of advanced operators, ranked relevance, or performance/scale across full mail history; a community comment even flags missing basic navigation features, suggesting search UX is still immature. missing for 10: documented search operators/syntax, evidence of ranking/relevance across full historical mail, performance benchmarks, independent hands-on confirmation of search speed/precision.

   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

Shortcuts

1. power-userDo everything from the keyboard — comprehensive shortcuts and a command palette — in an interface fast enough to never make me wait

   weight 3 · round to Missive
   Missive~partialcommunity6/10

   Missive documents a command bar (⌘/Ctrl+K) supporting search, snooze, and other quick commands, plus configurable swipe/keyboard shortcuts, which is direct evidence of keyboard-driven command palette functionality. However, there's no comprehensive shortcut list, no dedicated performance benchmarks, and community comments call the UI 'unintuitive' with 'design flaws' though also 'snappy' — mixed signal on speed/polish. Missing for 10: a full documented shortcut reference covering all major actions, explicit performance/latency claims, and independent hands-on confirmation of speed and keyboard completeness.

   • [claimed-docs] “You can also snooze by swiping a conversation (configurable in Settings > Preferences > Swipes), or by opening the command bar with ⌘/Ctrl +…”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”
   • [community] “"We choose Missive for now because Missive feels like a proper snappy desktop app and is vastly cheaper ($15 vs $50 per user). Front feels l…”
   • [community] “"I fear that we will eventually switch to Front because Missive is unintuitive or (please someone build that) Gmail with collaboration featu…”

   proof ↗⚑ flag

   Zero!disputedcontradicted2/10

   Zero's own roadmap lists 'customizable keyboard shortcuts' as a planned (not yet shipped) feature, and a hands-on community comment explicitly states the product lacks 'real keyboard navigation' today, directly contradicting any power-user keyboard-first claim; no command palette is mentioned anywhere in the evidence. missing for 10: shipped keyboard shortcut system, command palette, any evidence of interface speed/responsiveness for power users.

   • [claimed-docs] “Customizable keyboard shortcuts”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”

   proof ↗⚑ flag

Channels

1. team-leadThe same inbox also handles adjacent customer channels — SMS, WhatsApp, social, or live chat — beside email

   weight 1 · round to Missive
   Missive~partialclaimed6/10

   Pricing docs explicitly list "Email, SMS, social accounts" as channels handled in the same inbox, and developer docs mention support for "custom channels" via API, confirming Missive unifies email with at least SMS and social channels. However, there is no explicit evidence of native WhatsApp or live-chat channel support, only generic 'custom channels' extensibility. Missing for 10: explicit WhatsApp integration, native live-chat channel, and independent confirmation of multi-channel unification in practice.

   • [claimed-docs] “Email, SMS, social accounts”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Routing

1. team-leadAssign conversations to teammates and route incoming mail with rules so ownership is explicit

   weight 2 · round to Missive
   Missive✓fullclaimed8/10

   Missive's docs explicitly describe assigning conversations to a team or specific person while maintaining visibility (missive-docs-6), shared inboxes/distribution lists (missive-docs-32, missive-docs-28), and automated routing via rules (up to 1000 rules per missive-docs-11/25/36), directly matching the story's ask for explicit ownership assignment and rule-based routing. Missing for 10: independent/hands-on corroboration of rule-based mail routing in practice, and more detail on how rule conditions/criteria are configured.

   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other’s toes.”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is a personal AI-powered email client with unified inbox, labels, and MCP tooling, but no evidence anywhere in the pack describes team features like assigning conversations to teammates or configuring routing/ownership rules — capabilities relevant for shared team inboxes. This is a fair axis for an email client, but no evidence supports it, so it's 'none' rather than 'na'.

   ⚑ flag

Shared inbox

1. team-leadWe can discuss an email in an internal side-thread — comments and @mentions beside the message — instead of forwarding copies around

   weight 2 · round to Missive
   Missive~partialclaimed5/10

   Missive's docs point to team collaboration around conversations — 'collaborate behind the scenes without changing your workflow', 'chat with your team' in groups/spaces, and 'compose emails together, get reviewed in real time' — which align with discussing a message internally rather than forwarding it. However, none of the evidence explicitly names a side-thread comment feature or @mention tagging mechanic attached to a message. missing for 10: explicit documentation of inline comment threads on conversations, explicit @mention functionality, and independent/hands-on confirmation that this replaces forwarding workflows.

   • [claimed-docs] “See what’s going on, know who’s doing what, and collaborate behind the scenes — without changing your workflow.”
   • [claimed-docs] “collaborate behind the scenes — without changing your workflow.”
   • [claimed-docs] “Chat with your team. In groups, dedicated team spaces, or one-on-one.”
   • [claimed-docs] “Chat with your team. In groups, dedicated team sp”
   • [claimed-docs] “Compose emails together, get reviewed in real time, and share attachments.”
   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence covers email management, MCP AI features, and self-hosting, but nothing describes internal side-threads with comments/@mentions for team discussion of emails without forwarding.

   ⚑ flag

2. team-leadMy team works shared inboxes together — shared accounts or team channels where everyone sees the same conversation state

   weight 3 · round to Missive
   Missive✓fullcommunity9/10

   Missive's core product docs directly describe shared/team inboxes with multiple people working the same inbox without conflict, conversation assignment while maintaining visibility, distribution-list-to-shared-inbox mapping, per-action audit logging, and dedicated team spaces/channels — exactly the shared-conversation-state model the story describes (missive-docs-6, missive-docs-9, missive-docs-19, missive-docs-28, missive-docs-32, missive-docs-35, missive-docs-30/48). Independent community commentary corroborates it is used specifically for team email collaboration (missive-comm-3), and no evidence contradicts the shared-inbox mechanics themselves (complaints found are about general UX/bugs, not this capability). Missing for 10: a hands-on third-party account specifically confirming real-time shared conversation-state syncing across users (vs. general collaboration praise).

   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”
   • [claimed-docs] “Every action within Missive is logged, so you know who did what, and when.”
   • [claimed-docs] “Give each team a tailored space so they can seamlessly focus on their work.”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other’s toes.”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other's toes.”
   • [claimed-docs] “See what’s going on, know who’s doing what, and collaborate behind the scenes — without changing your workflow.”
   • [community] “"I love Streak for singleplayer but prefer Missive or Front for collaboration."”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is positioned as a personal AI-powered unified inbox for individual users (Gmail/Outlook accounts), with no evidence of shared inboxes, team channels, or shared conversation state across multiple users; features described are individual email management, MCP tooling, and self-hosting, not multi-user collaboration.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Followups

1. power-userSnooze conversations and set follow-up reminders that resurface a thread if nobody replies

   weight 2 · round to Missive
   Missive~partialclaimed6/10

   Missive's docs clearly document snoozing a conversation until a specific time so it resurfaces in the Inbox, including quick access via swipe or command bar (missive-docs-supp-1, missive-docs-supp-2). However, there is no evidence of a distinct 'follow-up reminder' feature that resurfaces a thread specifically if nobody replies (as opposed to a fixed snooze time) — the story's reply-tracking trigger is unevidenced. Missing for 10: documentation of a no-reply-triggered follow-up reminder mechanism, and any independent/hands-on confirmation of snooze/reminder reliability.

   • [claimed-docs] “Snoozing temporarily hides a conversation until a specific time, then brings it back to your Inbox. Use it to defer emails you can't deal wi…”
   • [claimed-docs] “You can also snooze by swiping a conversation (configurable in Settings > Preferences > Swipes), or by opening the command bar with ⌘/Ctrl +…”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions snooze, follow-up reminders, or resurfacing threads after no reply; the documented features cover labels, search, compose, AI Q&A, and self-hosting only.

   ⚑ flag

Inbox structure

1. power-userSelect many conversations at once and archive, label, or mark them done in one stroke

   weight 1 · round to Zero
   Missive—none0/10

   The evidence pack covers command bar search, snoozing, canned responses, MCP/AI assistant integration, and team collaboration features, but nothing documents multi-select bulk actions (archive/label/mark done across many conversations at once). Missing for 10: any docs or changelog entry describing bulk selection UI, keyboard multi-select, or batch archive/label/mark-done operations.

   • [claimed-docs] “You can also snooze by swiping a conversation (configurable in Settings > Preferences > Swipes), or by opening the command bar with ⌘/Ctrl +…”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”

   proof ↗⚑ flag

   Zero~partialcommunity4/10

   Zero's MCP docs explicitly list 'Bulk delete emails' and 'Bulk archive emails' plus label modification tools, showing some bulk-action capability, but this is exposed via an AI/MCP tool interface rather than confirmed as a native UI multi-select action, and there's no mention of a 'mark done' state or how many items can be selected/acted on interactively. Community commentary even flags gaps in basic power-user UI ergonomics (no real keyboard navigation), suggesting bulk in-UI triage may be immature. missing for 10: confirmed UI multi-select archive/label/done action, evidence of a 'done' state, independent hands-on confirmation of bulk UI workflow.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Bulk delete emails - Bulk archive emails”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”

   proof ↗⚑ flag

2. power-userSplit my inbox into focused streams — important, team, newsletters, calendar invites — so triage happens in priority order, not arrival order

   weight 3 · round to Missive
   Missive~partialclaimed4/10

   Missive's docs mention rule automation (up to 1000 rules), team spaces, and shared/team inboxes, which could be used to organize conversations by category, but there is no explicit documentation of a dedicated 'streams' or 'focused inbox' feature that lets a user split a single inbox into priority-ordered views (important, team, newsletters, calendar invites) as described in the story. missing for 10: explicit inbox-view/stream creation feature, priority-based triage ordering, and evidence of calendar-invite handling as a distinct stream.

   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Give each team a tailored space so they can seamlessly focus on their work.”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero supports labels, filtering, unified inbox, and AI Q&A, but there is no mention of dedicated inbox streams/views separating important, team, newsletter, and calendar-invite emails for priority-ordered triage. Labeling/filtering capabilities exist but no evidence of a stream-based triage UI or auto-categorized views as described in the story.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag