How I Built PDF Diff: a scoped case study in AEC workflow review

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, one office, or one project. It showed up as a broader review habit that consumed attention and made small misses more likely.

That observation set the direction for the tool: the first release had to help teams notice drawing changes faster without forcing a new collaboration platform or a new cloud workflow.

I kept the release scope narrow on purpose. PDF Diff compares exported drawing PDFs locally, supports Split and Diff review modes, and stays focused on revision visibility instead of turning into a full document-management system.

Three decisions shaped the first release. First, I kept processing local so the tool would fit review environments that prefer clear data boundaries. Second, I chose a simple Windows-first distribution path so people could evaluate the tool quickly. Third, I explained the current limits openly instead of implying that the tool already covers every AEC workflow.

I added a lightweight feedback path early because the tool needs real workflow reactions, not only my own assumptions. The roadmap, feedback form, and docs are there so the next steps stay visible.