Who it is for
People who do finance work for a living and have more of it than hours.
Bookkeeping practices
The recurring client work that fills evenings. Hand it the matching, the tie-outs and the month-end file, and review what comes back instead of building it.
Small-business finance teams
One or two people covering the whole back office. It takes the multi-step jobs that sit at the bottom of the list, and leaves the judgement calls with you.
Finance students
Workbooks with live formulas you can open and change, not a pasted answer. Built for coursework as well as client work.
How it works
Describe the job
Write it the way you would to a colleague and attach the files: exports, statements, the PO list.
It does the steps
It works out what the job needs, runs the numbers and builds the file. No turn-by-turn steering.
You get the work back
A real workbook you can open, with a plain note on anything it thinks you should look at twice.
One real job
An April invoice match, asked in plain words.
It came back in 3 min 32 s as a workbook: every invoice matched to its order and receipt, 6 rows flagged with the reason and the dollar difference, and a total clear to pay of 28,117.10.
Test files we built from public vendor-payment data (Montgomery County, Maryland), with five problems we planted. These vendors are not our customers. Built by the beta on 24 Sep 2026.
The ask, word for word
Three-way match for April AP, client is the same distributor. Attached: open POs, receiving log, and the vendor invoices we got in April. Build me a workbook that matches every invoice to its PO and receipt, flags anything that shouldn't be paid as-is (price, quantity, duplicates, no PO etc) with the reason and the dollar difference, and gives me the total that's clear to pay this week.
Why Obrussa
A worker, not a genius. Enough for the job, and honest about what it did.
Sized for the job
Most back-office work does not need the largest model. We build a worker that is enough for the task, at a price a small office can carry.
Built to check its work
It is designed to test what it made before handing it over, and to tell you in plain words where to look. It will still be wrong sometimes.
Easy to work with
Ask in your own words and attach the files, the way you would with someone on your team. No prompt tricks, no forms to fill in first.
Set up for your firm, not rebuilt
Each company gets its own settings: what it may touch, what goes back to a person. Configuration, never a custom model per client.
The founders
Two founders in Miami, and we are hiring a technical lead.
Aidan Shaughnessy
Co-founder. Business, product and the people we build for. Came to this from markets, where he learned to try to disprove his own results first.
Loreto Chiovari
Co-founder. Brand, design and the company's outward face, including the mark at the top of this page.
Plain about where we are
In beta, and it says so
We let people in a group at a time and fix what each group finds before the next one starts. It will get things wrong; check anything that matters.
What happens to your files
Your text is sent to the model provider that answers it. The beta shows you its terms, and you agree, before your first job.
No badges we have not earned
We have no independent security audit yet, such as SOC 2, so we show no badge. When we have one, it will be here with the report behind it.
Hand it the first job.
The beta opens a group at a time. Leave an email and we will tell you when yours opens.