Relay
A visual automation platform that connects email, Slack, CRM, documents and approvals — with AI where judgement is needed.
- Operations automation platform
- 21-Day Launch
- Web app, Slack app, Integrations
finance-approvals
8 members · Relay connected
Bill created · Oakline Logistics
@Dana Whitfield an invoice over £2,500 needs your approval.
Northwind Supplies
£3,840.00incl. £640.00 VAT
- Invoice
- INV-20418
- Due date
- 12 Oct 2026
- Purchase order
- PO-1187
- Cost centre
- Facilities
Rule: total over £2,500 · reminder in 24 h
What Relay does
Relay lets an operations manager see and change how work moves through the business. Triggers, AI steps, approvals and actions are arranged on one canvas, and every run is traceable.
Key decisions
Business verbs, not API terms.
Steps are called receive, read, decide, approve, update and notify, so an operator can build a flow without knowing what an API is.
No custom code steps.
Code would turn every flow into something only a developer can maintain. Templates for the four most common loops cover the first version.
Every run can be opened up.
When an invoice goes missing, the operator can open the run and see what each step received and did.
Operations run on invisible glue: inboxes, forwards and someone remembering.
In most growing companies, work moves between tools by hand. An invoice arrives by email, gets forwarded for approval, is re-typed into accounting, and somebody posts in Slack when it's done. When that person is on holiday, the process stops.
- No one can see how a process actually works end to end
- Approvals get lost in inboxes and chat threads
- Existing automation tools feel built for engineers
- When an automation fails, nobody notices until a customer does
The operations manager
Ops or finance lead at a 20–200 person company
Responsible for processes across teams, comfortable with spreadsheets, not a developer.
What they need to get done
- Map how a process works and change it without engineering
- Put approvals in front of the right person, with context
- See every run and fix failures fast
- Use AI to read and sort messy inputs safely
The assumption to prove
Non-technical operators will build and own automations if the canvas reads like a process map, not a program.
Design around business verbs — receive, read, decide, approve, update, notify — rather than API concepts. Start from templates for the four most common loops and make every run inspectable.
In the first version
- Visual canvas with triggers, AI steps, approvals and actions
- Connectors: email, Slack, CRM, Drive, accounting
- Approval inbox with context and one-click decisions
- Run history with step-by-step inspection
- Four starter templates
Deliberately left out
- Custom code steps
- On-premise deployment
- Marketplace for third-party connectors
- Branching beyond simple conditions
The core journey
Pick a template
Start from invoice approval, lead routing, triage or meeting follow-up
Connect tools
Sign in to email, Slack and accounting
Shape the flow
Add an AI step, a condition and an approver
Test with real input
Run on a sample document and inspect each step
Go live
Turn it on; approvals arrive in Slack
Monitor
Runs, failures and time saved, in one view
Design exploration
The first wireframes looked like every node editor on the market — powerful and intimidating. We moved from 'boxes and wires' towards a vertical process map that reads top to bottom like a checklist.
Read the invoice
Read from
Fields to extract
INV-20418.pdfWhen AI isn't sure
Read the invoice
Read from
Fields to extract
INV-20418.pdfWhen AI isn't sure
Free-form canvas or vertical flow?
Vertical flow with branches
Operators think in sequences. A top-down layout reads like a written procedure and prints cleanly for audits.
Where do approvals happen?
Where the approver already is
Slack and email approvals with full context get answered; a separate inbox gets ignored.
How visible should AI be?
Labelled step with confidence and fallback
Operators need to know when AI decided something, and what happens when it isn't sure.
Relay’s design system
A dark, focused workspace where colour means state: blue is running, amber waits for a person, green is done, red needs attention.
Relay Blue
Active step, primary action
Approval Amber
Waiting for a person
Done Green
Completed runs
Fault Red
Failures
Canvas
Workspace
Typography
System UI for interface text; mono for field mappings and run IDs; generous line height on the canvas for scanning.
Components
- Flow step card
- Connector chip
- AI step with confidence
- Approval card
- Run timeline
- Field mapper
Principles
- Colour is state
- Every run is inspectable
- Business verbs, not API terms
Key screens
Read the invoice
Read from
Fields to extract
INV-20418.pdfWhen AI isn't sure
£2,915.40 · Started 08:57 today · Paused at step 5 after 39 min
Couldn't create the bill in accounting
No supplier called “Harbour Office Co.” exists in accounting yet. Relay tried 3 times, then paused the run — the approval is kept.
Steps
- Receive invoice emailHOC-7731.pdf08:57
- Read the invoice7 fields · 93% sure4.2 s
- Check the amountOver £2,5000.1 s
- Ask finance leadApproved by Dana W.38 min
- Create bill3 attempts09:36
- Post confirmationNot run yet—
Step 5 data
InputOutputErrorPassed on from step 4
Last attempt · 09:36
finance-approvals
8 members · Relay connected
Bill created · Oakline Logistics
@Dana Whitfield an invoice over £2,500 needs your approval.
Northwind Supplies
£3,840.00incl. £640.00 VAT
- Invoice
- INV-20418
- Due date
- 12 Oct 2026
- Purchase order
- PO-1187
- Cost centre
- Facilities
Rule: total over £2,500 · reminder in 24 h
How it works underneath
A workflow engine with durable execution: each step is persisted, retried on failure and resumable after a human approval that may take hours.
- Person
- Interface
- Service
- AI
- Data
- External
Read the connections as a list
- Ops managertoRelay canvas
- Relay canvastoWorkflow engine
- CRM, Drive, XerotoWorkflow engine
- Workflow enginetoExtraction & classification
- Workflow enginetoPostgres (runs, steps)
- Workflow enginetoSlack / email
- Workflow enginetoCRM, Drive, Xero
- Ops manager
- CRM, Drive, Xero
- Relay canvas
- Workflow engine
- Extraction & classification
- Postgres (runs, steps)
- Slack / email
- Ops managertoRelay canvas
- Relay canvastoWorkflow engine
- CRM, Drive, XerotoWorkflow engine
- Workflow enginetoExtraction & classification
- Workflow enginetoPostgres (runs, steps)
- Workflow enginetoSlack / email
- Workflow enginetoCRM, Drive, Xero
Likely stack
- Next.js + TypeScript
- Durable workflow runtime
- Postgres
- OAuth connectors
- LLM structured outputs
- Slack interactive messages
A 21-day build plan
Pick the first loops
Choose the four templates, list connectors, define step types in business language.
Canvas design
Vertical flow wireframes, step cards, approval patterns; prototype tested with an ops walkthrough.
Engine and connectors
Durable execution, retries, OAuth connections, AI extraction with confidence thresholds.
Runs and approvals
Run history, step inspection, Slack approvals, failure alerts.
Templates and launch
Finish templates, test with sample documents, deploy with monitoring.
Across devices
Building flows is a desktop job. On mobile, Relay becomes what operators need away from a desk: approvals and failure alerts.
- Canvas is read-only below tablet width
- Approvals are full-screen cards
- Run failures deep-link to the failed step
finance-approvals
8 members · Relay connected
Bill created · Oakline Logistics
@Dana Whitfield an invoice over £2,500 needs your approval.
Northwind Supplies
£3,840.00incl. £640.00 VAT
- Invoice
- INV-20418
- Due date
- 12 Oct 2026
- Purchase order
- PO-1187
- Cost centre
- Facilities
Rule: total over £2,500 · reminder in 24 h
Automation that operations teams can read, own and trust — with AI doing the reading and people doing the deciding.
£2,915.40 · Started 08:57 today · Paused at step 5 after 39 min
Couldn't create the bill in accounting
No supplier called “Harbour Office Co.” exists in accounting yet. Relay tried 3 times, then paused the run — the approval is kept.
Steps
- Receive invoice emailHOC-7731.pdf08:57
- Read the invoice7 fields · 93% sure4.2 s
- Check the amountOver £2,5000.1 s
- Ask finance leadApproved by Dana W.38 min
- Create bill3 attempts09:36
- Post confirmationNot run yet—
Step 5 data
InputOutputErrorPassed on from step 4
Last attempt · 09:36
finance-approvals
8 members · Relay connected
Bill created · Oakline Logistics
@Dana Whitfield an invoice over £2,500 needs your approval.
Northwind Supplies
£3,840.00incl. £640.00 VAT
- Invoice
- INV-20418
- Due date
- 12 Oct 2026
- Purchase order
- PO-1187
- Cost centre
- Facilities
Rule: total over £2,500 · reminder in 24 h
A process your team still runs by copy and paste?
Tell us the steps as they happen today. We’ll scope the automation that removes the most of them first.
21-Day Launch
$3,700
For fuller products: several roles, AI agents that take actions, heavier integrations or a mobile MVP.
- Up to 5 core workflows
- Up to 20 screens
- Multiple roles & permissions
Your idea gets its own written scope and fixed price before anything starts. Compare packages
In the first version
- Vertical flow builder with 6 step types
- 5 connectors (email, Slack, CRM, Drive, accounting)
- AI extraction and classification steps
- Approvals in Slack and email
- Run history and failure alerts
- Four starter templates
Later, once it's proven
- Custom code steps
- Connector marketplace
- Advanced branching and loops
- Role-based workspaces