Demo
Watch Perch work on real files.
Recordings of Perch taking a task from start to finish: reading the files, doing the analysis, checking its own work, and citing the source behind every finding. Each one is written out step by step underneath, so you can read what happened instead of squinting at it.
An accounts payable audit on 100 files, from one instruction
Perch Terminal takes a single prompt and audits a folder of invoices, purchase orders, payment logs, and vendor records on a Mac. It writes its own analysis, checks its work against the instruction, and reports 93 findings with the IDs and dollar amounts behind each one.
What happens
- 01
One instruction
The whole task is a single prompt: audit MockCo's accounts payable in this folder, cross-reference every invoice against its purchase order, the payment log, and the vendor master, flag duplicates and mismatches, then write a findings report ranked by risk where every finding cites the specific invoice, PO, and payment IDs. 100 files, sitting on a Mac, nothing uploaded.
- 02
It reads and cross-references every file itself
No templates and no rules engine. Perch writes its own analysis against the invoices, purchase orders, payment log, vendor master, AP aging, and bank ledger extract, then runs it and reads the output.
- 03
Duplicates get caught by number, vendor, and amount
Not just matching invoice numbers. It groups by vendor and amount too, which is what catches the same charge arriving twice under two different references.
- 04
Then it audits its own work
Before finishing, it turns the original instruction into a ten-point checklist and verifies each requirement against the actual files and command output. Anything it cannot evidence is treated as not achieved.
- 05
93 findings, every one cited
3 critical: two duplicate invoices at risk of double payment and one duplicate PO. 42 high: $2,480 of payment variance, three vendor mismatches, and 36 invoices billing against vendors that are not in the master, worth $147,420 of unknown-vendor exposure. 48 medium, including $3,600 unpaid. The report is written to the workspace as a file.
Your turn
Run it yourself.
That audit ran on a sample folder in the desktop app. Point Perch at your own folder and it works the same way: read what is there, do the task, cite the source behind every finding.