It remembers every detail, so you don't have to
org.run keeps what it learns while doing the work, with where it learned it. It joins what the whole company knows with how each person likes to work, and brings the right layers to the next job so the work comes out right.
Run
Drafting the Bayfield invoice
Pulled from three layers
Personal, Priya only
Priya sends invoices from her own address
Company
Bayfield gets 10% off, approved by Priya
Bayfield account
Bayfield prefers invoices on the 15th
Learned from an email, 02 Jun 2026
Corrected by Priya, 21 Oct 2026
Priya
Finance
Corrected one memory: 1st to 15th
Company and personal memory, joined
Draft
Bayfield invoice
From
Priya, Finance
To
Dana Reyes, AP
Discount
10%, approved
Amount
$12,400
Send on
15 Nov 2026
Updated. Now sends on the 15th
Layers of memory
Company memory and your preferences, joined on every run
Memory is kept in layers, from what the whole company agreed down to how you like to work. Each run pulls from every layer that applies, and the company's layer always wins over a personal preference.
Company
What the whole company agreed: policies, approvals, pricing and who owns what. Shared with everyone who works on it.
Team
How each team does its work: finance's close checklist, support's tone, engineering's release steps.
Accounts
Each customer and vendor's history: contacts, terms, promises and what already happened.
Personal
How you like to work: when to ping you, how your drafts should sound, where you review. Private to you.
How it works
Learned on one job, used on the next
- 01
Learns as it works
Every email it reads, call it hears and approval you give leaves a fact behind: a preference, a promise, a limit, a contact. It keeps the fact and the source together.
- 02
Pulls in what matters
When a new piece of work starts, it brings in only the memories that apply. Drafting the Bayfield invoice pulls the 1st-of-month preference, the agreed discount and the right AP contact.
- 03
The work comes out right
The draft lands with the right date, the right terms and the right person on it. You review the work instead of rebuilding the context.
- 04
Asks less each time
Your edits and corrections go back into memory. The question it asked last month is one it does not need to ask again.
Yours to see and edit
Every memory has a source You hold the pen
Nothing it remembers is hidden from you. Open it, check it, change it or remove it, and the work follows.
See where it came from
Open any memory and see the email, the call or the approval it was learned from, with the date and who was involved.
Correct it in place
Bayfield moved to the 15th? Edit the memory and the next draft uses your version. Your correction outranks what it read.
Delete it
Remove a memory and it is gone from the next piece of work. It does not come back unless a new source teaches it again.
Team memory, private context
What the company agreed is shared with the team. What you told it about how you like to work stays with you.
Off your plate
Stop being the one who remembers
The context behind every piece of work used to live in someone's head or a thread nobody can find. org.run carries it for you.
- Re-reading the whole thread before you reply
- Reminding people that Bayfield wants invoices on the 1st
- Checking whether a customer was already refunded
- Hunting for who approved the discount, and when
- Writing down the promise you made on the call
- Re-briefing a new hire on every account
- Answering the same question for the third time
- Losing an account's history when its owner leaves
What it keeps
The facts the next piece of work depends on
Commitments
A promise made on a call or in an email, with its deadline. The Q3 pricing you said you would send actually goes out.
Decisions and approvals
Who approved what, for how much and when. Priya's 15% for Harborline is on file the next time Harborline asks.
Preferences
Bayfield wants invoices on the 1st. Maria prefers a call over email. Small facts that decide whether the work lands right.
People and contacts
Who to talk to at each customer and vendor, who covers for whom, and what changed when someone moved on.
What already happened
Maria was refunded twice in June. It knows before it acts, so the third refund goes to a person instead of out the door.
A source on every memory
Each memory points to the email, call or approval it came from, with a date, so you can check it, correct it or delete it.
Questions about memory
Decisions, approvals, commitments, contacts and preferences it has seen while doing the work, each with the source it learned it from. It does not keep a copy of everything. It keeps the facts the next piece of work needs.
Yes. Open any memory and see where it came from, when, and who was involved. You can correct it in place or delete it, and the next piece of work uses your version.
Edit it. Every memory shows its source, so you can check the email or call it came from first. Once you correct it, your version is the one it uses, and the change is kept in the memory's history.
No. What the company agreed, like a customer's terms or an approval, is team memory. What you tell it about how you like to work stays with you and is not shown to anyone else.
Their accounts keep their history. The preferences, promises and approvals tied to their work stay with the company, so whoever picks up the account starts with the context instead of an empty inbox.
Early access
Stop repeating yourself
Connect your tools and org.run starts remembering from the first piece of work.
Scoped, auditable and reversible from day one. Your data stays yours.