It sees the work as it happens
Your company already tells you what needs doing. It is spread across inboxes, call recordings, alerts and calendars. org.run reads all of it and turns it into work it can pick up.
Integrations
It plugs into your business — and takes action
Two-way connections, so what it sees in a tool it can also act on in that tool.
Reads, drafts, sends and schedules for you.
Captures decisions and turns them into action.
Pulls out the signal, risks and next steps.
Tracks changes, writes fixes and ships them.
Reconciles, reports and updates the books.
Keeps every customer record up to date.
Acts on the proprietary data your company runs on.
If your team uses it, org.run can operate it.
Two-way — it reads your data and takes action in it
How it works
From noise to a task with an owner
- 01
Connect the sources
Email, calendar, Slack, CRM, finance, code, the meeting recorder. Each one is a sign-in, scoped to what you allow.
- 02
It listens for signals
A customer email, a tense support ticket, a Sentry alert, a promise made on a call. Each becomes a candidate task, a new fact or a commitment.
- 03
It removes the duplicates
The same issue raised in Slack, email and a ticket becomes one task, not three. It links the evidence from each.
- 04
It routes the work
Every task gets an owner, a priority and a deadline, and a decision on whether org.run, a person or both should handle it.
Off your plate
Stop being the inbox for the whole company
The chasing, copying and remembering that eats the week. org.run picks it up from wherever it appears.
- Copying action items out of meeting notes
- Forwarding an email to the person who should own it
- Checking whether the same issue is already a ticket
- Remembering the pricing you promised on a call
- Watching dashboards for the number that moved
- Tracking which renewals are coming due
- Turning a Slack thread into a task someone owns
- Re-asking a customer for details they already sent
What it reads
Nine kinds of source, one stream of signals
Grouped by what is being watched. Every source produces the same thing: tasks, facts, commitments and evidence for your rules.
Connected systems
The tools your company runs on, read and write: email, calendar, Slack and Teams, CRM, finance, code repos, ticketing, docs and your core system of record.
Conversations
What people say. Meeting recordings, sales and support calls, email and chat threads. The Bayfield discovery call becomes the Bayfield proposal.
Internal monitors
Your own signals. Error and uptime alerts, metric thresholds on churn, cash and pipeline, and records that have gone overdue.
Time
Things that are due. The 7am Monday report, contract and renewal dates, and commitments people made with a deadline attached.
Direct requests
What people ask for. Chat with org.run, or forward an email to it, and the request goes into the same queue as everything else.
Work observation
What people do. Opt-in watchers per person, on the desktop, with on-device redaction, so it can learn a process by watching it done once.
Outside world
Things that happen to the company. App Store reviews, regulation changes, vendor status pages and competitor pricing.
Files and documents
Contracts, invoices, PDFs and shared drives, read for the facts, dates and promises they contain.
Databases and warehouses
Your system of record and data warehouse, read for the live state of the business.
Questions about capture
No. It reads the tools and recordings you connect, and nothing else. Watchers, which see what people do on screen, are on the roadmap, and when it arrives it will be opt-in per person with on-device redaction.
It turns it into signals: a candidate task, a new fact, a commitment someone made, or evidence for how you handle a kind of decision. Those signals drive the work. Raw data is not the point.
Before anything becomes a task it checks for the same issue elsewhere. A complaint raised in Slack, by email and in a ticket becomes one task, with all three linked as evidence.
Yes. Every connection is scoped when you add it, down to the workspace, channel, mailbox or project. You can narrow or revoke it at any time.
Connected systems, conversations and direct requests come first, along with monitors and scheduled work. Work observation and outside-world monitors come later.
Early access
Let org.run catch what falls between tools
Connect the first few sources and see what it turns into work in the first week.
Scoped, auditable and reversible from day one. Your data stays yours.