Corteal Run · finding to actionEarly access
From finding to done. With a person in the loop.
Run takes what Read, Watch, Verify and Analyze find and prepares the next step: a posting, an email, a task, a page, an edit. A person approves every step, and every action is logged with its source.
For operations and finance leaders at companies of 50 to 500 people.
- Read
Post 14 invoice lines to ERP
Invoice 30482 from Brennholt Castings. All 14 lines match purchase order 4500917.
ERP · purchase ledgerSource: Invoice 30482, p. 1–2Approved · queuedRejected · loggedOpen for editing - Read
Email Brennholt Castings a correction
Line 7 bills 40 pieces. The delivery note shows 36. A draft is ready in your mailbox.
Email · as youSource: Delivery note DN-8812Approved · queuedRejected · loggedOpen for editing - Analyze
Open a Jira task for Procurement
Process pump lead time is 11.4 weeks, against 10 approved. 62% of late orders use one foundry.
Jira · PROCSource: Lead time queryApproved · queuedRejected · loggedOpen for editing - Watch
Page the trade counter team
A customer has waited 2 min 40 s at the parts counter and nobody is within 6 m. Nearest free: Jonas.
Phone · TeamsSource: Counter camera 2Approved · queuedRejected · loggedOpen for editing - Verify
Update the warranty in 6 templates
Verify approved 24 months on 3 Sep. Six quote and contract templates still say 18.
Documents · DriveSource: Pump warrantyApproved · queuedRejected · loggedOpen for editing - Verify
Send 38 RFP answers for sign-off
Drafted from approved figures. 4 questions have no approved source and are left blank.
Email · J. LundSource: Answer deskApproved · queuedRejected · loggedOpen for editing
Sample data is illustrative. Halden Flowworks is a fictional company.
Fig 1.0 · One action, start to finish
Nothing happens until a person says yes.
Example: Verify approves a new warranty, and Run proposes the edits.
1 · Finding
VerifyPump warranty approved: 24 months
Approved in Corteal Verify by M. Aalto, Head of Service, on 3 Sep.
Owner approved2 · Run proposes
Update 6 templates that still say 18 months
18 months24 monthsQuote template, EN18 months24 monthsQuote template, DE18 months24 monthsService contractand 3 more in Drive
3 · A person approves
Review the 6 changes
Edit or reject any of them. Approver: M. Aalto.
4 · Done and logged
6 templates updated
Logged 3 Sep, 14:02: approved by M. Aalto, source Verify: Pump warranty. Each template keeps its previous version.
Logged
Fig 2.0 · Approve, edit or reject
Change it before it goes out.
Every proposal shows what it will do, the documents behind it and the checks it passed.
Hello,
On invoice 30482, line 7 bills 40 pieces of casting BC-2214. Our delivery note DN-8812 and purchase order 4500917 both show 36. Please send a corrected invoice for 36 pieces, a difference of €312.00.
Thank you,
K. Brandt
What the documents say
| Document | Pieces |
|---|---|
| Invoice 30482, line 7 | 40 |
| Delivery note DN-8812 | 36 |
| Purchase order 4500917 | 36 |
Checked before proposing
- Recipient matches the supplier record in the ERP.
- Amount at stake: 4 × €78.00 = €312.00.
- Nothing is sent until you approve.
Fig 3.0 · Playbooks
Write the rule once. Run proposes it every time.
A playbook says when to propose which action, and who approves. It never acts on its own.
- ReadWhen a supplier invoice matches its purchase orderPropose posting the lines to the ERPPropose only
- ReadWhen an invoice quantity differs from the delivery notePropose a correction email to the supplierPropose only
- WatchWhen a customer waits over 2 min with nobody within 6 mPropose a page to the nearest free colleaguePropose only
- VerifyWhen an owner approves a figurePropose updating documents that show the old onePropose only
- AnalyzeWhen lead time passes its approved figurePropose a task for the ownerPropose only
Fig 4.0 · Audit log
Every action, with its source.
Who approved it, when, in which system, and the finding that started it.
| Time | Action | Source | Approved by | Result |
|---|---|---|---|---|
| 14:02 | Updated 6 templates | Verify · Pump warranty | M. Aalto | Done |
| 13:40 | Posted 14 invoice lines | Read · Invoice 30482 | K. Brandt | Edited, done |
| 11:15 | Paged the trade counter | Watch · Counter camera 2 | Counter lead | Done |
| 10:52 | Opened task PROC-218 | Analyze · Lead time | A. Voss | Done |
| 10:20 | Sent a correction email | Read · Delivery note DN-8812 | K. Brandt | Done |
| 09:48 | Sent 38 RFP answers | Verify · Answer desk | J. Lund | Rejected |
| 09:05 | Created an Asana task | Analyze · Warranty claims | T. Okonkwo | Done |
Fig 5.0 · Connected systems
Works inside the tools you already use.
Each connection is limited to the actions you allow, with the approver's own access.
Limits on every connection
- Runs with the approver's own access, never more.
- Email goes only to the recipients named in the proposal.
- Edits stay inside the folders and projects you choose.
Logos belong to their owners and show where actions may land, not a partnership.
Fig 6.0 · How it works
Connect, write playbooks, approve, check.
We start with one playbook and one approver.
- 1
Connect
Scoped access to the systems you choose.
- 2
Write playbooks
When this finding appears, propose that action. Name who approves.
- 3
Review the inbox
Approve, edit or reject each step.
- 4
Check the log
Every action, with its source.
Fig 7.0 · Who it is for
For operations leaders at 50 to 500 person companies.
Buys it
COO or head of operations
Runs it
Operations and finance admins
Approves
The owner of each step
Teams start when
- Findings sit in a report and nobody acts.
- The same corrections are typed by hand every week.
- An alert arrives and nobody knows who owns it.
- Approved figures never reach the old documents.
Security and privacy
Your data stays in your environment.
Inside your environment
EU hosting or on-premise, as you choose.
Access scope respected
Run can do only what the approver could do, in the systems you connect.
A person approves every step
Playbooks propose. Nothing runs, sends or posts until someone approves.
Logged with its source
Action, finding, approver, edits, time, system and result.
Questions
What operations teams ask us.
- Does Run ever act on its own?
- No. Every step waits for a person to approve it. Playbooks only propose.
- What can it do?
- Post to your ERP, send email from the approver's mailbox, create tasks in Jira or Asana, send a message or page, and edit documents in chosen folders. Each connection is limited to the actions you allow.
- Can I change an action first?
- Yes. Edit the text, the lines or the recipient, or reject it. Edits are logged next to the original.
- What if it proposes something wrong?
- Reject it. The rejection is logged and you can switch the playbook off. Nothing has changed in your systems until you approve.
- Who can approve?
- The owner you name for each playbook, within the access they already have.
- What is logged?
- The action, the finding it came from, who approved or edited it, the time, the system and the result.
- Where does the data live?
- Inside your environment: EU hosting or on-premise, as you choose.
- What does early access mean?
- We are building Run with a small first group. Playbooks and connections are set together, and we have no customer results to show yet. Ask us for the current terms.