Say it in plain language, it does the work
Chase the three overdue invoices from Q3. Bayfield's renewal moved to March. Prepare the board deck for Thursday. Type it where you already work, and org.run shows the plan, runs it across your tools and comes back with the result.
org.run
Direct message
Maya09:12
Chase the three overdue invoices from Q3.
org.run09:12
Three invoices, $31,900 in total. Here is the plan:
Pull the three overdue invoices
Check each thread for a reply- Send a reminder to each contact
Post the summary in #finance
Northwind is 60 days over on $18,400. A reminder to a key account needs your sign-off. Preview attached.
Maya09:14
Approved. Offer them a 14-day plan.
org.run09:15
Done. Three reminders sent.
Northwind got the 14-day plan. Summary and the follow-up dates are in #finance.
3 tools, 7 steps loggedKept for next time: Northwind prefers payment plans
Runs with Maya's access, every step logged
How it works
A message in, finished work out
- 01
You say it
A task or a fact, in a sentence. No form, no fields, no picking a workflow. Anyone on the team can do it, from the org.run app or from Slack and Teams.
- 02
It shows the plan
It replies with the steps it will take and the tools it will touch. If something is genuinely unclear, it asks one question. Otherwise it starts.
- 03
It does the work
It reads and writes across the systems you run on: pulls the invoices from QuickBooks, checks the email threads, sends the reminders, posts the summary. The steps tick through in the thread.
- 04
It stops at your line
A send to a key account, a refund over your limit, anything one-way. Those pause in the thread and wait for your yes. Then it finishes and brings you the result.
Where you can chat
It is wherever you already type
The same org.run, the same permissions, in whichever window is open. Start in one place and pick the thread up in another.
Slack and Teams
Message it directly or mention it in a channel. The plan, the progress and the result land in the same thread, with approve and edit buttons when a step needs you.
The org.run app
A chat with the full run beside it: every step, every tool it touched, the evidence it used and the preview of what it is about to do.
Forward an email
Forward a thread to org.run with a line on top: handle this, or just so you know. It becomes a task or a fact like anything else you tell it.
Off your plate
Stop translating what you want into clicks
The message is the brief. You skip the part where you open five tools to make one thing happen.
- Opening five tools to chase one invoice
- Writing a ticket for something you could just say
- Updating the CRM after you already told someone
- Pulling the numbers before you can ask for the deck
- Re-explaining context that was in last week's thread
- Remembering which tool a task lives in
- Checking back to see whether it got done
- Teaching a new hire where everything is before they can ask for anything
Built for a message, not a form
Everything in the thread
Asks only when it must
It uses what it already knows about your company to fill the gaps. One clarifying question when something is truly ambiguous, never a questionnaire.
A plan before it acts
The steps and the tools, shown up front. Change a step or tell it to skip one, and it adjusts before anything is sent, changed or paid.
Runs across your tools
Reads and writes in email, CRM, finance, code, docs and chat. One request can span all of them, and each step shows which tool it touched.
Pauses at your line
High-stakes steps wait in the thread with the evidence and a preview. Approve, edit or reject, and it carries on.
See approvalsKeeps what you tell it
Say Bayfield's renewal moved to March once. The renewal reminder, the forecast and the next proposal all use the new date.
Everyone can ask, within their access
Anyone on the team can start work. It acts with that person's permissions and your rules, so an intern cannot issue a refund by asking nicely.
Questions about chat
Anything that runs across the tools you have connected: chase invoices, prepare a deck, update a customer record, draft and send a proposal, open the fix for a bug. If part of a task is outside what it can reach, it says so and does the rest.
It shows the plan first. Read-only steps start straight away. Anything that sends, changes or pays follows your rules: auto, ask or never. One-way actions are set to ask by default.
Rarely. It fills gaps from what it already knows about your company, your customers and how you have handled similar work. It asks one question when the answer would change what it does, and remembers the answer for next time.
It updates the record. Bayfield's renewal moved to March changes the renewal date, and any work that depends on it, such as the reminder and the forecast, uses the new one. It tells you what it changed.
Yes, and each person acts within their own access. A request runs with that person's permissions and your rules, and every run is logged with who asked for it.
Early access
Say it once and watch it get done
Connect your tools, open a thread, and hand over the first task.
Scoped, auditable and reversible from day one. Your data stays yours.