The problem often starts before the viewer even opens: someone sends or receives a file that's enormous because nobody optimized it at the source. 'Software takes up a lot of hard disk space and creation of files from multiple extensions takes a long time' — the file is big because it was exported from Illustrator or InDesign at maximum quality, with no downsampling, and it stays that way through every step of the workflow.
The gap here is that compression tools exist, but they live inside the same bloated software that's causing the slowness. You'd need to open the file in Acrobat to compress it in Acrobat — which defeats the purpose when the file takes ten minutes to open. There's no lightweight, fast, standalone path to 'make this file smaller before I do anything else with it.'
Teams that deal with this daily — legal departments processing scanned case files, insurance companies handling claim documents, marketing teams managing brand asset PDFs — don't have a repeatable triage step in their workflow. Files arrive big, stay big, and every downstream step suffers. The person who has to review the file isn't the person who created it, so they can't fix it at the source. That structural separation between creator and recipient is why nobody complains loudly enough to force a fix inside the existing tools.
This is a business because document volume in these teams grows continuously. A legal team that ingests 200 PDFs a week this year will ingest 300 next year. The cost of not having this is measured in analyst hours spent waiting and in storage costs that accumulate silently until someone notices the invoice.
What to build
Build a lightweight desktop and CLI tool that batch-compresses incoming PDFs using configurable image downsampling and font subsetting profiles, produces a compression report showing size reduction per file, and integrates with shared network folders or cloud storage buckets so document-heavy teams can run it as an automatic step before files hit their review queue.
Where to start
Win first with mid-sized law firms that receive scanned discovery documents from opposing counsel — the files are predictably large, the pain is daily, and the IT buyer can be reached through legal technology consultant networks without a long enterprise sales cycle.
The hard part
The hardest early problem is trust: buyers in legal and financial services are acutely sensitive to any tool that touches their documents, and you'll need to demonstrate — not just claim — that compression is lossless for text and signature layers, which means investing in certification or third-party validation before your first enterprise conversation.
How it makes money
Usage-based pricing per gigabyte processed per month, with a flat monthly minimum — this aligns cost to actual document volume and makes it easy for buyers to justify internally by comparing against storage costs saved.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Document Creation.
More ideas in Document Creation