About Ori

The work after
the work.

Ori exists because the most expensive workday tax is not thinking. It is translating a meeting, email, spreadsheet, or portal update into five more chores across five more apps.

What we build

A Windows agent
that does.

Ori learns recurring workflows by watching how people already work. Then it repeats those workflows in the real apps, with visible steps and human approval for important actions.

Why Windows

The desk where
work lives.

Most operational work still happens on Windows PCs, inside Office, browsers, CRMs, portals, and internal tools. Ori starts there because that is where the work actually is.

How we think

Local first,
human led.

The agent should be observable, correctable, and quiet until needed. Your computer is not just an input device. It is the workplace Ori learns from.

Point of view

Agents should finish
actual work.

We are not trying to build another chat box beside the work. Ori is built to operate inside the work: the document, the spreadsheet, the inbox, the browser tab, and the queue that still needs cleaning up after the meeting ends.