Deliverables
It ends with a file.
Most assistants hand you text and leave the assembly to you. Perch builds the workbook, the deck, the memo, and the diagram, checks each one before delivery, and leaves the evidence attached.
What it produces
Real files in the formats your work already lives in, not markdown you have to reformat.
Spreadsheets
XLSX · CSV · TSV · Google Sheets
Source values on input tabs, formulas on analysis tabs, and reconciliation and exception tabs when the workbook drives a decision. Invoice numbers, account numbers, and tickers stay text, so nothing gets silently coerced into a number.
Presentations
PPTX · slide artifacts
Board decks, pitch decks, and research summaries built from an outline, one takeaway per slide, with speaker notes and charts drawn from the data rather than described from memory.
Documents
DOCX · Google Docs
Memos, letters, reports, policies, and redlines with tracked changes. The same drafting discipline as Writing Studio, delivered as the file your team already works in.
PDFs
Read · create · split · merge
Extract and cite by page, pull tables and forms, read scans optically when there is no text layer, and produce a report at the end. A page citation points at a page you can open.
Diagrams
Mermaid · draw.io
Workflows, org charts, entity networks, control graphs, and architecture maps. Structure drawn from what Perch actually read in the folder, not an illustration of a guess.
Analysis behind them
Sandboxed Python and Node
Totals, matches, and reconciliations run as real code in a sealed sandbox, so a figure in the workbook traces back to the script that produced it instead of to a model's arithmetic.
Checked before it ships
A file that opens is not the same as a file that is right.
Every artifact runs a verification pass before Perch hands it over. The check is specific to what the file is supposed to do.
Workbooks
The file exists, formulas are present where they should be, totals reconcile, and CSV exports keep exact values.
Decks
Slide count, readable text, layout that does not overflow, and charts and images that actually rendered.
Drafts
Claims checked against the sources behind them, with anything unsupported marked rather than quietly shipped.
Delivery
Sent, with proof that it sent.
Perch can put the finished work where it belongs: a Google Doc, a Sheet, a calendar invite, a Gmail draft or send. It does this inside the browser session you are already signed into, so there is no separate API grant to issue and later remember to revoke.
The part worth knowing is what counts as done. A URL alone is not treated as proof. Perch requires actual evidence that the message sent or that the document contains what it should, and that receipt travels with the result. If it cannot verify delivery, it says so instead of reporting success.
Where it runs
Perch AI Web
Ask for a document and the web chat produces a downloadable file from the conversation. Good for a memo, a summary, or a report you want out of the browser and into your hands.
Desktop and CLI
The full path. Perch reads the folder, runs the analysis in the sandbox, builds the workbook or deck from the result, verifies it, and writes it back to the folder you are working in.
Artifact work is part of Perch on every plan. See how skills load for what Perch reaches for and when.
Ask for the file, not the answer.
Point Perch at a folder and ask for the reconciliation workbook, the board deck, or the memo. Free to start, on every surface.