How I Built PDF Diff: A Case Study in AEC Workflow Review
A case study on the workflow problem, the decisions behind the first release, and how the feedback loop is set up.
Problem Definition & Validation
I built PDF Diff after repeatedly seeing the same pattern across AEC workflows: revised drawing sets were being checked manually, page by page, under time pressure. The issue was not tied to one employer or one office. It showed up as a broader review habit that consumed attention and made small misses more likely. Recently sharing this concept with the broader architectural community confirmed this is an industry-wide bottleneck. Teams needed to notice drawing changes faster, without being forced into a new cloud collaboration platform.
Release Scope
I kept the release scope intentionally narrow. PDF Diff focuses solely on revision visibility instead of trying to become a full document-management system. The workflow loop is complete with Split/Diff review modes, Cloud Marks for visual annotation, and actionable PDF/PNG exports.
Product Decisions & Trade-offs
Keep it local
No server, no hybrid model. Drawing files never leave the machine, which removes the upload question entirely and makes IT and security review straightforward.
No GPU required
The tool runs on CPU and RAM only so it performs consistently on standard office PCs, not just high-end workstations.
Ship Windows first, keep it portable
Distributed as a single EXE through GitHub with no installer. Anyone can download and run it in under two minutes without IT involvement.
Bilingual by Design
AEC workflows span global teams and local offices. Including native English and Japanese interfaces from day one ensures the tool is immediately accessible to practitioners across different working environments.
The Feedback Loop
I stated the limits of the tool clearly because overstating the scope makes feedback useless. I added a lightweight feedback path early because the tool needs real workflow reactions, not only my own assumptions. The roadmap, changelog, and docs are public so users can contribute to what comes next.