Underwriting
Every statement, read like an underwriter would.
Three agents on every file. A reader that shows its work, a verifier that argues with the application, a tamper check that looks at the PDF itself. Then your sheets, your offer, your memo.
The reader
It reads the page, not a guess about the page.
The text layer when there is one, OCR when there is not. Columns found by geometry, rows by their lines, every amount tied back to a box on the page you can open.
Any layout
Chase, Wells, BofA, credit unions, statements printed to PDF. The reader learns a bank's layout the first time and keeps it as a template.
Scans, through OCR
A photographed or scanned statement goes to the metered reader under the document's name; the desk carries on as if it had a text layer.
Reconciled, or it says so
Opening plus every row must equal closing. When it does not, the rows that broke it are marked and their confidence halves.
Categorised by what it is
Revenue, transfers, loan proceeds, refunds, lender pulls, NSF and fees. Reclassify a row from the ledger and the month recomputes.
Provenance on every figure
Click a number in the report and the statement opens beside it with the line highlighted. Show the page, not the parser.
Positions and cadence
Each lender, its cadence, typical pull, pace a month, share of revenue, and a stopped date when the pulls stopped.
The verifier
Someone has to argue with the application.
The verifier reads the record on the file — stated revenue, positions, time in business — and holds the statements to it. Months are compared to each other; duplicates, gaps and the month that does not fit are named. It writes findings in sentences, not codes.
- Deposits against stated revenue, with the difference
- Duplicate and missing months across the file
- The tamper check: producer, fonts, spacing, arithmetic, a score and a band
- Judge again after any change, in one click
Sheets and offers
Your guidelines, as rules the desk applies.
Write a sheet the way you would explain it to a new underwriter: months required, balance floors, NSF ceilings, holdback, positions. Every file is judged by every sheet and the figure that decided each rule is right there. The offer is priced from the sheet the file passes, with comparables from your own funded book, and you counter it inline.
- As many sheets as you have paper grades
- Thresholds under each figure in the report
- Approve, counter, ask for more, or decline, on the record
- The deal memo, one page, from the file
Intake
Statements that file themselves.
Forward a submission to the desk's intake address and its PDFs land on the right deal, are read and verified, and the timeline says who sent them and when. A merchant who connects their bank through Plaid gives you months of clean rows with no PDF at all.
- Email intake, matched to the deal by application
- Plaid pulls with the same categories as a PDF read
- Broker to funder: submit a file to another desk and see the decision
- Remittance on funding, pulled on the schedule the offer set
A submission arrives
The subject names the deal, the PDFs are statements, the file exists or is opened.
The desk reads it
Each statement is read and verified; a failed read says why on the timeline.
You open a finished file
Figures, positions, findings and sheets are waiting. Judge and send.
Pricing
One read, one statement.
Every plan has every agent, every seat, every feature. Plans meter reads; packs top them up and never expire.
Starter
Ten statements on us. No card.
- 10 statement reads
- Every agent: reader, verifier, tamper check
- Sheets, offers and the deal memo
- Statements by email
Growth
For a desk that reads every day.
- 250 statement reads a month
- Unused reads roll over while you subscribe
- Plaid pulls and OCR of scans included
- Team seats, no per-seat charge
- Email support, same day
Scale
For a shop that funds at volume.
- 1,000 statement reads a month
- Everything in Growth
- Funder marketplace and submissions
- API access and webhooks
- Priority support
Questions
What desks ask.
How long does a read take?
A statement with a text layer reads in seconds. A scan takes as long as the OCR pass, usually under a minute for a few pages. The timeline shows each step as it happens.
What if the reader gets a row wrong?
Change its category from the ledger; the month's figures, positions and the sheets recompute. Rows the arithmetic disagreed with are already marked for you.
Can I bring my own guidelines?
Yes. Sheets are yours to write and edit in the desk: months, balances, NSFs, holdback, positions and more, with a threshold under each figure of the report.
Do you keep the statements?
They live in your workspace's own bucket so the page can be opened beside any figure. Delete a statement and its rows, bytes and timeline go with it.
Is there an API?
The desk runs on the same API the workspace uses. Scale includes API access and webhooks; write to us for the reference.
Open the desk. Drop a statement in.
Ten reads on us, no card. Your first file is read before you finish the coffee.