3-week document sprint; ran historical PDFs through the parser; low-confidence rows quarantined for analyst approval.
Operating layerOnboardingAI teammates
Five category pages for sector-specific case studiesView categories →
Case study·CRE advisory
PDF P&L to Excel conversion
From operator P&L PDFs re-keyed by hand — to a parsed, traceable workbook reviewed line-by-line
-88%
Conversion time per P&L PDFFrom ~3 hours of typing to ~20 minutes of review per workbook
“The tedious part moved from typing to checking.”
UK CRE healthcare advisory firm·~140 operator P&L PDFs processed per quarter across valuation engagements·3-week pilot·United Kingdom
01Pilot envelope
Pilot length3 weeks
First signal48 hours
First ROI21 days
Team alongside3 seats · 2 colleagues
02What it owns
Reports toValuation Manager, with the Operations Lead consulted on the firm's chart of accounts and template conventions.
Owns
- PDF intake — operator P&Ls in the engagement SharePoint folder picked up, period and operator confirmed, and queued for extraction
- Row-level extraction — line items, sub-totals and footnotes parsed with a per-row confidence score and a link back to the source page
- Template mapping — extracted rows mapped onto the firm's valuation workbook, preserving the operator's chart of accounts and prior-quarter labels
- Low-confidence quarantine — any row below the agreed confidence threshold held in a review tab and flagged to the named analyst
- Source-linked workbook — every populated cell carries a link back to the page and table region on the PDF for the manager's review
Does not do
- Valuation analysis — populates the workbook only; analysts and the Valuation Manager own the model and its assumptions
- Adjusting operator numbers — quarantines uncertain rows for review and never silently corrects an operator figure
- Sending workbooks to clients — drafts only; the engagement lead reviews and releases every deliverable
Done looks like
Analysts open a pre-populated, source-linked workbook in minutes instead of typing one in hours. The Valuation Manager reviews extraction confidence and exceptions, not whether each cell was typed correctly.
03The team
AI teammates2
MayaReads the operator P&L PDFs in SharePoint, extracts line items, sub-totals and footnotes, and tags every row with a confidence score and a page reference back to the source.


OwenMaps extracted rows onto the firm's valuation workbook template, preserves the operator's chart of accounts, and quarantines any row below the agreed confidence threshold for analyst approval.


Human team3
- 4 Valuation analystsValuations
- Valuation ManagerValuations
- Operations LeadOperations
04Connected stack
05What it returned
-88%Conversion time per P&L PDFFrom ~3 hours of typing to ~20 minutes of review per workbook
94%Row-level traceabilityPopulated cells linked back to a page and table region on the source PDF
31 hrsManual rekeying removed in pilot batchReallocated to analysis and reviewer feedback on the historical PDF run
- Day 0Co-ordinator sessionValuation Manager, analysts and Operations Lead align on the firm's template, the chart-of-accounts conventions and the confidence threshold for quarantine.
- Day 2First signalMaya completes a read-only extraction pass over a representative operator P&L; the Valuation Manager confirms row mapping and flags two footnote categories for review.
- Day 7Historical batch runThe prior quarter's PDFs are processed end-to-end; analysts review extraction confidence and correct the mapping for two operator-specific line items.
- Day 14Approval-gated workbook hand-offOwen formats workbooks against the firm's template and routes low-confidence rows to the named analyst; the review tab is adopted as the default check.
- Day 21ROI reviewSponsor signs off on the three baseline metrics and approves rolling the workflow into the next quarter's valuation engagements.
06Related templates
↗Get started
Want this for your team?
Each design-partner pilot starts the same way: one workflow, the minimum useful context, and a first ROI signal measured in days.
