);
}
/* --- A. Hero (committed: "between" composition, refined) --- */
function Hero({ onWaitlistClick }) {
return (
Inference agents · for Gmail and Outlook
Inference agents for your inbox.
They read between your emails — surfacing the patterns no single email reveals.
Works with Gmail
Works with Outlook
);
}
/* Tiny monochrome provider glyphs — not the trademarked colored marks */
function GmailGlyph() {
return (
);
}
function OutlookGlyph() {
return (
);
}
function BetweenComp() {
// L1 experience: chip lives inline with the sender/timestamp row of a real
// Gmail/Outlook thread. Clicking the chip reveals the inference popover.
// We show both states at once — chip visible on the thread, popover open
// beneath it — so the relationship reads in one glance.
const threads = [
{
from: "Reza Karimi", co: "Acme",
subj: "QBR Friday — quick SSO confirm?",
excerpt: "Just prepping the deck for Friday — we're showing SSO live in Q4 to our security team. All good on your end?",
date: "9:12 AM",
unread: true,
hasChip: true
},
{
from: "You", to: "eng-leads",
subj: "re: Q4 roadmap cuts",
excerpt: "Approved. We're cutting SSO from Q4 to ship the export refactor first. SSO slides to Q1 at earliest.",
date: "Sep 18",
unread: false,
hasChip: false
},
{
from: "You", to: "Reza Karimi",
subj: "re: expansion + SSO timeline",
excerpt: "Yes, SSO is locked in for Q4 rollout — happy to put that in the renewal contract.",
date: "Jul 14",
unread: false,
hasChip: false
}
];
return (
INFERENCE · DRAWN FROM 3 THREADSRENEWAL · AT RISK
{/* Gmail-style inbox surface */}
{/* dashed connector — chip → popover */}
{/* Inference popover — what appears when the chip is clicked */}
{/* tiny anchor triangle pointing up to the chip */}
{/* agent badge row */}
ReoCustomer commitments tracker
{/* inference headline */}
Acme expects SSO live in Q4 — your team cut it last week. Their QBR is Friday, and a $420K expansion is on the line.
{/* source chip */}
3 threads · Jul 14 – today
{/* footer: audience + actions */}
);
}
/* --- A.5 Getting Started — three-step user journey, post-hero --- */
function GettingStarted({ onWaitlistClick }) {
const steps = [
{
n: "01",
title: "Sign in with Gmail or Outlook",
body: "OAuth in two clicks. Reo asks for read access — never send-on-your-behalf. You can revoke it any time.",
visual: ,
duration: "~ 10 seconds"
},
{
n: "02",
title: "Pick your scope and your agents",
body: "Choose how far back Reo can read (up to 6 months) and assemble your team — from the library, with AI, or written by hand.",
visual: ,
duration: "~ 40 seconds"
},
{
n: "03",
title: "Reo surfaces inferences — you click to act",
body: "Every inference comes with sources and one-click actions across the tools you already use. Reo also learns what you act on and suggests new agents.",
visual: ,
duration: "ongoing"
}
];
return (
Up and running in 90 seconds.
Three steps · no configuration to write
{steps.map((s) => (
{s.n}{s.duration}
{s.title}
{s.body}
{s.visual}
))}
Gmail and Outlook · cancel any time · data deleted within 30 days
);
}
/* --- Reo learns: shows how the agent suggests new agents + integrations
* based on what the user acts on. Slim, sober, single horizontal row. */
function ReoLearnsCallout() {
return (
And it learns
Reo watches what you act on — and quietly proposes new agents and tools.
Inferred from week 03 · review weekly
{/* Left: suggested new agent */}
Suggested new agent
Pricing-discussion drift
You acted 4× on price-related threads this month.
+ Add
{/* Right: suggested integration */}
Suggested integration
Loop the #cs-leads channel
You forward customer-risk threads to your team 2–3× per week.
+ Connect Slack
{/* footer caption */}
● Suggestions inferred locally · never sent until you approve
You can dismiss any suggestion · Reo stops proposing it
);
}
/* --- C. Agents teaser (library metaphor, not app-store grid) ---
* Each agent carries a real-world example scenario users can click to see.
* Examples are dollar-tied, calendar-urgent, and inference-true to the
* promise of the hero — to make the agent's value obvious in 5 seconds. */
const ALL_SKILLS = [
{
cat: "patterns", glyph: "clock",
name: "Customer commitments tracker",
description: "Overdue and approaching — across every thread, not just the loud ones.",
example: {
headline: "Stripe renewal is in 4 weeks. You committed to audit logs at signing. We don't have them.",
emails: [
{ from: "You → Stripe", subj: "re: contract terms — audit logs", date: "Apr 14, 2026 · 3:42 PM", excerpt: "Confirming: SSO and audit logs ready by October renewal. Happy to put both in the contract." },
{ from: "Priya → eng-leads", subj: "Q3 sprint priorities", date: "Aug 22, 2026 · 11:08 AM", excerpt: "Audit logs slipping — pushing to Q1 to make room for the Aurora migration." },
{ from: "Stripe procurement", subj: "Renewal kickoff — Oct 14", date: "Yesterday · 4:10 PM", excerpt: "We'll start the renewal review Monday. Anything we should be prepared to discuss?" }
],
sources: ["3 threads · Apr 14 – yesterday"],
audience: "you only",
primary: "Loop in eng now",
secondary: "Acknowledge to Stripe"
}
},
{
cat: "patterns", glyph: "cross-arrows",
name: "Cross-customer contradictions",
description: "Same feature, different stories. Reo flags when two customers were told different things.",
example: {
headline: "Voro and Beam are on the same plan — but you told them different things about SSO.",
emails: [
{ from: "You → Voro", subj: "re: SSO setup", date: "Jul 8 · 2:14 PM", excerpt: "SSO is available on your plan — just ping support and they'll flip it on." },
{ from: "You → Beam", subj: "re: SSO availability", date: "Sep 1 · 9:30 AM", excerpt: "SSO is on the Enterprise tier — happy to put together pricing for the upgrade." },
{ from: "Voro · Reza", subj: "re: SSO working great", date: "Last week", excerpt: "SSO's been live for a month — thanks for getting that done." }
],
sources: ["3 threads · same product tier"],
audience: "you only",
primary: "Reply to Beam",
secondary: "Open billing tier review"
}
},
{
cat: "patterns", glyph: "diverge",
name: "Stakeholder alignment drift",
description: "When two team members disagree silently through you, instead of with each other.",
example: {
headline: "Priya and Marcus disagree on the API change — both told you privately, neither told the other.",
emails: [
{ from: "Priya · eng-lead", subj: "re: API v2 timeline", date: "Aug 12 · 10:14 AM", excerpt: "We can ship the v2 API by end of Q4. Auth changes are ready, just need design sign-off." },
{ from: "Marcus · design-lead", subj: "API v2 — needs another sprint", date: "Aug 12 · 4:20 PM", excerpt: "Design isn't finalized yet — we need at least one more sprint before this is safe to ship." },
{ from: "You → product-leads", subj: "v2 status check", date: "This morning", excerpt: "Tomorrow's all-hands — what should I say about API v2 timing?" }
],
sources: ["2 threads · same day, never crossed"],
audience: "you only",
primary: "Open a joint thread",
secondary: "Defer the all-hands answer"
}
},
{
cat: "patterns", glyph: "wave",
name: "Cooling counterparty threads",
description: "Relationships going quiet that used to be warm. Catch them before they're cold.",
example: {
headline: "Pier renewed in February for $180K. They've gone from weekly chat to 32 days of silence.",
emails: [
{ from: "Pier · Amanda", subj: "re: contract signed!", date: "Feb 4 · 2:10 PM", excerpt: "Excited to keep working together. Looking forward to the audit-log work in Q2 — talk soon." },
{ from: "Pier · Amanda", subj: "re: Q2 product update", date: "May 18", excerpt: "Thanks for the update — will pass along to the team." },
{ from: "Pier · procurement", subj: "Renewal options query", date: "32 days ago", excerpt: "We're starting our 2027 budget planning — wanted to understand what renewal looks like." }
],
sources: ["3 threads · Feb – today"],
audience: "you only",
primary: "Schedule a check-in",
secondary: "Loop in CS lead"
}
},
{
cat: "patterns", glyph: "log",
name: "Decision audit log",
description: "What you've decided and why, captured from the threads where you actually decided it.",
example: {
headline: "On Tuesday you decided to defer the Postgres migration to Q1. Two team docs still show Q4.",
emails: [
{ from: "You → eng-leads", subj: "re: migration timing", date: "Tuesday · 11:02 AM", excerpt: "Aligned — pushing Postgres-to-Aurora to Q1. We need to focus Q4 on SSO." },
{ from: "Priya · roadmap doc", subj: "[link] roadmap.md updated", date: "Wednesday", excerpt: "Latest roadmap doc — still showing Postgres migration kicking off in Q4 week 4." },
{ from: "Marcus · eng-leads", subj: "Q4 capacity planning", date: "Thursday · 9:11 AM", excerpt: "Counting on Postgres team for Q4 — let me know if anything changes." }
],
sources: ["3 threads · this week"],
audience: "team · eng-leads",
primary: "Send decision summary",
secondary: "Pin to decision log"
}
},
{
cat: "safety", glyph: "shield",
name: "Sensitive content quarantine",
description: "HR, medical, legal, financial, privileged — auto-excluded by default. You opt in, never out.",
example: {
headline: "23 threads quarantined this week. Reo never read them, never indexed them, can't answer questions about them.",
emails: [
{ from: "[QUARANTINED · HR]", subj: "Sarah — performance review draft", date: "This week", excerpt: "Contents not indexed. Reo does not analyze HR threads by default." },
{ from: "[QUARANTINED · MEDICAL]", subj: "2026 health insurance enrollment", date: "This week", excerpt: "Contents not indexed. Reo does not analyze medical threads by default." },
{ from: "[QUARANTINED · LEGAL]", subj: "re: NDA — outside counsel privileged", date: "This week", excerpt: "Contents not indexed. Reo does not analyze legal threads by default." }
],
sources: ["23 threads · auto-detected · never opened"],
audience: "you only · admins cannot view",
primary: "Review quarantine list",
secondary: "Adjust quarantine rules"
}
},
{
cat: "safety", glyph: "eye-off",
name: "Privileged thread protection",
description: "Attorney-client threads never analyzed. Detected and excluded at ingest, before reaching the inference layer.",
example: {
headline: "4 attorney-client threads detected and excluded at ingest. They are not in the index. They cannot be queried.",
emails: [
{ from: "[EXCLUDED · ATTORNEY-CLIENT]", subj: "re: Walker v. Acme — strategy", date: "Sep 24", excerpt: "Excluded by privilege detector. Not retrievable by any agent." },
{ from: "[EXCLUDED · ATTORNEY-CLIENT]", subj: "Walker matter — discovery review", date: "Sep 30", excerpt: "Excluded by privilege detector. Not retrievable by any agent." },
{ from: "[EXCLUDED · ATTORNEY-CLIENT]", subj: "re: outside counsel — settlement framing", date: "Today", excerpt: "Excluded by privilege detector. Not retrievable by any agent." }
],
sources: ["4 threads · privilege detector · audit log"],
audience: "you only",
primary: "Open privilege audit",
secondary: "View detection rules"
}
},
{
cat: "ops", glyph: "target",
name: "Roadmap commitment conflicts",
description: "Same feature window committed twice. Reo notices and surfaces it.",
example: {
headline: "Customer Portal is promised to Acme AND Beam in Q4. Engineering can only ship one.",
emails: [
{ from: "You → Acme", subj: "re: Customer Portal timing", date: "Aug 14 · 10:08 AM", excerpt: "Confirming — Customer Portal will be live for you in Q4 this year. Plan around that." },
{ from: "You → Beam", subj: "re: Q4 roadmap", date: "Sep 2 · 2:48 PM", excerpt: "Customer Portal is locked in for Q4. Looking forward to the rollout with you." },
{ from: "Priya · capacity plan", subj: "Q4 engineering capacity", date: "Sep 10", excerpt: "Realistically we can ship Customer Portal for one of them, not both. Which?" }
],
sources: ["3 threads · Aug 14 – Sep 10"],
audience: "you only",
primary: "Open conflict review",
secondary: "Flag to product-leads"
}
},
{
cat: "ops", glyph: "bell",
name: "SLA breach watch",
description: "Service-level promises slipping toward their deadline, ranked by impact.",
example: {
headline: "Acme P0 has been open 25 hours. SLA is 4. You replied once, never followed up.",
emails: [
{ from: "Acme · ops", subj: "P0 — billing showing wrong amounts", date: "Mon 9:30 AM", excerpt: "Customers are seeing the wrong amounts on their invoices. This needs to be looked at urgently." },
{ from: "You → Acme", subj: "re: P0", date: "Mon 12:15 PM", excerpt: "I'll get back to you with an update today — investigating with eng now." },
{ from: "Acme · ops", subj: "re: P0 — any update?", date: "Tue 11:08 AM", excerpt: "Following up — we still haven't heard back. Three more customer reports came in this morning." }
],
sources: ["4 threads · SLA: 4h response"],
audience: "you only",
primary: "Escalate to on-call",
secondary: "Draft status update"
}
},
{
cat: "ops", glyph: "ear",
name: "Repeated question tracker",
description: "When a customer asks the same thing twice in 30 days, you hear about it once.",
example: {
headline: "Beam has asked about API rate limits three times. You answered once. They're not sure they got an answer.",
emails: [
{ from: "Beam · Priya", subj: "API rate limits — quick question", date: "Aug 14", excerpt: "Hey — what's the rate limit on the /events endpoint? Trying to plan ingestion." },
{ from: "Beam · Priya", subj: "re: API limits (different question)", date: "Aug 28", excerpt: "Wanted to confirm — does the rate limit reset per minute or per hour?" },
{ from: "Beam · Priya", subj: "Rate limits one more time", date: "Sep 22", excerpt: "Sorry to keep asking — what's the actual limit per minute? We're getting throttled in staging." }
],
sources: ["3 threads · same question, different phrasings"],
audience: "you only",
primary: "Reply with the answer",
secondary: "Pin to FAQ doc"
}
},
{
cat: "custom", glyph: "currency",
name: "Price-change sentinel",
description: "Vendor adjusts a price after sign-off — Reo catches the diff and flags it.",
custom: true,
prompt: "Notice when a vendor changes a price after we've signed off.",
example: {
headline: "AWS quoted $42K/mo on Jul 1. Latest invoice is $48K/mo. The 14% increase isn't explained anywhere.",
emails: [
{ from: "AWS · account exec", subj: "Aurora cluster — quote", date: "Jul 1 · 11:30 AM", excerpt: "Quoted: $42,000/mo for the m7g.16xlarge Aurora cluster, committed annual. Term: 12 months." },
{ from: "You → AWS", subj: "re: Aurora quote — accepted", date: "Jul 8 · 9:14 AM", excerpt: "Signed. Please bill against our standard PO. Expecting first invoice early August." },
{ from: "AWS · billing", subj: "September invoice — Aurora cluster", date: "Sep 10", excerpt: "September invoice: $48,000.00. Detail in attached PDF. Net 30." }
],
sources: ["2 threads + 1 invoice · Jul 1 vs Sep 10"],
audience: "you only",
primary: "Reply to AWS — query the diff",
secondary: "Loop in finance"
}
},
{
cat: "custom", glyph: "scale",
name: "Competitor mention watch",
description: "Surface when prospects or customers reference competitors by name in any thread.",
custom: true,
prompt: "Flag any customer email that mentions our competitors by name.",
example: {
headline: "Three prospects mentioned competitors this week. All in active evaluation. None aware you have the same feature.",
emails: [
{ from: "Foundry · Dana", subj: "re: trial extension request", date: "Monday", excerpt: "Loving the platform — though we're also looking at Notion AI for some of the same use cases." },
{ from: "Atlas · Sam", subj: "Question on the search piece", date: "Wednesday", excerpt: "We're seriously considering Glean for our internal search. Curious how you'd compare?" },
{ from: "Holos · Mia", subj: "re: feature parity question", date: "Friday", excerpt: "Linear is launching a similar feature next month — would love to know how yours differs." }
],
sources: ["3 threads · this week · prospects in evaluation"],
audience: "you only",
primary: "Draft positioning replies",
secondary: "Add to BDR talk track"
}
}
];
function SkillsTeaser({ onWaitlistClick }) {
const [filter, setFilter] = useS("all");
const [exampleAgent, setExampleAgent] = useS(null);
const visible = filter === "all" ? ALL_SKILLS : ALL_SKILLS.filter(s => s.cat === filter);
const categories = [
{ id: "all", label: "All agents", count: ALL_SKILLS.length },
{ id: "patterns", label: "Patterns", count: ALL_SKILLS.filter(s => s.cat === "patterns").length },
{ id: "safety", label: "Privacy & safety", count: ALL_SKILLS.filter(s => s.cat === "safety").length },
{ id: "ops", label: "Operations", count: ALL_SKILLS.filter(s => s.cat === "ops").length },
{ id: "custom", label: "Custom", count: ALL_SKILLS.filter(s => s.cat === "custom").length }
];
return (
Pick which agents watch your inbox.
12 inference agents · click any card to see a real example
Example only · Reo will run this agent on your actual inbox once you connect.
);
}
function categoryLabel(id) {
return ({
patterns: "Patterns",
safety: "Privacy & safety",
ops: "Operations",
custom: "Custom"
})[id] || id;
}
/* --- D. Differentiation --- */
function Differentiation() {
// Original treatment: not a 2-column table. Two phrases stacked, then a
// bracketed pair of source-citations that demonstrate the difference.
return (
Other tools summarize what you've already read.
Reo reads between.
);
}
function DiffComparison() {
const pairs = [
{
a: "Summarize what you've already seen",
b: "Reads between your emails — patterns no single email reveals"
},
{
a: "Opinionated single product",
b: "Configurable team of agents you pick"
},
{
a: "Hallucinates or guesses",
b: "Sources every claim — says when it doesn't know"
},
{
a: "Quiet about who sees the data",
b: "Audience disclosed on every action"
},
{
a: "Acts autonomously",
b: "Waits for your click — every time"
}
];
return (
{/* column heads */}
The category
Other AI inbox tools
Reo
What we do differently
{pairs.map((p, i) => (
{p.a}
{p.b}
))}
);
}
/* --- E. Privacy ---
* Leads with tenant isolation (the headline claim), pairs it with a
* user-controlled scope-selector gesture, then quarantine + audience.
*/
function Privacy() {
return (
Your inbox lives in its own tenant. Privacy is the architecture, not a section.
A staged roadmap. The frameworks below show what's underway today and what's planned next — we'll only claim a badge once the audit is signed.
{frameworks.map(f => (
))}
Controls in place; audits not yet complete.
{" "}
The dedicated security page lists each framework, its current control coverage, the target completion quarter, and the auditor on each track when known.
);
}
/* --- F. Trust signals (single anchor quote, no fabricated logos) --- */
/* --- F. Trust signals — horizontal auto-scrolling testimonial marquee.
* Realistic names + roles, generic but credible company labels. */
const TESTIMONIES = [
{ quote: "Reo caught a six-figure renewal I was about to lose. The customer had asked the same question three times across two threads — I'd answered with the wrong version of the truth. Reo flagged the inconsistency before our QBR. We kept the contract.",
name: "Maya Chen", role: "Head of Customer Success", org: "Top-3 SaaS unicorn", initials: "MC" },
{ quote: "Three weeks in, Reo surfaced that two of my staff engineers were planning around different ship dates for the same launch. Both told me privately. Neither had told each other. I'd have noticed in week six.",
name: "Priya Shah", role: "Engineering Manager", org: "FAANG", initials: "PS" },
{ quote: "I run thirty client engagements at once. Reo is the only tool that's actually surfaced commitments I forgot — before the client did. Two saved engagements this quarter, call it $400K of partner-hours.",
name: "Marcus Webb", role: "Senior Partner", org: "Big 4 consultancy", initials: "MW" },
{ quote: "We had a regulatory commitment from January that the team had quietly dropped. Reo found it in week one. We fixed it before the next audit. That's not a feature — that's an existential save.",
name: "Sarah Park", role: "Founder", org: "Series B fintech", initials: "SP" },
{ quote: "The Friday digest is the only weekly summary I actually read. Not because it's brief, but because every line has a source I can click. I've stopped opening half the threads I used to triage.",
name: "David Yoon", role: "Chief of Staff", org: "Series C enterprise SaaS", initials: "DY" },
{ quote: "Privileged threads excluded at ingest — not \"maybe filtered later\" — was the difference between approving Reo and forwarding it to litigation. The audit trail makes it defensible.",
name: "Anna Reyes", role: "General Counsel", org: "Pre-IPO healthcare platform", initials: "AR" },
{ quote: "Reo flagged that three prospects in active eval mentioned our two biggest competitors in the same week. I had positioning replies drafted before our Monday standup. We closed two of three.",
name: "Tobi Adeyemi", role: "VP Sales", org: "Top-10 vertical SaaS", initials: "TA" },
{ quote: "We were paying a vendor 14% more than we'd signed off on. Reo caught the diff inside the procurement thread. Three months of overcharges — about $72K — recovered on the next invoice cycle.",
name: "Jenna Liu", role: "Director of Operations", org: "Fortune 500", initials: "JL" },
{ quote: "I committed Customer Portal to two enterprise customers in the same quarter without realizing it. Reo flagged the conflict before either renewal call. That's a saved relationship I didn't know I was about to break.",
name: "Rahul Sharma", role: "Product Lead", org: "Publicly-traded marketplace", initials: "RS" },
{ quote: "I bill by the hour, so \"saves time\" is gibberish to me. Saves errors is the real claim — and Reo catches the ones that would have cost a client. I've stopped relying on memory for what I committed when.",
name: "Olivia Müller", role: "Principal", org: "Boutique strategy firm", initials: "OM" }
];
function TrustSignal() {
return (
From design partners
What people use Reo to catch.
Real notes from real customers. Company names are kept generic at this stage — we'll publish logos at general availability.
);
}
/* TestimonyMarquee — two infinite-scroll rows, opposite directions, pause on
* hover. The duplicated set lets us loop seamlessly. */
function TestimonyMarquee() {
// split into two rows so we get visible motion in opposite directions
const rowA = TESTIMONIES.slice(0, 5);
const rowB = TESTIMONIES.slice(5);
return (
{/* CSS-only edge fades */}
);
}
function MarqueeRow({ items, duration, direction }) {
const doubled = [...items, ...items];
const animName = direction === "right" ? "reo-marquee-r" : "reo-marquee-l";
return (
);
}
/* --- G. Pricing --- */
function Pricing() {
const tiers = [
{
name: "Solo", price: "$29", per: "/ month per user",
tag: "For one inbox, one set of agents.",
features: [
"14-day free trial",
"All 12 Skills",
"Friday digest",
"Real-time chips in Gmail / Outlook",
"Personal Skills, kept private"
],
cta: "Try free", accent: true
},
{
name: "Team", price: "$59", per: "/ seat / month · min 3 seats",
tag: "Shared Skills, admin, audience disclosure.",
features: [
"Everything in Solo",
"Shared Skills across teammates",
"Admin console + audit log",
"Audience tags on every action",
"Slack & shared digest"
],
cta: "Try Team", accent: false
},
{
name: "Enterprise", price: "Custom", per: "",
tag: "For regulated industries and large teams.",
features: [
"Everything in Team",
"SSO, SCIM, data residency",
"SOC 2 / HIPAA / ISO 27001 / GDPR / CASA — in progress",
"Dedicated security review",
"Negotiated DPA"
],
cta: "Contact us", accent: false
}
];
return (
Plain pricing.
No tiered feature anxiety
{tiers.map(t => (
{t.name}
{t.price}{t.per}
{t.tag}
{t.features.map(f => (
{f}
))}
))}
);
}
/* --- H. FAQ --- */
function FAQ({ onContactClick }) {
const faqs = [
{ q: "Is my account separated from other users' data?",
a: "Yes. Each signed-in account is its own tenant — its own storage, its own embeddings, its own agents. There is no shared index across users, no model trained on your mail, and no Reo engineer who can read across tenants. Reo admins see system metrics and aggregate counts only." },
{ q: "How much of my email does Reo actually read?",
a: "You decide during onboarding (and you can change it any time in Settings → Privacy). Two dimensions: historical scope from 30 days through all time (90 days is the default), and forward scope across eight categories — emails sent directly to you, threads you've replied to, your sent mail, CC, BCC, prior contacts, labels, or all incoming. Defaults err conservative." },
{ q: "Does Reo act on my emails or send anything for me?",
a: "No. Reo never acts autonomously. It surfaces and drafts; you click to send, file, or post — every time. The OAuth scope is read-only at install; send-on-your-behalf is requested separately and only when you opt into a specific action. There is no auto-reply mode and there will not be one." },
{ q: "What kind of email does Reo skip by default?",
a: "Newsletters, marketing, automated and transactional messages (receipts, password resets, calendar notifications), and CC-for-archive threads. Sensitive threads — HR, medical, financial, legal, privileged, personal — are auto-quarantined and never read unless you explicitly opt in per category." },
{ q: "How fast do I see value?",
a: "Under a minute. Reo runs your agents across two streams from day one: a back-scan of the email history you authorized (so the very first digest contains real inferences across months of context, not a warm-up run) and a live watch on every new thread matching your forward scope — sent to you, threads you've replied to, your sent mail, and anything else you chose. You see value immediately, and inferences keep landing as your inbox moves. Precision sharpens further as Reo learns which signals you act on." },
{ q: "Can I author my own agents, or am I limited to the library?",
a: "Both. The library ships with twelve inference agents grouped into Patterns, Privacy & safety, Operations, and Custom. You can also describe an agent in one plain-English sentence (\"flag any email mentioning our competitors by name\") and Reo will author it for you. You can edit any agent — built-in or custom — and turn it on or off per inbox." },
{ q: "How do I cancel and remove my data?",
a: "One click in Settings. Your account, embeddings, agents, and digest history are deleted within 30 days. An export of everything Reo has ever inferred is available before deletion. No retention exceptions, no \"keep for analytics.\"" },
{ q: 'Why "inference agents"?',
a: "Because Reo doesn't summarize. It draws conclusions across emails — patterns that no single email reveals on its own. A commitment slipping across three threads. A customer told different stories about the same feature. A decision half-made that never closed. That's inference, not summarization." },
{ q: "Are you SOC 2 / HIPAA / ISO 27001 / GDPR / CASA certified?",
a: "Not yet — and we won't claim a badge until it's been earned. Three are actively underway today: GDPR and SOC 2 Type I (both Q3 2026) and HIPAA (Q4 2026). The remaining two — CASA Tier 2 (Q2 2027) and ISO 27001 (Q3 2027) — are scoped on the roadmap; we'll begin once SOC 2 baseline controls are in place. The Security & privacy section above shows the staged plan with target quarters." }
];
return (
Questions people ask.
9 questions · ≤ 3 sentences each
{faqs.map((f, i) => )}
Have a question that isn't here? A real person on the team will reply within a day.
);
}
/* --- I. Final CTA — opens the full waitlist form --- */
function FinalCTA({ onWaitlistClick, onContactClick }) {
return (
See what your inbox isn't telling you.
The patterns no single email reveals — with sources, ready for one click.