Features

Product intake, review, discovery, and delivery handoff in one system.

Relay is built for product and engineering teams that need better source control for decisions before tickets and implementation work begin.

Slack intake

Create initiatives with `/intake`, attach message threads, capture files, and keep status visible without switching tools.

Inbound email

Route longer briefs, forwarded customer conversations, and supported attachments into the right initiative.

Quality checks

Review confidence, coverage, conflicts, warnings, thresholds, and relevance before document generation.

Document generation

Generate structured product documents with problem, goals, stories, scope, constraints, questions, and success criteria.

Technical discovery

Ask focused follow-up questions in Slack after document approval, with unresolved items preserved downstream.

Linear handoff

Generate delivery tasks, dependencies, estimates, and reusable Relay task IDs that sync to Linear.

GitHub context

Index selected repositories so task generation can account for relevant codebase summaries and repo ownership.

Blueprints and packs

Use GitHub PR review for implementation blueprints, then generate repo-specific implementation packs.

Provider routing

Track generation usage, route providers where configured, and keep cost and token usage visible in billing.

Evidence review

Approve work with provenance still attached.

Relay keeps generated sections connected to source material so reviewers can inspect strong signals, inferred assumptions, unresolved conflicts, and missing coverage.

  • Markdown and DOCX export for approved documents.
  • Readiness questions when material gaps remain.
Document reviewConfidence 86%
ProblemGoalsScopeRisksSuccess
4 Slack threads and 2 docs support this section
CoverageConflictsOpen questions
CoverageStrong
RelevanceHigh
Conflicts2 unresolved
ReadinessQuestions sent

Quality controls

Proceed when context is strong, pause when it is not.

Quality checks help teams avoid turning incomplete Slack threads into delivery work too early. Failed attempts and regenerations remain visible without becoming the billing basis.

Implementation path

Move from document approval to delivery with fewer handoff gaps.

Generated tasks can sync to Linear, repository context can come from GitHub, and blueprint PRs provide an engineering review gate before implementation packs are generated.

Delivery handoffBlueprint ready
LinearCreate scoped delivery tasks
Ready
GitHubIndex repository context
Connected
BlueprintReview implementation approach
Open PR
PackGenerate task context for delivery
Queued

Connected tools

Relay works around the tools teams already trust.

Slack

Primary working surface for intake, quality reports, approvals, discovery, and task triggers.

Linear

Delivery task sync with estimates, dependencies, issue reuse, and state reflection.

GitHub

Repository indexing, blueprint review, validation statuses, and implementation handoff.

Email and files

Inbound context from emails, documents, PDFs, spreadsheets, slides, and transcripts.