01
The problem
A legal technology platform processing court reporter transcriptions at scale had a billing team spending over 20 hours a day downloading deposition PDFs, counting pages, extracting timestamps, calculating billable hours, and re-entering everything into an internal system with no API. The internal engineering team was focused on product, not integrations.
"I've had several demos with several companies, and everybody tells me the same thing. That unless you have API access, we can't help you."
"I'm kind of at a crossroad where I have to decide do I need to hire more people, or can I use some automation so that I can alleviate that?"
02
What Loopfour automated
- Downloads deposition PDFs directly from the internal billing portal
- Extracts text from only the first and last three pages, no OCR required
- Captures page count (excluding blanks), start time, and end time
- Applies business rules, including "whichever start time is earlier"
- Calculates total billable hours and enters results back into the system via UI interaction
- Self-heals if the UI changes, and falls back to human review over Slack when it can't
03
Results
| Metric | Before | After |
|---|---|---|
| Processing time per deposition | ~2 minutes manual | Seconds, automated |
| Daily labor | 20+ person-hours | Zero manual touch |
| Monthly labor cost | ~400 hours/month | Eliminated |
| Processing schedule | During business hours | Overnight batch, full queue |
| Accuracy | Human errors in page counting | Deterministic, with blank-page detection |
| Error handling | Discovered after the fact | Self-healing with Slack alerts |
No system migration was required. The automation works inside the existing browser-based system, the existing PDF uploads, and the existing billing fields, and it runs in a SOC 2 Type II compliant, sandboxed browser environment.
04
Why it matters for controllers
An automation that types into a browser is only trustworthy if every keystroke is auditable. This one applies the same business rule the same way every time, and flags anything it can't resolve instead of guessing.
Facing a similar billing bottleneck with no API in sight?
Book a demo