What Landed
Matthew Berman built Folio, a free, open-source PDF reader and editor, to replace Adobe Acrobat. He did it after hitting Acrobat's bloat on a fresh Windows install ("a bunch of features I don't need"). The available transcript is only the intro. It does not say which model or tooling built Folio, how long it took, or how close it gets to Acrobat's features.
Why It Matters
This is one more anecdote that the build-vs-buy line has moved for commodity utilities. Tools that sell feature breadth, where most users need only a small subset, are now open to bespoke replacement, and that weakens per-seat pricing at renewal. The enterprise reality is less exciting. A personal tool is not a deployable one. PDF parsing is a classic malware vector, and the features enterprises actually pay for are redaction, digital signatures, PDF/A, accessibility and support. None of those are addressed here. Treat this as a directional signal for licensing strategy, not as evidence that an AI-built tool is ready for enterprise use.
Worth Raising With Customers
- Renewal leverage: In the next licensing audit, flag single-purpose utilities (PDF, file conversion, light editors, internal dashboards) where a credible in-house build exists. Even if they never build it, the option strengthens the negotiating position.
- Know the full cost before building: An AI-built replacement takes on security review, parser hardening, compliance features and indefinite maintenance. The coding session is the cheap part.
- Pick the right first targets: The best candidates are internal-only tools with narrow feature use and no regulatory surface. Anything touching signatures, records retention or untrusted external files should stay with the vendor for now.