Relay · Private beta
The AI-native way to resolve complex workflows.
Relay reads your documents, reasons over the context, and takes action across your tools — so your team reviews outcomes instead of doing the busywork.
Built for operations teams whose work lives in documents: claims, contracts, compliance, diligence — anywhere the bottleneck is reading, understanding and acting.
Built with Claude.
Request beta access →The problem
Today, operations teams spend hours each day reading, copying and re-keying information between systems.
70%
of an operations analyst's day goes to reading and re-entering information — not deciding.
5+
systems touched to resolve a single case: inbox, drive, CRM, spreadsheet, ticketing.
Days
of cycle time lost to handoffs, queues and "waiting on review".
The work isn't hard because it requires genius — it's hard because it requires reading everything, remembering everything and never getting tired. That's exactly what machines should do.
Our solution
Relay uses AI agents to ingest, understand and act — end to end.
01
Ingest
Documents, email and data flow in from your existing tools — shared drives, inboxes, CRMs, ticketing systems. No migration, no re-platforming.
02
Understand
Claude reads the full context — not just keywords. Entities, relationships, deadlines and contradictions are extracted into a structured model of the case.
03
Reason
The agent plans the work: what to check, what to compare, what policy applies. Long-context reasoning means nothing gets dropped between steps.
04
Act
Tool calls via MCP and APIs update your systems, notify the right people and draft the output — with a full audit trail of every decision.
05
Review
Low-confidence or high-stakes steps pause for a human, with the evidence assembled and the reasoning explained. One click to approve, edit or reject.
Use cases
Where Relay fits best.
Claims & case review
Read every document in a case file, cross-check facts against policy, draft a resolution and flag only the exceptions for human review.
Contract & compliance ops
Extract obligations, dates and clauses from hundreds of pages, compare them against your playbooks, and keep a living register that updates itself.
Back-office reconciliation
Match records across systems that were never designed to talk to each other, explain every discrepancy, and push corrections through your existing tools.
Research & diligence
Turn a pile of PDFs, emails and spreadsheets into a structured brief with citations — in minutes, not days.
Why AI · Why Claude
Where Claude sits in the architecture.
User
↓
2labs Product
↓
AI Orchestration
├── Claude
├── Tools / APIs
├── MCP
└── Internal Knowledge
↓
Action / OutputWe use Claude for reasoning-intensive tasks, structured extraction, agentic workflows and code generation. Claude lets us handle long-context workflows while keeping the product simple for users.
A single case can span hundreds of pages and dozens of tool calls. Claude's long context and reliable tool use are what make an end-to-end agent practical rather than a demo.
- Long-context reasoning
- Agentic workflows
- Structured outputs
- Tool use
- Code generation
- Reliable handling of complex instructions
Trust & safety
Built for teams that can't afford mistakes.
No training on your data
Customer data is never used to train models. Full stop.
Full audit trail
Every agent action, tool call and human override is logged and exportable.
Permission-aware
Agents inherit the access rights of the workflow — they can't see or do what your team can't.
Human-in-the-loop
You decide which steps run autonomously and which always require approval.
FAQ
Common questions.
How long does onboarding take?
Most design partners see their first real workflow running within two to four weeks, starting from a narrow, high-volume process.
Do we need to change our existing tools?
No. Relay connects to the systems you already use through APIs and MCP connectors.
What happens when the AI is wrong?
Every action is reversible and logged. Low-confidence work is routed to a human before anything is written to your systems.
How is pricing structured?
We're finalizing pricing with our beta partners. It will be tied to outcomes and volume, not seats.
See your own workflow running on Relay.
Tell us about the process that eats your team's week. We'll show you what it looks like when an agent does it.
Request beta access →