The recurring work, done on time
The Monday report, the invoice chase, the monthly SaaS audit, the quarterly access review. Describe it once and it runs on its own, across your tools, every time it is due.
Cadences
Monday, 1st of the month
07:00 · Every Monday
Management report
Posted to leadership before standup
08:30 · Every Monday
Invoice chase
19 reminders sent, toned by how late
Corvane, 71 days late, held for you
09:00 · 1st of the month
SaaS spend audit
6 unused seats found, owners asked in Slack
10:14 · Offer signed, Lena Ortiz
New-hire onboarding
Accounts created, day-one plan sent
Next up
Access review, first working day of the quarter
See it run
The scheduled work, done before anyone logs in
▍
Every team's numbers, the reasons behind the big moves and one judgement call from you. The deck reached every attendee hours before the meeting.
How it works
Describe it once, and org.run runs it every time
- 01
You describe it, or it proposes one
Say it in plain language: chase overdue invoices every Monday at 8:30. Or org.run sees the same work done the same way three weeks running and proposes the cadence, with the steps it saw.
- 02
It dry runs first
Before it goes live, it runs against last month's data and shows you what it would have sent, changed or flagged. You fix the steps until the dry run is right.
- 03
It runs on its own
When the schedule hits or the event lands, it does the whole run: reads the data from your tools, does the work, and writes the results back where they belong.
- 04
It stops at your line
A balance past your escalation threshold, an admin downgrade, a discount over your limit. Those pause and come to you. Everything under the line finishes without you.
Two kinds of trigger
On a schedule, or when something happens
Some work is due at a time. Some work is due because of an event. A cadence can start on either.
On a schedule
Every Monday at 07:00, the management report. Every Monday at 08:30, the invoice chase. The 1st of the month, the SaaS spend audit. The first working day of the quarter, the access review. Set the time once, in plain language.
On an event
An offer is signed, so onboarding starts. A deal moves to closed-won, so the handover begins. A ticket breaches its SLA, so the escalation runs. The event comes from your tools and the cadence starts the moment it lands.
Off your plate
Stop being the calendar reminder
The work still happens on time. You stop being the one who remembers it, starts it and chases it through.
- Building the same Monday report from the same five tabs
- Remembering which invoices to chase this week
- Pulling the SaaS bill apart to find the seats nobody uses
- Starting the access review because the auditor asked
- Kicking off onboarding by hand every time an offer is signed
- Checking whether last week's run actually happened
- Re-explaining the steps when the person who did it leaves
- Setting reminders for work that should start itself
Built for work that repeats
Everything a cadence needs to run unattended
Written in plain language
Describe the cadence the way you would brief a person. org.run turns it into steps you can read and edit, and keeps your sentence beside them.
Proposed from repeat work
When it sees the same work done the same way, week after week, it proposes the cadence with the steps and tools it saw. You say yes or change it.
Dry runs before it goes live
Every new or changed cadence runs against past data first. You see what it would have sent, changed or flagged before any of it is real.
A stop at your line
Your rules apply inside every run. Anything past a limit pauses and comes to you in Slack or Teams, with the evidence and a preview.
Checks after it runs
Did the report post? Did the reminders land? Each run confirms its own result, and retries or tells you when something did not go through.
Every run logged
Each run records what it read, what it did, what it held for you and what happened after. A missed run is flagged, never silent.
Questions about cadences
Describe it in plain language: the trigger, the steps and where the result should go. org.run turns it into a run you can read, dry runs it against past data, and asks you before it goes live. It also proposes cadences on its own when it sees the same work repeat.
A schedule, like 7am every Monday or the 1st of the month, or an event from one of your tools, like an offer being signed, a deal moving stage or a ticket breaching its SLA.
Your rules apply inside every run. Anything past a limit, such as a balance over your escalation threshold or an admin being downgraded, pauses and comes to you with the context. The rest of the run finishes on its own.
Yes. Pause it, change a step or move the schedule, all in plain language. A changed cadence dry runs again before the new version goes live, so you see the difference first.
Every run is logged with what it read, what it did and what it held for you. If a run fails or a source is unreachable, it tells you instead of staying quiet, and you can open any past run to see exactly what happened.
Early access
Put the work that repeats on a schedule
Pick the first cadence, the business review deck or the invoice chase, and let org.run run it from next week.
Scoped, auditable and reversible from day one. Your data stays yours.