Honest answers
to hard questions.

Yes. Seam is read-only — we never write to your tools. When you ask a question, Seam fetches only the relevant content from your connected sources in real time. Raw document text is never stored by Seam. Your content is processed ephemerally and discarded after each response.

No, never. Seam uses Anthropic's Claude API to generate answers. Anthropic does not train on API inputs by default. Each query sends only the relevant retrieved context to Claude for that moment — your workspace content is never retained or used to train any model.

Access is tied to each user's Google OAuth login. Every user's connected sources are scoped to their own accounts — a junior PM can only search documents their own connected accounts have access to. Row-level security (RLS) in Supabase ensures strict data isolation between users.

Seam is an early-stage product. The underlying data layer (Supabase) is SOC 2 Type II certified. Full SOC 2 compliance for Seam itself is on the roadmap. Your document content is never stored by Seam — only OAuth tokens (encrypted) and your profile are retained.

Seam currently connects to Notion and Slack via live MCP (Model Context Protocol) — meaning every search queries your sources in real time with no indexing lag. Your content is never copied into a Seam-owned database; it stays in your tools and is read live on every search.

Instead of batch-indexing your content and searching a cached copy, Seam queries Notion and Slack directly at the moment you ask a question, via their official hosted MCP servers. The benefit: answers always reflect the latest state of your workspace. No sync delays, no stale results.

Jira and Confluence are on the near-term roadmap. Today, Seam works with Notion and Slack — where most PM decisions live for the teams we built this for. If you're blocked on Jira, reach out — it's the most-requested integration.

Seam detects the failure at query time and falls back to any remaining available sources. You'll see a reconnect prompt in Integrations. Reconnecting takes under 30 seconds and restores full live search immediately.

Every answer includes source cards — the actual documents and threads Claude used to generate the answer. If the source card doesn't exist for a claim, don't share the answer. Our internal evals scored hallucination resistance at 4.68/5 across 20 realistic PM queries. The system is designed to say nothing rather than invent.

Yes — Seam queries your sources live at the time of every search. There is no batch-sync delay. If you updated a Notion page 5 minutes ago, the next query will read the updated version.

Yes. Every answer shows which sources were used — the document or Slack thread title and the name of the connected workspace. Source links go directly back to the original content so stakeholders can verify in one click.

Native search is keyword-only and siloed per tool — you search Notion, then Slack, then manually compare. Seam runs a single natural language query across all your connected sources simultaneously and returns one synthesised, cited answer. The difference is between "find documents about X" and "tell me what was actually decided about X." For any question that spans multiple tools, Seam saves 20–30 minutes per query.

PMs lose an average of 25 minutes per context switch when hunting across tools for past decisions. For a PM doing 3–5 of these queries per day, that's 75–125 minutes recovered daily — roughly 6–10 hours per week. Seam is designed to close that gap.

Seam is built for PM-native queries: Decision Recall ("Why did we descope SSO?"), Spec Lookup ("What are the billing specs?"), Stakeholder Commitments ("What did we promise Acme Corp?"), and Onboarding ("Walk me through the auth flow decisions"). It's optimised for the questions PMs actually ask — not general-purpose chat.

Yes — Seam is in beta. Sign in with Google and connect Notion or Slack for free. No credit card required. Pricing will be introduced later; early users will receive advance notice before anything changes.

Your documents live in Notion and Slack — Seam searches them live and never stores copies. If Seam shuts down tomorrow, your underlying tools are completely unaffected. You own your data; we only ever read it.

Email hello@seam.so for any issue. We reply to every email. For common issues — sync failures, auth errors, reconnecting a source — the Integrations and Settings pages surface the error and a one-click fix for most cases.