Non-destructive edit session recorder for Lightroom Classic

Lightroom Classic users face a specific version of this problem that's structurally different from Photoshop's. Lightroom is supposed to be non-destructive — it stores edits as metadata rather than pixels — but users still hit walls when they want to walk back through a session's worth of decisions. The History panel in Lightroom logs every slider move as a separate state, so 'editing requires thousands of tiny steps' and the history list becomes unusable noise. There's no way to mark meaningful moments, no way to jump to 'where I was before I tried this color grade,' and no export of the decision trail so a second editor or the same editor next week can understand what happened.

The gap persists because Lightroom's history is designed as a safety net, not a workflow tool. It stores states but doesn't help you navigate them — it has no labels, no branching, no comparison between two non-adjacent states. The buyer here is often a studio with multiple editors touching the same catalog, but Lightroom's history is per-device and not shared, so if one editor passes a file to another, the history is invisible to the recipient. Nobody builds around this because it requires deep knowledge of the Lightroom catalog format (SQLite-based, documented enough to work with) and because Adobe doesn't expose the history as a proper API, so third-party tools have historically avoided it.

What's missing is a session-level annotation layer on top of Lightroom's existing history: something that watches the catalog, groups slider changes into meaningful 'moments' (by time gap, by module switch, or by user-defined markers), lets users label and compare those moments, and exports a human-readable decision log that a second editor or the same editor returning to a file can actually use. Users who lose work because they 'can't click the undo button anymore' are often not hitting a technical limit — they're hitting a navigation limit. The history is there; they just can't find where they want to go.

This is a business because catalog-based workflows recur daily, the audience (wedding and portrait studios) processes thousands of images per month, and the cost of a wrong edit applied to 300 images from a wedding shoot is measured in hours of rework. A studio paying $15/month per seat to avoid that rework is making a rational economic decision, not a luxury purchase.

What to build

Build a macOS and Windows desktop companion that reads a Lightroom Classic catalog file in real time, groups raw history entries into labeled session moments based on time gaps and module transitions, lets users annotate and compare any two moments side by side, and exports a structured edit log as a shareable PDF or JSON file that another editor can reference when picking up the same catalog.

Where to start

Start with studios that already share catalogs across two or more editors — this is the specific workflow where the lack of shared, navigable history costs the most time, and it's a narrow enough segment that you can reach them through wedding photography forums and studio management communities with a very specific value proposition.

The hard part

Lightroom Classic's catalog is a SQLite database that Lightroom locks aggressively while open — reading from it in real time without triggering corruption warnings or data races requires careful read-only access patterns, and any mistake here destroys user trust immediately because the catalog is the studio's entire asset record.

How it makes money

Monthly subscription at $18-25/month per studio (not per seat), covering up to five editors sharing a catalog, with a higher tier for larger teams — studio owners control the subscription and it's a studio cost, not an individual expense.